- Joined
- Jan 28, 2018
Configure the kernel with EFISTUB, stick it on a 32mb (or bigger, depends on what you need) FAT (maybe ext, you can try but it is not guaranteed to work) partition (with directories like this: EFI/boot/bootx64.efi to make sure it gets found by your firmware) and you don't need a bootmanager, as the kernel can boot directly. I'm not sure how it is with fancier firmware if you have any but there's a lot of configuration options these days. Especially when I'm only booting one configuration I'd forego the boot-manager altogether, grub is a POS. You will have to tell the kernel were / is in it's command line, though. This is best done by UUID. You can also configure an initramfs to do things for you before loading your main init, like mounting an encrypted drive. It's not necessary for the partition to be mounted. I don't know how dynamic managers like the (e)udevs do it as they were a mess years ago and I stopped using them, but you might have more luck by adding the partition by UUID also, not by direct path. "blkid" to get the UUIDs is in util-linux or busybox.Got gentoo running on my main machine. Learned a lot about shit I've been avoiding - namely grub and EFI. Did a barebones minimal install, the most functional things I have are tmux, vim and bashtop right now.
now get rid of dbus, policy- and consolekit, udev (you can use mdev or a static /dev instead, another thing that's advertised for "embedded only" but works just fine and has no arcane configuration, nobody needs automounting anyways and if you really need it, there are ways - for programs that needs udev "find /sys/" you can google for udev zero, there are ebuilds) and pam and you got rid of the worst brain damage of recent years. gtk3 (if you want to use a lot of the more common GUI programs like browsers) will demand dbus for one of it's components but you can patch that build-time dependency out. Or just don't start the dbus service if that's too complicated. I also advise to use runit, but not gentoos default configuration that somehow depends on openrc and is configured in an utterly retarded way that makes runit itself somehow use openrc and is pretty much the dumbest thing I've ever seen in an ebuild. (which I can only explain by the fact that the maintainer is a confirmed systemd shill) Just kick that entire dependency out and do a local ebuild with your own scripts as soon as you're up to it.
Now watch your system actually idling when it is, you know, idle. I was absolutely shocked how a default install of Ubuntu amounted to a 1.xx load average just sitting there on a dualcore machine.
Last edited: