initrd on installed kernels
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I was wondering why are we using initd on installed debian kernels.
Let me explain myself: I can perfectly understand that initrd is needed
for d-i, but, when I recently updated an x86 woody box to testing,
upgrading its kernel to 2.4.26 debian, I noticed that the initrd thingy
was installed (got the nice warning about lilo).
I didn't pay much attention to that at that time, knowing it was the
new default for debian kernels. But, I started giggling when I realized
the total boot time (time before first login prompt) of the box was
almost tripled (that's a P2 400).
So here comes my suggestion: why not having a specific kernel deb for
d-i *with* (the one corresponding to the version selected for the
stable installer), and the rest of the kernel debs *without* initrd, as
they used to be? That implies that d-i would have to install a
non-initrd kernel, obviously.
I'm relating here a 2.4 experience, but as far as I can tell, the same
is relevant wrt 2.6.
Please don't flame, that's just a question. Well, ok, if you wanna
flame anyway, go ahead ;)
Thx,
- --
Thibaut VARENE
The PA/Linux ESIEE Team
http://www.pateam.org/
PS: my question about proper 2.6 packaging still holds, see
http://lists.debian.org/debian-kernel/2004/06/msg00177.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFA2eZGHjLD2rfS8GMRAgJ+AKC/hpbei+G8k5/1jklHxsV6LOyLZACfSfBN
is7KxszjipmzIwb9QbXwSLw=
=KMdT
-----END PGP SIGNATURE-----
Reply to: