Tech Insider					     Technology and Trends


			      USENET Archives

Newsgroups: comp.os.linux.announce
Path: gmd.de!xlink.net!fauern!zib-berlin.de!netmbx.de!Germany.EU.net!
EU.net!uknet!warwick!zaphod.crihan.fr!jussieu.fr!univ-lyon1.fr!
ghost.dsi.unimi.it!batcomputer!cornell!bounce-bounce
From: ja...@purplet.demon.co.uk (Mike Jagdis)
Subject: Bootsys-5
Message-ID: <1994Mar17.191212.18812@cs.cornell.edu>
Followup-To: comp.os.linux.misc
Keywords: bootsys5, init, booting, runlevel
Sender: m...@cs.cornell.edu (Matt Welsh)
Reply-To: ja...@purplet.demon.co.uk (Mike Jagdis)
Organization: None
Date: Thu, 17 Mar 1994 19:12:12 GMT
Approved: linux-annou...@tc.cornell.edu (Matt Welsh)
Lines: 62

Uploaded to sunsite.unc.edu, tsx-11.mit.edu and funet.hut.fi

Bootsys-5 replaces the old, aged and decaying bootsys-4a.

Bootsys-5 is a (more or less) complete true SYSV boot and runlevel
environment.

The included init understands both bdflush and update and knows how to
fall back if bdflush isn't supported by the running kernel. Any SYSV
init should work but how would I know? :-)

The bootsys environment is designed to allow packages to easily install
boot time check scripts and daemon management scripts. It is specifically
designed for The Purple Distribution of Linux available in the UK BBS
community but not necessarily elsewhere except by chance. This is basically
ripped out of The Purple Distribution. The INSTALL script may be dodgy
since it is *not* the normal way this is installed.

Bootsys takes a policy of never requiring naive users to edit system
critical shell scripts. Configuration information is held in simple
and relatively loose format file in /etc/default. Many of these may
be edited using shell scripts rather than directly with vi. Such
scripts are installed in /etc/config.

Bootsys is modules ready. It understands what to do with load=... and
noload=... passed on the LILO boot line, plus it keeps a table of
selected modules in /etc/default/modules. Not a lot of the kernel
is modular yet though :-).

Bootsys has been around a long while. However this version should almost
certainly not be used with any kernel earlier than 0.99pl15. In particular
the network interface setup script assumes you are using the newest
version of route...

                   Mike


Title        = SYSV style system boot and run level management
Version      = 0.5
Desc1        = Flexible boot environment. Policy of simple configuration
Desc2        = files - naive users should never edit critical shell scripts.
Desc3        = Init has built in support for update and bdflush - with auto
Desc4        = fallback if kernel doesn't support bdflush. Boot time kernel
Desc5        = module loading. Designed for easy package management.
Author       = Mike Jagdis
AuthorEmail  = ja...@purplet.demon.co.uk
Required1    = awk, cat, chmod, chown, grep, rm, tr, others...
Required2    = libc.so.4.5.21
Required3    =
Required4    =
CopyPolicy1  = Do it. Send fixes/enhancements. Send beer. Send money.
CopyPolicy2  = Send women. Send CDs. Whatever. Just leave my name in there.
Keywords     = boot, init, script, runlevel, module, package, system
Comment1     = This is pulled straight from The Purple Distribution where
Comment2     = it has worked for years. This, however, may be incomplete
Comment3     = or simply broken. I can't predict every setup so you probably
Comment4     = need to know what you are doing to install this initially.
Entered      = 15MAR1994
EnteredBy    = Mike Jagdis
CheckedEmail = ja...@purple.demon.co.uk
End

			        About USENET

USENET (Users’ Network) was a bulletin board shared among many computer
systems around the world. USENET was a logical network, sitting on top
of several physical networks, among them UUCP, BLICN, BERKNET, X.25, and
the ARPANET. Sites on USENET included many universities, private companies
and research organizations. See USENET Archives.

		       SCO Files Lawsuit Against IBM

March 7, 2003 - The SCO Group filed legal action against IBM in the State 
Court of Utah for trade secrets misappropriation, tortious interference, 
unfair competition and breach of contract. The complaint alleges that IBM 
made concentrated efforts to improperly destroy the economic value of 
UNIX, particularly UNIX on Intel, to benefit IBM's Linux services 
business. See SCO vs IBM.

The materials and information included in this website may only be used
for purposes such as criticism, review, private study, scholarship, or
research.

Electronic mail:			       WorldWideWeb:
   tech-insider@outlook.com			  http://tech-insider.org/