You are talking of the CDROM on the server right?
In my case I have a DVD in /dev/dsk/c0t3d0 so:
In HP ( PA-RISC anyway...) you would find a directory for this usage in / :
drwxr-xr-x 2 root sys 96 Feb 26 2002 SD_CDROM
And so you would:
mount /dev/dsk/c0t3d0 /SD_CDROM
I never tried using SAM since Im next to the server when having to put a CD...
hi
when i want to mount my cdrom i got this error
cd9660: /dev/acd0c: Invalid argument
this is how my /etc/fstab looks like:
#device mntpoint FStype Options Dump pass
/dev/ad0s1b none swap sw 0 0... (2 Replies)
I have an external cdrom drive, which am tring to
mount.
I issued the following
mkdir cdrom to create a mount point
then
mount -F cdfs /dev/dsk/c0t4d0s7 /cdrom
but this is unsuccessful instead received an error
message mount point not found
can you help (5 Replies)
I am trying to remote mount a cdrom (Sun Ultra 10 running release 7) on another system.
I followed the following procedure offered by a friend:
To allow a drive to be mounted, edit /etc/dfs/dfstab file to include the following line:
share -F nfs -o ro /usr/man
On computer with drive... (3 Replies)
On Sun Fire V240, cdrom doesn't automount. I can manually mount the cdrom, however it pretty annoying. I have checked the vold demon and its seems to be running. Here is the output from
/etc/inetd.conf
pg inetd.conf
daytime stream tcp6 nowait root internal
daytime dgram udp6 ... (2 Replies)
Hi guy's, my first post here on the forum :p
I did a quick search here, but did not find a direct hit, so decided to post my question.
I'm taking my first steps into AIX, and right now I'm trying to install some software that I've downloaded as a zip file, and have this extracted into a mounted... (1 Reply)
I am trying to mount my a cd in my SCO 5.0.7 box and keep getting this:
Alessandra! -->#mount -r /dev/cd0 /mnt
mount: cannot stat '/dev/cd0'
Alessandra! -->hwconfig
name=kernel vec=- dma=- rel=3.2v5.0.7 kid=2003-02-18
name=cpu vec=- dma=- unit=1... (0 Replies)
Hi there
I am trying to mount a cdrom using:
mount /cdrom
and I get the error:
mount: mount point cannot be determined
If I try the command
mount cdrom /cdrom
nfs mount: nfs file system; use path
I tried running mountall
and mountall -F NFS
but to no avail (3 Replies)
Hi people, I am a new user of Unix, I want to ask a basic question. I have a solaris 10 system. I want to use the cd-rom but I can't see what's inside in the cd. I put the cd and then ;
root@hubatusvr # mount /dev/dsk/c0t3d0s2 /cdrom
mount: /dev/dsk/c0t3d0s2 is already mounted or /cdrom is busy... (2 Replies)
Hi
I have created a RHEL6 machine that is hosted on VMWare player that in turn runs off my Windows 7 PC.
When I try and mount the CDROM on the RHEL6 box I get the following output:
$ mount /dev/cdrom/media
mount: can't find /dev/cdrom/media in /etc/fstab or /etc/mtab
$
Here is the... (3 Replies)
Discussion started by: accipiter1
3 Replies
LEARN ABOUT X11R4
volfs
volfs(7FS) File Systems volfs(7FS)NAME
volfs - Volume Management file system
DESCRIPTION
volfs is the Volume Management file system rooted at root_dir. The default location for root-dir is /vol, but this can be overridden using
the -d option of vold (see vold(1M)). This file system is maintained by the Volume Management daemon, vold, and will be considered to be
/vol for this description.
Media can be accessed in a logical manner (no association with a particular piece of hardware), or a physical manner (associated with a
particular piece of hardware).
Logical names for media are referred to through /vol/dsk and /vol/rdsk. /vol/dsk provides block access to random access devices. /vol/rdsk
provides character access to random access devices.
The /vol/rdsk and /vol/dsk directories are mirrors of one another. Any change to one is reflected in the other immediately. The dev_t for a
volume will be the same for both the block and character device.
The default permissions for /vol are mode=0555, owner=root, group=sys. The default permissions for /vol/dsk and /vol/rdsk are mode=01777,
owner=root, group=sys.
Physical references to media are obtained through /vol/dev. This hierarchy reflects the structure of the /dev name space. The default per-
missions for all directories in the /vol/dev hierarchy are mode=0555, owner=root, group=sys.
mkdir(2), rmdir(2), unlink(2) (rm), symlink(2) (ln -s), link(2) (ln), and rename(2) (mv) are supported, subject to normal file and direc-
tory permissions.
The following system calls are not supported in the /vol filesystem: creat(2), only when creating a file, and mknod(2).
If the media does not contain file systems that can be automatically mounted by rmmount(1M), users can gain access to the media through the
following /vol locations:
+-----------------------------------+------------------------------------+
| Location | State of Media |
+-----------------------------------+------------------------------------+
|/vol/dev/diskette0/unnamed_floppy | formatted unnamed floppy-block |
| | device access |
+-----------------------------------+------------------------------------+
|/vol/dev/rdiskette0/unnamed_floppy | formatted unnamed floppy-raw |
| | device access |
+-----------------------------------+------------------------------------+
|/vol/dev/diskette0/unlabeled | unlabeled floppy-block device |
| | access |
+-----------------------------------+------------------------------------+
|/vol/dev/rdiskette0/unlabeled | unlabeled floppy-raw device access |
+-----------------------------------+------------------------------------+
|/vol/dev/dsk/c0t6/unnamed_cdrom | CD-ROM-block device access |
+-----------------------------------+------------------------------------+
|/vol/dev/rdsk/c0t6/unnamed_cdrom | CD-ROM-raw device access |
+-----------------------------------+------------------------------------+
For more information on the location of CD-ROM and floppy media, see System Administration Guide: Basic Administration or rmmount(1M).
Partitions
Some media support the concept of a partition. If the label identifies partitions on the media, the name of the media becomes a directory
with partitions under it. Only valid partitions are represented. Partitions cannot be moved out of a directory.
For example, if disk volume 'foo' has three valid partitions, 0, 2, and 5, then:
/vol/dsk/foo/s0
/vol/dsk/foo/s2
/vol/dsk/foo/s5
for block access and
/vol/rdsk/foo/s0
/vol/rdsk/foo/s2
/vol/rdsk/foo/s5
for character access.
If a volume is relabeled to reflect different partitions, the name space changes to reflect the new partition layout.
A format program can check to see if there are others with the volume open and not allow the format to occur if it is. Volume Management,
however, does not explicitly prevent the rewriting of a label while others have the volume open. If a partition of a volume is open, and
the volume is relabeled to remove that partition, it will appear exactly as if the volume were missing. A notify event will be generated
and the user may cancel the operation with volcancel(1), if desired.
SEE ALSO volcancel(1), volcheck(1), volmissing(1)rmmount(1M), vold(1M), rmmount.conf(4), vold.conf(4)
System Administration Guide: Basic Administration
SunOS 5.10 8 Feb 1995 volfs(7FS)