Abstract
Third-party software
Example 1. Resuming a download with wget
wget
can resume interrupted downloads. A command such as the one below will download a Fedora image, and can be executed again to continue the download if needed.
wget --continue http://download.fedoraproject.org/pub/fedora/linux/releases/19/Fedora/x86_64/Fedora-19-x86_64-netinst.iso
spin
ISO image files, or as a netinstall
image. Refer to the Fedora Live Images guide at http://docs.fedoraproject.org to learn more about spins.
Table 1. Comparing image types
Image type | Features | |||
---|---|---|---|---|
DVD image |
| |||
netinstall image |
| |||
Spin images |
|
File size limits
FAT32
, cannot handle large files like the DVD image. If downloading with such a system, you should choose a smaller image.
Fedora
, the release version, the image's target architecture, and the type of image.
Example 2. Filenames
Fedora-Live-Desktop-x86_64-19-1.iso
Fedora-Live-Desktop-i686-19-1.iso
Fedora-19-x86_64-netinst.iso
i386
for 32-bit PCs, including the Pentium and Athlon processor families. The architecture is usually x86_64
for 64-bit PCs, including the Athlon 64 processor family. The architecture is usually ppc
for PowerPC computers, including most of Apple's Macintosh offerings before they began using Intel chips in the MacBook. If in doubt, your system probably requires the x86_64
versions.
Fedora-19-i386-DVD.iso
. You may also need the CHECKSUM
file to verify that the files you have downloaded are complete and correct.
CHECKSUM
file. It contains one line for each of the available ISO files with a content verification code, called a hash, computed from the original ISO files.
BitTorrent Automatic Error Checking
Third-party software
CHECKSUM
with a text editor, such as Notepad, to display its contents. Make sure the hash displayed by the hash tool for each of the downloaded ISO files exactly matches the corresponding hash in the CHECKSUM
file.
sha256sum.exe
available from http://www.labtestproject.com/files/win/sha256sum/sha256sum.exe. If you have any problems accessing sha256sum.exe
, you can try to grab md5sum.exe
from http://etree.org/software.html. If you have downloaded md5sum.exe
be sure to substitute for the correct tool below.
sha256sum.exe
program computes and displays hashes. To use it, save sha256sum.exe
to the same directory as the ISO files. Select Run... from the Start menu and then enter cmd
for the name of the program to start a Command Prompt window. Then change into the download directory. Run sha256sum
with each ISO file like this:
cd "C:\Documents and Settings\Owner\My Documents\My Downloads\Fedora"
sha256sum.exe Fedora-19-i386-DVD.iso
CHECKSUM
with a text editor, such as Notepad, to display its contents. Make sure the hash displayed by sha256sum.exe
for each of the downloaded ISO files exactly matches the corresponding hash in the CHECKSUM
file.
CHECKSUM
with a text editor, such as TextEdit, to display its contents. Make sure the hash displayed by HashTab for each of the downloaded ISO files exactly matches the corresponding hash in the CHECKSUM
file.
shasum
command. In order to correctly validate the files, the 256-bit algorithm must be specified. Change into the directory that holds the ISO image files, then run shasum
. For example:
cd Desktop
shasum -a 256 Fedora-19-i386-DVD.iso
sha256sum
, for example:
$cd Downloads
$sha256sum Fedora-19-i386-DVD.iso
CHECKSUM
with a text editor, such as gedit or kwrite, to display its contents. Make sure the hash displayed by sha256sum for each of the downloaded ISO files exactly matches the corresponding hash in the CHECKSUM
file.
4X
as the write speed.
su -c 'yum install wodim'
wodim --devices
. This should give something like the following:
[zoglesby@zlaptop ~]$ wodim --devices wodim: Overview of accessible drives (1 found) : ------------------------------------------------------------------------- 0 dev='/dev/scd0' rwrw-- : 'TSSTcorp' 'DVD+-RW TS-T633C' -------------------------------------------------------------------------
wodim -v dev=/dev/xxx speed=4 -eject /path/to/Fedora.iso
.
Replace values
Ensure your USB media has sufficient space
Unusual USB Media
Note — This Method Is Not Destructive
Important — Enable Extra Packages for Enterprise Linux
Note — This Method Is Not Destructive
su -c 'yum -y install liveusb-creator'
liveusb-creator
on the command line. Enter the root password for your system when LiveUSB Creator prompts you for it.
Important — Enable Extra Packages for Enterprise Linux
Note — This Method Is Not Destructive
su -c 'yum -y install livecd-tools'
/dev/disk/by-label
, or use the findfs
:
su -c 'findfs LABEL="MyLabel"'
/var/log/messages
log for details:
su -c 'less /var/log/messages'
livecd-iso-to-disk
command to write the ISO image to the media:
su -c 'livecd-iso-to-disk the_image.iso /dev/sdX1'
Warning — These instructions could destroy data
Note
su -
dmesg
shortly after connecting the drive. The output will identify the device node
of the drive, in this case /dev/sdd
:
[36255.217474] usb 2-1.7: Manufacturer: Kingston [36255.217476] usb 2-1.7: SerialNumber: 0019E06B0848SK88050A1E7C [36255.218125] usb-storage 2-1.7:1.0: USB Mass Storage device detected [36255.218188] scsi7 : usb-storage 2-1.7:1.0 [36256.221078] scsi 7:0:0:0: Direct-Access Kingston DT 101 II 1.00 PQ: 0 ANSI: 2 [36256.221399] sd 7:0:0:0: Attached scsi generic sg4 type 0 [36256.222051] sd 7:0:0:0: [sdd] 3930112 512-byte logical blocks: (2.01 GB/1.87 GiB) [36256.222815] [sdd]d 7:0:0:0: [sdd] Write Protect is off [36256.222818] sd 7:0:0:0: [sdd] Mode Sense: 22 00 00 00 [36256.223547] sd 7:0:0:0: [sdd] No Caching mode page found [36256.223550] sd 7:0:0:0: [sdd] Assuming drive cache: write through [36256.226945] sd 7:0:0:0: [sdd] No Caching mode page found [36256.226947] sd 7:0:0:0: [sddsdd] Assuming drive cache: write through [36256.483172] sdd: sdd1
/dev/sdd
) and the partition name (similar to /dev/sdd1
) both appear in several lines towards the end of the output. You will use the device name, the procedure will be creating a new partition.
dd
command to transfer the boot ISO image to the USB device:
# dd if=path/image_name.iso of=device
device
is the device name for the USB flash drive. Ensure you specify the device name, not the partition name. For example:
# dd if=~/Download/Fedora-19-x86_64-DVD.iso of=/dev/sdc
Note — This Method Is Not Destructive
/dev/disk/by-label
, or use the findfs
:
su -c 'findfs LABEL="MyLabel"'
/var/log/messages
log for details:
su -c 'less /var/log/messages'
su -
to become root, and enter the root password when your system prompts you.
/tmp/livecd
as the mount point, type mkdir /tmp/livecd
and press Enter.
mount -o loop /path/to/image/file/imagefile.iso /path/to/mount/point
, where /path/to/image/file is the location of the image file that you downloaded, imagefile.iso
is the image file, and /path/to/mount/point is the mount point that you just created.
LiveOS
directory of the image that you just mounted. mount point where you just mounted the Fedora image. For example, cd /tmp/livecd/LiveOS
.
./livecd-iso-to-disk /path/to/image/file/imagefile.iso device
, where /path/to/image/file
is the location of the image file that you downloaded, imagefile.iso
is the image file, and device
is the USB media device.
Example 3. Mounting a Fedora live image file and using livecd-iso-to-disk to create live USB media
Fedora-19-i686-Live.iso
, to a folder named Downloads
in your home directory. You have a USB flash drive plugged into your computer, named /dev/sdc
, with a partition named /dev/sdc1
su -
mkdir /mnt/livecd
mount -o loop /home/Username/Downloads/Fedora-19-i686-Live.iso /mnt/livecd
LiveOS
directory of the live CD image:
cd /mnt/livecd/LiveOS
./livecd-iso-to-disk /home/Username/Downloads/Fedora-19-i686-Live.iso /dev/sdc1
Warning — These instructions could destroy data
Note
su -
dmesg
shortly after connecting the drive. The output will identify the device node
of the drive, in this case /dev/sdd
:
[36255.217474] usb 2-1.7: Manufacturer: Kingston [36255.217476] usb 2-1.7: SerialNumber: 0019E06B0848SK88050A1E7C [36255.218125] usb-storage 2-1.7:1.0: USB Mass Storage device detected [36255.218188] scsi7 : usb-storage 2-1.7:1.0 [36256.221078] scsi 7:0:0:0: Direct-Access Kingston DT 101 II 1.00 PQ: 0 ANSI: 2 [36256.221399] sd 7:0:0:0: Attached scsi generic sg4 type 0 [36256.222051] sd 7:0:0:0: [sdd] 3930112 512-byte logical blocks: (2.01 GB/1.87 GiB) [36256.222815] [sdd]d 7:0:0:0: [sdd] Write Protect is off [36256.222818] sd 7:0:0:0: [sdd] Mode Sense: 22 00 00 00 [36256.223547] sd 7:0:0:0: [sdd] No Caching mode page found [36256.223550] sd 7:0:0:0: [sdd] Assuming drive cache: write through [36256.226945] sd 7:0:0:0: [sdd] No Caching mode page found [36256.226947] sd 7:0:0:0: [sddsdd] Assuming drive cache: write through [36256.483172] sdd: sdd1
/dev/sdd
) and the partition name (similar to /dev/sdd1
) both appear in several lines towards the end of the output. You will use the device name, the procedure will be creating a new partition.
dd
command to transfer the boot ISO image to the USB device:
# dd if=path/image_name.iso of=device
device
is the device name for the USB flash drive. Ensure you specify the device name, not the partition name. For example:
# dd if=~/Download/Fedora-19-x86_64-DVD.iso of=/dev/sdc
Fedora Documentation
and the component readme-burning-isos
. The following link automatically loads this information for you: http://bugzilla.redhat.com/.
Summary
field.
Description
field and give us the details of the error or suggestion as specifically as you can. If possible, include some surrounding text so we know where the error occurs or the suggestion fits.
Document URL: Section number and name: Error or suggestion: Additional information:
Revision History | |||||
---|---|---|---|---|---|
Revision 19-1 | Sun Jul 7 2013 | ||||
| |||||
Revision 19 | Wed Jul 3 2013 | ||||
| |||||
Revision 17 | Mon May 28 2012 | ||||
| |||||
Revision 14-1 | Tue Jul 27 2010 | ||||
| |||||
Revision 13.1.0 | Mon Apr 12 2010 | ||||
|