From owner-freebsd-bugs Sun Feb 11 22:20: 4 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4320A37B491 for ; Sun, 11 Feb 2001 22:20:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f1C6K2O16726; Sun, 11 Feb 2001 22:20:02 -0800 (PST) (envelope-from gnats) Date: Sun, 11 Feb 2001 22:20:02 -0800 (PST) Message-Id: <200102120620.f1C6K2O16726@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Bruce Evans Subject: Re: kern/25018: lstat(2) returns bogus permissions on symlinks Reply-To: Bruce Evans Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/25018; it has been noted by GNATS. From: Bruce Evans To: mkamm@gmx.net Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/25018: lstat(2) returns bogus permissions on symlinks Date: Mon, 12 Feb 2001 17:11:43 +1100 (EST) On Sat, 10 Feb 2001 mkamm@gmx.net wrote: > >How-To-Repeat: > > (umask 321 && ln -s "have strange but nontheless nonexistant perms" symlinks) > ls -l symlinks > > The permissions shown reflect the umask value at the time of the > symlink(2) call rather than the more intuitive "lrwxrwxrwx" or > in case of mount -onosymfollow "l---------". Fixing this makes lchmod(2) more useless than it already is :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message