linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jbrown1050@hotpop.com>
To: "Earl R. Lapus" <elapus@ntsp.nec.co.jp>
Cc: linux-admin@vger.kernel.org
Subject: Re: cannot do chmod
Date: Wed, 28 May 2003 21:42:02 -0400	[thread overview]
Message-ID: <20030529014201.GA20484@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <000501c3251c$b4aca070$8f3b1cac@TIBET>

On Wed, May 28, 2003 at 09:26:11PM +0800, Earl R. Lapus wrote:
> Good day...
> 
> I need help on this... I mounted my windows partition on
> the /mnt/win directory. The strange thing is that there is
> no execute permission for the group and others category 
> on the /mnt/win directory. So I tried to `chmod -v go+x /mnt/win'
> and it printed out that the chmod was successful. BUT when
> I do an `ls -l /mnt' the file permissions were unchanged. This is the first
> time I encountered this problem and I really have no idea why
> this is happening.
> 
> The reason why I want to place an execute permission on the /mnt/win
> directory is that I want other non-root users to access the windows 
> partition. 
> 
> Does this have to do with the mount options? If it does, I placed the
> contents of my fstab below in case you guys want to find anything wrong
> with it. I don't know anything else that might cause this problem. 
> 
> [these are the contents of my fstab]
> 
> /dev/hda5        swap             swap        defaults         0   0
> /dev/hda7        /                ext3        defaults         1   1
> /dev/hda6        /home            ext3        defaults         1   2
> /dev/hda3        /mnt/win         vfat        defaults         1   0

Try this line out:

/dev/hda3     /mnt/win      vfat     defaults,umask=000,mode=777  1  0

Set 'mode=' to whatever permissions you want the files to be.

> /dev/cdrom       /mnt/cdrom       iso9660     noauto,owner,ro  0   0
> /dev/fd0         /mnt/floppy      auto        noauto,owner     0   0
> devpts           /dev/pts         devpts      gid=5,mode=620   0   0
> proc             /proc            proc        defaults         0   0
> 
> 
> =================================
>  There are seven words in this sentence.
> =================================
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
 /"\  ASCII ribbon              | http://www.geocities.com/jbrown1050/
 \ /  campain against           | Linux User:190064
  X   HTML in e-mail and        | Linux Machine:84163
 /*\  news, and unneeded MIME   | 
----------------------------------------------------------------------
You too can spend five years in prison; just distribute this program
once US Senator Hollings's CBDTPA bill is passed into law:
perl -e 'while(<>) { print;}'



  reply	other threads:[~2003-05-29  1:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28 13:26 cannot do chmod Earl R. Lapus
2003-05-29  1:42 ` Jim C. Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-29  1:35 Andrew Lister

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030529014201.GA20484@jbrown.mylinuxbox.org \
    --to=jbrown1050@hotpop.com \
    --cc=elapus@ntsp.nec.co.jp \
    --cc=jbrown105@speedymail.org \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).