tags 367870 +wontfix
stop
Hi,
On 24 May 2006, Martin Michlmayr said:
> * Manoj Srivastava <[EMAIL PROTECTED]> [2006-05-23 22:15]:
>> were the first I have heard about this, so I am not sure how to
>> handle this. Discussion with the d-i team folks seem to indicate
>> that the behaviour of kernel package need not change, which is
>> welcome news. I would much rather not change the default and
>> unleash kernel upgrades on unsuspecting users.
>
> Why not? The question which defaults to "no" warns the user that
> this kernel needs an initrd and that they have to make sure their
> boot loader support it. However, GRUB, which is the default in
> etch, supports initrds by default so I don't see why this question
> would default to no.
Etch is not released. Sarge is. And even for Etch + 1, I
would prefer that one was sure that a boot loader was in use that
could handle initrd's without configuration -- I have an open bug
that reflects a problem using grub dues to symbolic links in /boot,
which means that the grub setip was such that just havng an initrd
around was not good enough -- the symbolic link needed to be around.
manoj
--
QOTD: "What do you mean, you had the dog fixed? Just what made you
think he was broken!"
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.datasync.com/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
