On Thu, Aug 25, 2005 at 01:01:10AM +0200, Marco d'Itri wrote: > On Aug 24, martin f krafft <madduck@debian.org> wrote: > > > udev has also been the hotplug multiplexer for some time now. > > Yeah. Horrible. Will udev become an editor and MTA too, maybe after > > etch? > No. But since it had to deal with most events, applying the same process > to the others was a natural extension of its design. > > > 2.4 kernels will not be supported in etch, > > I don't think this is an authoritative statement. At the moment, > > some architectures do not work with 2.6. > It's an educated guess. I consulted some of the interested maintainers > and followed the debian-kernel list, and so far there is no sign that > 2.4 will be supported (and if 2.6 will not be fixed on architectures > like sparc32, too bad for them). Although being able to ship just one kernel for all our ports in etch is everyone's first choice, the release team has not made any decision yet to exclude 2.4 kernels from etch if they're needed for a particular arch or subarch. Given that the kernel team is still rolling new 2.4 updates in unstable, and d-i still defaults to 2.4 on a majority of archs, I think it is premature to drop hotplug support for 2.4 at this point. It would certainly be a big help to the release team in making this decision if the kernel team would begin to drop 2.4 kernels as early as possible in the release cycle for those architectures where they believe they are no longer needed. Together with working out which ports are actually viable for etch under the new requirements (which of course first requires fully specifying those requirements), we should be able to get a clear picture in a couple of months of just what the kernel requirements are for etch. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature