Q: When do you will include XFS (or any other patch to the kernel)?
A: I will not patch the plain vanilla kernel. If i start patching
   the kernel i need to monitor these patches for any serious/dangerous
   bugs that may corrupt your data, and that is just to much work.
   Use the toolset to build your own CD.

Q: partimage cannot find any partitions
A: first mount a partition, then run partimage again

Q: the boot process aborts with the message "unable to open an 
   initial console".
A: you need to unpackage the tarball as root.

Q: What is about packet filtering software on the rescuecd iso
A: i thought about that, but i think the main goal of the cd iso
   is a rescuecd, so the tcp/ip stuff just consumes space which
   can be used for other, more important software and/or device
   drivers. if you want to build a router, use the rescuecd kit to
   create a system that will fit your needs.

Q: isolinux aborts with the following error message (or something similar) 
   while booting:
    ISOLINUX 1.62.....
    isolinx: Disk error 00, drive F0
A: try another bootloader - change the BOOTLOADER option in the system_config
   file.

Q: my computer won't boot from cdroms. It only boots from floppy disks.
   Can I use your rescue system nevertheless?
A: Yes, just use the script utils/make_boot_disk to make a boot floppy
   or download th boot floppy image from http://rescuecd.sf.net/download.html.

Q: the build script aborts with the following error message (or something
   similar):
   cdrecord: Input/output error. blank unit: scsi sendcmd: retryable error
   CDB:  A1 01 00 00 00 00 00 00 00 00 00 00
   status: 0x2 (CHECK CONDITION)
   Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
   Sense Key: 0x2 Not Ready, Segment 0
   Sense Code: 0x30 Qual 0x00 (incompatible medium installed) Fru 0x0
   Sense flags: Blk 0 (not valid)
   cmd finished after 0.003s timeout 9600s
   cdrecord: Cannot blank disk, aborting.
A: comment out the parameter SCSIBLANK="blank=fast" in the config file
   config_build

Q: When will you include the newest version of tool XXX, i really need it?
A: i am happy to hear any suggestions of missing tools or tools that would 
   increase the usability of the rescue system and if i have the same 
   opinion on that tool i will include it in the next release, but only
   if the tool is part of the debian woody distribution, resp. is mentioned
   in docs/packages.
   i will not include any other tool.
   if i add a tool which is not part of the debian woody distribution
   the problem is that i need to monitor that tool for any serious/dangerous
   bugs that may corrupt your data. but if i stay inside the debian distro
   i only need to do an "apt-get update && apt-get dist-upgrade" every now and 
   then to hold the system up 2 date.
   
Q: Your rescue system looks neat, but i can't login:-) What's the password?
A: The standard password is "rescue" and for those that not already knew it,
   the username is "root".

Q: the eth0 interface is not up and not configured after booting into the 
   rescue system
A: only the localhost interface is up by default, if you want to bring up
   the other interfaces try "ifup -a".

Q: ifup -a does not work
A: per default only the localhost interface is up. If you did not configured
   your NIC through the config script you need to bring it up by hand:
	1. load the NIC driver
	   # modprobe 8139too
	2. configure the NIC
	   # ifconfig eth0 inet 192.168.0.99 up
	   or via dhcp:
	   # dhclient eth0
	3. set the default gateway if any
	   # route add default gw 192.168.0.1