Sponsored Content
Operating Systems Solaris Sharing DVD Drive in LDoms Environment Post 302288815 by taran on Wednesday 18th of February 2009 04:42:10 AM
Old 02-18-2009
man vold.conf
http://docs.sun.com/app/docs/doc/816...&a=view&q=vold


commands not line in the file

svcadm refresh volfs
svcadm restart volfs


-----------------

ldm add-vdsdev options=ro /dev/dsk/c*t*d*s2 cdrom@primary-vds0

ldm add-vdisk cdrom cdrom@primary-vds0 xxxx
ldm add-vdisk cdrom cdrom@primary-vds0 xxxx2
ldm add-vdisk cdrom cdrom@primary-vds0 xxxx3

Last edited by taran; 02-18-2009 at 05:53 AM..
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Sharing Tape Drive from other machine

Pls. correct me for the required steps which we need to do to share the Tape drive or whatever drive from other machine in network . 1.related files : /etc/hosts ,/etc/hosts.equiv , ....? 2. we need to insert the user & machine name inside hosts.equiv . (machinname1 username1 ... (1 Reply)
Discussion started by: nikk
1 Replies

2. UNIX for Dummies Questions & Answers

Sharing a Unix Drive Over The Internet ... but

I don't know if this can be done, otherwise, my project will come to a screeching halt. I have a SCO 5.0.5 machine connected to the internet with a static IP address. I need to be able to share a drive : /shareddrive I need to map to it from a windows machine: hence, what i'd like to... (3 Replies)
Discussion started by: gseyforth
3 Replies

3. Solaris

how to burn a CD/DVD in solaris8 environment

Hi, Boss Now i update my Ultra 10 with a DVD-R/W. but i do not know how to burn a date DVD or a self-Run iso date. any body can give me some advice? like which burner or software can be used in my system?:o BTW,my O/S is Solaris 8 (8 Replies)
Discussion started by: surainbow
8 Replies

4. AIX

Sharing a tape drive across the network.

I'm building a new server that doesn't have an internal tape drive. It is running 5.3ML8. I have another server running 5.1ML9 that has an LTO1 drive I'd like to share. Is this possible, or should I look into twin-tailing it, if that's even supported anymore. (0 Replies)
Discussion started by: tommysalami
0 Replies

5. AIX

dvd media in drive

Hello, It's some tool in AIX to check what kind of media (DVD+RW DVD-RW DVD-RAM) is inserted in drive? In linux there is very nice tool called dvd+rw-mediainfo. (0 Replies)
Discussion started by: vikus
0 Replies

6. Solaris

Sharing devices (tape drive) to local zone

I have to setup a local zone and need to share the fiber attached tape drive that is connected to the global zone. What is the best way to do this? Will sharing the /dev/rmt directory via lofs work? Any help is appreciated! (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies

7. AIX

Sharing tape drive across systems

Is it possible to NFS mount raw tape drive device file ( /dev/rmt0) across system ? I make a mksysb image on local disk and am trying to copy a mksysb image to a tape, but the tape drive is attached to a server which is at a lower TL I don't think there is way to NFS mount a tape drive in... (3 Replies)
Discussion started by: mk8570
3 Replies

8. UNIX for Dummies Questions & Answers

Mount the cd/dvd drive

· Next, you will need to install the software package that provides DHCP services (a.k.a. the DHCP daemon software). It is located on the installation DVD ISO image for the CentOS Linux Distribution. Associate the (Disc 1 of 2) DVD ISO with the virtual machine's CD/DVD optical drive, create a... (1 Reply)
Discussion started by: beerpong1
1 Replies

9. AIX

problem on sharing cdrom drive in AIX with linux

HI i have setuped a nfs between a AIX system and a linux os ,keeping AIX as sever i need to share the CDrom in AIX server with the linux operating system. ie. linux os machine does't have a cdrom . will i be able be share ..i tried a lot but it gives a message which resembles NFS access... (3 Replies)
Discussion started by: raguraja
3 Replies
vold.conf(4)							   File Formats 						      vold.conf(4)

NAME
vold.conf - volume management configuration file SYNOPSIS
/etc/vold.conf DESCRIPTION
The vold.conf file contains the removable media configuration information used by vold(1M). This information includes the database to use, labels that are supported, devices to use, actions to take when certain media events occur, and the list of file systems that are unsafe to eject without unmounting. Modify vold.conf to specify which program should be called when media events (actions) occur or when you need to add another device to your system. See EXAMPLES for more information on adding devices. If you modify vold.conf, you must tell vold to reread vold.conf by sending a HUP signal. Use the following command: # kill -HUP `pgrep vold` File Format The syntax for the vold.conf file is shown here. # Database to use db database # Labels supported label label_type shared_object device # Devices to use use device type special shared_object symname [ options ] # Actions insert regex [ options ] program program args eject regex [ options ] program program args notify regex [ options ] program program args # List of file system types unsafe to eject unsafe fs_type fs_type Of these syntax fields, you can safely modify Devices to use and Actions. Do not modify the db line. Devices to Use Field All use device statements must be grouped together by device type. (For example, all use cdrom statements must be grouped together and all use floppy statements must be grouped together.) The explanations of the syntax for the Devices to use field are as follows: device The type of removable media device to be used. Legal values are cdrom, floppy, pcmem and rmdisk. type The specific capabilities of the device. Legal value is drive. special This sh(1) expression specifies the device or devices to be used. Path usually begins with /dev. shared_object The name of the program that manages this device. vold(1M) expects to find this program in /usr/lib/vold. symname The symbolic name that refers to this device. The symname is placed in the device directory. options The user, group, and mode permissions for the media inserted (optional). The special and symname parameters are related. If special contains any shell wildcard characters (that is, has one or more asterisks or question marks in it), then the syname must end with"%d". In this case, the devices that are found to match the regular expression are sorted, then numbered. The first device will have a zero filled in for the "%d", the second device found will have a one, and so on. If the special specification does not have any shell wildcard characters then the symname parameter must explicitly specify a number at its end (see EXAMPLES below). Actions Field Here are the explanations of the syntax for the Actions field. insert|eject|notify The media event prompting the event. regex This sh(1) regular expression is matched against each entry in the /vol file system that is being affected by this event. options You can specify what user or group name that this event is to run as (optional). program The full path name of an executable program to be run when regex is matched. program args Arguments to the program. Default Values The default vold.conf file is shown here. # Volume Daemon Configuration file # # Database to use (must be first) db db_mem.so # Labels supported label cdrom label_cdrom.so cdrom label dos label_dos.so floppy rmdisk pcmem label sun label_sun.so floppy rmdisk pcmem # Devices to use use cdrom drive /dev/rdsk/c*s2 dev_cdrom.so cdrom%d use floppy drive /dev/rdiskette[0-9] dev_floppy.so floppy%d use pcmem drive /dev/rdsk/c*s2 dev_pcmem.so pcmem%d forceload=true use rmdisk drive /dev/rdsk/c*s2 dev_rmdisk.so rmdisk%d # Actions eject dev/diskette[0-9]/* user=root /usr/sbin/rmmount eject dev/dsk/* user=root /usr/sbin/rmmount insert dev/diskette[0-9]/* user=root /usr/sbin/rmmount insert dev/dsk/* user=root /usr/sbin/rmmount notify rdsk/* group=tty user=root /usr/lib/vold/volmissing -p remount dev/diskette[0-9]/* user=root /usr/sbin/rmmount remount dev/dsk/* user=root /usr/sbin/rmmount # List of file system types unsafe to eject unsafe ufs hsfs pcfs udfs EXAMPLES
Example 1: A sample vold.conf file. To add a CD-ROM drive to the vold.conf file that does not match the default regular expression (/dev/rdsk/c*s2), you must explicitly list its device path and what symbolic name (with %d) you want the device path to have. For example, to add a CD-ROM drive that has the path /dev/rdsk/my/cdroms? (where s? are the different slices), add the following line to vold.conf (all on one line): use cdrom drive /dev/rdsk/my/cdroms2 dev_cdrom.so cdrom%d Then, when media is inserted in this CD-ROM drive, vold assigns it the next symbolic name. For example, if two CD-ROMs match the default regular expression, they would be named cdrom0 and cdrom1. And, any that match the added regular expression would be named starting with cdrom2. For a diskette that does not match the vold.conf default regular expression (vol/dev/aliases/floppy[0-9]), a similar line would have to be added. For example, to add a diskette whose path was /dev/my/fd0, you would add the following to vold.conf: use floppy drive /dev/my/fd0 dev_floppy.so floppy%d SEE ALSO
sh(1), volcancel(1), volcheck(1), volmissing(1), rmmount(1M), rpc.smserverd(1M), vold(1M), rmmount.conf(4), volfs(7FS) NOTES
vold manages both the block and character device for removable media. However, to make the configuration file easier to set up and scan, only one of these devices needs to be specified. If you follow the conventions specified below, vold figures out both device names if only one of them is specified. For example, if you specify the block device, it figures out the pathname to the character device; if you specify the pathname to the character device, it figures out the block device. CD-ROM Naming Conventions The CD-ROM pathname must have a directory component of rdsk (for the character device) and dsk for the block device. For example, if you specify the character device using the line: use cdrom drive /dev/rdsk/my/cdroms2 dev_cdrom.so cdrom%d then it is assumed that the block device is at /dev/dsk/my/cdroms2 Diskette Naming Conventions For diskettes, vold requires that the device pathnames end in either rfd[0-9] or rdiskette[0-9] for the character device, and fd[0-9] or diskette[0-9] for the block device. As with the CD-ROM, it generates either the block name given the character name, or the character name given the block name. SunOS 5.10 21 Jun 2002 vold.conf(4)
All times are GMT -4. The time now is 08:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy