Sponsored Content
Operating Systems Solaris Sun Blade 100 cdrom problems... Post 302195885 by arjunreddy3 on Friday 16th of May 2008 06:16:28 AM
Old 05-16-2008
cdroms are automaticly mounted by vold. no way to store info vfstab.

once againg u restart the vold service.
#cd /etc/init.d
#sh volmgt stop
#sh volmgt start
#cd
 

10 More Discussions You Might Find Interesting

1. Solaris

Anyone has problems with new Blade 2500????

Hi guys, I am a new member here. This is my first post. I try to purchase some new Blade 2500 for the company. However, the vendor suggests me to get Blade 2000 instead. The vendor said he has many problems with new Silver Blade 2500's. Has anyone here had simlar experience with blade 2500?... (4 Replies)
Discussion started by: facaizhu
4 Replies

2. UNIX for Dummies Questions & Answers

sun blade 100 test-all frozen at pci@1f,0/usb/c,3

platform: sunblade 100 Solaris 10. When running a test-all from the ok prompt on this new (to me) system, it locks up at pci@1f,0/usb/c,3. It's been there for about 25 minutes. I do have a usb keyboard and mouse attached, both are known good. There is no flash stick/ thumb drive... (0 Replies)
Discussion started by: montana77
0 Replies

3. Solaris

Sun Blade 100 Disk Compatibility

It's me again, I was taking my Sun Blade 100 apart last night to see what kind of drive I have. It is a Seagate ST320011A Barracuda ATA IV 20 GB 7200 RPM Ultra ATA/100 IDE. Now 20 gig ain't all that big anymore and I got to thinking about putting a couple bigger drives in there. although I... (7 Replies)
Discussion started by: BrewDudeBob
7 Replies

4. Solaris

Sun Blade 100 Memory Upgrade

Hi, I've been a member for a while but have never posted. I have a Sun Blade 100 desktop and I just installed Solaris 10 and it is unbearably slow. I only have 128 Meg of RAM and need to upgrade. I have searched and found many online resources that have RAM, but I was wondering if anyone has... (12 Replies)
Discussion started by: BrewDudeBob
12 Replies

5. UNIX for Dummies Questions & Answers

Serial Connection sun blade 100 to pc

Hi, If someone please help as my efforts been exhausted in connecting my sun blade 100 serial to my pc. I am using null modem with DB9(female) in sun blade and DB9(female, using gender change) in pc. I am trying both hyper/putty 9600 8 N 1 configurations. Thanks (2 Replies)
Discussion started by: younics
2 Replies

6. Solaris

Sun Blade 150 not a Sun?

I have recently re-installed Solaris 10 on a Sun Blade 150 followed by a patch set (10_Recommended) dated 2011.12.05. I have just noticed /bin/sun now returns false, rather than true. See below. $ uname -a SunOS myblade1 5.10 Generic_147440-07 sun4u sparc SUNW,Sun-Blade-100 $ /bin/sparc &&... (1 Reply)
Discussion started by: apmcd47
1 Replies

7. UNIX for Dummies Questions & Answers

Reinstalling Solaris 9 on Sun Blade 100

For the past ten years I have owned a blade 100, and I had Solaris 9 running on it. Due to the fact, 9 is woefully out of date, I wanted to try 10, but 10 needed more ram, so I beefed up the ram to the full 2 gig. I have two 15 gig ide drives in the box (stock drives). But unfortunately solaris... (2 Replies)
Discussion started by: RichardET
2 Replies

8. Solaris

Sun Blade 150 wont boot off cdrom

Hello, Ive just aquired a blade 150 off ebay.Im new to suns and are having a problem getting it to boot off the cdrom.Openboot continuously tries to do a network boot and I cant enter any commands.Im using an average pc keyboard and it definetly works.Thanks for any help.:wall: (3 Replies)
Discussion started by: chucky
3 Replies

9. Solaris

Memory problems in Blade 6340

We have a 6000 chassis with three blades in it. Two of the blades have "Oracle/Sun" memory in them with no complaints. The third blade is populated with Dataram dimms. That 3rd blade continues to flag a slot bad. Oracle has said they would not support the blade with Dataram memory it it. I didn't... (1 Reply)
Discussion started by: brownwrap
1 Replies

10. Solaris

Execution problems with sun blade 150

hello i have a forte gamma camera Philips device . and its a medical device. this medical device is came with sun blade 150 pc and pegasys is printed on the sun blade pc .the problem is when i switched the power on , the sun blade runs and a white screen appear with the information about the... (6 Replies)
Discussion started by: moh_abaloo
6 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 04:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy