From owner-freebsd-current@FreeBSD.ORG Tue Jan 20 00:23:15 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0501BFBF for ; Tue, 20 Jan 2015 00:23:15 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id CFE2AFCF for ; Tue, 20 Jan 2015 00:23:14 +0000 (UTC) Received: from [192.168.1.2] (Seawolf.HML3.ScaleEngine.net [209.51.186.28]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 7253C8DD8F for ; Tue, 20 Jan 2015 00:23:07 +0000 (UTC) Message-ID: <54BD9FF1.5090202@freebsd.org> Date: Mon, 19 Jan 2015 19:23:13 -0500 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: old bug: mount_nfs path/name is limited to 88 chars References: <1401700998.16283447.1421681564732.JavaMail.root@uoguelph.ca> <201501191544.t0JFiP7O027952@mech-as221.men.bris.ac.uk> <99F7DA1A-66EB-4F69-BAFA-0D72E4207248@gmail.com> In-Reply-To: <99F7DA1A-66EB-4F69-BAFA-0D72E4207248@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="JgxPqPOsG5diGVGNOj2utUWSQfnD0OTQj" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2015 00:23:15 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --JgxPqPOsG5diGVGNOj2utUWSQfnD0OTQj Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015-01-19 16:20, Garrett Cooper wrote: > On Jan 19, 2015, at 8:46, Brandon Allbery wrote: >=20 >> 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 nee= d to >> originate in -current). >=20 > A compat layer needs to be created for all of the affected syscalls, an= d the change needs to be made. That=92s it in a nutshell. >=20 > Doing it in 11 makes sense since there is a compat layer for 10 now=85 = 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. >=20 > Thanks! >=20 Especially with ZFS, I find I have a lot more mounts now, under longer and longer path names, and then I have =2Ezfs/snapshots/snapshotnamehere/path/to/file etc. Definitely a +1 for "this is something we need for 11" --=20 Allan Jude --JgxPqPOsG5diGVGNOj2utUWSQfnD0OTQj Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJUvZ/zAAoJEJrBFpNRJZKf7LQP/ix7WdEbA6idiy68IV8BAlr2 RA3zwm7D1xMy0aIQ8aa18QaYESqM0Hn8sRYgXV2ATfwcMjsF1c3KNz6CaCIeF3oQ +kDN5CPQZ/Azbx+Kr60IieEBDvP9IcKN8HkqDsc6UMEsUhzYJbYT901qawn+Aisx SsFdpo86T7wXGvbgTulLZmgrlGgipC7EbO0BMj2kcZe6EzqWi3F1AI4JDzjhPp7v qE+Z78VTyxc96kdd98T1DcNJ3jNt2TetJzja9Iesaga9uSvAyoga2cVhwKMDR2dO nyhfRomLuQmlwmc9lQdBkuPZKeIq6kgXBXYbh768+mA+weGgkFbFoxO2+VhNpJEo MpW93/bxjTv+jqj9da4FpJiWdoBLc22WyPvZmB30Qk8efPr0p3O5vPhP/usztXvm kt4O2Qx5xS0V+4Rcmgsh4QRF9DxI1qmEIKwUcZddQIr4zM1/vLBe61Z5rGWnxlr0 5XIhYu00EumSu9YYWoaQ9Ty70HC8qBBmIgXHojFtO9sTnO71IoivjYBmmEiAOaSo XMz3/BTJcul+8BsRn5FD+MDabRhG9d1TW70nN9Xj8wFq//fTaPP9c7E2LAUknCjR 5cCKD8/lnfNDsM20WvOIH6mFt3C3dQ2y6Fuse8YWvysFROuqkxQPcH5aAI9pp1CT AJUrSa35dc6Hw8ihDwGA =fOof -----END PGP SIGNATURE----- --JgxPqPOsG5diGVGNOj2utUWSQfnD0OTQj--