Terry Lambert wrote:
> "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?

Not true anymore.  release/i386/mkisoimages.sh:
        bootable="-b boot/cdboot -no-emul-boot"
-r-xr-xr-x  1 root  wheel  1136 Jul  5 02:20 /boot/cdboot*
I believe we still use the old way on RELENG_4, but the support all got
MFC'ed.  Several release candidates used cdboot for better testing exposure.

"All of this is for nothing if we don't go to the stars" - JMS/B5

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to