Linux-kernel mailing list archive 2000-15,: Re: devfs - why not ?

# Re: devfs - why not ?

Richard Gooch (rgooch@ras.ucalgary.ca)
Thu, 13 Apr 2000 17:30:54 -0600

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: H. Peter Anvin: "Re: What /proc should contain [was: /proc/driver/microcode]"
- Previous message: Steve Dodd: "[PATCH] 2.3.99x: SMP race in getblk()?"
- In reply to: Alan Cox: "Re: devfs - why not ?"
- Next in thread: Brian Swetland: "Re: devfs - why not ?"
- Reply: Brian Swetland: "Re: devfs - why not ?"

Johannes Erdfelt writes:
> On Thu, Apr 13, 2000, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > > Mice. There, try that one. The two hypothetical mice have no USB serial
> > > numbers.
> >
> > You completely miss the point of this discussion. At least until I have
> > a file system on my mouse.
>
> Huh?
>
> The beginning of this discussion was me saying:
>
> > > It isn't a silver bullet for hot swap devices tho. We still have device
> > > naming issues. How do I track that this USB to Ethernet device is eth1
> > > and assign eth1 to it all the time.
>
> The point of the discussion is that there is no solution to the problem
> right now and devfs isn't a solution either.
>
> UUID's on filesystems may be a specific solution to a specific problem,
> but it still doesn't solve the fact that it's a specific solution.
>
> And no some seems care.
>
> I see no reason why I need a filesystem on my mouse to get correct
> naming for the device.
>
> 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.

So is there anything that distinguishes the two mice? Unique serial
numbers, model numbers, whatever?

Regards,

Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca

-
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/

- Next message: H. Peter Anvin: "Re: What /proc should contain [was: /proc/driver/microcode]"
- Previous message: Steve Dodd: "[PATCH] 2.3.99x: SMP race in getblk()?"
- In reply to: Alan Cox: "Re: devfs - why not ?"
- Next in thread: Brian Swetland: "Re: devfs - why not ?"
- Reply: Brian Swetland: "Re: devfs - why not ?"