In message <[EMAIL PROTECTED]>, David Gilbert writes: >But filesystems also have persistence. In the trivial case, the >persistence of the object (say ... a disk) preserved the filesystems >node. But if I walk into /dev and change the permissions on a node, >this persists only until the next reboot.
Rubbish! When did you last see your changes to /proc survive a reboot ? What you call a "filesystem" is really a name-resolution facility which translates what you think of as a "filename" into a particular kernel object. That kernel object can be a file on a persistent media, a file on a non-persistent media, a socket, a FIFO, a device, a process and almost any oddball thing you can can come up with. Persistence is a very optional property and it has nothing to do with the object living in the filesystem naming space. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
