Commit c783c535 authored by T(A)ILS developers's avatar T(A)ILS developers

doc: installing on a USB → installing onto a USB stick

parent 751abc18
......@@ -18,7 +18,7 @@ being complete yet.
<h1>Documentation</h1>
<ul>
<li>[[Installing on a USB]]</li>
<li>[[Installing onto a USB stick]]</li>
<li>[[Walkthrough]]</li>
<li>[[Virtualization]]</li>
<li>[[TrueCrypt]]</li>
......
[[!meta title="Installing on a USB"]]
[[!meta title="Installing onto a USB stick"]]
[[!toc levels=2]]
## Why running from a USB?
## Why running from a USB stick?
Running T(A)ILS from a CD has its virtues but it certainly also have its
limitations. While CDs are portable they usually do not fit in your pocket in a
comfortable manner. But a USB memory stick certainly fits any pocket or your key
ring. In addition, CDs are read-only and thus no data can be saved to them, but
that is, again, not the case with USB drives. However, storing sensitive data on
comfortable manner. But a USB stick certainly fits any pocket or your key ring.
In addition, CDs are read-only and thus no data can be saved to them, but that
is, again, not the case with USB sticks. However, storing sensitive data on
writeable media could be dangerous if it got into the wrong hands. Similarly, if
we get a virus or manages to damage the system in other ways, the system is
tainted or unusable from that point and all consecutive boots, either with or
without your knowledge. Clearly that is not good.
Note that the method of installing T(A)ILS to USB is pretty crude at the moment
(a more intuituve way is planned). If you do not know precisely what the things
mentioned below mean it is recommended to stop now as you otherwise might risk
overwriting any present hard drives. Proceed at your own discretion!
Note that the method of installing T(A)ILS onto a USB stick is pretty crude at
the moment (a more intuituve way is planned). If you do not know precisely what
the things mentioned below mean it is recommended to stop now as you otherwise
might risk overwriting any present hard drives. Proceed at your own discretion!
## 1st method: from another T(A)ILS CD or USB
## 1st method: from another running T(A)ILS Live CD or USB
If you are already able to run T(A)ILS from a CD or a USB (the source), use this
method to clone it to another USB (the destination).
If you are already able to run T(A)ILS from a CD or a USB stick (the source),
use this method to clone it onto another USB stick (the destination).
**1 — Boot T(A)ILS from the source CD or USB.**
**1 — Boot T(A)ILS from the source CD or USB stick.**
**2 — Find out the device name of the source T(A)ILS.**
If you're running T(A)ILS from a CD the device name should be `/dev/cdrom`.
If you're running T(A)ILS from a USB the device name should be something like
`/dev/sdb`, `/dev/sdc`, etc.
If you're running T(A)ILS from a USB stick, the device name should be something
like `/dev/sdb`, `/dev/sdc`, etc.
If you're not sure about it's precise name:
......@@ -42,26 +42,28 @@ In the `messages` file, search for the first occurrence of a `removable disk`
named `sd`<em>something</em>. If you only have your T(A)ILS key plugged it
should be the right one.
In the example on this screenshot the source USB was named `sdb` and so the
device name would be `/dev/sdb`. Yours could be different.
In the example on this screenshot the source USB stick was named `sdb` and so
the device name would be `/dev/sdb`. Yours could be different.
![Logs containing \[sdb\]: Attached SCSI removable disk](installing_on_a_usb/source-usb.png)
![Logs containing \[sdb\]: Attached SCSI removable
disk](installing_onto_a_usb_stick/source-usb.png)
**3 — Find out the device name of the destination USB.**
**3 — Find out the device name of the destination USB stick.**
Open the `messages` file from the log file viewer again in *Applications* →
*System Tools* → *Log File Viewer*.
Unplug and plug back the destination USB: some new lines should appear in bold
at the end of the file. They correspond to you plugging the USB. Find how was
the USB named and deduce the device name from it.
Unplug and plug back the destination USB stick: some new lines should appear in
bold at the end of the file. They correspond to you plugging it. Find how was
the USB stick named and deduce the device name from it.
In the example on this screenshot the destination USB was named `sdc` and so the
device name would be `/dev/sdc`. Yours could de different.
In the example on this screenshot the destination USB stick was named `sdc` and
so the device name would be `/dev/sdc`. Yours could de different.
![Logs containing \[sdc\]: Attached SCSI removable disk](installing_on_a_usb/destination-usb.png)
![Logs containing \[sdc\]: Attached SCSI removable
disk](installing_onto_a_usb_stick/destination-usb.png)
**4 — Copy the source T(A)ILS to the destination USB.**
**4 — Copy the source T(A)ILS onto the destination USB stick.**
Open a terminal by going in *Applications* → *Accessories* → *Terminal* and
issue the following command, replacing `[source]` by the name found in step 2
......@@ -75,7 +77,7 @@ In the example on the screenshots the command would be:
**5 — Press enter and wait.**
If you don't see any error message, T(A)ILS is being copied to the key. The
If you don't see any error message, T(A)ILS is being copied onto the key. The
whole process might take a while, from a few minutes to more than a hour. Be
patient…
......@@ -103,10 +105,11 @@ could be :
## 2nd method: from an ISO image
If you [[downloaded|download]] an ISO image (the source), use this method to
create a bootable USB from it (the destination). This method implies using Linux
and possibly the Gnome Desktop environment.
create a bootable USB stick from it (the destination). This method implies using
Linux and possibly the Gnome Desktop environment.
**1 — Find out the name of the destination USB as in step 3 of the 1st method.**
**1 — Find out the name of the destination USB stick as in step 3 of the 1st
method.**
**2 — Do the copy from the terminal.**
......@@ -127,7 +130,7 @@ You could get something like this :
**3 — Press enter and wait.**
If you don't see any error message, T(A)ILS is being copied to the key. The
If you don't see any error message, T(A)ILS is being copied onto the key. The
whole process might take a while, from a few minutes to more than a hour. Be
patient…
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment