Re: /sys/block vs. /sys/class/block
From: Benjamin Herrenschmidt (benh_at_kernel.crashing.org)
Date: 12/23/04
- Previous message: cranium2003: "device driver program not running problem"
- In reply to: David Weinehall: "Re: /sys/block vs. /sys/class/block"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: David Weinehall <tao@debian.org> Date: Thu, 23 Dec 2004 07:55:33 +0100
> > But I guess I should ask, who really cares about this, so late in the
> > sysfs structure game? Is /sys/block/ really a big problem for anyone?
> > And if it is, I'd much rather someone make the required driver core
> > changes to fix this up properly, than just put a symlink to paper over
> > some userspace issue.
>
> Maybe because *for once* it'd be nice to actually have inconsistencies
> gotten rid of in their relative infancy instead of waiting 10 years
> and then having to explain them as existing only for hysterical
> raisins...
Agreed.
Ben.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: cranium2003: "device driver program not running problem"
- In reply to: David Weinehall: "Re: /sys/block vs. /sys/class/block"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
