Date: Mon, 19 Jan 2015 11:46:57 -0500 From: Brandon Allbery <allbery.b@gmail.com> To: mexas@bris.ac.uk Cc: rmacklem@uoguelph.ca, freebsd-stable <freebsd-stable@freebsd.org>, freebsd current <freebsd-current@freebsd.org> Subject: Re: old bug: mount_nfs path/name is limited to 88 chars Message-ID: <CAKFCL4Vv5Uf7p737uE-riDBw57KTJ7r7QSmn7Bj7i=gn1yo5UA@mail.gmail.com> In-Reply-To: <201501191544.t0JFiP7O027952@mech-as221.men.bris.ac.uk> References: <1401700998.16283447.1421681564732.JavaMail.root@uoguelph.ca> <201501191544.t0JFiP7O027952@mech-as221.men.bris.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 19, 2015 at 10:44 AM, Anton Shterenlikht <mexas@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). -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKFCL4Vv5Uf7p737uE-riDBw57KTJ7r7QSmn7Bj7i=gn1yo5UA>