I installed CoreOS on a 9-year-old MacBook
1–10 of 31 posts
Re: I installed CoreOS on a 9-year-old MacBook
#2Re: I installed CoreOS on a 9-year-old MacBook
#3The 32-bit EFI vs 64-bit system issue has reared its head again with some Windows 8 tablets (e.g. HP Stream 7). Switching the iso's EFI boot files is an easy way to solve this.
Re: I installed CoreOS on a 9-year-old MacBook
#4Re: I installed CoreOS on a 9-year-old MacBook
#5There are still some things that make it unintuitive and in my view incomplete (eg. a command to copy/cut/paste/delete volumes).
A couple things I've found out: You should definitely use the Overlay FS driver as soon as possible; don't use DeviceMapper. Also, It can be convenient to use data volume containers but watch out for orphaned files in /var/lib/docker/tmp and always use -v.
Re: I installed CoreOS on a 9-year-old MacBook
#6Re: I installed CoreOS on a 9-year-old MacBook
#7Awesome article. I have been thinking about setting up a RPi as a server lately as well. Do you know if RancherOS will run on the Pi2?
Re: I installed CoreOS on a 9-year-old MacBook
#8It was pretty popular with my classmates for some time -- there was a self-written forum on it where you could upload photos, and people used it to share holiday pictures (this was before Facebook allowed everyone to share stuff online)
Unfortunately at some point the HD crashed and I lost the database since I had no backup of it -- I just didn't know where MySQL stored its files.
Re: I installed CoreOS on a 9-year-old MacBook
#9Re: I installed CoreOS on a 9-year-old MacBook
#10That 32-bit EFI with 64-bit CPU is a real curse for installing recent Linux (although Ubuntu did release "amd64+mac" ISO images for these computers, I think even 14.04 is available this way).
Additionally, my internal DVD drive for this MacBook failed, so I had to use an external DVD drive for booting said Ubuntu. It had the weirdest bug -- you had to reboot from rEFInd three times for the EFI boot to recognize that the external DVD drive has a bootable DVD in it. First time, it won't see it, second time, it won't see it, and on the third reboot, it magically does.
The reason is likely because the drive spins up too slow and the EFI boot timeouts unless the drive is powered up from an earlier spinup.
Besides the internal drive failing, the machine with Ubuntu on it is perfectly usable as a main laptop for a student. It shows how the laptop scene did not improve that much in the last 9 years -- and that one can save quite a bit of money if he buys a reliable machine and treats it well.