Path: utzoo!utgpu!watserv1!watmath!att!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!wuarchive!uunet!virtech!cpcahil
From: cpcahil@virtech.uucp (Conor P. Cahill)
Newsgroups: comp.unix.internals
Subject: Re: Waaah! My bit bucket is missing...
Message-ID: <1990Nov26.135532.24319@virtech.uucp>
Date: 26 Nov 90 13:55:32 GMT
References: <1YX6d1#4Tp8f44pkCfd9Ls4PT1wjkW3=eric@snark.thyrsus.com>
Reply-To: cpcahil@virtech.UUCP (Conor P. Cahill)
Organization: Virtual Technologies Inc., Sterling VA
Lines: 20

First off, if you want help, don't include the following line:

> Followup-To: poster

It confuses some admittedly broken news reading software and may make
someone decide that they don't want to go throught the trouble to help you.

In article <1YX6d1#4Tp8f44pkCfd9Ls4PT1wjkW3=eric@snark.thyrsus.com> eric@snark.thyrsus.com (Eric S. Raymond) writes:
>A silly thing happened today. Something nuked my /dev/null device. I know
>how to use mknod all right, but I cannot seem to find the spec for /dev/null
>anywhere in the conf files. I'm using AT&T System V Release 3.2.

For system V, the norm is that /dev/null has the same major device
number as /dev/mem and /dev/kmem but has the minor device number of 2.


-- 
Conor P. Cahill            (703)430-9247        Virtual Technologies, Inc.,
uunet!virtech!cpcahil                           46030 Manekin Plaza, Suite 160
                                                Sterling, VA 22170