On Mon, 5 Mar 2001, Boris Popov wrote:
> On Sun, 4 Mar 2001, Adrian Chadd wrote:
>
> > > Blame Adrian Chadd ([EMAIL PROTECTED]) :) 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
