hacking init - (nf)

Mon Apr 2 22:06:44 AEST 1984

#R:amd70:-448100:fortune:26900036:000:640
fortune!rpw3    Apr  2 02:51:00 1984

The simplest way I know of to test a new "init" without your filesystem
disappearing down the rabbit hole in case said "init" is broken, is:

	Make a corresponding test kernel, for which the hardwired code
	(which exec's "/etc/init") instead exec's "/etc/init.test". Call
	this kernel "/unix.test.init" (or something). Boot it. If it dies
	a horrible death (probably in "init.test"), re-boot "/unix" and
	breath a sigh of relief!

Is that what you wanted to know?

Rob Warnock

UUCP:	{ihnp4,ucbvax!amd70,hpda,harpo,sri-unix,allegra}!fortune!rpw3
DDD:	(415)595-8444
USPS:	Fortune Systems Corp, 101 Twin Dolphin Drive, Redwood City, CA 94065