2 Aug
2019
2 Aug
'19
2:35 p.m.
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...)
Noel
2 Aug
2 Aug
3:01 p.m.
New subject: Who's behind the UNIX filesystem permission
On Fri, Aug 2, 2019 at 10:58 AM Noel Chiappa <jnc(a)mercury.lcs.mit.edu>
wrote:
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...)
Indeed, nice catch, Noel.
3:17 p.m.
New subject: Who's behind the UNIX filesystem permission
On 8/2/2019 10:35 AM, Noel Chiappa wrote:
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.
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...)
9:23 p.m.
New subject: Who's behind the UNIX filesystem permission
On Fri, 2 Aug 2019, Arthur Krewat wrote:
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.
That's why I use the symbolic modes on "chmod" instead of the octal ones
:-)
-- Dave
1729
days inactive
1730
days old
4 comments
5 participants
participants (5)
-
Arthur Krewat -
Clem Cole -
Dave Horsfall -
jnc＠mercury.lcs.mit.edu -
Nemo