From owner-freebsd-arch  Mon Jul  3  6:43:41 2000
Delivered-To: freebsd-arch@freebsd.org
Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.2.163])
	by hub.freebsd.org (Postfix) with ESMTP id ECA3937B5B7
	for <arch@freebsd.org>; Mon,  3 Jul 2000 06:43:36 -0700 (PDT)
	(envelope-from sheldonh@axl.ops.uunet.co.za)
Received: from sheldonh (helo=axl.ops.uunet.co.za)
	by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1)
	id 1396VT-0007zu-00; Mon, 03 Jul 2000 15:43:27 +0200
From: Sheldon Hearn <sheldonh@uunet.co.za>
To: James Howard <howardjp@glue.umd.edu>
Cc: arch@FreeBSD.ORG
Subject: Re: truncate(1) implementation details 
In-reply-to: Your message of "Mon, 03 Jul 2000 09:40:06 -0400."
             <Pine.GSO.4.21.0007030936580.5251-100000@y.glue.umd.edu> 
Date: Mon, 03 Jul 2000 15:43:27 +0200
Message-ID: <30745.962631807@axl.ops.uunet.co.za>
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Mon, 03 Jul 2000 09:40:06 -0400, James Howard wrote:

> Yes.  Maybe a -v to tell us what is happening.  Wow, adding options right
> and left.

None of which would be required if we just didn't create the files. 
Sometimes, simplicity is elegant. ;-)

> > 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.

Oooh, I was right.  It fails on ENOTSUPP.  Great, an addition for the
truncate(2) manual page.  :-)

Ciao,
Sheldon.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message