Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place! |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
10-22-2002, 03:03 PM
|
#1
|
LQ Newbie
Registered: Oct 2002
Posts: 8
Rep:
|
/etc/fstab problem
Hello,
I've successfully set up a Win32 /Redhat dual boot situation here at the office.
Using the
#mkdir /mnt/data
#mount /dev/sda5 /mnt/data
I am manually able to mount the Fat32 partition.
When I update the /etc/fstab
with an appropriate /dev/sda5 line and
run a manual
#mount /mnt/data
I am successfully able to mount the Fat32 partition.
However, when I reboot, the reboot
somehow blows away the line I just appended in /etc/fstab
and the /mnt/data directory disappears.
What's going on? How can I remedy this problem?
Thanks.
--juggler
|
|
|
10-22-2002, 03:04 PM
|
#2
|
LQ Newbie
Registered: Oct 2002
Posts: 8
Original Poster
Rep:
|
P.S.
The version of Redhat is 7.3
|
|
|
10-22-2002, 04:09 PM
|
#3
|
Member
Registered: Jul 2002
Location: Santa Cruz, CA
Distribution: lfs
Posts: 538
Rep:
|
that sounds really wierd. Are you sure that you saved your /etc/fstab? do:
cat /etc/fstab
and post that here.
the /mnt/data directory DISAPPEARS? that shouldn't happen do
ls /mnt
and see if it's there. You also might need to be doing this:
mount -t vfat /dev/scda5 /mnt/data
and a line like this in /etc/fstab :
/dev/scda5 /mnt/data vfat defaults 0 0
I don't know... that's all I can think of.
good luck
-Adam
Last edited by adam_boz; 10-22-2002 at 04:10 PM.
|
|
|
10-22-2002, 07:08 PM
|
#4
|
LQ Newbie
Registered: Oct 2002
Posts: 8
Original Poster
Rep:
|
New fstab problem
I figured out that if "kudzu" is included anywhere on the /dev/sda5 options, kudzu for whatever reason wipes out
/mnt/data and erases the /dev/sda5 line in our /etc/fstab.
Our /etc/fstab line now
reads:
/dev/sda5 /mnt/data vfat defaults,uid=500,gid=100 0 0
Is there any way we can do a
uid=*,gid=*
or open up the /mnt/data to a multitude of uids (e.g. uid=500-700)? It's kind of a pain to manually enter all UIDs in. I tried simply setting
gid=100
but then the user with uid=500 no longer had access.
Thanks.
|
|
|
10-22-2002, 07:30 PM
|
#5
|
LQ Guru
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu ; CentOS ; Raspbian
Posts: 12,613
Rep:
|
Do you want everyone on earth (or at least with an account with access to that computer) to have access to that directory? IF so, remove uid and gid and place:
umask=000
Instead.
Cool
|
|
|
10-23-2002, 11:22 AM
|
#6
|
LQ Newbie
Registered: Oct 2002
Posts: 8
Original Poster
Rep:
|
How about...
That sounds like a nice workaround.
How about allowing just a single group, say the users
group (GID=500) to be able to access /mnt/data? How would I go about doing that?
|
|
|
10-23-2002, 12:28 PM
|
#7
|
Member
Registered: Jul 2002
Location: Santa Cruz, CA
Distribution: lfs
Posts: 538
Rep:
|
I don't know how to use fstab for that, but you can do this:
chown -R :500 /mnt/data
and make sure that it has group read/write .... whatever you want
ooh... I forgot it's a vfat partition.... I'm not sure if that'll work, but you can try
good luck
-Adam
|
|
|
10-23-2002, 01:56 PM
|
#8
|
LQ Guru
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu ; CentOS ; Raspbian
Posts: 12,613
Rep:
|
Re: How about...
Quote:
Originally posted by juggler
That sounds like a nice workaround.
How about allowing just a single group, say the users
group (GID=500) to be able to access /mnt/data? How would I go about doing that?
|
What umask does is basically set the chmod. SO a umask of 000 (umask=000) sets a chmod of 777 which means everyone and their dog has all permissions.
So a better way of putting this (and quoting from Acid):
Quote:
so therefore a umask of 333 equates to a chmod of 444 (777-333) which is r--r--r-- in more conventional terms. umask 022 would be rwxr-xr-x (chmod 755) and so on.
|
from this thread: http://www.linuxquestions.org/questi...threadid=25234
You want to allow full group access, but no one else :
umask=007
What this will set is:
user full perm
group full perm
world (everyone else) no perm
And chown user:group /path/to/folder
This should, I believe set the correct values and abilities for that.
Cool
|
|
|
All times are GMT -5. The time now is 11:29 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|