X-Git-Url: https://git.grml.org/?a=blobdiff_plain;f=grml2usb%2Findex.html;h=a14f69bbf6f8d3684e47e62ed054395232fa7691;hb=43681327a7dbb267ebd85e7f3cd998ae9b86a4e0;hp=434a1e194c267570f7eb7d97296fadba8bf8e6e7;hpb=c39f079208e4a8e8a354e19e17d34ee43699e908;p=grml.org.git diff --git a/grml2usb/index.html b/grml2usb/index.html index 434a1e1..a14f69b 100644 --- a/grml2usb/index.html +++ b/grml2usb/index.html @@ -2,15 +2,25 @@ "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> - - + + grml2usb(8) - +

grml2usb(8)

Table of Contents

- +

Table of Contents

1. Name

grml2usb - install grml ISO(s) on usb device for booting

2. Synopsis

grml2usb [ options ] <ISO[s]> <device>

Important! The grml team does not take responsibility for loss of any data!

3. Introduction

grml2usb installs grml on a given partition of your usb device and makes it @@ -590,16 +779,9 @@ MBR using the --skip-mbr option or if you encounter any problems with t default MBR consider using --syslinux-mbr instead.

- - - -

- -	Whereas grml2usb is the script to install recent grml ISOs (>=2009.10) the -script grml2usb-compat supports older grml releases (<2009.10) as well.

4. Options

The ISO[s] should be the path to one or multiple grml-ISOs and/or the path to @@ -616,7 +798,8 @@ don’t need one) and a bootloader won’t be installed automatically.

Use specified bootoptions as default. To use flavour name as a argument for a -boot parameter use %flavour which will be expanded to the flavour name. +boot parameter use %flavour which will be expanded to the flavour name. To add +multiple bootoptions you can specify the option multiple time.

@@ -692,18 +875,6 @@ Display usage information and exit.

---lilo-binary=… -: -
-Use specified lilo executable for installing master boot record (MBR) when using -the --syslinux-mbr option. By default any system wide (from $PATH) lilo -executable is taken. If there can not be find any lilo executable the -statically compiled version of the grml2usb Debian package (see -/usr/share/grml2usb/lilo/lilo.static.[amd64|i386]) is taken. -
-
--mbr-menu: @@ -739,8 +910,7 @@ Do not install /boot/addons/ files (like dos, grub, memdisk,…).; Remove specified bootoption (could be a regex) from existing boot options. Use -multiple entries for removing different bootoptions at once. (Note: this option -is not support in grml2usb-compat.) +multiple entries for removing different bootoptions at once.
@@ -791,8 +961,7 @@ Install syslinux' master boot record (MBR, which is booting from the partition with the "active" flag set) instead of the default one. If you encounter any problems with the default MBR you can try using the syslinux MBR instead. If that works for you please let us know so we can adjust our default -MBR accordingly. Note: When using the --syslinux-mbr option lilo is executed -before the MBR is installed so the according partitions are set active. +MBR accordingly.

@@ -815,9 +984,12 @@ Enable verbose mode.

5. Developers Corner

5.1. Directory layout on usb device

boot/ ->
@@ -888,12 +1060,16 @@ Enable verbose mode.
   |   `-- grml-small.squashfs  [squashfs file for grml-small]
   `-- ...

5.2. Grabbing the source

% git clone git://git.grml.org/grml2usb.git

5.3. Developers Debugging Hints

To play with grml2usb you can avoid using a real device via a loopback file setup, like:

@@ -917,13 +1093,18 @@ setup, like:

# mkfs.vfat /dev/loop1
 # grml2usb --bootloader-only /grml/isos/grml-small_2009.10.iso /dev/loop1

5.4. Performance tracing

# blktrace -d /dev/sdX -o - | blkparse -i -
 # grml2usb grml_2009.10.iso /dev/sdX1

6. Troubleshooting and Pitfalls when booting

Here is a list of common error messages from BIOS/bootloader when trying to boot @@ -1081,9 +1262,12 @@ isolinux/syslinux fixes the problem.

7. Frequently Asked Questions (FAQ)

7.1. Where can I get grml2usb?

grml2usb is available as Debian package via the grml-testing Debian repository.

If you do not want to (or can’t) use the grml2usb Debian package you can either @@ -1109,19 +1293,9 @@ files provided either via the Debian package, the git tree or the file grml2usb.tgz.

7.2. What’s the difference between grml2hd and grml2usb?

grml2hd installs a running grml system to a harddisk. When rebooting the -harddisk installation can be modified and changes will find their way to the -harddisk immediately. grml2usb copies just the compressed chroot filesystem -(being the squashfs file), some further informational files and a bootloader to -your device. This way you don’t need as much space as with a harddisk -installation (just a USB device with >=ISO size) and when rebooting the system -your changes will be lost (unless you are using the persistency feature, see -http://wiki.grml.org/doku.php?id=persistency). -Think of using a better CD version: booting is (usually) faster, you don’t need -to burn a new CD when a new ISO version arrives (just install the new ISO using -grml2usb) and you can carry additional files on a writable medium with yourself.

7.3. Why can’t I just dd the ISO to a USB device?

7.2. Why can’t I just dd the ISO to a USB device?

Well, you can. :) Starting with grml 2009.10 the ISOs are dd-able straight out-of-the-box.

@@ -1143,39 +1317,35 @@ system available) running:

flexible system like with grml2usb (no multi-ISO setup, no additional default bootoptions,…) but it’s a nice way to get a working USB boot setup if you don’t have grml2usb available.

7.4. What’s the difference between grml2usb and just using dd?

+ +

7.3. What’s the difference between grml2usb and just using dd?

grml2usb does not remove any data from your USB device and does not alter the partition table at all. grml2usb provides multi-ISO support, support for adding default bootoptions and selecting the bootloader (syslinux vs. grub) without having to manually touch the ISO at all.

7.5. What’s grml2iso?

7.4. What’s grml2iso?

grml2iso is a script which uses grml2usb to generate a multiboot ISO out of several grml ISOs. See man grml2iso for further details.

7.6. grml2usb fails with "Fatal: file default.cfg could not be found."

If you are trying to install an older grml ISO (older than grml 2009.10) with a -recent version of grml2usb then you might notice:

Fatal: file default.cfg could not be found.
-Note:  this grml2usb version requires an ISO generated by grml-live >=0.9.24 ...
-       ... either use grml releases >=2009.10 or switch to an older grml2usb version.
-       Please visit http://grml.org/grml2usb/#grml2usb-compat for further information
-Fatal: a critical error happend during execution (not a grml ISO?), giving up

Breaking the backward compatibility was necessary to avoid maintainability hell. -If you want to install older grml ISOs please use the grml2usb-compat script -which provides support for older releases.

grml2usb supports grub version 1 (grub1) as well as grub version 2 (grub2). Whereas grub1 uses menu.lst the new version grub2 needs grub.cfg. Providing both files allows grml2usb to install grub on the target device no matter which grub version is available on the host where grml2usb is executed on.

7.8. grub-install fails with 'The file ../boot/grub/stage1 not read correctly"?!

7.6. grub-install fails with 'The file ../boot/grub/stage1 not read correctly"?!

Check whether the partition has the right partition type. For example do NOT use FAT16 (partition type 6) when using a ext3 filesystem on the partition but instead use the correct partition type (83 - Linux) then.

7.9. grub-install complains about /sbin/grub-install and/or xfs_freeze?!

7.7. grub-install complains about /sbin/grub-install and/or xfs_freeze?!

The following message:

@@ -1184,7 +1354,9 @@ xfs_freeze: specified file ["/tmp/tmpqaBK6z/boot/grub"] is not on an XFS filesys

This is "normal". grub-install sends those messages to stderr. To avoid hiding any possible real error messages grml2usb doesn’t ignore those messages.

7.10. grub-install complains about /boot/grub/device.map?!

7.8. grub-install complains about /boot/grub/device.map?!

The following message:

@@ -1192,7 +1364,9 @@ possible real error messages grml2usb doesn’t ignore those messages.

This is "normal" (at least with grub1). This isn’t a problem, because the device.map file will be generated on the target device anyway.

7.11. grub-install complains about a unary operator?!

7.9. grub-install complains about a unary operator?!

The following message:

@@ -1200,7 +1374,9 @@ device.map file will be generated on the target device anyway.

This is "normal". Just ignore it. (It usually doesn’t appear on the second invocation on the same device.)

7.12. grub-install fails with grub-probe: error: unknown filesystem?!

7.10. grub-install fails with grub-probe: error: unknown filesystem?!

The following message:

@@ -1213,7 +1389,9 @@ filesystem on the device. For example using FAT16 as filesystem type and using FAT32 as filesystem on the partition will not work. Either set filesystem type to FAT32 or format the partition using FAT16. It is essential that device partition table and filesystem use the same filesystem type.

7.13. grub-setup fails after Attempting to install GRUB to a partition instead of the MBR?!

7.11. grub-setup fails after Attempting to install GRUB to a partition instead of the MBR?!

The following message:

@@ -1228,12 +1406,16 @@ Partition Boot Record) instead of MBR (Master Boot Record).

install grub into the MBR (Master Boot Record) using the --grub-mbr option of grml2usb or 3) switch to syslinux as bootmanager (just drop the --grub option).

7.14. I’m getting something like "Error: /usr/share/grml2usb/grub/splash.xpm.gz can not be read"!?

7.12. I’m getting something like "Error: /usr/share/grml2usb/grub/splash.xpm.gz can not be read"!?

Looks like you’ve only the grml2usb script itself available. Please make sure you’ve the grml2usb Debian package installed. The most resent stable version is available via the grml-testing Debian repository. If you do not have a Debian system please see section Where can I get grml2usb? in this FAQ.

7.15. Why do I have to use a FAT16/FAT32 filesystem?

7.13. Why do I have to use a FAT16/FAT32 filesystem?

Syslinux (currently) does not support any other filesystems besides FAT16/FAT32 (though that’s a sane default if you want to share your files with other (operating) systems). If you want to use a different filesystem (like ext2/3) @@ -1246,17 +1428,32 @@ use the bootloader grub instead using grml2usb’s --grub option.FAT32 is supported since syslinux version 3.0.

7.16. I think I’ve got a really cool idea!

7.14. Addons → Hardware Detection Tool freezes

This usually means that the machine you ran grml2usb on had syslinux 3.x +installed. The version of hdt (Hardware detection tool) shipping with Grml +2010.12 and newer requires syslinux 4.x.

7.15. I think I’ve got a really cool idea!

Great! Please check out the TODO file. Feel free to report your wishes to the author. Patches highly appreciated.

7.17. I’ve problems with booting from USB.

7.16. I’ve problems with booting from USB.

Check out Troubleshooting and Pitfalls when booting.

7.18. I’ve found a bug!

7.17. I’ve found a bug!

Please report it to the author. Please provide usage examples and output of your grml2usb commandline (consider using the "--verbose" option).

8. Usage examples

@@ -1295,20 +1492,16 @@ syslinux being the default) and install a master boot record (MBR) to the MBR of /dev/sdX.

# grml2usb-compat /home/grml/grml_2009.05.iso /dev/sdX1

Install older grml ISO on device /dev/sdX1.

# grml2usb --bootoptions="lang=de ssh=mysecret" grml_2009.10.iso /dev/sdX1

# grml2usb --bootoptions="lang=de ssh=mysecret" grml_2009.10.iso /dev/sdX1
+# grml2usb --bootoptions="lang=de" --bootoptions="ssh=mysecret" grml_2009.10.iso /dev/sdX1

Install specified ISO on device /dev/sdX1 and use "lang=de ssh=mysecret" as default bootoptions.

# grml2usb --remove-bootoption="vga=791" --remove-bootoption="quiet" grml_2009.10.iso /dev/sdX1

# grml2usb --remove-bootoption="vga=791" --remove-bootoption="nomce" grml_2009.10.iso /dev/sdX1

Install specified ISO on device /dev/sdX1 remove vga=791 and quiet from existing bootoptions.

Install specified ISO on device /dev/sdX1 remove vga=791 and nomce from existing bootoptions.

# grml2usb --bootoptions="persistent-path=%flavour_name" grml64_2010.04.iso grml_2010.04.iso /dev/sdX1

@@ -1317,24 +1510,31 @@ default bootoptions.

to every menu entry. %flavour_name will be expanded to the flavour of the specific iso, e.g. grml64 and grml.

9. Online Ressources

Check out the grml2usb webpage and the grml2usb git repository.

10. Bugs

Please report feedback, bugreports and wishes to the author.

11. Author

Michael Prokop <mika@grml.org>

grml2usb(8)

1. Name

2. Synopsis

3. Introduction

4. Options

5. Developers Corner

5.1. Directory layout on usb device

5.1. Directory layout on usb device

5.2. Grabbing the source

5.2. Grabbing the source

5.3. Developers Debugging Hints

5.3. Developers Debugging Hints

5.4. Performance tracing

5.4. Performance tracing

6. Troubleshooting and Pitfalls when booting

7. Frequently Asked Questions (FAQ)

7.1. Where can I get grml2usb?

7.1. Where can I get grml2usb?

7.2. What’s the difference between grml2hd and grml2usb?

7.3. Why can’t I just dd the ISO to a USB device?

7.2. Why can’t I just dd the ISO to a USB device?

7.4. What’s the difference between grml2usb and just using dd?

7.3. What’s the difference between grml2usb and just using dd?

7.5. What’s grml2iso?

7.4. What’s grml2iso?

7.6. grml2usb fails with "Fatal: file default.cfg could not be found."

7.7. Why is there a menu.lst and a grub.cfg inside /boot/grub/?

7.5. Why is there a menu.lst and a grub.cfg inside /boot/grub/?

7.8. grub-install fails with 'The file ../boot/grub/stage1 not read correctly"?!

7.6. grub-install fails with 'The file ../boot/grub/stage1 not read correctly"?!

7.9. grub-install complains about /sbin/grub-install and/or xfs_freeze?!

7.7. grub-install complains about /sbin/grub-install and/or xfs_freeze?!

7.10. grub-install complains about /boot/grub/device.map?!

7.8. grub-install complains about /boot/grub/device.map?!

7.11. grub-install complains about a unary operator?!

7.9. grub-install complains about a unary operator?!

7.12. grub-install fails with grub-probe: error: unknown filesystem?!

7.10. grub-install fails with grub-probe: error: unknown filesystem?!

7.13. grub-setup fails after Attempting to install GRUB to a partition instead of the MBR?!

7.11. grub-setup fails after Attempting to install GRUB to a partition instead of the MBR?!

7.14. I’m getting something like "Error: /usr/share/grml2usb/grub/splash.xpm.gz can not be read"!?

7.12. I’m getting something like "Error: /usr/share/grml2usb/grub/splash.xpm.gz can not be read"!?

7.15. Why do I have to use a FAT16/FAT32 filesystem?

7.13. Why do I have to use a FAT16/FAT32 filesystem?

7.16. I think I’ve got a really cool idea!

7.14. Addons → Hardware Detection Tool freezes

7.15. I think I’ve got a really cool idea!

7.17. I’ve problems with booting from USB.

7.16. I’ve problems with booting from USB.

7.18. I’ve found a bug!

7.17. I’ve found a bug!

8. Usage examples

9. Online Ressources

10. Bugs

11. Author