Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964799AbWBMTJk (ORCPT ); Mon, 13 Feb 2006 14:09:40 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964805AbWBMTJk (ORCPT ); Mon, 13 Feb 2006 14:09:40 -0500 Received: from iabervon.org ([66.92.72.58]:26886 "EHLO iabervon.org") by vger.kernel.org with ESMTP id S964799AbWBMTJj (ORCPT ); Mon, 13 Feb 2006 14:09:39 -0500 Date: Mon, 13 Feb 2006 14:09:55 -0500 (EST) From: Daniel Barkalow To: dtor_core@ameritech.net cc: Greg KH , Bill Davidsen , Nix , Jens Axboe , Joerg Schilling , linux-kernel@vger.kernel.org Subject: Re: CD writing in future Linux (stirring up a hornets' nest) In-Reply-To: Message-ID: References: <43D7AF56.nailDFJ882IWI@burner> <20060125173127.GR4212@suse.de> <43D7C1DF.1070606@gmx.de> <878xt3rfjc.fsf@amaterasu.srvr.nix> <43ED005F.5060804@tmr.com> <20060210235654.GA22512@kroah.com> <20060213062158.GA2335@kroah.com> <20060213175142.GB20952@kroah.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1828 Lines: 38 On Mon, 13 Feb 2006, Dmitry Torokhov wrote: > On 2/13/06, Greg KH wrote: > > On Mon, Feb 13, 2006 at 03:05:49AM -0500, Daniel Barkalow wrote: > > > Are there guidelines on having a generic cdrom export information from its > > > block interface, rather than through its bus? I'm not finding any > > > documentation of sys/block/, aside from that it exists. > > > > That information should go into the device directory, not the sys/block > > directory (as it referrs to the device attributes, not the block gendev > > attributes.) > > > > Not necessarily - it would be easier for userspace programs if we had > a separate class in sysfs - /sys/class/cdrom. The problem with this > approach is that we do not allow a device belong o several classes > without introducing intermediate class devices (I mean a DVD+RW shoudl > probably belong to classes cdrom, dvdrom, cdwriter and dvdwriter). I don't think it needs to be a class, but I think that there should be a single place with a directory for each device that could be what you want, with a file that tells you if it is. That's why I was looking at block/; these things must be block devices, and there aren't an huge number of block devices. I suppose "grep 1 /sys/block/*/device/dvdwriter" is just as good; I hadn't dug far enough in to realize that the reason I wasn't seeing anything informative in /sys/block/*/device/ was that I didn't have any devices with informative drivers, not that it was actually supposed to only have links to other things. -Daniel *This .sig left intentionally blank* - 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/