Date: Thu, 24 Sep 1998 15:28:47 -0700 From: David Greenman <dg@root.com> To: Nathan Dorfman <nathan@rtfm.net> Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: /dev/null breakage in 2.2.7 Message-ID: <199809242228.PAA16207@implode.root.com> In-Reply-To: Your message of "Thu, 24 Sep 1998 15:14:59 EDT." <19980924151459.A14371@binary.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>in 2.2.7-S (shortly past 2.2.7-R), reading /dev/null begins producing the >output of this cron job: > >*/10 * * * * root /home/nathan/pop3ck mail xxxxxxxxxx@alphame.com 3 > /dev/null 2>&1 > >nathan@shell.fcc.net:~% cat /dev/null >Connecting to xxx.xxx.xxx.xxx...connected. >Read +OK. > >Writing nothing to /dev/null makes it work right again: > >shell# cat > /dev/null >shell# cat /dev/null >shell# > >Then, > >shell# echo foo > /dev/null >shell# cat /dev/null >foo >shell# > >Is my bit bucket overflowing? :-P is this known/fixed in a newer -STABLE? It looks like someone/something removed /dev/null and it has become a regular file. You can fix this with "cd /dev; ./MAKEDEV std". -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809242228.PAA16207>