This crash2418.iso image contain almost complete support
for getting all your hardware going on a Intel i386/i486/i586/i686
Pentium Pro and Pentium II III 4 systems. All AMD CPU's like Athlon T-bird XP,
Duron and Cyrix CPU's should be no problem either. 
Network, SCSI, USB, filesystem (also ext3) support is included.
I use these images always first when I get a new Intel based system in front 
of me.


crash2418.iso :	the bootable iso, boots linux kernel 2.4.18
		this kernel is build for a i386. 

crash2418-smp-fixed.iso :
		The smp-fixed iso fixes some problems on SMP systems, like e.g. 
		Compaq Proliant servers which have more as one CPU.
		After using CRK 2.4.18, booting a Compaq Proliant
		again resulted in loss of CPU's inside the BIOS.
		This is now fixed by removing MTRR, APIC and IO-APIC stuff
		from the kernel.

crash2418-i386.iso :
		This iso uses glibc version 2.2.4 wich also runs on i386, 
		i486 and i586 compatible CPU's. The previous CRK v.2.4.18 
		contained glibc libs which only ran on i686 compatible CPU's 
		and higher. Read also :

http://www.cs.helsinki.fi/linux/linux-kernel/2002-01/0067.html

		All possible stuff from kernel 2.4.18 has been enabled
		and possibly mostly as modules. 

		Just burn the iso with your own favorite CD-Burn program. 
		For instance Adaptec EASY CD-Creator or Nero can do it.
		The minimum RAM to boot it is 16 Mb physical ram. 
		This is because a 8 Mb ramdisk filesystem is created.
		After booting the kernel it will load through initrd the
		rootrh72.img runtime. 

		If you have only 16 Mb physical RAM and want to use some
		of the modules on the cdrom then
		for instance mount first a filesystem (e.g. msdos)
		and install a swapfile :

		login as root, no password required :)

		# mount -t msdos /dev/hda1 /mnt
		# dd if=/dev/zero of=/mnt/swapfile bs=1024 count=16384
		# mkswap /mnt/swapfile 16384
		# sync
		# swapon /mnt/swapfile

		To install extented utilities like :
		( vim ftp ps telnet (tiny telnet) and reiserfs utils) run :

		# install-cdrom

( install-cdrom will fail when you boot from a scsi cdrom, workaround is
  to copy the scsi module from the crash2418.iso to a floppy, i.e. if
  you have a Adaptec 2940U2W scsi controller, copy aic7xxx.o to a floppy,
  maybe gzip it first. Mount the floppy with mount /dev/fd0 /floppy and 
  then load the scsi driver with : insmod /floppy/aic7xxx.o
  Next you can mount the scsi cdrom on /cdrom with : 
  mount -t iso9660 -oro /dev/scd0 /cdrom )

  		After that run 
		
		# /cdrom/sbin/install-utils

Or just copy manually from /cdrom/utils directory tree what you really need.

After running install-cdrom the cdrom is mounted on /cdrom 
and the modules are then inside /cdrom/modules/2.4.18/ . To use a module 
just find it inside the modules directory tree and just do a 
insmod module.o.

Say for instance you have a Boomerang 3com905b fastethernet card.
Locate the apropiate module inside modules.list. The 3com905b card is
supported under Linux by the 3c59x.o module. ( To find out which module
name is supporting which hardware I, at this time of writing, point
to the Linux kernel source. This source can be found at :

	ftp://ftp.kernel.org/pub/linux/kernel/v2.4/linux-2.4.x.tar.gz

I have included the kernel source Documentation inside 
/cdrom/modules/Documentation though. Inside /cdrom/modules/dev is now
the MAKEDEV package. See below how to use it.

Installing the 3c59x.o module is rather simple :

		# cd /cdrom/modules/2.4.18/kernel/drivers/net
		# insmod 3c59x.o

You might even consider makeing a symlink like this :

		# cd /lib/modules
		# ln -s /cdrom/modules/2.4.18 .

Then modprobe can be used, and even a /etc/modules.conf can be used, but
I haven't tested that yet. Linking the modules directory on cdrom to 
/lib/modules (like above shown) is i think now the easiest thing to do.
After you have fired up all the modules you need, you can just umount /cdrom 
so your own cdrom disks can be inserted.

Getting the network going :

1. # vi /etc/hosts		(plug in all your ip numbers 
				 and host names you are going
				 to use .)

2. Make sure the apropiate ethernet card module is loaded (see above)

   # cd /etc/sysconfig/network-scripts
   # cp ifcfg-eth0.org ifcfg-eth0
   # vi ifcfg-eth0		(plug your ip number and netmask
				 and broadcast address)
   # cd /etc/rc.d/init.d
   # ./network stop ; ./network start
   # ping hostname		( ping some host on the network )

Mounting a remote NFS share to make a backup over the network :

