![]() | |||||||||||
Messages in this thread |
Matthew Reppert wrote: > At the very least, sysfs' and devfs' approaches to devices differ in > philosophy. devfs says "here's a device node, you can tell where it is > in the bus hierarchy by looking at its filename". sysfs, on the other > hand, says "here's the device hierarchy", and gives you enough information > to create device nodes for each point in the hierarchy if you wish to do > so. > There's an interesting security implication here. I used to think "why don't they make a device node instead of exporting numbers, udev could then simply make a link to it" It'd be simpler, and the minimalists could use the node in sysf directly. The security advantage is that we don't get a device with some default permissions that might get abused. The udev config can decide to create a node with stricter than usual permissions, or decide to not make the node at all. Helge Hafting - 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/ | ||||||||||
| Last update: 2005-03-22 14:00 [from the cache] ©2003-2008 | |||||||||||