Peter Samuelson writes:
>
> [Horst von Brand <vonbrand@sleipnir.valparaiso.cl>]
> > You can then also painlessly set (and preserve) permissions on the
> > device in the filessytem. Cost is one inode on disk per device.
>
> Wait -- don't chown/chmod/mknod also generate devfsd events? Why can't
Yes.
> devfsd take those events and operate on a parallel directory tree?
> And
It can. All the mechanism is there.
> then use that parallel tree to chmod/chown next time the device
> inserts itself, i.e. after insmod or reboot. (Remember, devfsd is
> notified on every file creation, if it cares.) No tar kludge
> involved.
Correct.
> I could have sworn this was Richard's idea, not mine. devfsd,
Yes, I think it was.
> properly implemented, can solve a *lot* of these problems. If the
> current devfsd is a WIP, don't blame it on devfs design problems.
You can do it now. Sure, you may need to write a script to support
this, but the mechanism is there.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
-
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/
This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:21 EST