From owner-freebsd-bugs Thu Sep 24 15:28:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00106 for freebsd-bugs-outgoing; Thu, 24 Sep 1998 15:28:10 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29989 for ; Thu, 24 Sep 1998 15:28:04 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id PAA16207; Thu, 24 Sep 1998 15:28:47 -0700 (PDT) Message-Id: <199809242228.PAA16207@implode.root.com> To: Nathan Dorfman cc: freebsd-bugs@FreeBSD.ORG Subject: Re: /dev/null breakage in 2.2.7 In-reply-to: Your message of "Thu, 24 Sep 1998 15:14:59 EDT." <19980924151459.A14371@binary.net> From: David Greenman Reply-To: dg@root.com Date: Thu, 24 Sep 1998 15:28:47 -0700 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >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