Date: Mon, 15 Dec 1997 20:44:08 -0800 (PST) From: Jin Guojun (ITG staff) <jin@george.lbl.gov> To: hackers@freebsd.org Subject: suggestion on using boot.config Message-ID: <199712160444.UAA16864@george.lbl.gov>
next in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712160444.UAA16864>