| 1 |
On Thu, 19 Jul 2012 07:05:39 -0400 |
| 2 |
Rich Freeman <rich0@g.o> wrote: |
| 3 |
|
| 4 |
> As others have mentioned, coreutils doesn't impact the initramfs much |
| 5 |
> anyway, though other tools like mdadm/lvm/etc are more likely to. |
| 6 |
> |
| 7 |
> I think the more practical issue is that it isn't straightforward to |
| 8 |
> do in an automated way. I suppose we could keep an always-up-to-date |
| 9 |
> kernel and initramfs SOMEWHERE, but that won't necessarily be where |
| 10 |
> the user boots it from. Also, we need flexibility as users tend to |
| 11 |
> tweak these things - dracut has lots of options for how the initramfs |
| 12 |
> is built, users might use any of several initramfs implementations, |
| 13 |
> and the kernel config is frequently tweaked, and doesn't always work |
| 14 |
> if you just do a make oldconfig. Usually the way other distros make |
| 15 |
> all of this work is by making everything generic and not support |
| 16 |
> configurability. |
| 17 |
> |
| 18 |
> Rich |
| 19 |
> |
| 20 |
|
| 21 |
For me, the issue isn't so much that it's *hard* to rebuild an |
| 22 |
initramfs as that it's not obvious *when* to do so. For the kernel, |
| 23 |
this is a trivial problem: when sys-kernel/gentoo-sources bumps, |
| 24 |
rebuild the kernel. For an initramfs, when do I rebuild? When there's a |
| 25 |
new, what? Coreutils? Mdadm? LVM? Glibc? Busybox? Something-firmware? |
| 26 |
What about any less-obvious libraries they might link to, like zlib or |
| 27 |
something? All of those things are presumably in my initramfs, but |
| 28 |
there's no canonical list I'm aware of that tells me "if one of the |
| 29 |
packages in this list updates, you must rebuild your initramfs if you |
| 30 |
wish to take advantage of the upgrade". |
| 31 |
|
| 32 |
Chris |
Archives