Q: How can I use bootcd to run a diskless PC?
A: 1. Install another PC (that has disk and cd-burner) as usual. Be sure 
      not to use more than 650 MB.
   2. Build a bootcd with bootcdwrite from this PC.
   3. Run the diskless PC from the CD. 
   4. Save changes to a floppy with bootcdflopcp.
   5. Next time you boot, be sure the bios tries to boot the cd before the
      floppy.

Q: How can I use bootcd to install many PCs?
A: 1. Install a PC (that has a cd-burner) as usual. Be sure not to use 
      more than 650 MB.
   2. Build a bootcd with bootcdwrite.
   3. Boot one of the PCs you want to install with the bootcd.
   4. Be sure /etc/bootcd/bootcd2disk.conf has all Variables set to "auto"
   5. Use bootcd2disk. This will format the first disk, copy the cd to it
      and make it bootable
   6. Now boot from the PC and change hostname, ip-adress ...

Q: Can I change the amount of RAM available for ramdisk at boottime?
A: Yes: Interrupt the boot process and type "linux ramdisk_size=2048"
   This will build two 2MB disks.

Q: How can I use my bootcd on a PC which detects the CDROM as another device
   (not the device defined in bootcdwrite.conf as CDDEV)
A: Start booting again from the bootcd, interrupt and continue with 
   "linux root=/dev/scd0" (Or whatever your CD device is)

Q: What has to be compiled in the kernel?
A: First of all, if you use a standard debian kernel from the rescue-disk
   everything should work. 
   
   This Question is only important for you if you have compiled your
   own kernel.

   To boot from bootcd the kernel must be able to read from cdrom.  
   A ramdisk is necessary to run bootcd. This has to be compiled built-in 
   in the kernel because it is needed before the kernel is able to load 
   additional modules.
   
   <*> means you must configure the feature as built-in.  <M> means you can
   configure the feature as built-in or as module. 
   If you use modules you have to make sure that the modules are loaded by
   editing /etc/modules.

   To build a bootcd with bootcdwrite you need:

     Block devices --->
       <M> Loopback device support	                    CONFIG_BLK_DEV_LOOP

   To run from bootcd you need:

     Block devices --->
       <*> RAM disk support                                  CONFIG_BLK_DEV_RAM
       <*> Initial RAM disk (initrd) support              CONFIG_BLK_DEV_INITRD

     File systems --->
       <*> Second extended fs support (for RAMDISK)              CONFIG_EXT2_FS
       <*> ISO 9660 CDROM file system support                 CONFIG_ISO9660_FS

     If you have a scsi CDROM Drive you need
       SCSI support --->
         <*> SCSI support
         <*> SCSI CD-ROM support      
         SCSI low-level drivers --->
           <*> "Driver for your scsi-card"

     If you have a non scsi CDROM Drive you need eihter:

       ATA/IDE/MFM/RLL support --->
         <*> ATA/IDE/MFM/RLL support
	 IDE, ATA and ATAPI Block devices --->
	   <*> Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
	   <*> Include IDE/ATAPI CDROM support

     or you need:

       Old CD-ROM drivers (not SCSI, not IDE)  --->
         [*] Support non-SCSI/IDE/ATAPI CDROM drives
         <*> "Driver for your CDROM"

     If your CDROM doesn't support booting from it, you have to
     boot from an MSDOS Floppy. You need:

       File systems --->
         <*> DOS FAT fs support                                   CONFIG_FAT_FS
         <*> MSDOS fs support                                   CONFIG_MSDOS_FS
	 <*> VFAT (Windows-95) fs support                        CONFIG_VFAT_FS
