public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Igor Gueths" <igueths@yahoo.com>
To: <speakup@braille.uwo.ca>
Subject: Re: debian /var/lock permissions
Date: Fri, 22 Mar 2002 16:17:17 -0500	[thread overview]
Message-ID: <002801c1d1e6$f30a3420$01213e18@mycomputer> (raw)
In-Reply-To: <Pine.LNX.4.44.0203221545190.3831-100000@babel.hpcc.noaa.gov>

Hi Jim. I think I get it now, but what are the bit numbers for read and right? So based on the fact that I know execute is 7, chmod 777 myfile.txt would give root, user, and world read right and execute permissions on myfile.txt?
----- Original Message ----- 
From: <jwantz@hpcc2.hpcc.noaa.gov>
To: <speakup@braille.uwo.ca>
Sent: Friday, March 22, 2002 3:52 PM
Subject: Re: debian /var/lock permissions


> Hi,
> Each group represents root, user and world in that order.  Of course 
> each bit represents a permission.  The permissions are in the same order 
> as what you would see when you did a 'ls -l' command i.e. read, write, 
> execute.
> Therefore a 7 would mean read, write and execute permissions for that 
> particular group.
> 
> An example would be: chmod 774 myfile.txt.
> In this case root would have read, write and execute permissions.  So 
> would the owner of the file.  All others would have only read 
> permissions.
> 
>      Jim Wantz
> On Fri, 22 Mar 2002, Kenny Hitt wrote:
> 
> > Hi.  Each permission needs one bit.  Remember binary.
> > 
> >           Kenny
> > 
> > On Fri, Mar 22, 2002 at 03:01:43PM -0500, Igor Gueths wrote:
> > > Hi William. I've never gotten the logic behind the numbering systems to set file permissions. Like how do you get from something like chmod +x /home/file.txt to chmod 755 /home/file.txt. I'm just curious as to whether someone has figured out the logic behind this. 
> > > ----- Original Message ----- 
> > > From: William Hubbs <kc5eiv@kc5eiv.ddts.net>
> > > To: Speakup Mailing List <speakup@braille.uwo.ca>
> > > Sent: Friday, March 22, 2002 1:32 PM
> > > Subject: debian /var/lock permissions
> > > 
> > > 
> > > > Cheryl,
> > > > 
> > > > I am running debian 3.0 (woody), and I just checked the permissions on
> > > > /var/lock here:
> > > > 
> > > > drwxrwxrwt    3 root     root         1024 Mar 14 11:56 /var/lock
> > > > 
> > > > To get that permission, type, as root,
> > > > 
> > > > chmod 1777 /var/lock
> > > > 
> > > > William
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > 
> > > 
> > > _________________________________________________________
> > > Do You Yahoo!?
> > > Get your free @yahoo.com address at http://mail.yahoo.com
> > > 
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com



  reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 William Hubbs
 ` Igor Gueths
   ` Kenny Hitt
     ` jwantz
       ` Igor Gueths [this message]
         ` Cheryl Homiak
           ` jwantz
         ` jwantz
   ` Cheryl Homiak

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='002801c1d1e6$f30a3420$01213e18@mycomputer' \
    --to=igueths@yahoo.com \
    --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).