Init - SCO Xenix System V replacement

Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!killer!rpp386!jfh
From: j...@rpp386.Dallas.TX.US (John F. Haugh II)
Newsgroups: alt.sources
Subject: Init - SCO Xenix System V replacement
Summary: beta test release of UNIX(tm) System V clone for SCO Xenix
Message-ID: <13858@rpp386.Dallas.TX.US>
Date: 22 Mar 89 14:28:06 GMT
Reply-To: j...@rpp386.Dallas.TX.US (John F. Haugh II)
Distribution: usa
Organization: River Parishes Programming, Dallas TX
Lines: 1147

This is the beta test release of the init I've been munging on.
It is currently being used on this site with some results.  It
is not complete and does not contain a telinit.  You have to
send it various signals to get things to happen ...

So far it seems to work.

Caveats -
	- no telinit yet
	- still flaky as a pie crust
	- only tested on Xenix/386 2.2.1
	- syscon and systty aren't implemented yet

Debugging an init is EXTREMELY troublesome.  If you are unable
to reboot frequently and from a floppy, I would not suggest
getting involved just yet.  This init is easier to debug in a
production setting than the real McCoy as this version can be
restarted without rebooting the system.  Nice trick.

How to use this beasty -

Create your /etc/inittab just like normal.  You need to have
some experience with inittabs.  Here is mine as a starter:
--
id:S:initdefault:
rc:Ss2:wait:/etc/rc < /dev/console > /dev/console 2>&1
co:Ss:wait:/bin/su - root < /dev/console > /dev/console 2>&1
01:2:respawn:/etc/getty tty01 m	# Screen 1
02:2:respawn:/etc/getty tty02 m	# Screen 2
03:2:respawn:/etc/getty tty03 m	# Screen 3
d1:2:respawn:/etc/getty tty1A v	# Anchor Automation Modem
d2:2:respawn:/etc/getty tty2A v	# Everex Modem
--

Create a new /etc/rc file.  The old one is probably kinda
useless if you are running SCO Xenix.  It doesn't know about
being called in single user mode.

Save your old init someplace handy and make and install
this version.

Reboot.  You will now be in single user mode.

To change run levels, signal init with SIGUSR1 [ signal
16 ] and you will be prompted on the console for a new
run level.  Enter the new runlevel at the prompt.

To restart init, signal init with SIGUSR2 [ signal 17 ]
and init will kill all active processes and re-exec
itself.  This is very useful for replacing init without
rebooting.

To re-read the inittab, send init a signal 1, 2, or 3.

You might want to read the config.h file.  There are only
a few options at this stage of the game.

If you aren't completely frightened, or REALLY DESPARATELY
need a real init, complete with source code, unwrap this
sucker and get on with the show ...

WARNING - SCREWING WITH INIT CAN GET YOUR MACHINE REAL
UNUSABLE REAL FAST.  ALWAYS ALWAYS ALWAYS make plenty of
backups and sacrifice virgins to the computer gods before
screwing with this.  Don't say I didn't warn you.

THIS POSTING COPYRIGHT, 1989, JOHN F. HAUGH II
ALL RIGHTS RESERVED.

Use and redistribution in a USENET-like manner permitted,
all other uses prohibited.
--
Code
-- 
John F. Haugh II                        +-Quote of the Week:-------------------
VoiceNet: (214) 250-3311   Data: -6272  | "Do not drink and bake"
InterNet: j...@rpp386.Dallas.TX.US       |         -- Arnold Swartzenegger
UucpNet : <backbone>!killer!rpp386!jfh  +--------------------------------------