Messages in this thread | | | Date | Mon, 20 Dec 2004 19:16:45 +1100 | From | Nick Piggin <> | Subject | Re: /sys/block vs. /sys/class/block |
| |
Benjamin Herrenschmidt wrote: > I'm trying to understand why we have /sys/block instead > of /sys/class/block, and so far, I haven't found a single good argument > justifying it... It just messes up the so far logical layout of sysfs > for no apparent reason. > > I also didn't find where /sys/block is created, but that's maybe because > I didn't search too hard :) So I'm not coming up with a patch yet, but > unless somebody can convince me it should stay here, I'll do so soon. > > If the reason not to fix it is backward compatibility, then that would > really be a shame we managed already to turn the brand new sysfs into a > mess with no hope of fixing it... If there is really a problem there, > maybe we could move it and keep a compat symlink for a few kernel > revs... ? >
Seems like that's where it belongs.
The reason why it is in /sys/block is because it is apparently a "subsystem", and using decl_subsys - drivers/block/genhd.c
Nick - 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/
| |