Date: Sat, 27 Jul 2002 14:58:14 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Peter Wemm <peter@wemm.org> Cc: "M. Warner Losh" <imp@bsdimp.com>, 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: <3D431776.C869FD9@mindspring.com> References: <20020727202333.9AC512A7D6@canning.wemm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Wemm wrote: > > 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. Doesn't this require newer hardware/BIOS/firmware than most equipment has these days? I'm pretty sure that my ASUS box with a Toshiba 3401B won't boot from one of these, except on my really old AHA1742, which can't tell it's not just another hard drive... Is this going to be the default for distribution, or is the "fake floppy" boot CDROM still going to be "disc #1"? -- 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?3D431776.C869FD9>