On Fri, 9 Jul 1999, Patrick Welche wrote:

> > Let me know how it works!
> 
> I think this is related :( In a bid to work out what's up with my panic
> ridden computer, I tried building (a few times) an INSTALL disk - fdset -
> and I invariably get stuck at
> 
> ...
> SPECIAL /bin/rm etc/pwd.db
> COPY    ${CURDIR}/../../../../etc/etc.i386/MAKEDEV      dev/MAKEDEV
> SPECIAL cd dev; sh MAKEDEV ramdisk
> 
> in:
> 
>     0  9032  8802  29  -2  0    64  464 vnlock D+   p1    0:00.01 chown uucp tty01 dty01 
> 
> vnlock :(

Strange. I'll see if I can reproduce it. 

You're only using ffs, yes? Even over the vnd, it's just ffs?

In that case, all the locking should be the same as before. I didn't
change the locking protocol (what takes a locked vnode, what doesn't),
just how they do it.

> chowning in /dev/vnd0a on /mnt type ffs (local)
> 
> Oh dear, just tried ls /mnt/dev, and:
> 
>     0  9114  9074   0  -2  0   212  116 vnlock D+   p9    0:00.00 ls /mnt/dev 

Yes. /mnt/dev/vnd0a evidently was locked, so now /mnt/dev is locked in the
lookup on /mnt/dev/vnd0a. Do it again, and /mnt will be locked. Again, and
/ will be locked. The machine dies at that point. :-)

Take care,

Bill