Re: EXT2 Filesystem permissions (bug)?

[Hua Zhong]

> Do linux even support the sticky bit (t) I can't see a reason to use it, why would I want the file to be stored in the swap ?? 

For files I think it was used in days when there was no VM, so that you could 
hint the system to put frequently used executables always in memory (like vi, 
sh, etc).  After VM was invented, there is really no reason to use it.  I 
don't think newer OSes like Linux implemented this.
 
> Also I think S (setuid but no execute bit) have something to do with file locking but I'am not shure exactly how it works. 

On some unix systems S means using mandatory locking (instead of advisory 
locking).  I am not sure about Linux though.

> "H. Peter Anvin" wrote:
> > 
> > Followup to:  <[e-mail]>
> > By author:    Shawn Starr <[e-mail]>
> > In newsgroup: linux.dev.kernel
> > >
> > > Is this a bug or something thats undocumented somewhere?
> > >
> > > d--------T
> > > and
> > > drwSrwSrwT
> > >
> > > are these special bits? I'm not aware of +S and +T
> > >
> > 
> > It's neither a bug nor undocumented.
> > 
> > "info ls" would have told you the following:
> > 
> >      The permissions listed are similar to symbolic mode
> >      specifications
> >      (*note Symbolic Modes::.).  But `ls' combines multiple bits into
> >      the third character of each set of permissions as follows:
> >     `s'
> >           If the setuid or setgid bit and the corresponding executable
> >           bit are both set.
> > 
> >     `S'
> >           If the setuid or setgid bit is set but the corresponding
> >           executable bit is not set.
> > 
> >     `t'
> >           If the sticky bit and the other-executable bit are both set.
> > 
> >     `T'
> >           If the sticky bit is set but the other-executable bit is not
> >           set.
> > 
> >     `x'
> >           If the executable bit is set and none of the above apply.
> > 
> >     `-'
> >           Otherwise.
> > 
> >         -hpa
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [e-mail]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>