Re: Really 2.6.18?
maximilian attems <maks@sternwelten.at> writes:
>> But Maks, how we'll ensure that there's no regressions for our users?
>>
>> Or the idea is to suply two installation medias? One with released
>> kernel and other with the "new" kernel? That would be great but would
>> push a lot of more work on d-i team.
>
> it is meant to not be the default, but easily choosable like it was
> for sarge to blindy type linux26
> this allows to support hardware for etch that is not yet released and
> wouldn't be supported by 2.6.18. aka sexy new stuff :)
I see.
> as a side topic you mentioned fixes in grub, please don't forget
> about the optional existing .bak initrd entries?
I hadn't forget about them. I just want to have current fixed grub on
etch before new features. I know this is a trivial one but let's first
have a stable and ready for release package before we add new stuff.
If you can prepare a patch it could speedup things...
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: otavio@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
you the whole house."
Reply to: