hank-test/quick-docs
1
0
Fork 0
mirror of https://pagure.io/fedora-docs/quick-docs.git synced 2024-11-28 14:56:35 +00:00
Code Issues 1 Projects Releases Packages Wiki Activity Actions

Fix Using live image.

Browse source
This commit is contained in:
Robert Krátký 2018-01-20 16:39:47 +01:00
parent 76517034b0
commit a1fb1d9167
9 changed files with 230 additions and 443 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
_topic_map.yml
View file

@ -22,6 +22,8 @@ Topics:
File: installing-spotify
- Name: Adding new fonts in Fedora
File: adding-new-fonts-fedora
- Name: Creating and using a live installation image
File: creating-and-using-a-live-installation-image
- Name: (FIX ME!) Third party repositories
File: 3rd-party-repos
- Name: (FIX ME!) Anaconda
@ -66,16 +68,6 @@ Topics:
File: grub2
- Name: (FIX ME!) Kernel
File: kernel
- Name: Downloading Fedora
File: /modules/proc_downloading-fedora
- Name: How to create and use Live USB
File: /modules/proc_create-and-use-liveusb
- Name: Booting from USB sticks
File: /modules/proc_booting-from-usb-sticks
- Name: Troubleshooting a live USB
File: /modules/proc_troubleshooting-live-usb
- Name: How to create and use a live CD
File: /modules/proc_create-and-use-livecd
- Name: (FIX ME!) Mirroring
File: mirroring
- Name: (FIX ME!) CLI

215
en-US/create-and-use-livecd.adoc
View file

@ -1,215 +0,0 @@
= How to create and use a Live CD
'''
[IMPORTANT]
======
This page was automatically converted from https://fedoraproject.org/wiki/How_to_create_and_use_a_Live_CD
It is probably
* Badly formatted
* Missing graphics and tables that do not convert well from mediawiki
* Out-of-date
* In need of other love
Please fix it, remove this notice, and then add to `_topic_map.yml`
Pull requests accepted at https://pagure.io/fedora-docs/quick-docs
Once that is live, go to the original wiki page and add an `{{old}}`
tag, followed by a note like
....
{{admon/note|This page has a new home!|
This wiki page is no longer maintained. Please find the up-to-date
version at: https://docs.fedoraproject.org/whatever-the-url
}}
....
======
'''
This page explains how to make a custom-content Live CD or DVD on
Fedora-based systems including derived distributions such as RHEL,
CentOS and others.
[[getting-started]]
Getting started
~~~~~~~~~~~~~~~
To create a live image, the *livecd-creator* tool is used. Super user
privileges are needed. The tool is more or less self-documenting, use to
see options.
The *livecd-creator* tool is part of the `livecd-tools` package. If it
is not installed on your system, add it with link:dnf[DNF] or
link:yum[YUM]:
....
su -c 'yum install livecd-tools spin-kickstarts' #Versions prior to Fedora 22
or
su -c 'dnf install livecd-tools spin-kickstarts' #Fedora 22 and beyond
....
If you are interested in localized (i.e. translated into other
languages) live CD files, install also *l10n-kickstarts*.
[[configuring-the-image]]
Configuring the image
~~~~~~~~~~~~~~~~~~~~~
The configuration of the live image is defined by a file called
_kickstart_. It can include some basic system configuration items, the
package manifest and a script to be run at the end of the build process.
For the Fedora project, the most important live image configurations
files are:
* *https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/fedora-live-base.ks[fedora-live-base.ks]*
: The base live image system (included in the 'livecd-tools' package).
* For _Fedora 20 and earlier_:
*https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/fedora-livecd-desktop.ks[fedora-livecd-desktop.ks]*
: Complete desktop with applications and input/output support for all
supported locales in Fedora (this one is part of the 'spin-kickstarts'
package) - despite the name, this is the kickstart that generates the
~1GB-sized images for recent releases.
* For _Fedora 21 and later_:
*https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/fedora-live-workstation.ks[fedora-live-workstation.ks]*
- this is the Workstation product configuration.
_kickstart_ files for other spins (e.g. Fedora Electronics Lab) can be
found in after installing the 'spin-kickstarts' package. These pre-made
configuration files can be a great place to start, as they already have
some useful pre and post-installation scripts.
image:system-config-kickstart.png[system-config-kickstart,title="fig:system-config-kickstart"]
You can create a customized _kickstart_ file by running . Note that you
might have to install the package first with in Fedora 22 and beyond or
in earlier versions of Fedora. This tool is mainly intended for
generating kickstart files for automated installs, not live images, so
the output will probably not be usable without editing, but it may help
you to generate particular kickstart directives. Remember to add the
line:
....
%include /usr/share/spin-kickstarts/fedora-live-base.ks
....
at the beginning of your _kickstart_ file to include the base live
configuration.
[[making-the-image]]
Making the image
~~~~~~~~~~~~~~~~
To make the image, simply issue the following command:
....
livecd-creator --verbose \
--config=/path/to/kickstart/file.ks \
--fslabel=Image-Label \
--cache =/var/cache/live
....
The name given by _--fs-label_ is used:
* as a file system label on the ext3 and iso9660 file systems (As such,
it's visible on the desktop as the CD name).
* in the _isolinux_ boot loader.
If you have the repositories available locally and don't want to wait
for the download of packages, just substitute the URLs listed in the
configuration file to point to your local repositories.
[[examples]]
Examples
~~~~~~~~
[[spinning-the-fedora-desktop]]
Spinning the fedora desktop
^^^^^^^^^^^^^^^^^^^^^^^^^^^
The following command:
....
livecd-creator --verbose \
--config=/usr/share/spin-kickstarts/fedora-live-workstation.ks \
--fslabel=Fedora-LiveCD \
--cache=/var/cache/live
....
will create a live CD called "Fedora-LiveCD" using the
*fedora-live-workstation.ks* configuration file.
[[a-barebones-live-cd]]
A Barebones Live CD
^^^^^^^^^^^^^^^^^^^
The command
....
livecd-creator --verbose \
--config=/usr/share/doc/livecd-tools-`rpm -q livecd-tools --qf "%{VERSION}"`/livecd-fedora-minimal.ks \
--cache=/var/cache/live
....
will create a live CD that will boot to a login prompt.
[[testing-your-live-cd-using-kvm-or-qemu]]
Testing your Live CD using KVM or qemu
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
image:Screenshot_qemu_gtk3.png[QEMU running Fedora
17,title="QEMU running Fedora 17"]
As root:
`qemu-kvm -m 2048 -vga qxl -cdrom filename.iso`
If you do not have Wikipedia:Kernel-based_Virtual_Machine[ KVM] support,
you have to use qemu instead
`qemu-system-x86_64 -m 2048 -vga qxl -cdrom filename.iso`
Replace *filename.iso* with the name of your created Live CD image and
*qemu-system-x86_64* with an appropriate qemu binary for the target
system, e.g *qemu-system-i386*.
[[using-your-new-live-image]]
Using your new live image
~~~~~~~~~~~~~~~~~~~~~~~~~
You can http://docs.fedoraproject.org/readme-burning-isos/[burn your
image directly to a CD or a DVD] if it fits, or you can
link:How_to_create_and_use_Live_USB[ write it to a USB stick].
[[live-image-media-verification]]
Live Image Media Verification
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The live image can incorporate functionality to verify itself. To do so,
you need to have *isomd5sum* installed both on the system used for
creating the image and installed into the image. This is so that the
*implantisomd5* and *checkisomd5* utilities can be used. These utilities
take advantage of embedding an md5sum into the application area of the
iso9660 image. This then gets verified before mounting the real root
filesystem.
[[other-resources]]
Other Resources
~~~~~~~~~~~~~~~
* A link:Classroom[ Fedora Classroom] class covering
link:Classroom/Creating_Fedora_Remix[ creating Fedora remixes].
* If you are distributing your spin you need to be concerned about
link:JeroenVanMeeuwen/Revisor/FedoraRebrandRemixGuidelines[ trademark
usage and GPL responsibilities].
Category:Spins Category:LiveMedia
'''
See a typo, something missing or out of date, or anything else which can be
improved? Edit this document at https://pagure.io/fedora-docs/quick-docs.

11
en-US/creating-and-using-a-live-installation-image.adoc Normal file
View file

@ -0,0 +1,11 @@
= Creating and using a live installation image
include::modules/proc_downloading-fedora.adoc[leveloffset=+1]
include::modules/proc_creating-and-using-live-usb.adoc[leveloffset=+1]
include::modules/proc_booting-from-usb-sticks.adoc[leveloffset=+1]
include::modules/proc_troubleshooting-live-usb.adoc[leveloffset=+1]
include::modules/proc_creating-and-using-live-cd.adoc[leveloffset=+1]

0
en-US/images/Screenshot_qemu_gtk3.png → en-US/images/qemu_gtk3.png
View file

Side by side Swipe Overlay

Before

Width:  |  Height:  |  Size: 8 KiB

After

Width:  |  Height:  |  Size: 8 KiB

14
en-US/modules/proc_booting-from-usb-sticks.adoc
View file

@ -1,5 +1,6 @@
[id='booting_from_USB_sticks']
== Booting from USB sticks
= Booting from USB sticks
Almost all modern PCs can boot from USB sticks. However, how you tell the system to boot from a USB stick varies substantially from system to system. Initially, you can try this:
. Power off the computer.
@ -21,14 +22,16 @@ IMPORTANT: Your computer could become unbootable or lose functionality if you ch
If your system has a UEFI firmware, it will usually allow you to boot the stick in UEFI native mode or BIOS compatibility mode. If you boot in UEFI native mode and perform a Fedora installation, you will get a UEFI native Fedora installation. If you boot in BIOS compatibility mode and perform a Fedora installation, you will get a BIOS compatibility mode Fedora installation.
For more information on all this, see the http://fedoraproject.org/wiki/Unified_Extensible_Firmware_Interface[UEFI page]. USB sticks written from `x86_64` images with link:using-fedora-media-writer[Fedora Media Writer], `GNOME Disk Utility`, dd, other dd-style utilities, and link:how-to-create-and-use-a-live-CD[livecd-iso-to-disk] with --efi should be UEFI native bootable. Sticks written with other utilities may not be UEFI native bootable, and sticks written from i686 images will never be UEFI bootable.
For more information on all this, see the http://fedoraproject.org/wiki/Unified_Extensible_Firmware_Interface[UEFI page]. USB sticks written from x86_64 images with link:using-fedora-media-writer[Fedora Media Writer], GNOME Disk Utility, `dd`, other dd-style utilities, and link:proc_creating-and-using-live-cd.html[Creating and using live CD] with the --efi option specified, should be UEFI native bootable. Sticks written with other utilities may not be UEFI native bootable, and sticks written from i686 images will never be UEFI bootable.
[id='identifying_stick']
== Identifying a stick on Linux
Most of the writing methods will require you to know the `/dev` name for your USB stick, e.g. `/dev/sdc`, when using them on Linux. You do not need to know this in order to use `Fedora Media Writer`. To find this out:
Most of the writing methods will require you to know the `/dev` name for your USB stick, e.g. `/dev/sdc`, when using them on Linux. You do not need to know this in order to use Fedora Media Writer. To find this out:
. Insert the USB stick into a USB port.
. Open a terminal and run dmesg.
. Open a terminal and run `dmesg`.
. Near the end of the output, you will see something like:
+
[options="nowrap"]
@ -40,4 +43,5 @@ Most of the writing methods will require you to know the `/dev` name for your US
[NOTE]
====
This is the name of the disk you will use. We'll call it `sdX` from now on. If you have connected more than one USB stick to the system, be careful that you identify the correct one, often you will see a manufacturer name or capacity in the output which you can use to make sure you identified the correct stick.
This is the name of the disk you will use. We'll call it `sdX` from now on. If you have connected more than one USB stick to the system, be careful that you identify the correct one, often you will see a manufacturer name or capacity in the output which you can use to make sure you identified the correct stick.
====

168
en-US/modules/proc_create-and-use-livecd.adoc
View file

@ -1,168 +0,0 @@
[id='how-to-create-and-use-a-live-CD']
= How to create and use a live CD
[[getting-started]]
== Getting started
To create a live image, the `livecd-creator` tool is used. For this, super user
privileges are needed.
The `livecd-creator` tool is part of the `livecd-tools` package. If it
is not installed on your system, add it with link:dnf[DNF] or
link:yum[YUM]:
If you are using `yum`:
[options="nowrap"]
----
su -c 'yum install livecd-tools spin-kickstarts' #Versions prior to Fedora 22
----
If you are using `dnf`:
[options="nowrap"]
----
su -c 'dnf install livecd-tools spin-kickstarts' #Fedora 22 and beyond
----
If you are interested in localized (i.e. translated into other
languages) live CD files, install also *l10n-kickstarts*.
[id='configuring-the-image']
== Configuring the image
The configuration of the live image is defined by a file called
_kickstart_. It can include some basic system configuration items, the
package manifest and a script to be run at the end of the build process.
For the Fedora project, the most important live image configurations
files are:
* *https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/fedora-live-base.ks[fedora-live-base.ks]*
: The base live image system, included in the `livecd-tools` package.
* For _Fedora 20 and earlier_:
*https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/fedora-livecd-desktop.ks[fedora-livecd-desktop.ks]*
: Complete desktop with applications and input/output support for all
supported locales in Fedora. This one is part of the `spin-kickstarts`
package. Despite the name, this is the kickstart that generates the
~1GB-sized images for recent releases.
* For _Fedora 21 and later_:
*https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/fedora-live-workstation.ks[fedora-live-workstation.ks]*. This is the Workstation product configuration.
_kickstart_ files for other spins, e.g. Fedora Electronics Lab, can be
found in `/usr/share/spin-kickstarts/` after installing the `spin-kickstarts` package. These pre-made
configuration files can be a great place to start, as they already have
some useful pre and post-installation scripts.
image:system-config-kickstart.png[system-config-kickstart,title="fig:system-config-kickstart"]
You can create a customized _kickstart_ file by running `system-config-kickstart`.
[NOTE]
====
You might have to install the package first with `su -c "dnf install system-config-kickstart"` in Fedora 22 and beyond or `su -c "yum install system-config-kickstart"` in earlier versions of Fedora. This tool is mainly intended for generating kickstart files for automated installs, not live images, so the output will probably not be usable without editing, but it may help you to generate particular kickstart directives. Remember to add the line `%include /usr/share/spin-kickstarts/fedora-live-base.ks` at the beginning of your _kickstart_ file to include the base live configuration.
====
[id='making-the-image']
== Making the image
To make the image, simply issue the following command:
[options="nowrap"]
----
livecd-creator --verbose \
--config=/path/to/kickstart/file.ks \
--fslabel=Image-Label \
--cache =/var/cache/live
----
The name given by _--fs-label_ is used:
* As a file system label on the ext3 and iso9660 file systems. As such,
it's visible on the desktop as the CD name.
* In the _isolinux_ boot loader.
If you have the repositories available locally and don't want to wait
for the download of packages, just substitute the URLs listed in the
configuration file to point to your local repositories.
[NOTE]
====
If you have an x86_64 machine you're building on but you want a 32-bit happy iso image, add the following before your livecd-creator command:
[options="nowrap"]
----
setarch i686 livecd-creator [...]
----
====
[id='examples']
== Examples
[id='spinning-the-fedora-desktop']
=== Spinning the fedora desktop
The following command:
[options="nowrap"]
----
livecd-creator --verbose \
--config=/usr/share/spin-kickstarts/fedora-live-workstation.ks \
--fslabel=Fedora-LiveCD \
--cache=/var/cache/live
----
This will create a live CD called `Fedora-LiveCD` using the
*fedora-live-workstation.ks* configuration file.
[id='a-barebones-live-cd']
=== A Barebones live CD
The following command:
[options="nowrap"]
----
livecd-creator --verbose \
--config=/usr/share/doc/livecd-tools-`rpm -q livecd-tools --qf "%{VERSION}"`/livecd-fedora-minimal.ks \
--cache=/var/cache/live
----
This will create a live CD that will boot to a login prompt.
[id='testing-your-live-cd-using-kvm-or-qemu']
== Testing your live CD using KVM or qemu
image:Screenshot_qemu_gtk3.png[QEMU running Fedora
17,title="QEMU running Fedora 17"]
As root:
[options="nowrap"]
----
qemu-kvm -m 2048 -vga qxl -cdrom filename.iso
----
[NOTE]
====
If you do not have https://en.wikipedia.org/wiki/Kernel-based_Virtual_Machine[KVM] support, you have to use qemu instead.
[options="nowrap"]
----
qemu-system-x86_64 -m 2048 -vga qxl -cdrom filename.iso
----
====
Replace _filename.iso_ with the name of your created Live CD image and
_qemu-system-x86_64_ with an appropriate qemu binary for the target
system, e.g *qemu-system-i386*.
[id='using-your-new-live-image']
== Using your new live image
You can http://docs.fedoraproject.org/readme-burning-isos/[burn your
image directly to a CD or a DVD] if it fits, or you can
link:how_to_create_and_use_live_USB[write it to a USB stick].
[id='live-image-media-verification']
== Live image media verification
The live image can incorporate functionality to verify itself. To do so,
you need to have *isomd5sum* installed both on the system used for
creating the image and installed into the image. This is so that the
*implantisomd5* and *checkisomd5* utilities can be used. These utilities
take advantage of embedding an `md5sum` into the application area of the
`iso9660` image. This then gets verified before mounting the real root
filesystem.

146
en-US/modules/proc_creating-and-using-live-cd.adoc Normal file
View file

@ -0,0 +1,146 @@
[id='proc_creating-and-using-live-cd']
= Creating and using live CD
#FIXME# Needs modularization
[[getting-started]]
== Getting started
To create a live image, the `livecd-creator` tool is used. For this, super user privileges are needed.
The `livecd-creator` tool is part of the _livecd-tools_package. If it is not installed on your system, add it with DNF:
[options="nowrap"]
----
# dnf install livecd-tools spin-kickstarts
----
If you are interested in localized (i.e. translated into other languages) live CD files, install also _l10n-kickstarts_.
[id='configuring-the-image']
== Configuring the image
The configuration of the live image is defined by a file called _kickstart_. It can include some basic system configuration items, the package manifest, and a script to be run at the end of the build process.
For the Fedora project, the most important live image configurations files are:
* https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/fedora-live-base.ks[fedora-live-base.ks]
: The base live image system, included in the _livecd-tools_ package.
* For _Fedora 20 and earlier_: https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/fedora-livecd-desktop.ks[fedora-livecd-desktop.ks]
: Complete desktop with applications and input/output support for all supported locales in Fedora. This one is part of the `spin-kickstarts` package. Despite the name, this is the kickstart that generates the ~1GB-sized images for recent releases.
* For _Fedora 21 and later_: https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/fedora-live-workstation.ks[fedora-live-workstation.ks]. This is the Workstation product configuration.
_kickstart_ files for other spins, e.g. Fedora Electronics Lab, can be found in `/usr/share/spin-kickstarts/` after installing the `spin-kickstarts` package. These pre-made configuration files can be a great place to start, as they already have some useful pre and post-installation scripts.
image:system-config-kickstart.png[system-config-kickstart,title="fig:system-config-kickstart"]
You can create a customized _kickstart_ file by running `system-config-kickstart`.
[NOTE]
====
You might have to install the package first with `dnf install system-config-kickstart` in Fedora 22 and beyond or `yum install system-config-kickstart` in earlier versions of Fedora. This tool is mainly intended for generating kickstart files for automated installs, not live images, so the output will probably not be usable without editing, but it may help you to generate particular kickstart directives. Remember to add the line `%include /usr/share/spin-kickstarts/fedora-live-base.ks` at the beginning of your _kickstart_ file to include the base live configuration.
====
[id='making-the-image']
== Making the image
To make the image, simply issue the following command:
[options="nowrap"]
----
livecd-creator --verbose \
--config=/path/to/kickstart/file.ks \
--fslabel=Image-Label \
--cache =/var/cache/live
----
The name given by `--fs-label` is used:
* As a file system label on the ext3 and iso9660 file systems. As such, it's visible on the desktop as the CD name.
* In the _isolinux_ boot loader.
If you have the repositories available locally and don't want to wait for the download of packages, just substitute the URLs listed in the configuration file to point to your local repositories.
[NOTE]
====
If you have an x86_64 machine you're building on but you want a 32-bit happy iso image, add the following before your livecd-creator command:
[options="nowrap"]
----
setarch i686 livecd-creator [...]
----
====
[id='examples']
== Examples
[id='spinning-the-fedora-desktop']
=== Spinning the Fedora desktop
The following command:
[options="nowrap"]
----
livecd-creator --verbose \
--config=/usr/share/spin-kickstarts/fedora-live-workstation.ks \
--fslabel=Fedora-LiveCD \
--cache=/var/cache/live
----
This will create a live CD called *Fedora-LiveCD* using the `fedora-live-workstation.ks` configuration file.
[id='a-barebones-live-cd']
=== A Barebones live CD
The following command:
[options="nowrap"]
----
livecd-creator --verbose \
--config=/usr/share/doc/livecd-tools-$(rpm -q livecd-tools --qf "%{VERSION}")/livecd-fedora-minimal.ks \
--cache=/var/cache/live
----
This will create a live CD that will boot to a login prompt.
[id='testing-your-live-cd-using-kvm-or-qemu']
== Testing your live CD using KVM or qemu
image:qemu_gtk3.png[QEMU running Fedora 17,title="QEMU running Fedora 17"]
As root:
[options="nowrap"]
----
# qemu-kvm -m 2048 -vga qxl -cdrom filename.iso
----
[NOTE]
====
If you do not have https://en.wikipedia.org/wiki/Kernel-based_Virtual_Machine[KVM] support, you have to use qemu instead.
[options="nowrap"]
----
# qemu-system-x86_64 -m 2048 -vga qxl -cdrom filename.iso
----
====
Replace `_filename.iso_` with the name of your created Live CD image and `_qemu-system-x86_64_` with an appropriate qemu binary for the target system, e.g. `qemu-system-i386`.
[id='using-your-new-live-image']
== Using your new live image
You can http://docs.fedoraproject.org/readme-burning-isos/[burn your image directly to a CD or a DVD] if it fits, or you can link:#proc_creating-and-using-live-usb[write it to a USB stick].
[id='live-image-media-verification']
== Live image media verification
The live image can incorporate functionality to verify itself. To do so, you need to have _isomd5sum_ installed both on the system used for creating the image and installed into the image. This is so that the `implantisomd5` and `checkisomd5` utilities can be used. These utilities take advantage of embedding an _md5sum_ into the application area of the iso9660 image. This then gets verified before mounting the real root filesystem.

72
en-US/modules/proc_create-and-use-liveusb.adoc → en-US/modules/proc_creating-and-using-live-usb.adoc
View file

@ -1,8 +1,13 @@
[id='how_to_create_live_USB']
= How to create Live USB
:experimental:
[id='proc_creating-and-using-live-usb']
= Creating and using live USB
You can write all Fedora ISO images to a USB stick, making this a convenient way on any USB-bootable computer to either install Fedora or try a *live* Fedora environment without writing to the computer's hard disk. You will need a USB stick at least as large as the image you wish to write.
#FIXME# Needs modularization
[id='using-fedora-media-writer']
== Using Fedora Media Writer
@ -10,7 +15,7 @@ The best tool to create a Fedora USB stick is the https://github.com/MartinBriza
[IMPORTANT]
====
This method will destroy all data on the USB stick. If you need a non-destructive write method (to preserve existing data on your USB stick) and/or support for 'data persistence', you can use the xref:[livecd-iso-to-disk] utility on Fedora.
This method will destroy all data on the USB stick. If you need a non-destructive write method (to preserve existing data on your USB stick) or support for 'data persistence', you can use the link:using-the-livecd-iso-to-disk-tool[livecd-iso-to-disk] utility on Fedora.
====
Fedora Media Writer is graphical and easy to use. It can download recent Fedora images for you as well as writing them to the USB stick.
@ -19,12 +24,12 @@ On Fedora, you can use a Fedora graphical software installation tool to install
[options="nowrap"]
----
su -c 'dnf install mediawriter'
# dnf install mediawriter
----
On Windows and macOS, you can download the installer from the https://github.com/MartinBriza/MediaWriter/releases[releases page]. On other Linux distributions, if they support the https://flatpak.org/[Flatpak] application distribution system, you can download a flatpak from the https://github.com/MartinBriza/MediaWriter/releases[releases page].
To run the tool, look for `Fedora Media Writer` in the system menus. When you start `Fedora Media Writer`, the three dots at the bottom will be flashing while the tool checks for a new Fedora release.
To run the tool, look for *Fedora Media Writer* in the system menus. When you start Fedora Media Writer, the three dots at the bottom will be flashing while the tool checks for a new Fedora release.
To write the stick:
@ -40,23 +45,28 @@ On the title screen, you can choose Workstation, Server or your own .iso file. O
After writing, your USB stick will have a changed partition layout and some systems may report it to be about 10MB large. To return your USB stick to its factory configuration, insert the drive again while `Fedora Media Writer` is running. The application provides you with an option to restore to the factory layout. This layout includes a single `VFAT` partition.
[id='gnome-disk-utility']
== Using GNOME Disk Utility
IMPORTANT: This method will destroy all data on the USB stick. If you need a non-destructive write method (to preserve existing data on your USB stick) and/or support for 'data persistence', you can use the `livecd-iso-to-disk` utility on Fedora.
This method is for people running Linux, or another unix with GNOME, Nautilus and the GNOME Disk Utility installed. Particularly, if you are using a distribution other than Fedora which does not support Flatpak, this may be the easiest available method. A standard installation of Fedora, or a standard GNOME installation of many other distributions, should be able to use this method. On Fedora, ensure the packages `Package-x-generic-16.pngnautilus` and `Package-x-generic-16.pnggnome-disk-utility` are installed. Similar graphical `direct-write tools` may be available for other desktops, or you may use the command line `direct write` method.
This method is for people running Linux, or another unix with GNOME, Nautilus and the GNOME Disk Utility installed. Particularly, if you are using a distribution other than Fedora which does not support Flatpak, this may be the easiest available method. A standard installation of Fedora, or a standard GNOME installation of many other distributions, should be able to use this method. On Fedora, ensure the packages _nautilus_ and _gnome-disk-utility_ are installed. Similar graphical direct-write tools may be available for other desktops, or you may use the command-line _direct write_ method.
. Download a Fedora image, choose a USB stick that does not contain any data you need, and connect it.
. Run Nautilus (Files) for instance, open the *Overview* by pressing the *Start/Super* key, and type Files, then hit enter.
. Run Nautilus (Files), open the *Overview* by pressing the *Start/Super* key, type Files, and hit kbd:[Enter].
. Find the downloaded image, right-click on it, go to *Open With*, and click *Disk Image Writer*.
. Select your USB stick as the *Destination*, and click *Start Restoring*.
[id='command-line-method']
== Command line methods
=== Using the livecd-iso-to-disk tool
IMPORTANT: This method will destroy all data on the USB stick _if the *--format* parameter is passed_.
[id='using-the-livecd-iso-to-disk-tool']
=== Using the livecd-iso-to-disk tool
IMPORTANT: This method will destroy all data on the USB stick _if the `--format` parameter is passed_.
The `livecd-iso-to-disk` method is slightly less reliable than Fedora Media Writer and can be used reliably only from within Fedora: it does not work in Windows or OS X, and is not supported (and will usually fail) in non-Fedora distributions. However, it supports three advanced features which FMW does not include:
@ -68,53 +78,59 @@ By combining these features, you can carry your computer with you in your pocket
It is not a good idea to try and write a new Fedora release using the version of `livecd-iso-to-disk` in a much older Fedora release: it is best to only use a release a maximum of two versions older than the release you are trying to write.
Ensure the https://apps.fedoraproject.org/packages/livecd-tools[livecd-tools] package is installed: `su -c 'dnf install livecd-tools'`.
Ensure the https://apps.fedoraproject.org/packages/livecd-tools[livecd-tools] package is installed: `dnf install livecd-tools`.
[NOTE]
[NOTE]
====
Remember to identify your USB stick's device name first. In all cases, you can add the parameter `--efi` to render the stick bootable in native UEFI mode. Detailed usage information is available by running: `livecd-iso-to-disk --help` or `man livecd-iso-to-disk`.
To make an existing USB stick bootable as a Fedora image, without deleting any of the data on it, make sure that the USB drive is not mounted before executing the following, and give the root password when prompted:
[option="nowrap"]
----
su -c "livecd-iso-to-disk Fedora-Workstation-Live-x86_64-28-1.1.iso /dev/sdX"
# livecd-iso-to-disk Fedora-Workstation-Live-x86_64-28-1.1.iso /dev/sdX
----
In case it is not possible to boot from a disk created with the method shown above, before re-partitioning and re-formatting, often resetting the master boot record will enable booting:
[option="nowrap"]
----
su -c "livecd-iso-to-disk --reset-mbr Fedora-Workstation-Live-x86_64-28-1.1.iso /dev/sdX"
# livecd-iso-to-disk --reset-mbr Fedora-Workstation-Live-x86_64-28-1.1.iso /dev/sdX
----
====
IMPORTANT: Using the `--format` option in the following command will erase all data on the USB drive.
If necessary, you can have livecd-iso-to-disk re-partition and re-format the target stick:
If necessary, you can have `livecd-iso-to-disk` re-partition and re-format the target stick:
[option="nowrap"]
----
su -c "livecd-iso-to-disk --format --reset-mbr Fedora-Workstation-Live-x86_64-28-1.1.iso /dev/sdX"
# livecd-iso-to-disk --format --reset-mbr Fedora-Workstation-Live-x86_64-28-1.1.iso /dev/sdX
----
To include a persistent filesystem for `/home`, use the `--home-size-mb` parameter. For example:
[option="nowrap"]
----
su -c "livecd-iso-to-disk --home-size-mb 2048 Fedora-Workstation-Live-x86_64-28-1.1.iso /dev/sdX"
# livecd-iso-to-disk --home-size-mb 2048 Fedora-Workstation-Live-x86_64-28-1.1.iso /dev/sdX
----
This will create a 2 GiB filesystem that will be mounted as `/home` each time the stick is booted, allowing you to preserve data in `/home` across boots.
To enable 'data persistence' support - so changes you make to the entire live environment will persist across boots - add the `--overlay-size-mb` parameter to add a persistent data storage area to the target stick. For example:
[option="nowrap"]
----
su -c "livecd-iso-to-disk --overlay-size-mb 2048 Fedora-Workstation-Live-x86_64-28-1.1.iso /dev/sdX"
# livecd-iso-to-disk --overlay-size-mb 2048 Fedora-Workstation-Live-x86_64-28-1.1.iso /dev/sdX
----
Here, _2048_ is the desired size (in megabytes) of the overlay. The `livecd-iso-to-disk` tool will not accept an overlay size value greater than _4095_ for VFAT, but for ext[234] filesystems it is only limited by the available space.
Here, `_2048_` is the desired size (in megabytes) of the overlay. The `livecd-iso-to-disk` tool will not accept an overlay size value greater than _4095_ for VFAT, but for ext[234] filesystems it is only limited by the available space.
[NOTE]
====
Due to the way it's currently implemented, every single change to this form of overlay, writes AND deletes, subtracts from its free space so it will eventually be "used up" and your USB stick will no longer boot. You can use `dmsetup` status `live-rw` to see how much space remains in the overlay.
The output will contain something like snapshot `42296/204800`, indicating that 4229` of 204800 512-byte sectors are allocated. Because of these limitations, it is advisable to use the `system-level` persistence sparingly, for configuration changes and important security updates only. Or, if you have sufficient disk space available, changes to the `LiveOS` root filesystem snapshot can be merged into a new copy of the root filesystem.
The output will contain something like snapshot `42296/204800`, indicating that 4229 of 204800 512-byte sectors are allocated. Because of these limitations, it is advisable to use the `system-level` persistence sparingly, for configuration changes and important security updates only. Or, if you have sufficient disk space available, changes to the `LiveOS` root filesystem snapshot can be merged into a new copy of the root filesystem.
====
You can combine `--home-size-mb` and `--overlay-size-mb`, in which case data written to `/home` will not exhaust the persistent overlay.
@ -127,28 +143,29 @@ You can combine `--home-size-mb` and `--overlay-size-mb`, in which case data wri
This method will destroy all data on the USB stick. If you need a non-destructive write method, to preserve existing data on your USB stick, and/or support for `data persistence`, you can use the `livecd-iso-to-disk` utility on Fedora.
====
This method directly writes the image to the USB stick much like link:using-fedora-media-writer[Fedora Media Writer] or GNOME Disk Utility, but uses a command line utility named `dd`. Like the other _direct write_ methods, it will destroy all data on the stick and does not support any of the advanced features like data persistence, but it is a very reliable method. The `dd` tool is available on most Unix-like operating systems, including Linux distributions and OS X, and a Windows port is available. This may be your best method if you cannot use link:using-fedora-media-writer[Fedora Media Writer] or GNOME Disk Utility, or just if you prefer command line utilities and want a simple, quick way to write a stick.
This method directly writes the image to the USB stick much like link:#using-fedora-media-writer[Fedora Media Writer] or GNOME Disk Utility, but uses a command line utility named `dd`. Like the other _direct write_ methods, it will destroy all data on the stick and does not support any of the advanced features like data persistence, but it is a very reliable method. The `dd` tool is available on most Unix-like operating systems, including Linux distributions and OS X, and a Windows port is available. This may be your best method if you cannot use link:#using-fedora-media-writer[Fedora Media Writer] or GNOME Disk Utility, or just if you prefer command line utilities and want a simple, quick way to write a stick.
. Identify the name of the USB drive partition. If using this method on Windows, with the port linked above, the `dd --list` command should provide you with the correct name.
. *Unmount all mounted partition from that device*. This is very important, otherwise the written image might get corrupted. You can umount all mounted partitions from the device with `umount /dev/sdX*`, where _X_ is the appropriate letter, e.g. `umount /dev/sdc*`.
. *Unmount all mounted partition from that device*. This is very important, otherwise the written image might get corrupted. You can umount all mounted partitions from the device with `umount /dev/sdX*`, where `_X_` is the appropriate letter, e.g. `umount /dev/sdc*`.
. Write the ISO file to the device:
+
[options="nowrap"]
----
su -c 'dd if=/path/to/image.iso of=/dev/sdX bs=8M status=progress oflag=direct'
# dd if=/path/to/image.iso of=/dev/sdX bs=8M status=progress oflag=direct
----
. Wait until the command completes.
+
NOTE: If you see `dd: invalid status flag: 'progress'`, your dd version doesn't support the `status=progress` option and you'll need to remove it. In this case, you won't see writing progress.
[id='unetbootin']
== Using UNetbootin for Windows, OS X and Linux
== Using UNetbootin for Windows, OS X, and Linux
[NOTE]
====
UNetbootin may work in some cases but not others - for instance, it will likely create a stick that is bootable in BIOS mode, but not UEFI mode. Fedora cannot guarantee support for UNetbootin-written images.
While your results may vary, it is usually the case that the Fedora Media Writer, livecd-iso-to-disk, GNOME and dd methods give better results than UNetbootin. If you encounter problems with UNetbootin, please contact the UNetbootin developers, not the Fedora developers.
While your results may vary, it is usually the case that the Fedora Media Writer, `livecd-iso-to-disk`, GNOME, and `dd` methods give better results than UNetbootin. If you encounter problems with UNetbootin, please contact the UNetbootin developers, not the Fedora developers.
====
http://unetbootin.github.io/[UNetbootin] is a graphical, bootable USB image creator. Using it will allow you to preserve any data you have in the USB drive. If you have trouble booting, however, you may wish to try with a blank, cleanly FAT32-formatted drive.
@ -163,12 +180,13 @@ NOTE: If you are running a 64-bit Linux distribution, UNetbootin may fail to run
NOTE: If you do not see _sdX_ listed, you might have to reformat the drive. You can do this from most file manager or disk utility tools, e.g. the GNOME disk utility ("Disks") on Fedora. The FAT32 format is most likely to result in a bootable stick. This will cause you to lose all data on the drive.
[id='creating_usb_stick_from_a_running_live_environment']
== Creating a USB stick from a running live environment
If you are already running a live CD, DVD, or USB and want to convert that into a bootable USB stick, run the following command:
[option="nowrap"]
----
su -c "livecd-iso-to-disk /run/initramfs/livedev /dev/sdX"
# livecd-iso-to-disk /run/initramfs/livedev /dev/sdX"
----

35
en-US/modules/proc_troubleshooting-live-usb.adoc
View file

@ -1,10 +1,10 @@
[id='troubleshooting_live_USB']
= Troubleshooting a live USB
== livecd-iso-to-disk problems
Partition isn't marked bootable::
If you get the message `Partition isn't marked bootable!`, you need to mark the partition bootable. To do this, run `su -c 'parted /dev/sdX'`, and use the `toggle N` boot command, where X is the appropriate letter and N is the partition number. For example:
Partition isn't marked bootable:: If you get the message `Partition isn't marked bootable!`, you need to mark the partition bootable. To do this, run `parted /dev/sdX`, and use the `toggle N` boot command, where `_X_` is the appropriate letter, and `_N_` is the partition number. For example:
+
[option="nowrap"]
----
@ -12,17 +12,17 @@ $ parted /dev/sdb
GNU Parted 1.8.6
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
(parted) print
Model: Imation Flash Drive (scsi)
Disk /dev/sdX: 1062MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 1062MB 1062MB primary fat16
1 32.3kB 1062MB 1062MB primary fat16
(parted) toggle 1 boot
(parted) print
(parted) print
Model: Imation Flash Drive (scsi)
Disk /dev/sdX: 1062MB
Sector size (logical/physical): 512B/512B
@ -31,31 +31,30 @@ Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 1062MB 1062MB primary fat16 boot
(parted) quit
Information: Don't forget to update /etc/fstab, if necessary.
(parted) quit
Information: Don't forget to update /etc/fstab, if necessary.
----
Partitions need a filesystem label::
If you get the message `Need to have a filesystem label` or `UUID` for your USB device, you need to label the partition: `su -c "dosfslabel /dev/sdX LIVE"`.
Partitions need a filesystem label:: If you get the message `Need to have a filesystem label` or `UUID` for your USB device, you need to label the partition: `dosfslabel /dev/sdX LIVE`.
Partition has different physical/logical endings::
If you get this message from fdisk, you may need to reformat the flash drive when writing the image, by passing `--format` when writing the stick.
Partition has different physical/logical endings:: If you get this message from fdisk, you may need to reformat the flash drive when writing the image, by passing `--format` when writing the stick.
MBR appears to be blank::
If your test boot reports a corrupted boot sector, or you get the message `MBR appears to be blank.`, you need to install or reset the master boot record (MBR), by passing `--reset-mbr` when writing the stick.
MBR appears to be blank:: If your test boot reports a corrupted boot sector, or you get the message `MBR appears to be blank.`, you need to install or reset the master boot record (MBR), by passing `--reset-mbr` when writing the stick.
livecd-iso-to-disk on other Linux distributions:: `livecd-iso-to-disk` is not meant to be run from a non-Fedora system. Even if it happens to run and write a stick apparently successfully from some other distribution, the stick may well fail to boot. Use of `livecd-iso-to-disk` on any distribution other than Fedora is unsupported and not expected to work: please use an alternative method, such as link:#using-fedora-media-writer[Fedora Media Writer].
livecd-iso-to-disk on other Linux distributions::
`livecd-iso-to-disk` is not meant to be run from a non-Fedora system. Even if it happens to run and write a stick apparently successfully from some other distribution, the stick may well fail to boot. Use of `livecd-iso-to-disk` on any distribution other than Fedora is unsupported and not expected to work: please use an alternative method, such as xref:using-fedora-media-writer[Fedora Media Writer].
== Testing a USB stick using qemu
You can test your stick using QEMU.
[options="nowrap"]
----
su -c 'umount /dev/sdX1'
qemu -hda /dev/sdX -m 1024 -vga std
# umount /dev/sdX1
$ qemu -hda /dev/sdX -m 1024 -vga std
----
== Mounting a Live USB filesystem
You can use the https://github.com/livecd-tools/livecd-tools/blob/master/tools/liveimage-mount[liveimage-mount] script in the https://apps.fedoraproject.org/packages/livecd-tools[livecd-tools] package to mount an attached Live USB device or other LiveOS image, such as an ISO or Live CD. This is convenient when you want to copy in or out some file from the LiveOS filesystem on a Live USB, or just examine the files in a Live ISO or Live CD.
You can use the https://github.com/livecd-tools/livecd-tools/blob/master/tools/liveimage-mount[liveimage-mount] script in the https://apps.fedoraproject.org/packages/livecd-tools[livecd-tools] package to mount an attached Live USB device or other LiveOS image, such as an ISO or Live CD. This is convenient when you want to copy in or out some file from the LiveOS filesystem on a Live USB, or just examine the files in a Live ISO or Live CD.