Messages in this thread | | | Date | Mon, 13 Feb 2006 17:49:11 +0100 | From | Olivier Galibert <> | Subject | Re: CD writing in future Linux (stirring up a hornets' nest) |
| |
On Sun, Feb 12, 2006 at 10:24:12PM -0800, Greg KH wrote: > On Sun, Feb 12, 2006 at 10:14:06PM +0100, Olivier Galibert wrote: > > On Sun, Feb 12, 2006 at 08:46:33AM -0800, Greg KH wrote: > > > On Sun, Feb 12, 2006 at 01:04:51PM +0100, Olivier Galibert wrote: > > > > You need to call udevinfo for that, or parse /dev/.udev/*. Do you > > > > think it would be possible to have hotplug/udev/whatever exists in the > > > > future to give that information back in the kernel and have it appear > > > > in sysfs? > > > > > > No. Why would it when it is very simple to query udevinfo for that? > > > > In order not to depend on a userland package for the kernel service of > > device enumeration? It's udevinfo now, what will it be in two years? > > WTF? You are depending on that same program to create your device > nodes. If you don't want to use that program to do it, then use > something else, or use a static device tree, which works like always.
Funnily enough, my, say, mp3 usb key sync system would like to run as non-root and does not want to know or care about what program creates the device nodes. Too bad this otherwise beautiful and useful sysfs is crippled by design.
> sysfs exports everything that userspace needs to know, if it wants to > create a device node to talk to that specific device. udev used it to > create your /dev tree, while other programs use it to create temporary > device nodes to do other things to your devices. Either way, the kernel > doesn't know, or care what you call those device nodes.
You mean root is mandatory to talk with devices, whatever they are?
OG. - 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/
| |