The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Arthur Krewat <krewat@kilonet.net>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Who's behind the UNIX filesystem permission
Date: Fri, 2 Aug 2019 11:17:31 -0400	[thread overview]
Message-ID: <c132fb91-c996-1dc9-9d59-60f2cbb6439d@kilonet.net> (raw)
In-Reply-To: <20190802143531.96D4218C096@mercury.lcs.mit.edu>



On 8/2/2019 10:35 AM, Noel Chiappa wrote:
>      > From: Arthur Krewat
>
>      > there's the setuid bit on directories - otherwise known as the sticky
>      > bit.
>
> Minor nit; in V6 at least (not sure about later), the 'sticky' bit was a
> separate bit from SUID and SGID. (When set on a pure/split object file, it
> told the OS to retain the text image on the swap device even when no active
> process was using it. Hence the name...)
>

Ah yes, I remember that now... sorry.

Sticky bit is the low-order bit on the first octet which is usually left 
off and assumed to be zero. So to set it, it would be 1755. 4755 would 
be setuid. Woops.

art k.


  parent reply	other threads:[~2019-08-02 15:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02 14:35 Noel Chiappa
2019-08-02 15:01 ` Clem Cole
2019-08-02 15:17 ` Arthur Krewat [this message]
2019-08-02 21:23   ` Dave Horsfall
2019-08-03 12:51     ` Nemo
  -- strict thread matches above, loose matches on Subject: below --
2019-08-01 23:43 Noel Chiappa
2019-08-02  1:03 ` David Arnold
2019-08-02  4:36   ` Rob Pike
2019-08-07  2:35 ` Dave Horsfall
2019-08-01 12:35 Doug McIlroy
2019-08-01 16:22 ` John P. Linderman
2019-08-01 16:35   ` Arthur Krewat
2019-08-01 17:01 ` Nemo Nusquam
2019-08-01 18:26   ` Arthur Krewat
2019-08-01 20:14     ` Lyndon Nerenberg
2019-08-01 21:23 ` Dave Horsfall

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=c132fb91-c996-1dc9-9d59-60f2cbb6439d@kilonet.net \
    --to=krewat@kilonet.net \
    --cc=tuhs@minnie.tuhs.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).