hardenedbsd/HardenedBSD
1
0
Fork 0
mirror of https://git.hardenedbsd.org/hardenedbsd/HardenedBSD.git synced 2025-01-01 00:18:15 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

change to reflect reality.

Browse Source 
(yes I know I should have done one commit rod....)
This commit is contained in:
Julian Elischer 1995-05-03 23:10:35 +00:00
parent c79137536b
commit bacc93a004
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
sys/miscfs/devfs/README
View File

@ -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