From owner-freebsd-alpha Mon Dec 7 10:26:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28093 for freebsd-alpha-outgoing; Mon, 7 Dec 1998 10:26:59 -0800 (PST) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from pacific.net (pacific.pacific.net [199.4.80.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28088 for ; Mon, 7 Dec 1998 10:26:58 -0800 (PST) (envelope-from ufkartfm@pacific.net) Received: from pacific.net (slime-lake.pacific.net [209.209.2.250]) by pacific.net (8.8.7/8.8.7) with ESMTP id KAA22512; Mon, 7 Dec 1998 10:26:51 -0800 (PST) Message-ID: <366BAD7B.3F2E22DD@pacific.net> Date: Mon, 07 Dec 1998 10:27:07 +0000 From: curtis Organization: Flying Snail Ranch X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: Dima Ruban CC: "freebsd-alpha@FreeBSD.ORG" Subject: Re: Multia - FreeBSD/axp - boot.conf References: <199812071445.GAA96384@burka.rdy.com> <366B8C9F.8E68566F@pacific.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dima and list, I misstated, Dima is correct, and thanks to him, I discovered a few things I had not seen before. In order to verify what Dima was saying, I first tried to delete the good kernel (so I could make sure it was booting kernel.old), but the 'permission' on kernel would not allow me to do this. I built a new kernel and tried to boot the old one using the method I described below and it failed. HOWEVER, I was able to use the boot floppy to get back into the system: >>>boot dva0 [no flags] # mount /dev/da0a / # swapon /dev/da0b # cd /usr/src/sys/alpha/conf # ifconfig de0 192.168.1.19 # ftp to the P2 'put' my kernel configuration, vi it, 'get' it, compile a new kernel, and boot it. So, there is a way, to get back one's system and, in conclusion, adding boot.conf, at this time, may not be a good idea. My apologies if I created some confusion and another THANKS to Dima for pointing this out. curtis wrote: > > 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 -- 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