src/sys/miscfs/devfs/devfs_tree.c, branch release/2.2.6 FreeBSD source tree MFC: bring in changes from -current including some formatting changes 1997-11-13T18:22:21+00:00 Julian Elischer julian@FreeBSD.org 1997-11-13T18:22:21+00:00 83086f21f4b1d7a580a0c66465fcd40b9f8dde54 so that I can keep them in sync easier. 
so that I can keep them in sync easier.
YAMFC: bring devfs_tree.c -> 1.38 1997-08-27T01:32:30+00:00 Julian Elischer julian@FreeBSD.org 1997-08-27T01:32:30+00:00 5b0ee2ab36cd43f498948d02754155cc4cd4eb6d devfs_vfsops.c -> 1.18 devfs_vnops.c -> 1.37 various bug fixes. 
		devfs_vfsops.c -> 1.18
		devfs_vnops.c -> 1.37
various bug fixes.
YAMFC 1996-11-23T08:35:39+00:00 Poul-Henning Kamp phk@FreeBSD.org 1996-11-23T08:35:39+00:00 3b020d9f64673d5606c25605818e7ff4720dad68 






devfs_tree.c:	improve our bdevvp() function.
1996-10-28T11:36:06+00:00

Poul-Henning Kamp
phk@FreeBSD.org

1996-10-28T11:36:06+00:00

7f6a56eff721db67a3723108ff53e93ded499ebc

devfs_vnops.c:	move a debug printf to be consistent.





devfs_vnops.c:	move a debug printf to be consistent.







Started unspamming <sys/systm.h>.  Don't include <machine/stdarg.h>
1996-09-29T15:00:37+00:00

Bruce Evans
bde@FreeBSD.org

1996-09-29T15:00:37+00:00

dc927d0c6b1a019cbe3599965dd74c9afb19c674

to get the declaration of va_list; just use _BSD_VA_LIST.  Fixed
the 2 places that need <machine.stdarg.h> but didn't include it
explicitly.





to get the declaration of va_list; just use _BSD_VA_LIST.  Fixed
the 2 places that need <machine.stdarg.h> but didn't include it
explicitly.







Updated #includes to 4.4Lite style.
1996-09-10T08:32:01+00:00

Bruce Evans
bde@FreeBSD.org

1996-09-10T08:32:01+00:00

f313170d3c95b55eba72119af2c229a0e77a50a6












Submitted by: doug Rabson (dfr@render.com)
1996-08-13T19:48:41+00:00

Julian Elischer
julian@FreeBSD.org

1996-08-13T19:48:41+00:00

def534af64d35344a17c0dfd24285d0932ec8cca

cleaning up some of the vnode usage..

(I'm sure it still needs more..)
where can one find out what each vfs call expects to be locked
on completion, and how can one find out what each layer expects
to be freed on error.?





cleaning up some of the vnode usage..

(I'm sure it still needs more..)
where can one find out what each vfs call expects to be locked
on completion, and how can one find out what each layer expects
to be freed on error.?







symlink support in devfs.
1996-08-13T07:21:45+00:00

Julian Elischer
julian@FreeBSD.org

1996-08-13T07:21:45+00:00

ed9a71b7fc714f25f9c8682e0e88eee0960326f4

it only barely works so don't get too carried away..
I noticed that teh symlink is length 0..
I guess I'll fix that tomorrow..
it also sometimes panics with "cleaned vnode isn't" but it's not more
broken than it was before.. I really want to go over it with someone
who understands the lifecycle of a vnode better than I do..

terry?
kirk?
david?
john?





it only barely works so don't get too carried away..
I noticed that teh symlink is length 0..
I guess I'll fix that tomorrow..
it also sometimes panics with "cleaned vnode isn't" but it's not more
broken than it was before.. I really want to go over it with someone
who understands the lifecycle of a vnode better than I do..

terry?
kirk?
david?
john?







Only use the special bdevvp() for DEVFS if DEVFS_ROOT is defined.  This
1996-07-30T18:00:32+00:00

Bruce Evans
bde@FreeBSD.org

1996-07-30T18:00:32+00:00

8c2ff39670b5103b0a3e3173d91d93c2576d1b03

makes option DEVFS safe to use again (although mounting devfs is unsafe).





makes option DEVFS safe to use again (although mounting devfs is unsafe).







DEVFS needs a special bdevvp().
1996-07-24T21:22:36+00:00

Poul-Henning Kamp
phk@FreeBSD.org

1996-07-24T21:22:36+00:00

c74bb986382bf0017bf8ff494d88b9d916432b79

I just noticed some junk in my patch.  I'll remove that in a sec.





I just noticed some junk in my patch.  I'll remove that in a sec.