change to reflect reality.

(yes I know I should have done one commit rod....)

1 files changed, 6 insertions, 4 deletions

diff --git a/sys/miscfs/devfs/README b/sys/miscfs/devfs/README
index b45a46a..1004f04 100644
--- a/sys/miscfs/devfs/README
+++ b/sys/miscfs/devfs/README
@@ -104,15 +104,17 @@ result in a message "hanging vnode" and the system will panic.
 3/ the dates of all nodes is '0' i.e. 00:00 1st Jan 1970 UTC.
 It appears 'time' in the kernel hasn't been started at the time that
 the devfs is started up. (when the first device registers itself).
-notably, the VFS hasn't been started yet either so the devfs has to be careful
+The workaround is to interpret 0 to be the same as 'boottime'.
+This may actually become a 'feature'.
+5/notably, the VFS hasn't been started yet either so the devfs has to be careful
 to not use VFS features during probe time.
-4/ many features are not present yet..
+6/ many features are not present yet..
 e.g. symlinks, a comprehensive registration interface (only a crude one)
 ability to unlink and mv nodes.
-5/ I'm pretty sure my use of vnodes is bad and it may be 'losing'
+7/ I'm pretty sure my use of vnodes is bad and it may be 'losing'
 them, or alternatively, corrupting things.. I need a vnode specialist
 to look at this.
-6/ The back and front node structures have become very similar with time
+8/ The back and front node structures have become very similar with time
 and I decided to merge them to a single structure, 
 which is called a "dev_name" struct, as they can be thought of
 as the analogue of a directory entry, except that they are linked