Date: Tue, 5 Apr 2011 13:06:46 -0400 From: Ryan Stone <rysto32@gmail.com> To: gljennjohn@googlemail.com Cc: freebsd-fs@freebsd.org Subject: Re: Knob to turn off _POSIX_NO_TRUNC Message-ID: <BANLkTi=rA9uSzbzX0fV-8pci=p=Pa6PO6A@mail.gmail.com> In-Reply-To: <20110405183104.2304d94e@ernst.jennejohn.org> References: <20110405141631.GA78089@deviant.kiev.zoral.com.ua> <20110405172746.4a02fe42@ernst.jennejohn.org> <20110405154002.GD78089@deviant.kiev.zoral.com.ua> <20110405183104.2304d94e@ernst.jennejohn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 5, 2011 at 12:31 PM, Gary Jennejohn <gljennjohn@googlemail.com> wrote: > OK, but trimming to me as a native english speaker means returning ENAMET= OOLONG > rather than allowing names longer than NAME_MAX. =A0That is, after all, w= hat trimming > means - cutting off. The two behaviours here are: lookup_trim =3D=3D 1 -- filenames are silently truncated(i.e. trimmed) if longer than NAME_MAX lookup_trim =3D=3D 0 -- filenames longer than NAME_MAX are rejected with ENAMETOOLONG The name makes perfect sense to me, personally.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTi=rA9uSzbzX0fV-8pci=p=Pa6PO6A>