On 9/16/05, Greg KH <[email protected]> wrote:
> On Fri, Sep 16, 2005 at 10:44:36AM -0500, Dmitry Torokhov wrote:
> > I'll try fix the patch I posted last night (that implements the above,
> > or at least what Kay described with sub-devices residing under their
> > parent devices and symlinked into their classes), I believe it could
> > also be used for block, so it will be like:
> >
> > .../block/
> > |-- devices
> > | |-- sda
> > | | |-- device -> ../../../../
> > | | |-- sda1
> > | | | |-- dev
> > | | | `-- device -> ../../../../../block/partitions/sda1
> > | | |-- sda2
> > | | | |-- dev
> > | | | `-- device -> ../../../../../block/partitions/sda2
> > ...
> > `-- partitions
> > |-- sda1 -> ../../../class/block/devices/sda/sda1
> > |-- sda2 -> ../../../class/block/devices/sda/sda2
>
> Nah, that's a mess. I think the proposal I had would work for both
> input and block with a minimum of disruption. Still don't know about
> video though, David said he would take some time this weekend to get me
> some feedback, which is good, as I have to get on a 14 hour plane ride
> soon...
>
You have to adjust udev to accept mouseX being not on /sys/class/input
level anyway so disruption is still here.
--
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |