cvs commit: hints uclibc-bootfloppy.txt

tushar at linuxfromscratch.org tushar at linuxfromscratch.org
Fri Oct 31 20:36:53 PST 2003


tushar      03/10/31 21:36:53

  Modified:    .        uclibc-bootfloppy.txt
  Log:
  Updated Hint: uclibc-bootfloppy.txt
  
  Revision  Changes    Path
  1.8       +40 -18    hints/uclibc-bootfloppy.txt
  
  Index: uclibc-bootfloppy.txt
  ===================================================================
  RCS file: /home/cvsroot/hints/uclibc-bootfloppy.txt,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -u -r1.7 -r1.8
  --- uclibc-bootfloppy.txt	30 Oct 2003 15:10:10 -0000	1.7
  +++ uclibc-bootfloppy.txt	1 Nov 2003 04:36:53 -0000	1.8
  @@ -17,6 +17,12 @@
   a non-broken toolchain. It was tested on a (by and large) LFS-4.0
   system. The sudo utility is advised to have.
   
  +ATTACHMENTS:
  +http://www.linuxfromscratch.org/hints/downloads/attachments/uclibc-bootfloppy/busybox-0.60.5-Config.h
  +http://www.linuxfromscratch.org/hints/downloads/attachments/uclibc-bootfloppy/linux-2.4.22-.config
  +http://www.linuxfromscratch.org/hints/downloads/attachments/uclibc-bootfloppy/mkbootdisk
  +http://www.linuxfromscratch.org/patches/downloads/devfsd/devfsd-1.3.25-uclibc-1.patch
  +
   HINT:
   
   Contents
  @@ -51,12 +57,6 @@
   
   http://www.math-inst.hu/~ekho/lowlife/uclibc-bootfloppy.txt
   
  -* Some attachments of this hint can be found at
  -
  -http://www.linuxfromscratch.org/hints/downloads/attachments/uclibc-bootfloppy/
  -
  -or at the lowlife homepage.
  -
   * Comments, ideas, critics, flames are welcome.
   
   * (If you are an LFS user, you can skip this.) Although this document is
  @@ -75,11 +75,24 @@
   Introduction
   ------------
   
  -I feel that the bootfloppy created in the BLFS-book is not enough
  -customized to its task. It uses the system glibc and the system
  -bootscripts. These are overkill for a bootfloppy. Here we will create a
  -bootfloppy based on the uClibc C library, which is just made for such
  -purposes. 
  +When you are to put together a Linux bootfloppy, you need to decide what
  +implementation of the standard C libraries will you use. 
  +
  +One possibility is using the C library implementation which is common on
  +Linux based systems: glibc. It's advantage is that you have it at hand:
  +to make a glibc-based bootfloppy, the only thing you have to do is to is
  +to copy the necessary libs to the filesystem you will put on the floppy.
  +This is way chosen by the rescue floppy described in the BLFS-book:
  +
  +http://linuxfromscratch.org/blfs/view/test/postlfs/bootdisk.html
  +
  +However, glibc is far from being lightweight, and eats up much of the
  +rather limited space you have when working with a floppy. So you might
  +like seek for an alternative which suits much better to the capabilities
  +of the floppy environment.
  +
  +Here we will create a bootfloppy based on the uClibc C library, which is
  +just made for such purposes. 
   
   The bootfloppy will be cutting edge: uses uClibc and Busybox which are
   actively developed projects for the embedded platform. Moreover, I used
  @@ -319,6 +332,13 @@
   And don't forget to include support for the mouse type you will use with
   the bootfloppy (if you will use any). 
   
  +OK, one more remark. Here I don't digress on how to use initrd, but you may
  +have some reason for doing that. In this case with some kernels (eg., with 
  +linux-2.4.22) you might encounter with booting problems, which can be cured
  +by the appropriate kernel patch. For info on initrd and the patch you can
  +consult the "Creating a Custom Boot Disk" chapter of the BLFS-book, 
  +referenced in the Introduction.  
  + 
   Now compile the kernel with the 
   
   make dep && make bzImage && make modules
  @@ -542,13 +562,15 @@
   able to run those utilities which do not require much I/O (ls, cat,
   echo,...). Proceed on again as the bootdisk user.
   
  -Put a floppy to the floppy drive. If you use my mkbootdisk script,
  -check whether the device name of the floppy drive is set correctly in
  -the script (it is set to /dev/fd0 and no option can change it, in order
  -to prevent the bootdisk user in being able to muck up the development
  -platform), and whether the $MKE2FSAPP, $RDEVAPP variables in the script
  -store the correct path to the mke2fs, rdev utilities in your system
  -(they should if you follow standards). If everything is fine, simply run 
  +Put a floppy to the floppy drive (if you are not sure about its
  +integrity, you might want to run fdformat on it). If you use my
  +mkbootdisk script, check whether the device name of the floppy drive is
  +set correctly in the script (it is set to /dev/fd0 and no option can
  +change it, in order to prevent the bootdisk user in being able to muck
  +up the development platform), and whether the $MKE2FSAPP, $RDEVAPP
  +variables in the script store the correct path to the mke2fs, rdev
  +utilities in your system (they should if you follow standards). If
  +everything is fine, simply run 
   
   cd &&
   sudo mkbootdisk
  
  
  



More information about the hints mailing list