Never actually tried LFS but I have done Gentoo from stage 1 (back when that was an option), so I'm going to use your statement as an indication I can skip LFS ๐
So if you want to use systemd-boot
as the bootloader you have to (apparently) install the systemd-utils
package. Or you can just use GRUB / efistub.
Edit: looks like groche beat me to it ๐
It's probably been 4 years since I last had to rebuild my Gentoo, but I would be very surprised if there weren't good OpenRC instructions. I built mine with systemd and Gentoo handbook instructions always felt like 'Are you sure you don't want to use OpenRC? Ok, here are the systemd steps I guess'
An obviously talented programmer is no longer working on a free project that very few people can meaningfully contribute to - that is a shame.
I can't even get myself to learn rust, let alone make a GPU driver while reverse engineering blackbox hardware.
Joe Biden is breaking US law every day
You don't need to worry about him, our glorious court system has determined he's immune from those pesky 'laws'
I don't think he knows about second gun, Pip
I'm using Gentoo with systemd and a customized kernel, and additionally I have the /usr
partition LUKS encrypted.
Because /usr
is absolutely essential for systemd to function, I configured dracut to make a specially crafted initrd which activates the luks lvm and prompts for the password to decrypt and mount /usr
on startup before systemd init tries to run.
About a year or two ago, some update to dracut or some other dependency (assumption) caused the dracut generated initrd's to kernel panic. After multiple days of troubleshooting, I discovered that just copying forward an older initrd in /boot
and naming it to match the new kernel, e.g. initramfs-6.6.38-gentoo.img
, allows the system to boot normally .
So, my Gentoo is booting a kernel 6.6.something
with a ramdisk generated in the 5.9
kernel era. I am dreading the day when this behavior breaks and I can no longer update my kernel ๐ณ
Wtf I can't unsee this shit
wAkE uP sHeEpLe
Not sure where you got the 25kb number from.
This tool is written in go and is a 7.8 MB compiled binary.
Force uninstalled glibc on my Gentoo, which basically broke every shell and binary on the system. Was able to repair in place because I
- Had already compiled busybox statically
- Still had a copy of the stage 3 tarball on / which I could use to 'restore' glibc libraries
I don't know the name but I can tell you how sad they make me when they break and tear off and you have to use a lighter on the now extremely frayed end(s) of your shoelace for just a few seconds, and then pinch off the flame just lightly burning your fingies while molding the shoelace end into a cohesive black carcinogen.
Source: I am cheap