Tech Insider					     Technology and Trends


		   Linux Activists Mailing List Archives

Newsgroups: comp.os.linux.announce,comp.os.linux
Path: sparky!uunet!mcsun!news.funet.fi!hydra!klaava!wirzeniu
From: ja...@purplet.demon.co.uk (Mike Jagdis)
Subject: ANNOUNCE: bootsys3.taz - Complete SYSV boot env with added bells : -)
Message-ID: <1993Jan12.000938.26615@klaava.Helsinki.FI>
Followup-To: comp.os.linux
Keywords: init, boot, xdm
Sender: wirze...@klaava.Helsinki.FI (Lars Wirzenius)
Organization: University of Helsinki
Date: Tue, 12 Jan 1993 00:09:38 GMT
Approved: linux-annou...@tc.cornell.edu (Lars Wirzenius)
Lines: 48

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

	bootsys3.taz

Release 3 of my complete SYSV-a-like boot environment and init.
This archive replaces bootsys.taz which, in turn, replaced sysvboot.taz.
Please delete all earlier archives :-).

What does it do?

  Get the archive and see the README and FEATURES files. Basically...

The programs and scripts in bootsys provide full control of your system
from the boot stage onwards. Swap space is initialised and attached, file
systems are checked and mounted, daemons are started etc. etc.

  The scripts used all take configuration information from easy to
understand files in /etc/default.

  The init supplied as part of the bootsys package is a SYSV compatible
version with some enhancements. Multiple run levels are supported and a
number are ready configured covering everything from single user mode to
an X windows workstation setup using xdm. Run levels may be named using
special entries in inittab (again useful examples are provided) and these
may be used as arguments on the Lilo boot command line or as arguments to
telinit. e.g. 'linux su' might boot Linux in to single user mode, 'linux X'
may boot Linux straight to an xdm login screen and 'telinit network' may
terminate X and xdm and leave Linux in text mode with all network daemons
active. Ctrl-alt-del is trapped to sync before reboot. Init provides periodic
syncing at configurable intervals rendering update unnecessary. Oh... Go read
the FEATURES file...

  Documentation and manual pages are provided, as is an easy install
script and source to init (as well as an executable of course).

  Binaries of the latest mount, umount and shutdown are provided in case
your current ones don't have the NFS support in them.

  Note that the scripts assume you have awk and a working ps. To protect
your sanity when using multiple kernels I recommend the procps package :-).

  Bootsys requires H.J. Lu's 4.2 release of libc.

Reward for reading this far <G>: I have patched ftpd and xdm to use the
shadow login routines. Shout if you want patches. I'll diff 'em up
sometime...

			Mike

Path: sparky!uunet!caen!batcomputer!theory.TC.Cornell.EDU!mdw
From: ja...@purplet.demon.co.uk (Mike Jagdis)
Newsgroups: comp.os.linux.announce
Subject: ANNOUNCE: bootsys4.tgz - SYSV init and boot environment
Date: 26 Mar 1993 22:26:08 GMT
Organization: Cornell Theory Center
Lines: 36
Approved: linux-annou...@tc.cornell.edu (Matt Welsh)
Message-ID: <1ovvu0$nc2@fitz.TC.Cornell.EDU>
NNTP-Posting-Host: theory.tc.cornell.edu
Keywords: bootsys4, SYSV init, startup
Originator: m...@theory.TC.Cornell.EDU

The long awaited upgrade to my bootsys package :-). Please delete bootsys3.taz.

Bootsys4.tgz is now available on nic.funet.fi, sunsite.unc.edu and
tsx-11.mit.edu.

Bootsys is a combination of a robust SYSV style init plus configuration
scripts which check and mount filesystems, configure TCP/IP, start service
daemons etc.

Bootsys init is a superset of SYSV init.

Bootsys init understands the 'auto' flag passed by LILO 0.9 on timeouts
and performs an unattended boot.

Bootsys init handles periodic syncs itself. Update isn't necessary. The
frequency of syncs may be changed by editing inittab.

Bootsys init catches ctrl-alt-del and syncs before rebooting.

Bootsys defines a number of run levels which may be named. From the LILO
boot prompt you can type 'linux su', 'linux multi', 'linux net', 'linux X'
etc. to bring the system up single user, multi user, networked and under
XDM respectively. You can easily change the names by editing inittab if
English isn't your native language :-).

Bootsys handles most, if not all, the details of boot time configuration.
All you need do is to edit small and simple files in /etc/default/...

Most (all?) of the bugs reported in bootsys3 are fixed.

				Mike

P.S. Bootsys4 *requires* lib 4.3.2 or higher.

-- 
Send submissions for comp.os.linux.announce to: linux-annou...@tc.cornell.edu

Path: gmd.de!ira.uka.de!yale.edu!spool.mu.edu!darwin.sura.net!
zaphod.mps.ohio-state.edu!malgudi.oar.net!caen!batcomputer!
theory.TC.Cornell.EDU!mdw
From: Mike Jagdis <ja...@purplet.demon.co.uk>
Newsgroups: comp.os.linux.announce
Subject: ANNOUNCE: bootsy4a.tgz - boot environment for Linux
Date: 2 Apr 1993 03:01:18 GMT
Organization: Cornell Theory Center
Lines: 27
Approved: linux-annou...@tc.cornell.edu (Matt Welsh)
Message-ID: <1pga9u$1q8@fitz.TC.Cornell.EDU>
NNTP-Posting-Host: theory.tc.cornell.edu
Keywords: bootsys4, system V init, bootup
Originator: m...@theory.TC.Cornell.EDU

bootsy4a.tgz replaces bootsys4.tgz. Please delete bootsys4.tgz. Sorry guys!

bootsy4z.tgz is bootsys4.tgz with the missing executables included and
the mount problem in the filesys script fixed.

Yes, the included mount is Rick's 99.6 release which you need for libc 4.3.3.

If you already have bootsys4.tgz there is no real need to download this.
The fix to the /etc/init.d/filesys script is simply to replace the line
that says:

	mount -t $3 $1 $2 $4

with the lines:

	if [ -z "$4" ]; then
		mount -t $3 $1 $2
	else
		mount -t $3 $1 $2 -o $4
	fi

and all should be well.

                            Mike

-- 
Send submissions for comp.os.linux.announce to: linux-annou...@tc.cornell.edu

			        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 v 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/