Messages in this thread | | | Subject | Re: [PATCH] Permissions don't stick on ConfigFS attributes | From | (Eric W. Biederman) | Date | Sun, 21 Aug 2005 22:49:20 -0600 |
| |
I am confused. I am beginning to see shades of the devfs problems coming up again. sysfs is built to be world readable by everyone who has it mounted in their namespace. Writable files in sysfs I have never understood.
Given that we now have files which do not conform to one uniform policy for everyone is there any reason why we do not want to allocate a character device major number for all config values and dynamically allocate a minor number for each config value? Giving each config value its own unique entry under /dev.
Device nodes for each writable config value trivially handles persistence and user policy and should be easy to implement in the kernel. We already have a policy engine in userspace, udev to handle all of the chaos.
Why do we need another mechanism?
Are device nodes out of fashion these days?
Eric - 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/
| |