Date: Mon, 5 Mar 2001 18:24:25 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: Boris Popov <bp@butya.kz> Cc: Adrian Chadd <adrian@FreeBSD.ORG>, John Baldwin <jhb@FreeBSD.ORG>, Edwin Culp <eculp@EnContacto.Net>, current@FreeBSD.ORG Subject: Re: mount: /dev/ad0s1e: File name too long Message-ID: <Pine.BSF.4.21.0103051810530.1279-100000@besplex.bde.org> In-Reply-To: <Pine.BSF.4.21.0103050808010.97795-100000@lion.butya.kz>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0103051810530.1279-100000>