Date: Wed, 19 Apr 1995 21:02:45 -0700 From: Julian Elischer <julian> To: CVS-commiters, cvs-sys Subject: cvs commit: src/sys/miscfs/devfs devfs.doc Message-ID: <199504200402.VAA13928@freefall.cdrom.com>
next in thread | raw e-mail | index | archive | help
julian 95/04/19 21:02:45 Modified: sys/miscfs/devfs devfs.doc Log: Submitted by: julian NOTES FOR RELEASE 1 1/ this is very preliminary It's been included so that people can start to play with it. (and fix bugs?) 2/ Attempts to unmount a devfs structure while you are 'IN' in will result in a message "hanging vnode" and the system will panic. 3/ 'find /devfs -print' will only find the directories, and the devices don't show up.. (?) 'find /devfs -ls' DOES show all the devices. (!?) 4/ 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 to not use VFS features during probe time. 5/ many features are not present yet.. e.g. symlinks, a comprehensive registration interface (only a crude one) ability to unlink and mv nodes. 6/ 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. 7/ The back and front node structures have become very similar with time and I have decided to merge them to a single structure, which will be called a "devname" struct, as they can be thought of as the analogue of a directory entry, except that they are linked rather than in an array. (the "devnode" structs can be thought of as inodes)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504200402.VAA13928>