====== Differences ====== This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
eb_imagetypes [2007/03/12 14:37] stevem |
eb_imagetypes [2007/04/07 04:00] (current) stevem |
||
|---|---|---|---|
| Line 145: | Line 145: | ||
| </file> | </file> | ||
| - | ==== EtherBoot from USB flash key ==== | + | ==== EtherBoot from USB flash ==== |
| - | An EtherBoot initial load from USB flash media, perhaps a flash key, is quite staightforward provided of course that your BIOS can boot from USB in the first place. A modern machine will probably be able to do this. | + | An EtherBoot initial load from USB flash media is quite staightforward provided of course that your BIOS can boot from USB in the first place. A modern machine will probably be able to do this. |
| - | * BIOS | + | - BIOS |
| - | * USB master boot record | + | - USB master boot record |
| - | * USB partition boot record | + | - USB partition boot record |
| - | * SYSLINUX | + | - SYSLINUX |
| - | * EtherBoot | + | - EtherBoot |
| - | * Linux kernel | + | - Linux kernel |
| Your BIOS should really be able to boot from any sensible arrangement of partitions and boot sectors, but it might insist that a ZIP DRIVE geometry be used. | Your BIOS should really be able to boot from any sensible arrangement of partitions and boot sectors, but it might insist that a ZIP DRIVE geometry be used. | ||
| Line 166: | Line 166: | ||
| Once Linux is running with USB storage support, an inserted USB key will appear as a SCSI drive and be called something like ///dev/sda//, ///dev/sdb//, ///dev/sdc//,... in the following guide, the key is referred to as ///dev/sda//. | Once Linux is running with USB storage support, an inserted USB key will appear as a SCSI drive and be called something like ///dev/sda//, ///dev/sdb//, ///dev/sdc//,... in the following guide, the key is referred to as ///dev/sda//. | ||
| - | ** Ensure you are certain which device name is used by your flash key as this device is about to be irrevocably erased ** | + | ** Be certain which device name refers to your flash key as this device is about to be irrevocably erased ** |
| - | ===== USB Flash key - General disk drive boot geometry ===== | + | ===== USB Flash EtherBoot - General hard disk boot geometry ===== |
| * If necessary, prepare Linux to handle USB storage devices. This is up to your configuration and distribution. For example, you might find these modules present if they are not already linked into the kernel: | * If necessary, prepare Linux to handle USB storage devices. This is up to your configuration and distribution. For example, you might find these modules present if they are not already linked into the kernel: | ||
| + | |||
| Module Size Used by | Module Size Used by | ||
| sd_mod 19472 0 | sd_mod 19472 0 | ||
| Line 178: | Line 179: | ||
| usbcore 141956 4 usb_storage,libusual,uhci_hcd | usbcore 141956 4 usb_storage,libusual,uhci_hcd | ||
| - | * Insert USB flash key and run *dmesg* | + | * Insert USB flash key and examine //dmesg// output |
| sda: sda1 | sda: sda1 | ||
| sd 2:0:0:0: Attached scsi removable disk sda | sd 2:0:0:0: Attached scsi removable disk sda | ||
| - | * Wipe the master boot reord and recreate partitions (here we have a single one) | + | * Wipe the master boot record ** losing all data ** |
| dd if=/dev/zero of=/dev/sda bs=1k count=128 | dd if=/dev/zero of=/dev/sda bs=1k count=128 | ||
| - | sfdisk /dev/sda | + | |
| + | * Create new partition | ||
| + | |||
| + | sfdisk /dev/sda [ENTER for defaults then (w)rite partition table] | ||
| Device Boot Start End #cyls #blocks Id System | Device Boot Start End #cyls #blocks Id System | ||
| /dev/sda1 0+ 1021 1022- 124683+ 83 Linux | /dev/sda1 0+ 1021 1022- 124683+ 83 Linux | ||
| Line 195: | Line 200: | ||
| * Mark the partition as active: | * Mark the partition as active: | ||
| - | fdisk /dev/sda (a 1 w q) | + | sfdisk /dev/sda -A1 |
| - | * Create a DOS filesystem and install SYSLINUX on the newly created, active partition. | + | * Create a DOS filesystem on the newly created active partition |
| mkdosfs /dev/sda1 | mkdosfs /dev/sda1 | ||
| - | syslinux /dev/sda1 | ||
| + | * Install SYSLINUX onto it | ||
| + | syslinux /dev/sda1 | ||
| + | * Mount the device and copy over required //networkcard.zlilo// file and corresponding //syslinux.cfg// [[eb_imagetypes#Using lilo on a floppy|just as in a diskette boot]]. There will now be three files on the flash device | ||
| - | *Prepare an active, bootable partition on the USB key | + | root@shark(/flash)# ls |
| - | [[http://flashlinux.org.uk/make|Instructions]] | + | ldlinux.sys r8169.zli syslinux.cfg |
| - | *Install SYSLINUX onto the bootable partition | + | root@shark(/flash)# cat syslinux.cfg |
| + | default r8169.zli | ||
| - | syslinux /dev/sda1 | + | * Unmount the device, shutdown and reboot from the network. |
| - | To be tested and completed by stevem shortly | + | ===== USB Flash EtherBoot - ZIP drive geometry ===== |
| + | An older machine may insist on a geometry which appears to your BIOS as a standard ZIP drive having 64 heads and 32 sectors per track. The number of cylinders depends on the capacity of the drive. A ZIP drive boots from partition 4. | ||
| - | ===== USB Flash key - ZIP DRIVE geometry ===== | + | * Use the mkdiskimage script from SYSLINUX to create a blank DOS-formatted image on your flash key, letting mkdiskimage work out the size of the device. This may take a little while to complete. |
| - | A standard zip drive appears to your BIOS as having 64 heads and 32 sectors per track. The number of cylinders depends on the capacity of the drive. A zip drive insists on booting from partition 4. | + | |
| - | + | ||
| - | *Use the mkdiskimage script from SYSLINUX to create a blank DOS-formatted image on your flash key, letting mkdiskimage work out the size of the device. This may take a little while to complete. | + | |
| mkdiskimage -4 /dev/sda 0 64 32 | mkdiskimage -4 /dev/sda 0 64 32 | ||
| - | *Install syslinux onto the key. | + | * Install SYSLINUX onto the key. |
| syslinux /dev/sda4 | syslinux /dev/sda4 | ||
| - | Finally, use the Etherboot ''networkcard.zlilo'' file in place of the Linux kernel, /dev/sda4 in place of the diskette device and follow these [[http://www.etherboot.org/wiki/eb_imagetypes#lilogrubsyslinux_files_.zlilo|instructions]] | + | * Mount /dev/sda4 and copy over required //networkcard.zlilo// file and corresponding //syslinux.cfg// [[eb_imagetypes#Using lilo on a floppy|just as in a diskette boot]] |
| - | above so that syslinux will load Etherboot. | + | |
| + | * Unmount the device, shutdown and reboot from the network. | ||
| More recipies can be found [[http://www.beezmo.com/FloobyDustDir/FDKnoppixUsbDir/FDKnoppixUsb.htm|here]], with another source of information [[http://www.freesoftwaremagazine.com/articles/grub_intro|here]]. | More recipies can be found [[http://www.beezmo.com/FloobyDustDir/FDKnoppixUsbDir/FDKnoppixUsb.htm|here]], with another source of information [[http://www.freesoftwaremagazine.com/articles/grub_intro|here]]. | ||
