From owner-freebsd-questions Mon Jul 16 10: 2:57 2001 Delivered-To: freebsd-questions@freebsd.org Received: from ren.sasknow.com (ren.sasknow.com [207.195.92.131]) by hub.freebsd.org (Postfix) with ESMTP id 8EE4F37B403 for ; Mon, 16 Jul 2001 10:02:47 -0700 (PDT) (envelope-from ryan@sasknow.com) Received: from localhost (ryan@localhost) by ren.sasknow.com (8.9.3/8.9.3) with ESMTP id LAA44104; Mon, 16 Jul 2001 11:02:32 -0600 (CST) (envelope-from ryan@sasknow.com) Date: Mon, 16 Jul 2001 11:02:32 -0600 (CST) From: Ryan Thompson To: Klaus Steden Cc: Child , questions@FreeBSD.ORG Subject: Re: deleted /dev/null by mistake In-Reply-To: <20010715232550.J73359@cthulu.compt.com> Message-ID: Organization: SaskNow Technologies [www.sasknow.com] MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Klaus Steden wrote to Child: > > hi all > > one of my shell scripts did an rm -f /dev/null > > > (cd /dev && sh MAKEDEV) should do it (as root), > > or by hand ... > > mknod /dev/null c 2 2 > Remember to remove (rm) /dev/null immediately (i.e., in the same command) before you do that if you are doing this in multi-user mode, because, on most servers, stuff gets sent to /dev/null all the time, and if it was deleted, you'll have a regular file with a bunch of junk in it, and mknod won't attempt to unlink it before creating the new device node. - Ryan > Klaus > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > -- Ryan Thompson Network Administrator, Accounts SaskNow Technologies - http://www.sasknow.com #106-380 3120 8th St E - Saskatoon, SK - S7H 0W2 Tel: 306-664-3600 Fax: 306-664-1161 Saskatoon Toll-Free: 877-727-5669 (877-SASKNOW) North America To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message