<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
Greetings,<br><br>I'm just floating this for comment/consideration....ie; I don't think <br>it's fodder for the upcoming CLFS - 1.1.0 release...<br><br><br>It has occurred to me for some time, that this section on making<br>the new system bootable, is slowly being relegate in time, if for<br>no other reason that the actual floppy-drive hardware being<br>surely deprecated and made redundant...ie; this (and many other)<br>new motherboard(s) don't even have an FDC incorporate at all.<br><br>The option of creating a boot floppy will, quite obviously, still be<br>valid for many of folks out there reading the xLFS books, but <br>equally more and more people will be attempting these books<br>and procedures with no floppy drive unit at all...<br><br>So....presently (in CBLFS) we have this whole passage ;<br><br>----<br><br>Your shiny new CLFS system is almost complete. One of the last
things to do is to ensure that the system can be properly booted. The
instructions below apply only to computers of IA-32 architecture,
meaning mainstream PCs. Information on “<span class="quote">boot loading</span>” for
other architectures should be available in the usual resource-specific
locations for those architectures.Boot loading can be a complex area, so a few cautionary words
are in order. Be familiar with the current boot loader and any other
operating systems present on the hard drive(s) that need to be bootable.
Make sure that an emergency boot disk is ready to “<span class="quote">rescue</span>”
the computer if the computer becomes unusable (un-bootable).<BR>Earlier, we compiled and installed the GRUB boot loader software
in preparation for this step. The procedure involves writing some special
GRUB files to specific locations on the hard drive. We highly recommend
creating a GRUB boot floppy diskette as a backup. Insert a blank floppy
diskette and run the following commands:<br><BR>----<br><BR><br>First off the rank, if we're going to say 'apply only to computers of IA-32 architecture,
meaning mainstream PCs' ,<br>we might mean 'computers of IA-32/64 architecture, meaning mainstream PCs' that still have a floppy drive'...<br><br>Quote - ' Make sure that an emergency boot disk is ready to “<span class="quote">rescue</span>”
the computer if the computer becomes unusable (un-bootable)' .....this is the boot floppy we're about to create? What if one can't do this?....<br><br><br>My current thinking goes like this ;<br><br>If you have a floppy drive, then.....(see existing text)...<br><br>If your computer doesn't have a floppy drive, then.....(fill_in_the_blanks ;-)<br><br><br>Has anyone given this any thought (yet)? The only (hopefully consistent)<br>path I can think of, is to include "rescue" or emergency boot capabilities<br>as part of a CLFS live/boot cd. Then it would be easy to go about the above<br>fill_in_those_blanks by including text regarding downloading the live-cd<br>image, and what command (boot args) to issue at the boot_prompt to have<br>it act as a rescue/emergency boot disk for the newly created system -- for <br>that matter, one wouldn't even need to make the new system bootable at <br>all right at this juncture - one could indeed test the new system out before <br>commiting to a write of MBR.....<br><br>Anyhow....it's floated....any thoughts?<br><br><br>Regards,<br><br>Don <br><br /><hr />Enter today! <a href='http://www.livelife.ninemsn.com.au/compIntro.aspx?compId=4602' target='_new'>Win a Hotmail Go-Kart to race at Bathurst.</a></body>
</html>