Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
usbwithstorage [2009/09/24 10:17] tiriel |
usbwithstorage [2009/09/24 10:24] tiriel |
||
---|---|---|---|
Line 20: | Line 20: | ||
*{{:screenshots:disk_id.png?500|}} | *{{:screenshots:disk_id.png?500|}} | ||
*In the case depicted above the Disk Identifier is disk1, so the device would be ''/dev/disk1'', that's the device name we'll use for the rest of the tutorial, adapt to whatever your disk identifier is. | *In the case depicted above the Disk Identifier is disk1, so the device would be ''/dev/disk1'', that's the device name we'll use for the rest of the tutorial, adapt to whatever your disk identifier is. | ||
- | |||
==== 3. Deploying BKO ==== | ==== 3. Deploying BKO ==== | ||
- | To deploy BKO to your USB drive, fire up Terminal and cd to the directory you downloaded it and deploy it by using | + | To deploy BKO to your USB drive, fire up Terminal and cd to the directory where you downloaded it. Deploy it by using |
dd if=gpxe.usb of=dev/disk1 | dd if=gpxe.usb of=dev/disk1 | ||
Remember to substitute ''disk1'' for your own disk identifier. | Remember to substitute ''disk1'' for your own disk identifier. | ||
Line 29: | Line 28: | ||
==== 4. Recovering your storage space ==== | ==== 4. Recovering your storage space ==== | ||
At the moment, your BKO/gPXE should be up and ready, feel free to try it out. Nevertheless you will find that you're using your whole USB drive for a tool that uses barely 2MB of espace. We will be redefining the partition table so we can use the remaining espace. | At the moment, your BKO/gPXE should be up and ready, feel free to try it out. Nevertheless you will find that you're using your whole USB drive for a tool that uses barely 2MB of espace. We will be redefining the partition table so we can use the remaining espace. | ||
- | |||
There is a screenshot of this process below. | There is a screenshot of this process below. | ||
- | - Launch the fdisk utility by using | + | - From Terminal, launch the fdisk utility in interactive mode by using: |
* <code>fdisk -e /dev/disk1</code> | * <code>fdisk -e /dev/disk1</code> | ||
- | - Once fdisk starts, the prompt should look like | + | - Once fdisk starts, the prompt should look like: |
* <code>fdisk: 1></code> | * <code>fdisk: 1></code> | ||
- | - Issue the print command to get a preview of the partition table | + | - Issue the print command to get a preview of the partition table. |
* <code>fdisk: 1> print</code> | * <code>fdisk: 1> print</code> | ||
* BKO is installed on the forth partition, note the size of the partition, for you will need that number afterwards. | * BKO is installed on the forth partition, note the size of the partition, for you will need that number afterwards. | ||
- | - Edit the first partition to use it as the storage partition. | + | - Edit the first partition to be able to use it for storage. |
* <code>fdisk: 1> edit 1</code> | * <code>fdisk: 1> edit 1</code> | ||
- | - First you will be asked for the partition's id, enter ''0B'' that is the code for Win95 FAT-32 filesystem. | + | - First you will be asked for the partition's id, enter ''0B'', that is the code for the Win95 FAT-32 filesystem. |
- | - Then you will be asked if you want to edit in CHS (cylinder, head, sector) mode, say ''no'' unless you know what you're doing | + | - Then you will be asked if you want to edit in CHS (cylinder, head, sector) mode, say ''no'' unless you know what you're doing. |
- | - When prompted for the partition offset, enter the size of BKO's partition, in this case ''4064'' | + | - When prompted for the partition offset, enter the size of BKO's partition, in this case ''4064''. |
- Last you will be asked for the partition's size, leave the default value. | - Last you will be asked for the partition's size, leave the default value. | ||
- | - Issue the print command again to make sure the changes have been made | + | - Issue the print command again to make sure the changes have been made. |
* <code>fdisk: 1> edit 1</code> | * <code>fdisk: 1> edit 1</code> | ||
- Write the changes to the disk by issuing the write command. | - Write the changes to the disk by issuing the write command. | ||
* <code>fdisk: 1> write</code> | * <code>fdisk: 1> write</code> | ||
- | - Exit fdisk | + | - Exit fdisk. |
* <code>fdisk: 1> quit</code> | * <code>fdisk: 1> quit</code> | ||
{{:screenshots:fdisk.png?500|}} | {{:screenshots:fdisk.png?500|}} |