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

[Allan Jude]

On 2015-01-19 16:20, Garrett Cooper wrote:
> On Jan 19, 2015, at 8:46, Brandon Allbery <allbery.b at gmail.com> wrote:
> 
>> On Mon, Jan 19, 2015 at 10:44 AM, Anton Shterenlikht <mexas at bris.ac.uk>
>> 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 -current).
> 
> A compat layer needs to be created for all of the affected syscalls, and the change needs to be made. That’s it in a nutshell.
> 
> 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.
> 
> Thanks!
> 

Especially with ZFS, I find I have a lot more mounts now, under longer
and longer path names, and then I have
.zfs/snapshots/snapshotnamehere/path/to/file

etc.

Definitely a +1 for "this is something we need for 11"

-- 
Allan Jude

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 834 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20150119/56535fcd/attachment.sig>