At Thu, 2 Nov 2000 14:11:44 -0500 (EST),
Andrew Gallatin wrote:
> To clarify -- this is the native /bin/ls and NOT /compat/linux/bin/ls?
Yes.
> I don't suppose you could throw an older kernel on and show the output
> of /bin/ls /compat/linux/dev ?
Here is the output from the native /bin/ls on 5.0-CURRENT as of two
days ago. This operation causes panic on the latest CURRENT:
knu@archon[2]% uname -a
FreeBSD archon.local.idaemons.org 5.0-CURRENT FreeBSD 5.0-CURRENT #13: Tue Oct 31
15:11:38 JST 2000 [EMAIL PROTECTED]:/usr/local/src/sys/compile/ARCHON
i386
knu@archon[2]% ls -l /compat/linux/dev
total 0
brw-r--r-- 1 root wheel - 0, 0x00010002 Nov 2 20:28 hda
brw-r--r-- 1 root wheel - 0, 0x0001000a Nov 2 20:28 hdb
crw-rw-rw- 1 root wheel - 2, 2 Nov 2 20:28 null
crw-r--r-- 1 root wheel - 202, 0 Nov 2 20:17 rtc
lrwxr-xr-x 1 root wheel - 22 Nov 2 20:28 tty0@ -> /compat/linux/dev/tty1
lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty1@ -> /dev/ttyv0
lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty10@ -> /dev/ttyv9
lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty11@ -> /dev/ttyva
lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty12@ -> /dev/ttyvb
lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty2@ -> /dev/ttyv1
lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty3@ -> /dev/ttyv2
lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty4@ -> /dev/ttyv3
lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty5@ -> /dev/ttyv4
lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty6@ -> /dev/ttyv5
lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty7@ -> /dev/ttyv6
lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty8@ -> /dev/ttyv7
lrwxr-xr-x 1 root wheel - 10 Nov 2 20:28 tty9@ -> /dev/ttyv8
crw-r--r-- 1 root wheel - 200, 0 Nov 2 20:28 vmmon
crw-r--r-- 1 root wheel - 149, 0x00010001 Nov 2 20:35 vmnet1
As you see, hda and hdb are block devices that might cause the panic..
--
/
/__ __
/ ) ) ) ) / and.or.jp / ruby-lang.org
Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org
"We're only at home when we're on the run, on the wing, on the fly"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