1a. Here's a example : Imagine that your win2k server died because of
   a faulty service pack install. The win2k server is known on the
   network as win2000.company.net with ip-number 192.168.1.10 and
   netmask 255.255.255.0. Boot the win2k server with the crash245.iso
   and configure the network as outlined above using 192.168.1.10 as 
   the ip-number.  Also on the network is running your redhat 7.1
   workstation or server with hostname rh71.company.net and ip-number
   192.168.1.21 and netmask 255.255.255.0. On the linux server rh71
   configure a NFS share to be exported :

   [root@rh71 /]# vi /etc/exports 

   and add this line :

   /backup	win2000(rw,no_root_squash)

   [root@rh71 /]# mkdir /backup
   [root@rh71 /]# /etc/rc.d/init.d/nfs stop
   [root@rh71 /]# /etc/rc.d/init.d/nfs start
   [root@rh71 /]# showmount -e rh71
   Export list for rh71:
   /backup win2000.company.net

   Now your NFS backup server rh71 is ready for use. We move over to
   win2k server which is booted with crash245.iso. Make sure al modules
   for disk controllers like adaptec 2940U2W are loaded. Also load the
   NTFS file system module ntfs.o . Make sure /etc/hosts on the machine
   booted with the CRK contains at least these two lines:

   192.168.1.10		win2000
   192.168.1.21		rh71

   Next mount your NTFS partitions :

   # cd /lib/modules
   # ln -s /cdrom/modules/2.4.18 .
   # modprobe ntfs
   # cd /mnt
   # mkdir part1 part2 part3
   # mount -t ntfs -oro /dev/sda1 /mnt/part1
   # mount -t ntfs -oro /dev/sda2 /mnt/part2
   # mount -t ntfs -oro /dev/sdb1 /mnt/part3

   Next make sure you have the portmapper running and then mount the NFS
   share. Its important that the ip-number you configured on your
   network card (eth0) is known by the nfsserver inside its /etc/exports.
   If the ip number you used is known by the local DNS servers, then
   use the hostname of that ip-number inside /etc/exports.

   # /sbin/portmap
   # mkdir /backup
   # mount -t nfs -orw,rsize=8192,wsize=8192 rh71:/backup /backup

   Now just copy all the important data from /mnt/part1 2 and 3 to
   /backup .

1b. Same scenario as 1a, but now you upfront know maybe something might go
   wrong, when applying a hotfix, servicepack etc. 
   What you can do is do a "ghostlike" backup of your drive(s).
    
   On the win2k server (booted with the crk) mount the remote NFS share as 
   above and make sure you don't have your local drives mounted :

   # /sbin/portmap
   # mkdir /backup
   # mount -t nfs -orw,rsize=8192,wsize=8192 rh71:/backup /backup

   Next just do a dd (data dump) of your local drives to /backup :

   # dd if=/dev/sda bs=10M | gzip -c > /backup/dd-sda.gz
   # dd if=/dev/sdb bs=10M | gzip -c > /backup/dd-sdb.gz

   Now restart the machine with its native win2k OS and apply service packs
   hotfixes or whatever patch is needed. If something goes wrong then
   boot the machine again with the crk and mount the NFS share again like
   above. Putting the just backup-ed dd images back on the drives is done
   like this :

   # gzip -dc /backup/dd-sda.gz | dd of=/dev/sda bs=10M
   # gzip -dc /backup/dd-sdb.gz | dd of=/dev/sdb bs=10M


Getting SCSI going :

1. Make sure the apropiate scsi card module is loaded (see above)

   # cd /lib/modules
   # ln -s /cdrom/modules/2.4.18 .
   # modprobe aic7xxx		( If you have a Adaptec aha2940U2W card)

Creating extra Devices nodes :

1. Make a symlink as needed :

   # cd /etc
   # ln -s /cdrom/modules/dev/makedev.d .
   # cd /dev
   # cp /cdrom/modules/dev/MAKEDEV .
   # ./MAKEDEV rd/c0d0		( DAC960 device nodes for controller0 disk0)
   # ./MAKEDEV ida/c0d0		( Compaq Smart Array device nodes for c0d0 )
   # ./MAKEDEV ataraid/d0	( IDE RAID device nodes for disk0)

Getting FAT32 going :

1. install the vfat.o module :

   # cd /lib/modules
   # ln -s /cdrom/modules/2.4.18 .
   # modprobe vfat
   # mount -t vfat /dev/hda1 /mnt  ( If hda1 contains a FAT32 filesystem)

Getting EXT3 going :

1. install the ext3.o module :

   # cd /lib/modules
   # ln -s /cdrom/modules/2.4.18 .
   # modprobe ext3
   # mkfs.ext3 /dev/hda1	( make a journalled ext3 filesystem )
   # mount /dev/hda1 /mnt	( /dev/hda1 is mounted after this as ext3,
				  with ps ax , you can see a extra kjournald
				  is fired up )
   # umount /mnt
   # fsck.ext3 /dev/hda1	( filesystem check for ext3 , -f option 
				  will force a check )
   # mkfs.ext2 /dev/hda1	( make a ordinary ext2 filesystem )
   # mount /dev/hda1 /mnt	( /dev/hda1 is mounted as ext2 )
   # umount /mnt
   # tune2fs -j /dev/hda1	( the ext2 filesystem of /dev/hda1 is converted
				  to ext3 )
   # mount /dev/hda1 /mnt 	( /dev/hda1 is now mounted as ext3 )
   # mount 			( double check to see how your partitions are
				  mounted )

Getting PCMCIA going :

1. Make sure the cdrom is mounted on /cdrom and run 
   /cdrom/sbin/install-pcmcia .
   Next edit ifcfg-eth0 like outlined above in case of a pcmcia
   network card. Then run this :

   # /etc/rc.d/init.d/pcmcia start
        ( insert your pcmcia card , and thats it)

Recovering and re-installing LILO :

1. boot your machine with the kit.
   Next mount your root (/) partition on /mnt :

   # mount /dev/hda1 /mnt

   Eventually mount your boot partition on top of that :

   # mount /dev/hda2 /mnt/boot
   # vi /mnt/etc/lilo.conf              (adjust lilo.conf )
   # /mnt/sbin/lilo -r /mnt             (re-install lilo relative to /mnt)

   Newer versions of lilo even might need this syntax:

   # /mnt/sbin/lilo -r /mnt -w

   or even:
   
   # /mnt/sbin/lilo -L -r /mnt

Getting something else going :

   E-Mail me at stock@stokkie.net

Robert M. Stockmann
Last changed Fri Jan 31 03:49:05 CET 2003