Sean Eric Fagan 75bd443641 Explain why Warner is right, and I am wrong, in the removing of the ... file object. Also explain some possible directions to re-implement it -- I'm not sure it should be, given the minimal application use. (Other than having the debugger automatically access the symbols for a process, the main use I'd found was with some minor accounting ability, but _that_ depends on it being in the filesystem space; an ioctl access method would be useless in that case.) This is a code-less change; only a comment has been added.		1999-11-08 05:13:54 +00:00
..
deadfs	$Id$ -> $FreeBSD$	1999-08-28 01:08:13 +00:00
devfs	Remove the iskmemdev() function. Make it the responsibility of the mem.c	1999-11-07 12:01:32 +00:00
fdesc	Update for fileops.fo_stat() addition. Note, this would panic if	1999-11-08 03:36:29 +00:00
fifofs	$Id$ -> $FreeBSD$	1999-08-28 01:08:13 +00:00
kernfs	Seperate the export check in VFS_FHTOVP, exports are now checked via	1999-09-11 00:46:08 +00:00
nullfs	Seperate the export check in VFS_FHTOVP, exports are now checked via	1999-09-11 00:46:08 +00:00
portal	Seperate the export check in VFS_FHTOVP, exports are now checked via	1999-09-11 00:46:08 +00:00
procfs	Explain why Warner is right, and I am wrong, in the removing of the	1999-11-08 05:13:54 +00:00
specfs	Use vop_panic() instead of spec_badop().	1999-11-07 15:09:59 +00:00
umapfs	Seperate the export check in VFS_FHTOVP, exports are now checked via	1999-09-11 00:46:08 +00:00
union	useracc() the prequel:	1999-10-29 18:09:36 +00:00