| 1 |
On Monday 09 February 2009 18:51:24 Stroller wrote: |
| 2 |
> On 9 Feb 2009, at 10:32, Michael Hampicke wrote: |
| 3 |
> >>> It would appear that you need an initrd/initramfs to use this. |
| 4 |
> >> |
| 5 |
> >> Ah! Many thanks. I will live without this shortcut, then, I think. |
| 6 |
> > |
| 7 |
> > If you, like me, prefere to compile your own kernel, there's still an |
| 8 |
> > easy way to create a initrd for your kernel: with genkernel |
| 9 |
> > I use this command to compile my pre-configured kernel |
| 10 |
> > |
| 11 |
> > genkernel --no-clean --no-mrproper \ |
| 12 |
> > --makeopts=-j2 --loglevel=5 --install --symlink all |
| 13 |
> > |
| 14 |
> > To include support for disk labels use the switch --disklabel |
| 15 |
> |
| 16 |
> I am resistant to the idea of using an initrd, because IIRC it's an |
| 17 |
> extra file that has to be stored in /boot, creating extra "clutter" in |
| 18 |
> there. |
| 19 |
> |
| 20 |
> I'm kinda thinking that using the label prevents failed boots in the |
| 21 |
> event that the drives are recognised in a different order in the |
| 22 |
> future, but nevertheless I don't "like" initrd and the longer kernel |
| 23 |
> lines in grub.conf that they require. |
| 24 |
> |
| 25 |
> I appreciate this is somewhat irrational. |
| 26 |
|
| 27 |
Not really. |
| 28 |
|
| 29 |
initrds are there for two cases, and only two cases: 1) a generic boot process |
| 30 |
for precompiled binary distros where the maintainers has no idea what the |
| 31 |
user has and must support all combinations for all possible users. 2) Boot |
| 32 |
scenarios where you require access to the root device before you have access |
| 33 |
to the root device (/ on lvm, boot off some raid setups, etc) |
| 34 |
|
| 35 |
The first does not apply to gentoo at all. If you don't have the second, |
| 36 |
initrd is just extra unnecessary clutter and complexity and you are quite |
| 37 |
correct to resist it's presence. |
| 38 |
|
| 39 |
-- |
| 40 |
alan dot mckinnon at gmail dot com |
Archives