Bruce Evans <[EMAIL PROTECTED]> 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 al
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 li
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 hav
On Fri, Mar 02, 2001, John Baldwin wrote:
>
> On 02-Mar-01 Edwin Culp wrote:
> > I just found something new in current. When I rebooted with todays current,
> > it
> > put me into single user with the following message:
> >
> > mount: /dev/ad0s1e: File name
On 02-Mar-01 Edwin Culp wrote:
> I just found something new in current. When I rebooted with todays current,
> it
> put me into single user with the following message:
>
> mount: /dev/ad0s1e: File name too long
>
> The problem seems to be the directory that I have been
I just found something new in current. When I rebooted with todays current, it
put me into single user with the following message:
mount: /dev/ad0s1e: File name too long
The problem seems to be the directory that I have been mounting it under for a
couple of years. /var/ftp/release If I
