Re: /sys/block vs. /sys/class/block
From: Jens Axboe (axboe_at_suse.de)
Date: 12/20/04
- Previous message: Richard Ems: "Re: PROBLEM: Network hang: "eth0: Tx timed out (f0080), is buffer full?" (Plain) (Plain)"
- In reply to: Nick Piggin: "Re: /sys/block vs. /sys/class/block"
- Next in thread: Jan Engelhardt: "Re: /sys/block vs. /sys/class/block"
- Reply: Jan Engelhardt: "Re: /sys/block vs. /sys/class/block"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 20 Dec 2004 10:45:06 +0100 To: Nick Piggin <nickpiggin@yahoo.com.au>
On Mon, Dec 20 2004, Nick Piggin wrote:
> Benjamin Herrenschmidt wrote:
> >>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
> >
> >
> >I'm not convinced ... If you look at how /sys is organized, it really
> >doesn't make any sense ... block devives are really devices of "class
> >block", wether we have a block "subsystem" in there is irrelevant imho.
> >
>
> Sorry to be unclear: I was agreeing with you ;)
>
> I was just pointing out that the reason it is currently /sys/block is
> that decl_subsys call.
Ditto, the question is how to move it with as little pain as possible...
I think the symlink approach would be fine.
-- Jens Axboe - 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: Richard Ems: "Re: PROBLEM: Network hang: "eth0: Tx timed out (f0080), is buffer full?" (Plain) (Plain)"
- In reply to: Nick Piggin: "Re: /sys/block vs. /sys/class/block"
- Next in thread: Jan Engelhardt: "Re: /sys/block vs. /sys/class/block"
- Reply: Jan Engelhardt: "Re: /sys/block vs. /sys/class/block"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
