Date: Wed, 24 Jul 2002 21:56:40 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: tlambert2@mindspring.com Cc: doconnor@gsoft.com.au, matusita@jp.FreeBSD.org, ru@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: cvs commit: src/release/i386 drivers.conf Message-ID: <20020724.215640.26964830.imp@bsdimp.com> In-Reply-To: <3D3F7373.329CE5EF@mindspring.com> References: <3D3F5F40.AC5A33EF@mindspring.com> <1027563817.5847.15.camel@chowder.gsoft.com.au> <3D3F7373.329CE5EF@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <3D3F7373.329CE5EF@mindspring.com>
Terry Lambert <tlambert2@mindspring.com> writes:
: Daniel O'Connor wrote:
: > On Thu, 2002-07-25 at 11:45, Terry Lambert wrote:
: > > Anything in the boot path needs to be static, by definition,
: > > or you face the Catch-22 of needing to load the driver in
: > > order to be able to load the driver.
: >
: > Uhh, not really.
: > If your BIOS supports it (which it must for you to boot off it) then the
: > loader can load any extra modules you need.
: >
: > If your argument was true then the kernel would need to load itself :)
:
: Think "CDROM install".
Dude, what crack are you smoking? How many times to we have to tell
you. We have a boot loader that knows how to read the kernel from the
cdrom or scsi or whatever. IT is a tiny increment to also load
additional modules at that time that support those devices. What's
the real issue?
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020724.215640.26964830.imp>