public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Kenny Hitt <kennyhitt@yahoo.com>
To: speakup@braille.uwo.ca
Subject: Re: debian /var/lock permissions
Date: Fri, 22 Mar 2002 14:47:48 -0600	[thread overview]
Message-ID: <20020322204748.GA15566@learning> (raw)
In-Reply-To: <019401c1d1dc$63f38ac0$01213e18@mycomputer>

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


  reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 William Hubbs
 ` Igor Gueths
   ` Kenny Hitt [this message]
     ` jwantz
       ` Igor Gueths
         ` 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=20020322204748.GA15566@learning \
    --to=kennyhitt@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).