From owner-freebsd-questions Tue Sep 3 08:13:11 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA04193 for questions-outgoing; Tue, 3 Sep 1996 08:13:11 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA04188 for ; Tue, 3 Sep 1996 08:13:06 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id IAA03081; Tue, 3 Sep 1996 08:10:40 -0700 (PDT) Message-Id: <199609031510.IAA03081@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: David Hedley cc: freebsd-questions@freefall.freebsd.org Subject: Re: symlinks misfeature? In-reply-to: Your message of "Tue, 03 Sep 1996 14:44:21 BST." <19399.841758261@kiha> From: David Greenman Reply-To: dg@root.com Date: Tue, 03 Sep 1996 08:10:40 -0700 Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Having just done man 7 symlinks, I notice that it says symlinks are not >owned by the user that created them, but rather by the owner of the >directory. This is all very well until a user creates a symlink in /tmp >and then finds out they can't remove it as the symlink is 'owned' by >root (the owner of the directory), and /tmp has the sticky bit set. > >Is there any solution to this problem? I realise (being documented) it >isn't really a bug, but surely this behaviour is not desirable? If there >is a workaround for it I would knowing appreciate it! The solution will likely be that we'll have to revert the 4.4BSD behavior back to the traditional unix behavior. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project