Date: Wed, 24 Jul 2002 21:31:25 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: "M. Warner Losh" <imp@bsdimp.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: <3D3F7F1D.DB9576B2@mindspring.com> References: <3D3F5F40.AC5A33EF@mindspring.com> <1027563817.5847.15.camel@chowder.gsoft.com.au> <3D3F7373.329CE5EF@mindspring.com> <20020724.215640.26964830.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"M. Warner Losh" wrote: > : 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? So, given that the install from a CDROM boots from a floppy image that's faked up by the CDROM drive BIOS, and the image doesn't include the full boot loader, how exactly is it that the partial boot loader code acts like the full bootloader code for accessing the CDROM to load the modules necessary to access the CDROM? Yes, the suggestion is a good one for a kernel booted from a full loader installed from the hard drive. It's not so good if the modules are either going to be linked into the kernel, or in the MFS image -- linked into the kernel. Make sense now? 8-). -- Terry 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?3D3F7F1D.DB9576B2>