i have been having what is clearly a systems problem on a sparc2
running solaris2.4. i believe that some permissions have been changed
somewhere, but this was done before i got possession of the machine.
the problem surfaced when i tried to format, mount, and read and
write on diskettes. i finally was able to achieve all of those but
found that unless i did something about vold, i could not proceed.
with vold running, i can 'fdformat' and 'fdformat -d' and 'eject', but
i cannot 'mount -F ufs /dev/diskette /mnt' or the equivalent for
if i kill vold, then i can 'mount -F ufs /dev/diskette /mnt', write
and read diskettes, but i cannot 'fdformat' and 'fdformat -d' and
so what i do is kill vold to actually use the diskettes. thus i have
a workaround, which i would like to avoid, and have the system behave
when i log shutdown with telinit 0 i get the following message:
nfs umount: sasha:vold(pid199) server not responding: RPC: Program not
the boot which follows has no error messages.
when i look into /var/adm/vold.log after a reboot, i find a series of
error messages which lead me to an interesting place.
there are four lines which essentially say the same thing. here is the
first of them:
Wed Oct 22 10:45:22 1997 warning config file (/etc/vold.conf) line
19: /bin/volcheck;/usr/sbin/rmmount; No such file or directory
the others replace 19 with 20, 21,22.
ls -l /bin/volcheck /usr/sbin/rmmount yields
-r-sr-xr-x 1 root bin 4872 Jul 15 1994 /bin/volcheck
-r-sr-xr-x 1 bin bin 37260 Jul 15 1994 /usr/sbin/rmmount
so the files in question are actually present.
when i look at /etc/vold.conf, what do i find in lines 19-22?
insert /vol*/dev/diskette[0-9]/* user=root /bin/volcheck;/usr/sbin/rmmount -D
insert /vol*/dev/dsk/* user=root /bin/volcheck;/usr/sbin/rmmount -D
eject /vol*/dev/diskette[0-9]/* user=root /bin/volcheck;/usr/sbin/rmmount -D
eject /vol*/dev/dsk/* user=root /bin/volcheck;/usr/sbin/rmmount -D
this explains the above error messages, but they make no sense. can
anyone point to an obvious error in file ownership or permissions
which would explain why rmmount and cvolcheck cannot be found on boot,
is it the permisions -r-sr-xr-x for these files? what should they be?
experience is what allows a person to make new mistakes, instead of
the old ones.