Xref: utzoo comp.unix.questions:9465 comp.bugs.4bsd:1030 Path: utzoo!attcan!uunet!mcvax!enea!dkuug!freja!kimcm From: kimcm@freja.dk (Kim Christian Madsen) Newsgroups: comp.unix.questions,comp.bugs.4bsd Subject: Re^2: more unix jokes - /dev/null Keywords: poor man's Unix Message-ID: <4095@freja.dk> Date: 27 Sep 88 15:39:47 GMT References: <8488@smoke.ARPA> <26090@ucbvax.BERKELEY.EDU> <1049@sybase.sybase.com> <1414@star.cs.vu.nl> <4092@freja.dk> Organization: DIKU, U of Copenhagen, DK Lines: 16 Ahh one of the funny things that can happen when you accidentially lose your /dev/null, is that a lot of programs write a lot of garbage to /dev/null, and a lot of these programs are run with root priviledges (from cron) and therefore will generate (sooner or later) the plain file /dev/null. Now what is the dangerous thing about that you can always remove the file, and reinstall the null-driver, can't you? Well, depends on how fast you react -- If you're too slow the garbage from the file /dev/null has been copied to numerous other files, that were expected to be emptied...... Sincerely Kim Chr. Madsen