Can't share "/mnt/volume"

[Mike Kimmick]

Ned,

I was just reading some posts in USENET regarding the process of
updating fstab at boot time, and it appears that if kudzu runs and finds
discrepancies between the hardware it sees and entries in /etc/fstab, it
will try and update /etc/fstab accordingly.

You might try chkconfig kudzu off, reboot, and see what effect that has
on the status of Updating /etc/fstab.

It also occurred to me that if the /etc/fstab file can't be updated, you
should check it's permissions.  Mine is set to 0644; owner and group set
to root.

Mike Kimmick

On Thu, 2003-07-03 at 08:36, Ned Dupont wrote:
> Nope, nope, nope.
> Nothing is working. I have changed the fstab file a number of times, I
> have tried changing permissions on the mount directory both before and
> after mounting, I have tried mounting automatically and manually, I have
> tried to change the umask, but nothing works.My fstab entry, for that
> particular volume is...
> "/dev/hda2               /mnt/shared             hfs     auto,user,rw"
> with no numbers at the end.
> One thing I mentioned in an earlier email was that during start-up (when
> all the linux text is scrolling up the screen), the line "UPDATING
> FSTAB" always gets a "FAILED". Always. Do you think my current problems
> are somehow associated with that failure?
> Thanks,
> Ned
> 
> 
> On Wed, 2003-07-02 at 13:41, Longman, Bill wrote: 
> > > How do I allow users, other than ROOT, to SEE, and USE, the 
> > > contents of
> > > mounted volumes? Along a similar vein, why is it that, at 
> > > start up (when
> > > all the linux text is scrolling past my screen,"Updating /etc/fstab"
> > > always fails?\Any ideas?
> > 
> > Ned, it's certainly typical for filesystems to be mounted only by root. You
> > can add the "user" flag in the fstab file as one of the mount options on a
> > given filesystem. Then whoever mounts it can unmount it. You can go crazy
> > and use the "users" option, too. Then any ole user can mount and unmount at
> > will. Sometimes this is not advisable....
> > 
> > In your case, you need to mount the filesystem on an existing directory. For
> > instance, if in your fstab it says:
> > 
> > /dev/hda9 /mnt/volume hfs auto 1 1
> > 
> > then you'll have to make sure the /mnt/volume directory exists. Furthermore,
> > the lone empty directory, /mnt/volume, as it exists *in the root directory*
> > has its own permissions separate and distinct from the permissions that the
> > filesystem acquires once it gets mounted there.
> > 
> > Look what happens when I mount my ISO image:
> > 
> > $ cd /
> > $ ls -ld cd1
> > drwxrwxr-x    2 root   root   4096 Jul  2 10:45 cd1/
> > $ mount /cd1
> > $ ls -ld cd1
> > dr-xr-xr-x    9 root   root   4096 Mar 17 08:05 cd1/
> > 
> > This might help you solve the problem of getting others to mount and use
> > filesystems. I don't know why the /etc/fstab error is appearing at boot,
> > though. I suspect it might be from system device probes trying to add
> > available entries in there (like USB drives, etc.).
> > 
> > Bill
> > _______________________________________________
> > yellowdog-newbie mailing list
> > yellowdog-newbie@lists.terrasoftsolutions.com
> > http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-newbie
> 
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general@lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
-- 
Michael W. Kimmick
Software Administrator
Pueblo School District 70
24951 East Hwy 50
Pueblo, CO 81006
(719)295-6531