Date: Sun, 25 Mar 2012 16:32:53 -0700 From: Tim Kientzle <tim@kientzle.com> To: Gleb Kurtsou <gleb.kurtsou@gmail.com> Cc: freebsd-current FreeBSD <freebsd-current@freebsd.org> Subject: Re: /usr/bin/tar creates invalid lib file Message-ID: <903ACDC1-CE39-45A5-8F37-9FE9BC969F42@kientzle.com> In-Reply-To: <20120325214327.GA1238@reks> References: <4F6CD93D.70109@passap.ru> <4F6CEB1F.4040300@FreeBSD.org> <4F6D52DF.7080105@passap.ru> <4F34E618-DB66-464D-B5B2-900960D6C16B@kientzle.com> <4F6F155E.30902@passap.ru> <38D08B05-58E1-4266-9628-2C22836806D3@kientzle.com> <20120325214327.GA1238@reks>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 25, 2012, at 2:43 PM, Gleb Kurtsou wrote: > I experience a related issue. lseek(SEEK_HOLE) error checks are too > strict. Files are not added to archive if lseek(SEEK_HOLE) fails. > Ignoring lseek(SEEK_HOLE) at least in ENOTTY case would be preferable. Just noticed that lseek(1) doesn't document ENOTTY as a valid response code. Should it? Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?903ACDC1-CE39-45A5-8F37-9FE9BC969F42>