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