Date: Sun, 7 Jun 1998 06:17:15 -0500 From: Zach Heilig <zach@gaffaneys.com> To: Sue Blake <sue@welearn.com.au>, Dima Dorfman <dima@zwb.net> Cc: freebsd-doc@FreeBSD.ORG Subject: Re: Handbook Modifications Message-ID: <19980607061715.A11774@gaffaneys.com> In-Reply-To: <19980607202326.18464@welearn.com.au>; from Sue Blake on Sun, Jun 07, 1998 at 08:23:26PM %2B1000 References: <199806070926.FAA05759@nwalme.pair.com> <19980607202326.18464@welearn.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 07, 1998 at 08:23:26PM +1000, Sue Blake wrote: > You've got me wondering about the idea that userconfig should be removed > from custom kernels. Is it advantageous enough to be a "shouldn't > normally" for everyone? I've rebuilt my kernel about a dozen times with > never a hitch and I still don't feel confident about being stuck with one > that can't be reconfigured in an emergency. Is this just the paranoia > that comes from a newbie's lack of confidence? There is an interesting pnp feature that goes along with userconfig (it's not very well documented). I wouldn't take it out, but instead have at least these lines in the kernel config: ... options USERCONFIG options USERCONFIG_BOOT ... and something like: USERCONFIG pnp 1 0 os enable irq0 10 drq0 1 drq1 5 port0 0x220 port1 0x330 port2 0x388 ... other userconfig commands ... quit in /kernel.config. Now, that particular PNP sound card will be initialized even after rebuilding a kernel (and forgetting to boot with '-c' to tell the kernel it needs to initialize that card). -- Zach Heilig -- zach@gaffaneys.com Real Programs don't use shared text. Otherwise, how can they use functions for scratch space after they are finished calling them? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980607061715.A11774>