[lkml]   [1999]   [Oct]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: buglet in ext2 sticky bit?
    On Sun, Oct 24, 1999 at 10:06:15PM +0100, Matthew Kirkwood wrote:
    > On Sun, 24 Oct 1999, Jan Kara wrote:
    > > When it has sticky bit set than file can be deleted only by its owner
    > > or owner of the directory.
    > Intestingly, this works on Solaris 2.6 (both tmpfs and ufs).
    > I seem to be able to delete any file in /tmp which I own _or_ can write
    > to.
    > Stevens' APUE doesn't mention this feature, so I'd be tempted to call
    > it a bug in Solaris (can't test other OSes, unfortunately).
    Oops, I remember something about ownership of symlinks. A symlink in /tmp
    owned by root should never be unlinkable. Now we all know that the mode
    of a symlink is meaningless so its owner must be meaningful in order to
    create a difference in /tmp.

    As far as I can recall many UNIXes deviate with respect to being able
    to unlink files not owned by the euid in a 01777 directory like /tmp
    The same UNIXes fail to restore the ownership of symlinks. For example,
    on OSF/1 4.x "tar x.." doesn't lchown() symlinks to the original owner
    when invoked as root. At the other side, the meaningless effect umask(2)
    sometimes has on these symlinks is confusing as well (OSF/1 and linux
    do the right thing though).

    This dark corner in commercial UNIXes needs to be cleaned up but that's
    not our task :-)

    Frank van Maarseveen Driebergen The Netherlands

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:54    [W:0.021 / U:1.000 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site