Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83 (MC840302); site boring.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!harpo!decvax!linus!philabs!cmcl2!seismo!mcvax!boring!jack
From: jack@boring.UUCP
Newsgroups: net.unix-wizards
Subject: Re: Rebooting 4.2BSD on a 780
Message-ID: <6472@boring.UUCP>
Date: Fri, 21-Jun-85 19:14:58 EDT
Article-I.D.: boring.6472
Posted: Fri Jun 21 19:14:58 1985
Date-Received: Mon, 24-Jun-85 04:39:49 EDT
References: <11030@brl-tgr.ARPA> <412@mtxinu.UUCP> <332@basser.oz> <2331@mordor.UUCP>
Reply-To: jack@boring.UUCP (Jack Jansen)
Organization: CWI, Amsterdam
Lines: 15
Apparently-To: rnews@mcvax.LOCAL

In article <2331@mordor.UUCP> jdb@mordor.UUCP (John Bruner) writes
about his /boot, that, among other things, puts the name of the
kernel it booted into a string in that kernel.

In my opinion, this *can* be used on 4.2 *without* modifying
every program that reads /vmunix. Just run a program during
an early phase of startup that grabs the kernel name from /dev/kmem,
and have it setup a symbolic link in /vmunix.......

(Of course, /boot should default boot from, for instance, real-vmunix,
and not vmunix. Unless you want to build symbolic links into /boot.....)

-- 
	Jack Jansen, jack@mcvax.UUCP
	The shell is my oyster.