Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!sol.ctr.columbia.edu!ira.uka.de!math.fu-berlin.de!unidui!Germany.EU.net!mcsun!chsun!hslrswi!aut!nbladt From: nbladt@autelca.ascom.ch (Norbert Bladt) Subject: Re: /boot (was: Re: [386BSD] GCC 2.3.1 and kernel) Message-ID: <1992Nov18.074728.2241@autelca.ascom.ch> Keywords: 386BSD GCC kernel Organization: Ascom Autelca AG, Guemligen, Switzerland References: <1992Nov11.141408.167@dde.dk> <1992Nov16.131930.3414@prism.poly.edu> <1e8ob8INNh76@Germany.EU.net> Date: Wed, 18 Nov 1992 07:47:28 GMT Lines: 30 bs@qwerty.Germany.EU.net (Bernard Steiner) writes: >In article <1992Nov16.131930.3414@prism.poly.edu>, kapela@prism.poly.edu (Theodore S. Kapela) writes: >|> This way, if you have problems with the old >|> kernel, you can just hit a key (okay, maybe you need to do it a few times) >|> to get the bootstrap loader to look for alternate kernels. >...wich, of course, raises the question what on earth happened to good old >in-filesystem /boot that you would hit return at or give the device, partition >and filesystem name of your kernel to run. >Is it some sort of superset of wdboot/bootwd or is that parentage disclaimed ? I am using the new boot-blocks from Julian and with those it is possible to select (read: type in) any file to boot, at least in the root directory and even choose the drive (wd or sd). That might be the answer ! Norbert. PS. I know that it works, I had to do it a few days ago, to boot an old kernel because the serial drivers from cgd did hang my system and I want to test the serial ports with the old kernel. It is always a good idea to SAVE the old, working, kernel before moving the new one on top of it. -- Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland Phone: +41 31 999 65 52 FAX: +41 31 999 65 44 Mail: nbladt@autelca.ascom.ch UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt