| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| wiki:waitusb [2013/01/12 14:20] – [LABEL Version] changed tce-load args lverns | wiki:waitusb [2013/05/13 22:23] (current) – [LABEL Version] changed info about the location of the mtools config file lverns |
|---|
| | **//This page was most recently tested on Core 4.7.6//** |
| ====Basic Form==== | ====Basic Form==== |
| The form of this bootcode is as follows | The form of this bootcode is as follows |
| mlabel -i /dev/X ::mylabel | mlabel -i /dev/X ::mylabel |
| Where X is the name of the drive (e.g. sdb1) and where mylabel is the label you want to give your device (e.g. "shared_partition"). | Where X is the name of the drive (e.g. sdb1) and where mylabel is the label you want to give your device (e.g. "shared_partition"). |
| **mtools.tcz** can be a little gnarly to work with. If you need to create a configuration file, you are best off naming it /etc/mtools.config because ~/.mtoolsrc seems to be ignored. | **mlabel** can be a little annoying to work with and may ask you to add a line to its configuration file. This file can be named /etc/mtools.config or ~/.mtoolsrc For best results simply make /etc/mtools.config and ~/.mtoolsrc identical. |
| |
| ==OTHER== | ==OTHER== |
| ====Advantages of the Different Forms=== | ====Advantages of the Different Forms=== |
| Using the basic form is a quick fix and might allow the system to slow down for devices other than hard drives and usb drives.\\ LABELs are short and human-readable; however, since they are user defined, there is a possibility that your system might have two drives with the same label. This isn't a serious issue, but lets say you have two devices sda1 and sdb1. They both have the label "CORE". sda1 starts very quickly, while sdb1 starts very slowly. Unfortunately, the device that you want to wait for is sdb1. If you use the bootcode "waitusb=20:LABEL=CORE" then the system will wait until sda1 starts and will boot before sdb1 has time to get going.\\ | Using the basic form is a quick fix and might allow the system to slow down for devices other than hard drives and usb drives.\\ LABELs are short and human-readable; however, since they are user defined, there is a possibility that your system might have two drives with the same label. This isn't a serious issue, but lets say you have two devices sda1 and sdb1. They both have the label "CORE". sda1 starts very quickly, while sdb1 starts very slowly. Unfortunately, the device that you want to wait for is sdb1. If you use the bootcode "waitusb=20:LABEL=CORE" then the system will wait until sda1 starts and will boot before sdb1 has time to get going.\\ |
| Technically speaking, using UUID doesn't eliminate that risk entirely; however, since UUIDs are longer and usually contain a large variety of characters, the theoretical probability of two devices in a given system having the same UUID is lowered. | Technically speaking, using UUID doesn't eliminate that risk entirely; however, since UUIDs are longer and usually contain a large variety of characters, the theoretical probability of two devices in a given system having the same UUID is drastically lowered. |
| On the downside, UUIDs are not at all readable and copying them by hand is quite nasty, so if your setup requires you to type in your boot codes upon every boot, then the UUID version is not for you. | On the downside, UUIDs are not at all readable and copying them by hand is quite nasty, so if your setup requires you to type in your boot codes upon every boot, then the UUID version is not for you. |
| |
