Date: Wed, 07 Jan 1998 14:26:21 -0800 From: Julian Elischer <julian@whistle.com> To: "Jin Guojun (ITG staff)" <jin@george.lbl.gov> Cc: freebsd-hackers@FreeBSD.ORG, pjchilds@imforei.apana.org.au Subject: Re: suggestion on using boot.config Message-ID: <34B4010D.31DFF4F5@whistle.com> References: <199801071632.IAA09184@george.lbl.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
Jin Guojun (ITG staff) wrote: > > } In article <199712160444.UAA16864@george.lbl.gov> you wrote: > } > I do not know if this is a good place to address this issue. > } > } > For remote development, I would like to modified "boot.c" to rename > } > "/boot.config" to either "/boot.config.run" or "/boot.config.last" > } > after readfile("boot.config", boot_config, BOOT_CONFIG_SIZE); > } > } Hmm... doesn't "nextboot" do what you want? > } > } (I've only read the man page on it so don't shoot me if it doesn't) > } > } Peter > > Nop. It doesn't matter what I put in the nextboot strings, it just boots > from the default /kernel. According to the man page: > > nextboot -b /dev/rwd0 1:sd(0,a)/kernel.experimental wd(0,a)/kernel.old > > I changed it to : > > nextboot -b /dev/rwd0 1:wd(0,a)/kernel.test wd(0,a)/kernel > > Nothing happenes. > > -Jin well did you 1/ make sure you are not 'dangerously dedicated" 2/ recomopile and install the bootblocks with that option turned on?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?34B4010D.31DFF4F5>