Subject: Re: /etc/inittab (was: /etc/default )
To: None <current-users@NetBSD.ORG>
From: Greg A. Woods <firstname.lastname@example.org>
Date: 07/26/1995 16:55:54
[ On Tue, July 25, 1995 at 21:26:08 (-0700), Greg Earle wrote: ]
> Subject: Re: /etc/default
> Hey, let's make a change to the rc stuff ... cd to /etc/init.d ... move the
> original to a backup name ... create new one ... now go track down all the hard
> links in rc?.d to the original and rename them original_S##<something> ... now
> let's make new hard links to the new init.d script ... BLEAUGH
Whew! Did you get up on the wrong side of the bed?
Use "cp", not "mv", or better yet, "make" to invoke "install" from a
source tree where the master files are kept (and the make can make all
the links for you too).
It's only the traditional style of unix hacking that'll cause such
problems. Well thought out sys-admin procedures will easily avoid such
> Next somebody's gonna recommend something brilliant like the System V "init"
> use of a named pipe in /etc (/etc/initpipe) so we can have a named pipe in the
> filesystem and cause extremely common things that people do like "cd /etc ;
> grep <something> *" to get wedged ...
A named pipe is better than over-loading all the signals as they did in
SysVr2 and SysVr3, but of course as wise NetBSD systems programmers we
would put such a critter in /var/run (or /run, since it's gotta be there
right off the bat).
Greg A. Woods
+1 416 443-1734 VE3TCP robohack!woods
Planix, Inc. <email@example.com>; Secrets Of The Weird <firstname.lastname@example.org>