> Johannes Erdfelt wrote:
> > On Thu, Apr 13, 2000, David Elliott <dfe@infinite-internet.net> wrote:
> > > Johannes Erdfelt wrote:
> > > > On Thu, Apr 13, 2000, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > >
> > > > [SNIP]
> > > > I want mouse A to always be named mouse0, and mouse B to always be named
> > > > mouse1, EVEN if I connect mouse B in first. It should be named mouse1
> > > > and mouse0 should be empty.
> > >
> > > Why? mouse0 and mouse1 are kernel labels that are assigned based on which
> > > device was found first, same with eth0 and eth1.
> >
> > When I use /dev/mouse0, I always want it to be the same mouse, not the
> > mouse which happened to be enumerated first by the USB bus.
> >
> > I also want to know which mouse is which. As it is right now, the order
> > you plug things into the USB bus is they way they get named.
> >
> > I can never know what physical mouse /dev/mouse0 is connected to.
> >
> My point is that you shouldn't. Assume we don't have a devfs at all and
> /dev/mouse0 consistently maps to some MAJ/MIN combo. The kernel will
> /therefore
> assign mice as it finds them, which can even change from version to version of the
> kernel as far as I am concerned.
However, the device names (or majors/minors) should be independent on:
- kernel configuration (driver present or not)
- module loading sequence
-- ======================================================================= Andrzej M. Krzysztofowicz ankry@mif.pg.gda.pl phone (48)(58) 347 14 61 Faculty of Applied Phys. & Math., Technical University of Gdansk- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:24 EST