From owner-freebsd-hackers Wed Jan 7 14:36:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA19474 for hackers-outgoing; Wed, 7 Jan 1998 14:36:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA18979 for ; Wed, 7 Jan 1998 14:30:30 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA01704; Wed, 7 Jan 1998 14:29:29 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd001700; Wed Jan 7 14:29:22 1998 Message-ID: <34B4010D.31DFF4F5@whistle.com> Date: Wed, 07 Jan 1998 14:26:21 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: "Jin Guojun (ITG staff)" CC: freebsd-hackers@FreeBSD.ORG, pjchilds@imforei.apana.org.au Subject: Re: suggestion on using boot.config References: <199801071632.IAA09184@george.lbl.gov> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk 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?