08-27-2012
They're really not the same. Hard disks have partitions, ISO's do not. Hard disks are writable, ISO's are not.
It's possible certainly but there's not a direct translation -- you can't just boot an iso and get all your partitions, you have to have a special bootloader which arranges them for you, and then boots your system somehow in a manner it won't try to mount them again -- and it'd mean putting a ton of stuff into ram or unionfs so you don't get read-only-filesystem errors everywhere.
Besides, will your system even fit on ISO?
Last edited by Corona688; 08-27-2012 at 12:19 PM..
9 More Discussions You Might Find Interesting
1. Solaris
Hey all,
I'm a newbie to iso files and I just downloaded
the 2 iso files for *cough* ms2003 R2 *cough*
trial software. After I downloaded the iso files
I just dragged them to my burn software gui
and sure enough it burned to dvd 2 iso files.
When I attempted to boot the image using VMware... (0 Replies)
Discussion started by: bdsffl
0 Replies
2. UNIX for Dummies Questions & Answers
Good morning, I have no unix training. My daily backup failed with the following error. ' Cannot create /tmp/tape.bootimage because it already exists. I am using smit to run a rootvg and SAPvg backup. What should I do? (1 Reply)
Discussion started by: ubyankees
1 Replies
3. Linux
Hi everyone,
I want to run on VMWare the Linux XP 2010 Desktop 4.0.31 distro, Iīve downloaded the latest realese from its website (Trustverse Desktop 4.0 RC1 -build 31)-->http://www.linux-xp.com/desktop/download/.
Itīs 4.47 GB in size, but when I mount on an ISO software, the size is 2.75GB... (0 Replies)
Discussion started by: cgkmal
0 Replies
4. Linux
I just tried to run the command
kexec memtest86-4.0.iso
To boot into memtest86 using kexec.
This is the output:
Cannot determine the file type of memtest86-4.0.iso
How am I supposed to do this? (2 Replies)
Discussion started by: locoroco
2 Replies
5. Fedora
I need to boot the ultimate boot cd from an usb stick. Do I just copy the iso image to the usb key?
How do I make the usb stick bootable? (4 Replies)
Discussion started by: locoroco
4 Replies
6. Red Hat
Hi All,
I want to create kick start bootable ISO file. I have Centos 5.4 ISO and customized ks.cfg file. Now I need to recreate ISO with ks.cfg and content of existing ISO.
During installation, it automatically should pick the kick start file and need to proceed with the installation.
... (0 Replies)
Discussion started by: kalpeer
0 Replies
7. Boot Loaders
1)It is a great experience to achieve what I got today. I had downloaded GParted iso file (135 MB size). Now to make a bootable usb of it, I used unetbootin and to surprise I succeded in entering Gparted application and modified my partitions.
Earlier I was in a notion that it is used only for... (0 Replies)
Discussion started by: ravisingh
0 Replies
8. SuSE
Hi All,
I would need your assistance to make a bootable USB with SUSE LINUX Enterprise Server
I have already downloaded relevant OS (Trail Version) packages @
1) SLES-11-SP4-DVD-i586-GM-DVD1
2) SLES-11-SP4-DVD-i586-GM-DVD2
when I tried to open these packages with PowerISO one of the... (7 Replies)
Discussion started by: Leaner_963
7 Replies
9. Red Hat
Hi All
On one of my sandbox machine, I want to replace RHEL 6.2 to RHEL 7.3.
I am using both developer editions.
rhel-server-7.3-x86_64-dvd.iso ... This is what I have downloaded from
Red Hat Enterprise Linux Download | Red Hat Developers
My understanding is this file would work as a... (1 Reply)
Discussion started by: videsh77
1 Replies
CCD(4) BSD Kernel Interfaces Manual CCD(4)
NAME
ccd -- Concatenated disk driver
SYNOPSIS
pseudo-device ccd [count]
DESCRIPTION
The ccd driver provides the capability of combining one or more disks/partitions into one virtual disk.
This document assumes that you're familiar with how to generate kernels, how to properly configure disks and pseudo-devices in a kernel con-
figuration file, and how to partition disks.
Note that the 'raw' partitions of the disks must not be combined. Each component partition should be offset at least one cylinder from the
beginning of the component disk. This avoids potential conflicts between the component disk's disklabel and the ccd's disklabel. The kernel
will only allow component partitions of type FS_CCD. But for now, it allows partition of all types since some port lacks support of an on-
disk BSD disklabel. The partition of FS_UNUSED may be rejected because device driver of component disk will refuse it.
In order to compile in support for the ccd, you must add a line similar to the following to your kernel configuration file:
pseudo-device ccd 4 # concatenated disk devices
The count argument is how many ccds memory is allocated for at boot time. In this example, no more than 4 ccds may be configured.
A ccd may be either serially concatenated or interleaved. To serially concatenate the partitions, specify the interleave factor of 0.
If a ccd is interleaved correctly, a ``striping'' effect is achieved, which can increase performance. Since the interleave factor is
expressed in units of DEV_BSIZE, one must account for sector sizes other than DEV_BSIZE in order to calculate the correct interleave. The
kernel will not allow an interleave factor less than the size of the largest component sector divided by DEV_BSIZE.
Note that best performance is achieved if all component disks have the same geometry and size. Optimum striping cannot occur with different
disk types.
Also note that the total size of concatenated disk may vary depending on the interleave factor even if the exact same components are concate-
nated. And an old on-disk disklabel may be read after interleave factor change. As a result, the disklabel may contain wrong partition
geometry and will cause an error when doing I/O near the end of concatenated disk.
There is a run-time utility that is used for configuring ccds. See ccdconfig(8) for more information.
WARNINGS
If just one (or more) of the disks in a non-mirrored ccd fails, the entire file system will be lost.
FILES
/dev/{,r}ccd* ccd device special files.
SEE ALSO
config(1), MAKEDEV(8), ccdconfig(8), fsck(8), mount(8), newfs(8)
HISTORY
The concatenated disk driver was originally written at the University of Utah.
BSD
March 5, 2004 BSD