Re: status of 2.6.7 ? (Was Re: Bug#256763: kernel-image-2.6.6-i386: not ready for sarge just yet)
On Sat, Jul 03, 2004 at 11:54:03AM -0700, William Lee Irwin III wrote:
> On Wed, Jun 30, 2004 at 08:19:07AM +0200, Sven Luther wrote:
> >> For example, i know that the XF86Config-4 file needs to be changed when
> >> using a ps2 mouse, since it was /dev/psaux previously, and is
> >> /dev/input/mice now. Breaking X during the upgrade is hardly acceptable
> >> if we are going to make 2.6 the default.
> On Sat, Jul 03, 2004 at 07:17:08PM +0200, Christoph Hellwig wrote:
> > The /dev/psaux situation seems to be a big mess. I added /dev/psaux
> > upstream long ago so I wouldn't have to change my XF86Config for 2.4
> > vs 2.6. In the meantime X can have two different input devices
> > specified and won't fail if one of them doesn't work but gives strange
> > results when both work. And Debian has both on the default XF86Config.
> > Currently the Debian kernel has another config option to have /dev/psaux
> > support in the kernel but disabled by default. I really hate that hack
> > and would just remove /dev/psaux from the Debian kernel as apparently
> > our X packages don't need that transition-aid.
> Unless we've got a counterexample to its superfluity dropping it sounds
> like the way to go. The weird thing is Sven's going on about device nodes'
> names/locations. Sven, what's setting up your device nodes?
Huh ? They have always been there, i suppose they are generated by the
package providing them, or by MAKEDEV. There may be other solution, like
udev or devfs, they are all controversial, and you have to start from
the principle that any guy upgrading from woody to sarge will have the
traditional way of setting those.
Willian, could you enlighten us of the possible future standard that is
emerging for future kernels ? As well as how they will fit into this,
especially given the sarge release schedule which is again on track ?