>>1004710
But it's fun! It's the most fun I had with Linux since trying to get the xserver on Corel Linux to start up without crashing. It's like discovering something new, kind of, and it never hurts to learn more. Now that I'm thinking about it - no idea where that nice box and the hueg manual went.
>a pain to keep secure / up to date
I guess if you don't run any services, read about vulnerabilities once in a while and block as much traffic as possible it shouldn't be a problem. It's not like I'm using it as a server system. Keeping things as barebones as possible may actually make it easier to keep secure.
It uses sysvinit and reminds me a bit of BSD configuration - although that is, subjectively, still a bit nicer tbh.
Keeping it updated will naturally be bothersome. There's Guix on there now (since your .guix-profile/bin etc is included before the rest of your $PATH, it's no problem to build newer versions "on top" of the existing ones in /bin), but for everything further down I'll have to do everything by hand.
Clearly not intended for "production" use, but I have time on my hands and the only thing I'm producing is my power bill.
>>1005397
>libreboot and coreboot
Actually didn't think of that. The last thing I remember is some tranny drama though - and I'm scared that I might brick the thing because of some weird Apple quirks, that are not expected. The "UEFI" on there has no configuration menu, it just tries to boot the next best efi file on the harddisk. You can hold alt while starting to get into an onboard bootselector, which actually has mousesupport, for reasons unknown. From there you can try to boot efi refind, which can then boot legacy systems - or not. Sometimes it doesn't boot what you selected and just continues to boot the next best thing.
Apple is crap. I set up a timemachine server for my girlfriend and tried to backup her files over wifi - can't bother her to learn rsync or something. Her macbook was running hot for 8 hours or something, just to silently fail. It opens the connection to the server and then sends nothing while it's compressing the files. When at any point the connection is lost it scraps everything it has done and starts from the beginning. Then you turn up after 9 hours and ask yourself what the hell is taking so long. Timemachine won't tell you.