Date: Mon, 10 Nov 1997 18:19:48 +1100 From: Bruce Evans <bde@zeta.org.au> To: dg@root.com, itojun@itojun.org Cc: bugs@FreeBSD.ORG, elh@svic.com, hackers@FreeBSD.ORG, toor@dyson.iquest.net Subject: Re: 2.2.5 installation bug on 1gig machines Message-ID: <199711100719.SAA04061@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>> The problem with this is that the memory is already sized before >>'userconfig' is called (it needs to be that way for various reasons). This >>... > Current userconfig menu in the kernel is very nice (I was surprised > when I saw this for the first time), but I believe it is > good to have some device configuration menu/option/whatever in /boot. > > (on bsdi we can disable devices that way. Also, /boot will look > for the default settings in /etc/boot.default. In this way > the settings can be kept the same over kernel reconfiguration) FreeBSD with `options USERCONFIG_BOOT' can now keep settings in the text file /kernel.config. The file is left in boot loader memory by the boot loader, copied to kernel memory in locore.s and sourced by the UserConfig CLI at UserConfig time. Unfortunately, this has the same problem with memory sizing as interactive UserConfig. It should be easy enough to run at least the CLI part of UserConfig earlier (as early as ddb would be more than sufficient). It mainly needs to avoid using malloc(). It uses malloc() mainly to store changes (dset can't use the active changed values since some changes may be unrelated to configuration). Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199711100719.SAA04061>