Previously warp@whitestar.soark.net wrote: > We have to do that anyways for 2.0.36.. Only recompile, to work with 2.1 expect to fix a lot of code.. > When did we get sound modules? With 2.2.0 we could actually have some!! <shameless plug> You did know we have alsa packages, right? And they even work with both 2.0 and 2.1 kernels.... </plug> > > . We have to rework on the boot-floppies to cope with different > > and/or more modules etc. > > We have to do that anyways for 2.0.36.. No, same as with hamm: default to one kernel and supply the sources and images for 2.0.36 as well. > > > . We have to ensure that the new kernel headers won't infect > > various compilation of programs. > > I thought that was part of the idea of the glibc 2 header stuff.. Not everything can use that.. remember the hdparm disaster when we switched to 2.0.35 ? > Nope, works fine here and with countless others.. and 2.1 broke lots of packages last time I tried it, no to mention I got errors when booting since route works differently now, ipfwadm is replaces by ipchains, etc.. > If its not done for slink, then definitely for 2.2.. (2.2 for 2.2.x hmm) That is a whole different thing.. > I hope our release manager won't jump on any track without fully > considering it.. Remember the beginning/end of trainspotting? :) Wichert. -- ============================================================================== This combination of bytes forms a message written to you by Wichert Akkerman. E-Mail: wakkerma@wi.LeidenUniv.nl WWW: http://www.wi.leidenuniv.nl/~wichert/
Attachment:
pgpAzZxtvVyAq.pgp
Description: PGP signature