From owner-freebsd-hackers  Sun Jul 22  2:33:50 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from elm.phenome.org (elm.phenome.org [194.153.169.3])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7B4F537B403; Sun, 22 Jul 2001 02:33:45 -0700 (PDT)
	(envelope-from joshua@roughtrade.net)
Received: from localhost (joshua@localhost [127.0.0.1])
        by localhost (8.12.0.Beta7/8.12.0.Beta7/Debian 8.12.0.Beta7-1) with ESMTP id f6M9XiCC020292;
	Sun, 22 Jul 2001 10:33:44 +0100
Date: Sun, 22 Jul 2001 10:33:44 +0100 (BST)
From: Joshua Goodall <joshua@roughtrade.net>
X-X-Sender:  <joshua@elm.phenome.org>
To: <freebsd-fs@freebsd.org>, <freebsd-hackers@freebsd.org>
Subject: flags on symlinks
Message-ID: <Pine.LNX.4.33.0107220851520.4671-100000@elm.phenome.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


Is there a particular reason why there's no capability for setting flags
on symlinks? the chflags syscall uses namei with FOLLOW, and changing this
to NOFOLLOW allows chflags(2) to Do What I Want (i.e. SF_IMMUTABLE on a
VLNK)

is there a filesystem train crash awaiting me for doing this, or am I in
the clear? I realise it changes the semantics of chflags(1) so an
alternative syscall or a follow/nofollow boolean addition to struct
chflags_args is better than this hack.

regards

joshua


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message