[...]
> That is a flat out lie. With devfs, you can change the permissions just
> fine (with chown/chmod/chgrp/whatever utility you feel like using that
> works with other normal filesystems), and they will stay until the devfs
> filesystem is unmounted, and possibly even until you reboot, though I
> haven't tried that, and doubt it a bit... You could expect almost no less
> from a ramdisk (though it would stay until reboot on a ramdisk unless you
> reconfigured the ramdisk), or anything else that is stored on volatile
> media.
But you say, pemissions are permanent. What is it with you, is "permanent"
like in "stays the same unless changed" somehow hard to grasp?
> > If /dev is frequently cleaned up by a script and re-populated with
> > MAKEDEV whenever new hardware gets attached the situation is the same.
> > The configuration file for permissions/ownership would be MAKEDEV.
> What if you don't like the permissions MAKEDEV gives? devfs comes with a
> set of permissions that is not unlike the ones in the MAKEDEV script; it
> doesn't just blindly choose '777' as the permissions.
Change MAKEDEV? Write a MAKEDEV that uses /etc/makedev.conf as default
permissions when creating devices?
-- Dr. Horst H. von Brand mailto:vonbrand@inf.utfsm.cl Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/