Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site mtxinu.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!umcp-cs!gymble!lll-crg!dual!unisoft!mtxinu!ed
From: ed@mtxinu.UUCP (Ed Gould)
Newsgroups: net.unix-wizards
Subject: Re: Rebooting 4.2BSD on a 780
Message-ID: <412@mtxinu.UUCP>
Date: Mon, 17-Jun-85 20:07:05 EDT
Article-I.D.: mtxinu.412
Posted: Mon Jun 17 20:07:05 1985
Date-Received: Sun, 23-Jun-85 10:26:17 EDT
References: <11030@brl-tgr.ARPA>
Reply-To: ed@mtxinu.UUCP (Ed Gould)
Organization: mt Xinu, Berkeley, CA
Lines: 18

In article <11030@brl-tgr.ARPA> droms@PURDUE.ARPA (Ralph E Droms) writes:
>Is it possible to use /etc/reboot (4.2BSD) to cause a 780 to load a kernel
>from a file other than /vmunix?

Nope, not without hacking, anyway.  The string "xx(0,0)vmunix" is compiled
into the boot program (which is loaded off the floppy on a 780 by
defboo.cmd).  The "xx" is replaced by the right drive-type
code based on flags in registers.  See ???boo.cmd for details.

It should be possible to hack boot and the kernel to pass the right
flags along to boot so that something else could be done, but that
probably won't work either.  Many programs (e.g., ps, w) use the
namelist in /vmunix to find things in the kernel's memory.  They
won't know about your alternate kernel.

-- 
Ed Gould		    mt Xinu, 2910 Seventh St., Berkeley, CA  94710  USA
{ucbvax,decvax}!mtxinu!ed   +1 415 644 0146