From owner-freebsd-current Thu Mar 8 11: 3:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.wgate.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id C022E37B71A for ; Thu, 8 Mar 2001 11:03:30 -0800 (PST) (envelope-from rjesup@wgate.com) Received: from jesup.eng.tvol.net ([10.32.2.26]) by mail.wgate.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id GN5Y4A0S; Thu, 8 Mar 2001 14:03:45 -0500 Reply-To: Randell Jesup To: current@FreeBSD.ORG Subject: Re: mount: /dev/ad0s1e: File name too long From: Randell Jesup Date: 08 Mar 2001 14:03:46 -0500 In-Reply-To: Bruce Evans's message of "Mon, 5 Mar 2001 18:24:25 +1100 (EST)" Message-ID: User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: >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. And what if you have to use them (or want to)? If df/mount/etc have bugs, let's fix those (not that I think they're significant). -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message