Date: Tue, 2 Nov 1999 04:20:02 -0800 (PST) From: Lars =?iso-8859-1?Q?K=F6ller?= <Lars.Koeller@Uni-Bielefeld.DE> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/14322: mount respects permissions of underlying directoy!! Message-ID: <199911021220.EAA04392@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/14322; it has been noted by GNATS.
From: Lars =?iso-8859-1?Q?K=F6ller?= <Lars.Koeller@Uni-Bielefeld.DE>
To: Steve Brown <sb@napanet.net>
Cc: freebsd-gnats-submit@freebsd.org, lkoeller@cc.fh-lippe.de
Subject: Re: kern/14322: mount respects permissions of underlying directoy!!
Date: Tue, 02 Nov 1999 13:12:15 +0100
In reply to Steve Brown who wrote:
> The described condition is rather a normal happening; for over ten years I
> have always made sure my mount point and the mounted directory share
> permissions (UID and mode) in various flavours of UNIX -- I've seen this
> happen on Sun computers and ever since I have matched mounted and mount
> point permissions.
>
> Not saying it isn't a bug, but it sure can make you scratch your head the
> first time you see it :^)
A little test on our HP Cluster (HPUX 10.20) shows the expeted
behavior, only the permissions of the mounted directory are valid.
for the accessrights. The underlying directory perms aren't
valid anymore after the mount.
Does anybody know if this behavior has changed in some older FreeBSD
version, cause I remember a case where the permissions only of the
mounted directory are respected!
Is the default behavior mentioned in any manpage? I didn't found
one!
Regards
Lars
--
Lars Köller | Raum : V0-318 (Tel: 4964)
UNIX Systemad- | E-Mail : Lars.Koeller@Uni-Bielefeld.DE
ministration | PGP-Key: http://www.pgp.net/pgpnet/www-key.html
----------- FreeBSD, what else? ---- http://www.de.freebsd.org ---------
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911021220.EAA04392>