Date: Thu, 17 Oct 2002 15:04:23 +0100 From: Mark Murray <mark@grondar.za> To: "Robert Withrow" <bwithrow@nortelnetworks.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Linux compatibility and /dev/null Message-ID: <200210171404.g9HE4N01079983@grimreaper.grondar.org> In-Reply-To: <200210171353.g9HDrb211194@zrtps0m6.us.nortel.com> ; from "Robert Withrow" <bwithrow@nortelnetworks.com> "Thu, 17 Oct 2002 09:53:37 EDT." References: <200210171353.g9HDrb211194@zrtps0m6.us.nortel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> What gives? ls -l /dev/null says: > > crw-rw-rw- 1 root wheel 2, 2 Oct 9 12:45 /dev/null As it should. > That's groovy. But what about /compat/linux/dev/null? > > -rw-r--r-- 1 root wheel 0 Oct 2 17:59 /compat/linux/dev/null Huh??! A _file_??! It should be a device! > Hmm??? Doing "chmod 666 /compat/linux/dev/null" fixes the problem. Temporarily only. A better workaround is "rm /compat/linux/dev/null; mknod /compat/linux/dev/null c 2 2 root:wheel". With your solution, that file may fill up with unwanted junk. > This looks like a bug in the linux-base port. I'll file a PR. Indeed. Good move. M -- o Mark Murray \_ O.\_ Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200210171404.g9HE4N01079983>