Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 29 Jul 2015 05:48:50 +0100
From:      Jamie Landeg-Jones <jamie@dyslexicfish.net>
To:        ian.freislich@capeaugusta.com, gpalmer@freebsd.org
Cc:        david@catwhisker.org, current@freebsd.org
Subject:   Re: "broken" symbolic links in /usr/lib
Message-ID:  <201507290448.t6T4moDa019590@dyslexicfish.net>
In-Reply-To: <20150728232054.GG41419@in-addr.com>
References:  <20150728200034.GO1277@albert.catwhisker.org> <20150728184516.GN1277@albert.catwhisker.org> <E1ZK9QG-000CAR-KW@clue.co.za> <E1ZKAuN-000CK7-MG@clue.co.za> <E1ZKBJi-0000JZ-FS@clue.co.za> <20150728232054.GG41419@in-addr.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Gary Palmer <gpalmer@freebsd.org> wrote:

> As best that I can recall, the permissions of the directory underneath
> the mount point has been causing problems like this for as long as I've been
> using FreeBSD, which is over 20 years at this point.  It's certainly
> bit me in the distant past.

I concur. I always make mount point directories 0111,noschg,nodump - it makes
them stand out when not mounted, and also stops accidental directory deletion
potentially stopping a reboot from working.

But yeah, for 20+ years. I've also experienced problems if a mount-point
directory doesn't have +x access.

Cheers, Jamie



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201507290448.t6T4moDa019590>