[br_exp_karlheg_markv] Ready for review prior to trunk merge.

[karlheg@bittersweet.inetarena.com (Karl M. Hegbloom)]

 I'm done, I think.  I would like yous to pull out a copy and have a
 look to see if you like what I've done with it, and let me know if
 you would like me to merge that into the trunk.

 Run a normal CVS checkout of `boot-floppies', then:

  cd boot-floppies/utilities/dbootstrap
  cvs update -r br_exp_karlheg_markv

 and also...

  cd boot-floppies/scripts/rescue
  cvs update -r br_exp_karlheg_markv install.sh

 Then build it and try it out, let me know what you think.


 Changes are:

  `lilo.conf' is much expanded.

  The tzconfig dialog is switched to have the directories on the left
  and the files on the right.

  mount_partition uses a menu and/or a fill-in.

  There's a message prior to partitioning telling of the BIOS 1024
  cylinder limitation on systems that do not support CHS translation
  or LBA.  It gives a brief recommended partititioning strategy.

  I brought back the question about Linux 2.0 compatibility, unless
  quiet.  I wish I'd never mentioned it and started the debate and
  gotten it changed.  I'd rather be asked than never see the question.

  When you mount a partition called "/boot" (aka "/target/boot",
  internally), then when you go to install Lilo, it offers a menu of
  choices as to where to install the Lilo boot block.  You can put it
  in the "/boot" device, the "/", device or on the MBR.

  After you install the MBR, there's a nice message explaining about
  its features, with a reference to the fine manual.

   For this I started to make libfdisk keep a record in the partition
   structure of the start and end cylinder of partitions.  I will
   bring that in for woody, perhaps, unless I have more time this week
   than I anticipate.  It always returns numbers < 1024 on my machine
   because the bios is set for "Large" disks, meaning it has CHS
   translation turned on.  I think that means it would boot any
   partition on the drive.  In this situation, the "/boot" partition
   isn't required.

 I have NOT updated the documentation yet.  That's next, iff my
 modifications are to make it into the trunk, otherwise I won't
 bother.