> > Take this example: I've loopback mounted an UML disk image using fuse > > (no privileges required), and want to create some device nodes. I > > can't yet boot the UML because the device node is missing from the > > image. So what should I do. Currently I have to manipulate the > > mounted image as root. But that's really shouldn't be needed. > > That's something that shouldn't be solved in the filesystem, but rather > through exact semantics of unprivilegued mounts. Given that an > unprivilegued implies ignoring the device files we can easily allow > users to create them, because they're nothing special anymore. Exacly. And we already have an API for that: mknod(2). It would be quite stupid to introduce _another_ API to do the same. It would mean that all the tools, like mknod(8) would not work with the new API. Or am I misunderstanding your suggestion? Miklos - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
