Date: Mon, 18 Oct 2004 10:52:27 +0200 From: Alexander@Leidinger.net To: rse@engelschall.com Cc: freebsd-current@freebsd.org Subject: Re: Linux ABI and permissions to /dev Message-ID: <1098089547.4173844b1027a@netchild.homeip.net> In-Reply-To: <20041016170946.GA86123@engelschall.com> References: <20041015201033.GA51887@engelschall.com> <86acumu6dy.fsf@kamino.rfc1149.org> <20041016170946.GA86123@engelschall.com>
index | next in thread | previous in thread | raw e-mail
Zitat von "Ralf S. Engelschall" <rse@engelschall.com>: > > > Has anybody an idea where to search? There were no changes to devfs > > > recently and the recent changes to the Linuxulator seemed harmless to me > > > at the first glance... > > > > is there a /usr/compat/linux/dev directory? If there is try to remove > > it, so that it does not shadow the /dev/ direcotry > > Yes, I have a /compat/linux/dev directory: > > | # ls -l /compat/linux/dev/ > | total 0 > | brw-r--r-- 1 root wheel 0, 0x00010002 Sep 17 22:05 had > | brw-r--r-- 1 root wheel 0, 0x0001000a Sep 17 22:05 hdb > | lrwxr-xr-x 1 root wheel 22 Sep 17 22:05 tty0 -> > /compat/linux/dev/tty1 > | lrwxr-xr-x 1 root wheel 10 Sep 17 22:05 tty1 -> /dev/ttyv0 > | lrwxr-xr-x 1 root wheel 10 Sep 17 22:05 tty10 -> /dev/ttyv9 > | lrwxr-xr-x 1 root wheel 10 Sep 17 22:05 tty11 -> /dev/ttyva > | lrwxr-xr-x 1 root wheel 10 Sep 17 22:05 tty12 -> /dev/ttyvb > | lrwxr-xr-x 1 root wheel 10 Sep 17 22:05 tty2 -> /dev/ttyv1 > | lrwxr-xr-x 1 root wheel 10 Sep 17 22:05 tty3 -> /dev/ttyv2 > | lrwxr-xr-x 1 root wheel 10 Sep 17 22:05 tty4 -> /dev/ttyv3 > | lrwxr-xr-x 1 root wheel 10 Sep 17 22:05 tty5 -> /dev/ttyv4 > | lrwxr-xr-x 1 root wheel 10 Sep 17 22:05 tty6 -> /dev/ttyv5 > | lrwxr-xr-x 1 root wheel 10 Sep 17 22:05 tty7 -> /dev/ttyv6 > | lrwxr-xr-x 1 root wheel 10 Sep 17 22:05 tty8 -> /dev/ttyv7 > | lrwxr-xr-x 1 root wheel 10 Sep 17 22:05 tty9 -> /dev/ttyv8 > > And yes, your guess is right: once I remove it, the problem with > my "echo foo >/dev/null" or running "acroread" wents away. But the > /compat/linux/dev stuff is created by the "vmware3" port with its... > > | @exec mkdir -p %%LINUXBASE%%/dev;for n in 0 1 2 3 4 5 6 7 8 9; do ln -s > /dev/ttyv$n %%LINUXBASE%%/dev/tty$n;done > | @exec ln -s /dev/ttyva %%LINUXBASE%%/dev/tty10 > | @exec ln -s /dev/ttyvb %%LINUXBASE%%/dev/tty11 > | @exec mknod %%LINUXBASE%%/dev/had b 0 0x00010002 > | @exec mknod %%LINUXBASE%%/dev/hdb b 0 0x0001000a > > ...and unfortunately without at least the /compat/linux/dev/ttyv0 VMWare > ultimately fails on startup. So, for running VMWare one really needs > this directory. > > Additionally, the overlaying of /dev with /compat/linux/dev as the > "vmware3" port does, definetely _worked_ until about 2 weeks ago. So, > the question is what broke it? PHK (CCed) did some device nodes related commits to the filesystems. This could be related. Bye, Alexander.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1098089547.4173844b1027a>