Using "/usr/sbin/vold -d /vold" breaks "eject cdrom"

Using "/usr/sbin/vold -d /vold" breaks "eject cdrom"

Post by Kevin Messi » Thu, 19 May 1994 05:35:47




> We are a SunOS shop upgrading on of our Sparcstation 1s to Solaris 2.3.
> One problem we've encountered is that Solaris reserves the directory
> /vol for mounting cdroms, floppies, etc.  Unfortunately, we've also
> been using /vol as a auto-mount point for several of our globally
> accessible NFS file-systems.  Moreover, a lot of our scripts and
> software expect to be able to use /vol to access other files.

> We've tried changing vold's directory to '/vold', and this works but
> 'eject cdrom' doesn't work now (it reports "No such volume...").

> So, is there a way to get eject to work if we've changed vold's
> mount point?

> --


We have the same problem as you and we also redirect the volume manager
to use /vold instead of /vol.  I can usually get the cdrom to eject by
using "eject /vold/dev/rdsk/c0t6/*" or something like that.  To get floppies
to eject, use "eject /vold/dev/rdiskette0"
--

"You call me sweet, like I'm some kind of cheese" - Brian May
 
 
 

Using "/usr/sbin/vold -d /vold" breaks "eject cdrom"

Post by Erik E. Rantap » Wed, 18 May 1994 15:21:45


We are a SunOS shop upgrading on of our Sparcstation 1s to Solaris 2.3.
One problem we've encountered is that Solaris reserves the directory
/vol for mounting cdroms, floppies, etc.  Unfortunately, we've also
been using /vol as a auto-mount point for several of our globally
accessible NFS file-systems.  Moreover, a lot of our scripts and
software expect to be able to use /vol to access other files.

We've tried changing vold's directory to '/vold', and this works but
'eject cdrom' doesn't work now (it reports "No such volume...").

So, is there a way to get eject to work if we've changed vold's
mount point?

--