Date: Thu, 17 Oct 2002 11:55:39 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Mark Murray <mark@grondar.za> Cc: Robert Withrow <bwithrow@nortelnetworks.com>, freebsd-hackers@FreeBSD.ORG Subject: Re: Linux compatibility and /dev/null Message-ID: <3DAF07AB.665A7F7D@mindspring.com> References: <200210171353.g9HDrb211194@zrtps0m6.us.nortel.com> <200210171404.g9HE4N01079983@grimreaper.grondar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Murray wrote: > > -rw-r--r-- 1 root wheel 0 Oct 2 17:59 /compat/linux/dev/null > > Huh??! A _file_??! It should be a device! Definitely wrong. > > 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. Why not just remove it? If you remove it, the device will be looked up in the system directory instead, and it will get the real /dev/null instead of the compat version. There aren't supposed to be semantic differences between FreeBSD and Linux, for /dev/null. It sounds instead like there is a problem with the union of "/" and "/compat/linux" for "> xxx" redirects... certain kinds of opens. -- Terry 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?3DAF07AB.665A7F7D>