From owner-freebsd-arch Mon Jul 3 14:55:29 2000 Delivered-To: freebsd-arch@freebsd.org Received: from server.baldwin.cx (server.geekhouse.net [64.81.6.52]) by hub.freebsd.org (Postfix) with ESMTP id 27A6C37B64B for ; Mon, 3 Jul 2000 14:55:15 -0700 (PDT) (envelope-from john@baldwin.cx) Received: from john.baldwin.cx (root@john.baldwin.cx [192.168.1.18]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id OAA29908; Mon, 3 Jul 2000 14:55:13 -0700 (PDT) (envelope-from john@baldwin.cx) Received: (from john@localhost) by john.baldwin.cx (8.9.3/8.9.3) id OAA37008; Mon, 3 Jul 2000 14:56:15 -0700 (PDT) (envelope-from john) Message-Id: <200007032156.OAA37008@john.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <904.962613305@axl.ops.uunet.co.za> Date: Mon, 03 Jul 2000 14:56:15 -0700 (PDT) From: John Baldwin To: Sheldon Hearn Subject: RE: truncate(1) implementation details Cc: arch@FreeBSD.ORG Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Jul-00 Sheldon Hearn wrote: > > Hi folks, > > I'm looking through Alexander Langer's truncate(1) with a view to > importing it shortly. > > I raised some issues with Alexander and he responded with the message > below. The issue I'd like feedback on is whether or not truncate(1) > should create files given on the command-line when those files do not > exist at the time of invocation. > > My feeling is that truncate should not do so. Alexander's opinion is > given in the e-mail message. > > Any compelling arguments in either direction? I think it should create the file. touch(1)'s job is just to change the file access and mod times, yet it creates files. Thus, I think there is adequate precedent for truncate(1) creating files. --- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message