12-20-2015
Without any experience with those distributions, I'd say you can install the system with just DVD1. If, lateron, you want to recompile something, DVD2 might be needed. But, then, you will be able to copy the DVD2 .iso to your system and mount it on a loopback device.
10 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. Filesystems, Disks and Memory
In our HP/Unix system, our master scsi drive was bootable and our mirrored drive was non-bootable. Are any of these alternatives possible:
1) Make the non-bootable scsi drive bootable? How?
2) Create a bootable scsi drive, then copy the mirrored data to the newly created scsi drive?
I seek... (1 Reply)
Discussion started by: bfisk
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. Red Hat
Hello Everyone,
Can anyone let me know how to make minimal boot.iso from rhl6 installation dvd iso image. I have a dvd image with me but i want to make just a minimal boot media. Somehow it is not shipped with dvd iso. I know we can download boot.iso from redhat site but is there any anyway we... (5 Replies)
Discussion started by: Rohit Bhanot
5 Replies
8. Red Hat
Hi All,
I have one query on creating bootable ISO.
I have installed Centos 5.6 and done few configuration changes which is needed for deploying my App. Later I have deployed my app. Now Centos is up and running in a dedicated box along with my app.
Now I want to create the... (3 Replies)
Discussion started by: kalpeer
3 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
10. UNIX for Beginners Questions & Answers
I have a .dmg file which was created from a disk consisting of two partitions. When I mount the dmg both partitions pop up, so I know the imaging worked properly. One partition is HFS+ and the other is FAT32.
So far, I've been unable to find a way to restore the dmg to a flash drive where both... (17 Replies)
Discussion started by: paulcristo
17 Replies
lofs(7FS) File Systems lofs(7FS)
NAME
lofs - loopback virtual file system
SYNOPSIS
#include <sys/param.h>
#include <sys/mount.h>
int mount (const char* dir, const char* virtual, int mflag, lofs, NULL, 0);
DESCRIPTION
The loopback file system device allows new, virtual file systems to be created, which provide access to existing files using alternate
pathnames. Once the virtual file system is created, other file systems can be mounted within it, without affecting the original file sys-
tem. However, file systems which are subsequently mounted onto the original file system are visible to the virtual file system, unless or
until the corresponding mount point in the virtual file system is covered by a file system mounted there.
virtual is the mount point for the virtual file system. dir is the pathname of the existing file system. mflag specifies the mount options;
the MS_DATA bit in mflag must be set. If the MS_RDONLY bit in mflag is not set, accesses to the loop back file system are the same as
for the underlying file system. Otherwise, all accesses in the loopback file system will be read-only. All other mount(2) options are
inherited from the underlying file systems.
A loopback mount of '/' onto /tmp/newroot allows the entire file system hierarchy to appear as if it were duplicated under /tmp/newroot,
including any file systems mounted from remote NFS servers. All files would then be accessible either from a pathname relative to '/' or
from a pathname relative to /tmp/newroot until such time as a file system is mounted in /tmp/newroot, or any of its subdirectories.
Loopback mounts of '/' can be performed in conjunction with the chroot(2) system call, to provide a complete virtual file system to a
process or family of processes.
Recursive traversal of loopback mount points is not allowed. After the loopback mount of /tmp/newroot, the file /tmp/newroot/tmp/newroot
does not contain yet another file system hierarchy; rather, it appears just as /tmp/newroot did before the loopback mount was performed
(for example, as an empty directory).
Examples
lofs file systems are mounted using:
mount -F lofs /tmp /mnt
SEE ALSO
lofiadm(1M), mount(1M), chroot(2), mount(2), sysfs(2), vfstab(4), lofi(7D)
WARNINGS
Loopback mounts must be used with care; the potential for confusing users and applications is enormous. A loopback mount entry in
/etc/vfstab must be placed after the mount points of both directories it depends on. This is most easily accomplished by making the loop-
back mount entry the last in /etc/vfstab.
SunOS 5.10 10 Apr 2001 lofs(7FS)