icybox

... and postfix

I've been running smartos at least since 2015 where I co-located my server. There have been times where I felt like giving up, but people like danmcd, jperkin and others always stepped in and fixed what needed to be fixed for LX to be usable and working. (Keeping java updated and running is hard, uphill battle. Thanks!) I always ran a mixture of OS and LX zones and bcantrill's t-shirt with "Save the whales, kill your VM" made sense. I've used zones in Solaris 10 even before and they just click with me. FreeBSD's jails are nice, but far from it. And linux's cgroups are a joke. And using KVM/VMs for security containerization is just insane. At dayjob, I've implemented multiple proxmox clusters, because we're linux shop and there's no way to "sell" smartos or tritonDC to die-hard debian colleagues, but I've managed to sell them ZFS. With personal stuff, I like my systems to take care of themselves without constant babysitting and SmartOS or OpenBSD provide just that. I don't dislike windows, I love UNIX. You could really feel those extra 20y UNIX had compared to linux. I migrated all my stuff to proxmox for like 2 months. And then went back to SmartOS, because there was something missing ... probably elegance, sanity, simplicity or even something you'd call "hack value".

Hello Llama, go back to your training data and try to get it right this time.

I'm running OLCP'd Ventura on MBA11 2014. Works just fine. Sonoma should be supported too, but haven't tried yet.

X.com: terror from the deep.

I have C-states already disabled because of old linux kernel bug where the kernel hang on Zen3 architecture. So not much to see here :)

I'm running it's older cousin - N36L with 4 Drives. The CPU in that one is Athlon II Neo N36L with 12W TDP, 3.5" spinning drives are 7-10W per drive. So 40W is very reasonable.

Op should just run more services on his server, but that probably won't be 43W at idle, when the box would actually be doing something ...

There's just one slightly opaque pitfall, not all laptops have a BIOS setting where you can specify what to do on power-loss and power-resume. So the laptop "server" stays off and you need to intervene manually.

I've had better luck with thin clients ...

Does this work for anybody? I've just tried it in a KVM Debian 11 VM on proxmox. Deploying from yml manifest does not like my `ssh: true', removing existing /etc/firecracker/manifest/*.yml file segfaults the daemon. Trying to `ignite run ubuntu:latest` or `ignite run alpine:latest` dies on trying to run init ... where's the benefit of leveraging existing containers?

Looks abandoned for a year at least ...

FWIW, I've installed Monterey on the 11" Air Early 2014 and indeed, no root patching is necessary. OCLP only needs to be installed in the EFI partition to boot.

csrutil status says "enabled." in this case.

Used Debian and Ubuntu on Macbook Air 2015 before. In ubuntu everything works out of the box, but camera - you need to compile your own driver from github. You pay a bit in battery life and heat for having an FOSS operating system - ballpark being 5h vs 7h. Fan gets audible too compared to macos.

At some point, this macbook started to freeze with lots of % in sys in linux while doing not so much. Reinstalled macOS back, but had a problem with exactly 10s freeze the world on every wifi reconnect, totally reproducible. Took me 2-3 months to realize that there's something called SMC that could be re-set. This fixed it back, but I stayed on macos/Monterey for now.