Re: old bug: mount_nfs path/name is limited to 88 chars

2015-01-22 Thread Doug Ambrisko
On Tue, Jan 20, 2015 at 12:45:32PM +0100, Willem Jan Withagen wrote: | On 2015-01-20 2:05, Xin Li wrote: | >>Doing it in 11 makes sense since there is a compat layer for 10 | >>now? if I knew all of the steps I would happily do them as annoys | >>me from time to time as well with the path length is

Re: old bug: mount_nfs path/name is limited to 88 chars

2015-01-20 Thread Willem Jan Withagen
On 2015-01-20 2:05, Xin Li wrote: Doing it in 11 makes sense since there is a compat layer for 10 now… if I knew all of the steps I would happily do them as annoys me from time to time as well with the path length issue. Compat layer may break applications in other funny ways and we probably ha

Re: old bug: mount_nfs path/name is limited to 88 chars

2015-01-19 Thread Rick Macklem
Xin Li wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 01/19/15 13:20, Garrett Cooper wrote: > > On Jan 19, 2015, at 8:46, Brandon Allbery > > wrote: > > > >> On Mon, Jan 19, 2015 at 10:44 AM, Anton Shterenlikht > >> wrote: > >> > >>> So perhaps changing MNAMELEN will break s

Re: old bug: mount_nfs path/name is limited to 88 chars

2015-01-19 Thread Xin Li
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 01/19/15 13:20, Garrett Cooper wrote: > On Jan 19, 2015, at 8:46, Brandon Allbery > wrote: > >> On Mon, Jan 19, 2015 at 10:44 AM, Anton Shterenlikht >> wrote: >> >>> So perhaps changing MNAMELEN will break statfs(2) on -stable >>> too? >>> >>

Re: old bug: mount_nfs path/name is limited to 88 chars

2015-01-19 Thread Allan Jude
On 2015-01-19 16:20, Garrett Cooper wrote: > On Jan 19, 2015, at 8:46, Brandon Allbery wrote: > >> On Mon, Jan 19, 2015 at 10:44 AM, Anton Shterenlikht >> wrote: >> >>> So perhaps changing MNAMELEN will break statfs(2) on >>> -stable too? >>> >> >> I believe the context there is not so much "-cu

Re: old bug: mount_nfs path/name is limited to 88 chars

2015-01-19 Thread Willem Jan Withagen
On 19-1-2015 22:20, Garrett Cooper wrote: > On Jan 19, 2015, at 8:46, Brandon Allbery > wrote: > >> On Mon, Jan 19, 2015 at 10:44 AM, Anton Shterenlikht >> wrote: >> >>> So perhaps changing MNAMELEN will break statfs(2) on -stable >>> too? >>> >> >> I believe the context there is not so much

Re: old bug: mount_nfs path/name is limited to 88 chars

2015-01-19 Thread Garrett Cooper
On Jan 19, 2015, at 8:46, Brandon Allbery wrote: > On Mon, Jan 19, 2015 at 10:44 AM, Anton Shterenlikht > wrote: > >> So perhaps changing MNAMELEN will break statfs(2) on >> -stable too? >> > > I believe the context there is not so much "-current is special", as > "changing it for everyone is

Re: old bug: mount_nfs path/name is limited to 88 chars

2015-01-19 Thread Brandon Allbery
On Mon, Jan 19, 2015 at 10:44 AM, Anton Shterenlikht wrote: > So perhaps changing MNAMELEN will break statfs(2) on > -stable too? > I believe the context there is not so much "-current is special", as "changing it for everyone is bad news" (and this would necessarily need to originate in -curren

Re: old bug: mount_nfs path/name is limited to 88 chars

2015-01-19 Thread Anton Shterenlikht
>From rmack...@uoguelph.ca Mon Jan 19 15:37:25 2015 >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=167105 >> >> is a show stopper for me. The path/name length is >> beyond my control, so I cannot make it shorter. >> >> This discussion seems inconclusive: >> http://lists.freebsd.org/pipermai

Re: old bug: mount_nfs path/name is limited to 88 chars

2015-01-19 Thread Rick Macklem
Anton Shterenlikht wrote: > This bug: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=167105 > > is a show stopper for me. The path/name length is > beyond my control, so I cannot make it shorter. > > This discussion seems inconclusive: > http://lists.freebsd.org/pipermail/freebsd-hackers/201

old bug: mount_nfs path/name is limited to 88 chars

2015-01-19 Thread Anton Shterenlikht
This bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=167105 is a show stopper for me. The path/name length is beyond my control, so I cannot make it shorter. This discussion seems inconclusive: http://lists.freebsd.org/pipermail/freebsd-hackers/2012-April/038543.html Is there no easy solu