Date: Tue, 26 Apr 2011 20:05:53 -0400 From: Robert Lorentz <robert.lorentz@gmail.com> To: "Jason J. Hellenthal" <jhell@DataIX.net> Cc: freebsd-bugs@freebsd.org Subject: Re: kern/139014: [null] /dev/null must be immunable to delete/unlink Message-ID: <C6FACB82-CB49-4A82-9F58-6DE99AFB03B8@gmail.com> In-Reply-To: <20110426075557.GA10559@DataIX.net> References: <201104260250.p3Q2oAIi039320@freefall.freebsd.org> <20110426075557.GA10559@DataIX.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Jason - Thanks for responding. Also thanks for your help on freenode #freebsd (I'm on there as rcl sometimes) I've run your script and this is what I get: [-- Attachment #2 --] FreeBSD 9.0-CURRENT #0 r220986: Sun Apr 24 08:25:28 UTC 2011 root@bsdvm.localdomain:/usr/obj/root/current/current/sys/GENERIC BEFORE /dev/null: empty File: "/dev/null" Size: 0 FileType: Character Device Mode: (0666/crw-rw-rw-) Uid: ( 0/ root) Gid: ( 0/ wheel) Device: 255,83886080 Inode: 23 Links: 1 Access: Tue Apr 26 20:00:07 2011 Modify: Tue Apr 26 20:00:01 2011 Change: Tue Apr 26 20:00:01 2011 crw-rw-rw- 1 root wheel - 0, 23 Apr 26 20:00 /dev/null AFTER /dev/null: empty File: "/dev/null" Size: 0 FileType: Character Device Mode: (0777/crwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ wheel) Device: 255,83886080 Inode: 23 Links: 1 Access: Tue Apr 26 20:00:08 2011 Modify: Tue Apr 26 20:00:08 2011 Change: Tue Apr 26 20:00:08 2011 crwxrwxrwx 1 root wheel - 0, 23 Apr 26 20:00 /dev/null [-- Attachment #3 --] I see no real difference between our results except that my /dev/null starts as 666 and comes back as 777 and yours is always 777. Again, I'm not clear on the meaning of this PR - I will abandon and move on. It does seem that the PR should be either clarified or closed On Apr 26, 2011, at 3:55 AM, Jason J. Hellenthal wrote: > > Robert, > > Sure this could be a good PR to verify but as the condition does not > exist on 8.2-STABLE as of today, I feel that you are just going to be > chasing a ghost in the machine. > > This does not say that it wasn't relevant back then but as of now it is. > The PR didn't specify any realness to what was seen as I can tell from > reading it over it just says it disappeared and there could be many > possible reasons for that happening that fall back to the user in the > chair. > > Attached is output from the script with a little more verbosity to show > its current status. > > If the same can still be reproduced on a recent -CURRENT system then > so-be-it but otherwise this can be closed. > > On Tue, Apr 26, 2011 at 02:50:10AM +0000, Robert Lorentz wrote: >> The following reply was made to PR kern/139014; it has been noted by GNATS. >> >> From: Robert Lorentz <robert.lorentz@gmail.com> >> To: bug-followup@FreeBSD.org, >> fluffy@FreeBSD.org >> Cc: >> Subject: Re: kern/139014: [null] /dev/null must be immunable to delete/unlink >> Date: Mon, 25 Apr 2011 22:19:47 -0400 >> >> I've just started poking around the PR's to try to learn and help out, = >> and this one looked like a good first try.. >> >> Sure enough, as root on 9.0 -CURRENT I can "rm /dev/null" and it does = >> unlink and is missing. However, I just recreate it with mknod /dev/null = >> c 0 6 .. the behavior is identical on 8.2-RELEASE. >> >> Am I missing something here? Is there some kind of new default behavior = >> that should be implemented here?=20= > > -- > > Regards, > Jason J. Hellenthal > > <test.txt><test.sh>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C6FACB82-CB49-4A82-9F58-6DE99AFB03B8>