Date: Mon, 07 Dec 1998 08:06:55 +0000 From: curtis <ufkartfm@pacific.net> To: dima@best.net Cc: "freebsd-alpha@FreeBSD.ORG" <freebsd-alpha@FreeBSD.ORG> Subject: Re: Multia - FreeBSD/axp - boot.conf Message-ID: <366B8C9F.8E68566F@pacific.net> References: <199812071445.GAA96384@burka.rdy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Dima,
(smile) not necessarily 'screwed' - One can:
boot dka0 -file kernel.old
and enter (^D) control D at the prompt to get back the previous kernel
allowing one to telnet to back to the 'target' machine and make correct-
ions as necessary.
In my case, before I build a new kernel, I copy the 'working kernel' to
another file name - (smile) just in case my new kerenl breaks something
and can boot it, using the above method.
good luck and have fun, curtis
Dima Ruban wrote:
>
> curtis writes:
> > I found that putting boot.conf in /boot (on the Multia) will speed up
> > the hard disk boot process and eliminates having to press enter or wait
> > for a countdown. (smile - in other words, it saves an extra step)
> >
> > multia# pwd
> > /boot
> > multia# ls -l boot.conf
> > -rw-r--r-- 1 root wheel 20 Dec 7 14:22 boot.conf
> > multia# cat boot.conf
> > @load /kernel
> > @boot
>
> The problem with config like this is: if somehow you break /kernel -
> you screwed. You won't be able to anything. System will try to load
> your broken kernel no matter what.
--
curtis - ufkartfm@pacific.net - site administrator for Nobody
I want Nobody to control my life! How about you?
http://www.netvideo.com/nobody
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?366B8C9F.8E68566F>