Re: problems with the permissions for /mnt/windows parition
From: Day Brown (daybrown_at_hypertech.net)
Date: 10/05/03
- Next message: Stefan Thuwis: "Re: NVidia"
- Previous message: Paul Lutus: "Re: Systems Stops @ APM: BIOS..."
- In reply to: Carl: "Re: problems with the permissions for /mnt/windows parition"
- Next in thread: Robert Newson: "Re: problems with the permissions for /mnt/windows parition"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 05 Oct 2003 14:54:05 -0500 To: Carl <no_spam@yahoo.com>
Carl wrote:
> Thank you for your reply. I tried to use
>
> "/dev/hdb5 /mnt/windows vfat auto,uid=0,umask=022 0 0 "
>
> in my /etc/fstab to fix my problem, and the result was that I still had
> the same problem that I had before. After a few hours of struggle, I
> changed the above line to the following.
>
> "/dev/hdb5 /mnt/windows vfat auto,uid=0,gid=500,fmask=750,dmask=750"
>
> I rebooted the computer, and I saw the following error messages.
>
> mntent: line 10 in etc/fstab is bad
>
> After the linux booted up, I realized that I had to mount /mnt/windows
> partition manually as a root. After I did that, I tried both write
> permission and read permission as a user and I realized that the user
> could not write on that partition, but he could still read the files in
> the partittion. So it seems that I am on the right track now. However, I
> still can't edit my /etc/fstab file, so that this partition is mounted
> automatically. I tried to look for some easy-to-read documentation to
> figure out what I can do to fix the problem, however I could not find
> any. I tried "man mount" from my terminal window, but it was simply too
> difficult for me to understand. Do you happen to know any suitable
> manuals that I can read on the internet, in order to know how to set up
> /etc/fstab files? The ones that I saw were either too simple or too
> technical.
> Ofcourse, if you could point out where I made mistakes this time, that
> would be greatly appreciated. I think that for some reason, the kernel
> that came with my Redhat 9 had some problem with setting up "umask"
> option in /etc/fstab file. I just felt that way during my struggle this
> afternoon.
> Thank you very much, and have a good day.
>
>
> Paul Lutus wrote:
>
>> Carl wrote:
>>
>> < snip >
>>
>>> I wanted to make it so that the user curl whose user id is 500 has only
>>> read and execute permission for /mnt/windows and /mnt/windowsC
>>> partition.
>>
>>
>>
>> Then don't give that user ownership of the partition. Give it to root.
>> uid=0, umask=022. At present you are giving user 500 ownership of the
>> mount, which obviously means he has totoal control over it.
>>
>> Your current configuration: "uid=500,umask=2" means user 500 has total
>> control over the mount (owns it), as do members of his group, but others
>> have only read and execute permission. According to what you have posted,
>> this is not what you were after.
>>
>> AFAICS, this is what you want:
>>
>> /dev/hdb5 /mnt/windows vfat
>> auto,uid=0,umask=022 0 0
Yeah, I know, man is an atrociously obsolete document tool. so is info.
But one of the main reasons I'm called a troll is that I keep noting how
linux is an adapatation of a unix networking os, whereas dos/win were
built from the ground up for personal desktops, and as linux lovies will
tell you, suck at networking. but try
# fdisk -l
the pound sign is the linux text mode prompt rather than c:>
that'll give you a list of the drives which the os can see.
If you want to write to the win disk, you mite try being root. if you
have a $ instead of the #, you're a user, and wont have permission.
which is a continual pain in the rectal orifice with Linux, which dont
seem to realize you have a single user desktop. I've only been fooling
with Linux off and on since 96, so I'm still a newbie.
Redhat is one of the many distros which act like its the only os the
user would ever need. an elist attitude that results in crap like what
you are confronted with right now. There are a few with a more open
attitude. Corel, which is kinda dated, had icons on the tool bar for win
users to use to access the win drive.
You could try using the windows boot to write what you want on a floppy.
but linux is clumsy with that as well, not wanting mere users to muck
around with floppies. after you mount the FD, you havta umount it and
then mount it again to look at another floppy.
Anyhow, IIRC,
# mount -l
mite give you a list of the mounted drives.
if you want more regular, convenient access to the win drive, you mite
# mkdir /win
on the root, and then try to mount the win drive there...
@ mount /dev/hdb5 -tvfat /win
I remember in the old dos days with BBS newsgroups, some let you use
ANSI COLOR. so- the lines I suggest you type could be in red or
whatever. That functionality seems to have been lost in the rush to gui.
Anyhow, the above mite only let you read, not write. but then if you
want to write on the win drive, you mite find something like the dos
mtools.exe which will let you read the linux drive and copy from it-
when you have the win/dos session running. A safety feature, so that any
sabotage software on the linux system cant crash the win drive.
Of course, you mite also have the win drive formatted with NTFS or FAT
32, WHICH YOUR DISTRO CANT READ. that 'vfat' aint gonna get you there.
IIRC,
@ mount -t
will list the file structures your version of mount supports.
- Next message: Stefan Thuwis: "Re: NVidia"
- Previous message: Paul Lutus: "Re: Systems Stops @ APM: BIOS..."
- In reply to: Carl: "Re: problems with the permissions for /mnt/windows parition"
- Next in thread: Robert Newson: "Re: problems with the permissions for /mnt/windows parition"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
