On 13/11/2021 00:36, Jack wrote:
On 2021.11.12 18:34, Wol wrote:
I've just been swearing blue murder because when I run "make install"
it puts the kernel in /boot.
But when I run genkernel it mounts a completely different boot, sticks
the initramfs in there, and then unmounts it.
Which means when grub-mkconfig comes along, there's no initramfs and
my grub.cfg gets screwed.
WHY!!!
Check the genkernel config file carefully for relevant options. I use
genkernel, and it installs into the existing, mounted /boot and doesn't
mess with it.
Thanks. I've managed to find genkernel.conf (I sort of expect to find
gentoo config files in /???/portage, dunno why :-)
And yes, BY DEFAULT it looks for a boot partition, mounts and uses it!
I think this is the collision between someone who uses tools for
everything (it makes it easy for them), someone who doesn't use the
tools for anything (it's irrelevant), and someone who uses some of the
tools and it messes them up completely. "A little knowledge is a
dangerous thing".
Likewise genkernel assumes you're building the current kernel. I like to
get the kernel built and booting before I eselect it into default
status. That's screwed me over a couple of times.
The reason for this slightly odd config is that I have multiple root
vg's over raid, so I need just the one boot directory/partition. But if
I let a distro (any distro) mess about in there, it basically fucks up
the boot. SUSE had a go, pointed all of my kernels at the SUSE vg, and
forgot to tell grub about md or lvm. Whoops! Stil, it taught me a lot
about how to use the systemd recovery console ...
Cheers,
Wol
