From owner-freebsd-hackers Mon Dec 15 20:44:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA21358 for hackers-outgoing; Mon, 15 Dec 1997 20:44:18 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from george.lbl.gov (george-2.lbl.gov [131.243.2.12]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA21343 for ; Mon, 15 Dec 1997 20:44:09 -0800 (PST) (envelope-from jin@george.lbl.gov) Received: (from jin@localhost) by george.lbl.gov (8.8.8/LBL-ITG) id UAA16864 for hackers@freebsd.org; Mon, 15 Dec 1997 20:44:08 -0800 (PST) Date: Mon, 15 Dec 1997 20:44:08 -0800 (PST) From: Jin Guojun (ITG staff) Message-Id: <199712160444.UAA16864@george.lbl.gov> To: hackers@freebsd.org Subject: suggestion on using boot.config Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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); The reason for this change is just for remote development. This will avoid bad kernel/driver keep looping on panic during the development. For example, # more /boot.config /kernel.newdrv # ll /k* -rwxr-xr-x 1 root wheel 1282582 Dec 12 18:11 /kernel* -rwxr-xr-x 1 root wheel 1457189 Dec 12 09:43 /kernel.GENERIC* -rwxr-xr-x 1 root wheel 1507955 Dec 15 19:42 /kernel.newdrv* -rw-r--r-- 1 root wheel 0 Dec 12 09:43 /kernel.config This boot.config will boot system to /kernel.newdrv. If /kernel.newdrv is bad and there is no one near the machine, currently, the machine will never boot up. If /boot.config can be renamed in boot.c and maybe changed back after successfully booting, it will be panic on /kernel.newdrv and automatically boot to /kernel on the second time; so thing can keep going. Any Pro/Con? -Jin P.S. Please CC to me when reply. Thanks.