From owner-freebsd-arch Tue Jan 15 8:30:17 2002 Delivered-To: freebsd-arch@freebsd.org Received: from green.bikeshed.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 469BE37B416; Tue, 15 Jan 2002 08:30:10 -0800 (PST) Received: from localhost (green@localhost) by green.bikeshed.org (8.11.6/8.11.6) with ESMTP id g0FGU5k77068; Tue, 15 Jan 2002 11:30:05 -0500 (EST) (envelope-from green@green.bikeshed.org) Message-Id: <200201151630.g0FGU5k77068@green.bikeshed.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Poul-Henning Kamp Cc: Max Khon , arch@FreeBSD.ORG Subject: Re: request for review In-Reply-To: Your message of "Tue, 15 Jan 2002 11:53:46 +0100." <19068.1011092026@critter.freebsd.dk> From: "Brian F. Feldman" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Jan 2002 11:30:05 -0500 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > I think it is bogus for devices other than disks to flout a > va_blocksize, but I am on the other hand not sure what the > relevant (if any) standards say. > > If this patch makes things better, I'm all for it. Posix specifies that st_size for non-regular files is "unspecified", however it doesn't specify st_blksize at all. In the "spirit" of POSIX I'd say st_blksize is free to be anything we want it to be, and non-0 for VCHR is certainly a reasonable value of anything. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message