It kinda looks like you've stripped your kernel binary. If you havn't,
don't, certain programs need the kernel symbols to access kmem.
-Matt
Matthew Dillon
[EMAIL
Check if your /dev/null has been replaced by some stupid `real' file.
The `nlist failed' problem bit me several weeks ago on two machines (one
running 4-stable and the other running -current) and it turned out to be
a /dev/null problem. You may want to remove /dev/null maually and do a
`sh
/dev/null was not the problem. I removed and remade it. I am using
the latest MAKEDEV.
# ls -l /dev/null
crw-rw-rw- 1 root wheel2, 2 Apr 3 13:40 /dev/null
tomdean
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Aha! I am loading the kernel directly.
2:da(2,a)/kernel
I looked in the archives, but, did not see anything.
I am munging with a disk, da1. -current is on da2. 3.4 from the CD
on da0.
Next week I will have a boot manager again!
tomdean
To Unsubscribe: send mail to [EMAIL PROTECTED]
