Date: Mon, 3 Jul 2000 09:40:06 -0400 (EDT) From: James Howard <howardjp@glue.umd.edu> To: Sheldon Hearn <sheldonh@uunet.co.za> Cc: arch@FreeBSD.ORG Subject: Re: truncate(1) implementation details Message-ID: <Pine.GSO.4.21.0007030936580.5251-100000@y.glue.umd.edu> In-Reply-To: <30275.962630649@axl.ops.uunet.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 3 Jul 2000, Sheldon Hearn wrote: > Good point, this is a problem, but it has nothing to do with -c. Do you > agree that truncation that would reduce the number of bytes allocated to > a file below zero should silently set the file size to zero? Yes. Maybe a -v to tell us what is happening. Wow, adding options right and left. Of course, if this were done at MIT, we'd have to make sure it could read mail. > Block dewhat? :-) DOH! I forgot those were gone. > I would have expected truncate(2) to fail with ENOTSUPP on devices, but > that's not what the manual page says. Try it on /dev/zero for kicks and see what happens. Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.21.0007030936580.5251-100000>