cannot create partition entries for /dev/ad3
David Gilbert
dgilbert at dclg.ca
Thu Oct 9 08:13:52 PDT 2003
>>>>> "Daniel" == Daniel O'Connor <doconnor at gsoft.com.au> writes:
Daniel> The only reason most people will ever touch /dev is to either
Daniel> make devices (hence no longer necessary with devfs), or change
Daniel> permissions. The later is more difficult with devfs, but IMHO
Daniel> the tradeoff is worthwhile.
This brings me to my (small) beef with devfs. When you invoke an
abstraction, a metric of the usefulness of that abstraction is how
well the abstractions metaphors map onto the target system's
metaphors.
So as a filesystem, devfs does will by replicating the average
person's view of should be in /dev ... subject to what devices are
actually found...
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.
Now... part of the problem here is that there is no simple interface
for the kernel to access (and update) a file ... which might be an
easy way to store persistence... but that's all a larger design
problem.
Now we do have the /etc/devfs.conf ... but this doesn't (yet) approach
the topic of devices added and removed from the system. Maybe this is
a natural extension for devd.
Dave.
Dave.
--
============================================================================
|David Gilbert, Independent Contractor. | Two things can only be |
|Mail: dave at daveg.ca | equal if and only if they |
|http://daveg.ca | are precisely opposite. |
=========================================================GLO================
--
============================================================================
|David Gilbert, Independent Contractor. | Two things can only be |
|Mail: dave at daveg.ca | equal if and only if they |
|http://daveg.ca | are precisely opposite. |
=========================================================GLO================
More information about the freebsd-current
mailing list