Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 4 Mar 1999 18:08:11 -0500 (EST)
From:      Chris <chrismar@readington.com>
To:        "Donald J . Maddox" <dmaddox@conterra.com>
Cc:        Jeff Ehrenkrantz <admin@Gccomm.Net>, "'freebsd-questions@freebsd.org'" <freebsd-questions@FreeBSD.ORG>
Subject:   Re: Boot -c   in 3.1-RELEASE
Message-ID:  <Pine.BSF.4.10.9903041805120.19478-100000@walnut.readington.com>
In-Reply-To: <19990304180507.B1316@dmaddox.conterra.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Phew...I thought I was going NUTS!

Anyways...I did try /boot/boot.conf and I got the same results as I did
with /boot/boot.config ... I will put the revelant lines in
/boot/loader.rc and see what happens on the next reboot.

I am using 3.1-Stable, btw, so that might be why /boot/boot.conf didn't
work either... :-\

Thanks!
Chris

On Thu, 4 Mar 1999, Donald J . Maddox wrote:

> Ok, you're crazy :-)
> 
> No, really, I made a typo in my reply...  I meant to write
> /boot/boot.conf, not /boot/boot.config, but I have found out
> since writing this that, at least in -current (not sure about
> 3.1R), the preferred file name is now /boot/loader.rc,
> although /boot/boot.conf will still work.
> 
> Sorry about that...
> 
> On Thu, Mar 04, 1999 at 04:40:52PM -0500, Chris wrote:
> > Call me crazy, but this doesn't seem to work.  I must have tried this 5
> > times last night and I still had to boot -c and enter everything by hand.
> > 
> > Chris
> > 
> > On Mon, 1 Mar 1999, Donald J . Maddox wrote:
> > 
> > > In aout systems, the 'dset' program was used to write configuration
> > > changes directly to the aout kernel image.  It doesn't work with ELF
> > > kernels.  A utility called 'kget' was recently added to the -current
> > > tree to do something similar for ELF kernels, but that doesn't help
> > > you much...
> > > 
> > > You need to create a /boot/boot.config file that contains at least
> > > these lines:
> > > 
> > > load kernel
> > > load -t userconfig_script /boot/kernel.conf
> > > 
> > > Then, you need to create a /boot/kernel.conf file that contains the
> > > commands that you would normally type at the config> prompt.
> > > 
> > > On Mon, Mar 01, 1999 at 06:52:32AM -0500, Jeff Ehrenkrantz wrote:
> > > > Hello All,
> > > >  I recently Installed 3.1 Release on a drive having the old boot blocks.
> > > > Thus it is necessary for me to do a "boot -c" to tweak an Ethernet isa
> > > > address.  Although the system does work after this tweak. The change does
> > > > not get stored. This system is a minimum hard drive/system install so I
> > > > don't have the space to compile a custom kernel at this point. Can someone
> > > > tell me why the changes don't get saved? & any chance I can binary edit the
> > > > Generic Kernel to take care of my prob. Or is there some other solution
> > > > available
> > > > Regards.... ..je
> > > > 
> > > > 
> > > > 
> > > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > > with "unsubscribe freebsd-questions" in the body of the message
> > > > 
> > > 
> > > 
> > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > with "unsubscribe freebsd-questions" in the body of the message
> > > 
> > 
> > 
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9903041805120.19478-100000>