From owner-freebsd-current Sun Mar 4 23:24:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 7B3D937B718; Sun, 4 Mar 2001 23:24:48 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id SAA10091; Mon, 5 Mar 2001 18:24:33 +1100 Date: Mon, 5 Mar 2001 18:24:25 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Boris Popov Cc: Adrian Chadd , John Baldwin , Edwin Culp , current@FreeBSD.ORG Subject: Re: mount: /dev/ad0s1e: File name too long In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 5 Mar 2001, Boris Popov wrote: > On Sun, 4 Mar 2001, Adrian Chadd wrote: > > > > Blame Adrian Chadd (adrian@FreeBSD.org) :) Apparently the limit he's enforcing > > > on mount names is rather short... :) > > > > For those who asked, I'll MFC this to -stable once its settled down > > a little. There are a few other bits I need to do that have been pointed > > out to me before I'm happy with the change. > > I'm unsure if this necessary (and valid) because these things make > incompatible changes in API. Lets keep at least -stable consistent :) I think I prefer the old behaviour. The names preserved by the kernel can't possibly remain valid until unmount in all cases. Examples: - pathnames relative to the current directory work. These only remain valid if the process that does the mount also does the unmount (and doesn't chdir). - the pathnames may involve symlinks that go away or change before unmount. The fix for this is: don't do that. This is also a reaonable fix for long pathnames -- don't use them unless you really have to. Long names even mess up the most common uses of the preserved names -- displaying them in df, mount, etc. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message