public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Joseph C. Lininger" <jbahm@pcdesk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: permissions question
Date: Fri, 5 Dec 2003 11:51:27 -0700	[thread overview]
Message-ID: <001b01c3bb60$c9e1aa50$6700a8c0@morgan> (raw)
In-Reply-To: <20031205130245.GA1324@lrxms.net>


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

You need to ensure the group has read, write, and execute permission
for the directory, and read write permission for the files you want
to be accessable by the group. The following should accomplish this,
assuming you want the group to be able to read and write all files in
the directory.

chmod g=rwX <directory name> -R

Replace <directory name> with the name of the directory you are
setting permissions on. Also, note that the X is capitalized. If you
don't do this, you will set group execute on all of the files and the
directory, which is not what you want.
- ---
Joseph C. Lininger
jbahm@pcdesk.net
- ----- Original Message ----- 
From: <showell@lrxms.net>
To: <speakup@braille.uwo.ca>
Sent: Friday, December 05, 2003 6:02 AM
Subject: permissions question


> Folks,
> 
> I created a group, I made the directory and set it to be owned by
> root  and the group, I also made all the files owned by root and
> the group, I  then added myself to the group using the usermod
> program, but yet I  can't write to the directory. What could I be
> doing wrong here?
> I read over the man page for usermod and assumed based on what I
> read  that I was on the correct path.
> Any suggestions appreciated.
> 
> Scott
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBP9DTrSenap9Jqj2wEQJNFwCfZ3KRhJ0ESxQZRCcUs9fxNuJbomgAoOOK
tUHcJbcLRKnf262k7DzO7GoR
=Gq6s
-----END PGP SIGNATURE-----



  parent reply	other threads:[~ UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 showell
 ` Ari Moisio
   ` showell
     ` Sean McMahon
       ` showell
 ` Joseph C. Lininger [this message]
   ` How to stop X from starting at logon? Al Puzzuoli
     ` Erik Heil
       ` Kenny Hitt
         ` Joseph C. Lininger
           ` Kenny Hitt
             ` Joseph C. Lininger
       ` Charles Crawford
     ` Joseph C. Lininger
   ` permissions question showell

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='001b01c3bb60$c9e1aa50$6700a8c0@morgan' \
    --to=jbahm@pcdesk.net \
    --cc=speakup@braille.uwo.ca \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).