01-11-2002
I am not familiar with AIX, but on some systems, you can pass the "-o loop" option to the mount command in order to mount a file as a device to a folder (whew!). For example, I have used:
mount -o loop -t iso9660 ./my.iso ./mnt
, and it works just fine.... Check your man page for mount to look for your exact options, etc...
Hope this helps.
10 More Discussions You Might Find Interesting
1. Tips and Tutorials
Many software packages can be downloaded in the form of an ISO image. ISO images can also be created from CD and saved as ISO images:
$ cat /dev/somecd > somename.iso
Rather than burning the image to a CD-ROM to access its contents, it is easy to mount the image directly into the filesystem... (0 Replies)
Discussion started by: kduffin
0 Replies
2. AIX
Hi Guys,
How to mount ISO images in AIX environment.
I know how to do it in Solaris.
Thanks
Manu (0 Replies)
Discussion started by: b_manu78
0 Replies
3. Red Hat
Hi Guys,
I'm having a bit of trouble and im not sure what is the deal, I'm trying to mount an ISO on my RHEL box and it is not letting me...
mount -o loop -t iso9660 /home/bgalante/rhel-5-server-i386-disc3.iso /mnt
mount: Not a directory
any idea what i am doing wrong? (2 Replies)
Discussion started by: BG_JrAdmin
2 Replies
4. AIX
Hi,
I've got a recent problem with 2 file systems on an AIX 5.3 server. The fs's are marked to auto mount at startup and do show as being mounted after a a restart however if you cd to the mount point and 'df -g .' it shows the fs hasn't actually mounted.
$ mount |grep SQLT0001.0
... (2 Replies)
Discussion started by: m223464
2 Replies
5. Solaris
Hello.
When I use format command - It shows:
/dev/dsk/c0d0s4 is normally mounted on /u02 according to /etc/vfstab. Please remove this entry to use this device.
What does it mean? (4 Replies)
Discussion started by: panchpan
4 Replies
6. Solaris
Hi all,
Kind of an emergency situation, I have to NFS mount an AIX filesystem on to a Sun Solaris OS (5.10).
Typically from Sun to Sun is:
mount -F nfs <remote file system>/dir <mount point>
Which of course doesn't work if the remote file system is another OS (like AIX).
Is there... (1 Reply)
Discussion started by: jeffpas
1 Replies
7. UNIX for Dummies Questions & Answers
Say, we are going to mount a remote file system on our server. I am not too sure about how will data be transferred back to original host when it is written to the mounted FS. Could you please share an article or your knowledge on this?
Thanks in advance;
Stephen W. (2 Replies)
Discussion started by: swmk
2 Replies
8. AIX
Hi all,
Can anyone get the link to download the iso image of AIX as i am new to AIX need to study and work on the concepts of AIX.
Thnx in advance...
VINU:) (3 Replies)
Discussion started by: vinuvinod
3 Replies
9. UNIX for Dummies Questions & Answers
Hi Team ,
Team Can any give me a good explanation of mount file system.:wall:if we have do a df -k it show /var/orcl/abc/txt mounted on /var/orcl.
example :
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 4021876 0 ... (2 Replies)
Discussion started by: kkabc789
2 Replies
10. Red Hat
Hi gurus,
Need your help ,
Am facing some issue with one of the ext3 file system.while rebooting it failed to mount fs after running fsck i tried manuall but still no luck.However i made the machine up but am unable to mount file system can some one please help me.
root@vm258902]~# cat... (2 Replies)
Discussion started by: kapil514
2 Replies
LEARN ABOUT DEBIAN
mount.crypto_luks
mount.crypt(8) pam_mount mount.crypt(8)
Name
mount.crypt - mount a dm-crypt encrypted volume
Syntax
mount.crypt [-nrv] [-o options] device directory
Options
-o options
Set further mount options. mount.crypt will take out its own options it recognizes and passes any remaining options on to the under-
lying mount program. See below for possible options.
-n Do not update /etc/mtab. Note that this makes it impossible to unmount the volume by naming the container - you will have to pass
the mountpoint to umount.crypt.
-r Set up the loop device (if necessary) and crypto device in read-only mode. (The mount itself will necessarily also be read-only.)
Note that doing a remount using `mount /mnt -o remount,rw` will not make the mount readwrite. The crypto and loop devices will have
to be disassociated first.
-v Turn on debugging and be a bit more verbose.
Mount options
cipher The cryptsetup cipher used for the encrypted volume. This option is mandatory for PLAIN (non-LUKS) volumes. pmt-ehd(8) defaults to
creating volumes with "aes-cbc-essiv:sha256" as a cipher.
crypto_name
Select the name for the crypto device (optional). This option is currently only usable with dm-crypt systems.
fsck Run fsck on the container before mounting it.
fsk_cipher
The OpenSSL cipher used for the filesystem key. The special keyword "none" can be used to bypass decryption and pass the file con-
tents directly to libcryptsetup.
fsk_hash
The OpenSSL hash used for producing key and IV.
fstype The exact type of filesystem in the encrypted container. The default is to let the kernel autodetect.
hash The cryptsetup hash used for the encrypted volume. This defaults to no hashing, because pam_mount assumes EHD volumes with strong
and simple fskey generation.
keyfile
The path to the key file. This option is mandatory for "normal" crypto volumes and should not be used for LUKS volumes.
remount
Causes the filesystem to be remounted with new options. Note that mount.crypt cannot switch the underlying loop device (if applies)
or the crypto device between read-only and read-write once it is created; only the actual filesystem mount can be changed, with lim-
its. If the loop device is read-only, the crypto device will be read-only, and changing the mount to read-write is impossible. Sim-
ilarly, going from rw to ro will only mark the mount read-only, but not the crypto or loop device, thus making it impossible to set
the filesystem the crypto container is located on to read-only.
ro Same as the -r option.
verbose
Same as the -v option.
Obsolete mount options
This section is provided for reference.
loop This option used to set up a loop device, because cryptsetup(8) expects a block device. The option is ignored because mount.crypt
can figure this out on its own.
pam_mount 2011-12-15 mount.crypt(8)