Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!olivea!spool.mu.edu!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!math.fu-berlin.de!irz401!uriah!not-for-mail
From: j@bonnie.tcd-dresden.de (J Wunsch)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: bug with ufs file creation
Date: 20 Sep 1993 17:36:48 +0200
Organization: Textil Computer Design GmbH Dresden, Germany
Lines: 20
Message-ID: <27kimgINNdsn@bonnie.tcd-dresden.de>
References: <328@rook.ukc.ac.uk> <CD0AnI.1rM@taronga.com> <CD44wx.LHs@rex.uokhsc.edu> <1993Sep12.151731.2246@intellistor.com> <CDApKG.8op@flatlin.ka.sub.org>
NNTP-Posting-Host: bonnie.tcd-dresden.de
bad@flatlin.ka.sub.org (Christoph Badura) writes:
>>This allows a
>>simple method of permitting a "world usable" directory that individual
>>users could protect their files in..
>What's wrong with setting the sticky bit on that directory? Assuming
>you're running NET/2 or later, SVR4, Solaris, or recent versions of
>SunOS. Any other systems that support this?
But the actual sticky-bit permission semantics for a directory are horrid.
Okay, it's nice to have /tmp/foo protected from being deleted by every-
one. But, on the other hand, if i create /tmp/foo with permissions
0666, despite of anybody can write a null file over it, only root and
me are allowed to remove it. A bit strange...
--
in real life: J"org Wunsch | ) o o | primary: joerg_wunsch@tcd-dresden.de
above 1.8 MHz: DL 8 DTL | ) | | private: joerg_wunsch@uriah.sax.de
| . * ) == |
``An elephant is a mouse with an operating system.''