Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!ihlpe!daryl
From: daryl@ihlpe.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: Size of SysV "block"
Message-ID: <1852@ihlpe.ATT.COM>
Date: Wed, 8-Jul-87 22:31:49 EDT
Article-I.D.: ihlpe.1852
Posted: Wed Jul  8 22:31:49 1987
Date-Received: Sat, 11-Jul-87 15:45:04 EDT
References: <218@astra.necisa.oz> <348@forbrk.UUCP>
Organization: Engineering Design Process Department, AT&T Bell Labs
Lines: 20
Keywords: blocks sectors
Summary: not always

In article <348@forbrk.UUCP>, mats@forbrk.UUCP (Mats Wichmann) writes:
> In article <218@astra.necisa.oz> dave@astra.necisa.oz (Dave Horsfall) writes:
> >Can anyone tell me in an unambiguous manner just how many bytes
> >are in the following System V (2.?) "blocks"? 
> 
> >	ls -s   du   df   tar -b   cpio -B   mkfs   fsck   fsdb
> All of the preceding are 512 byte "blocks" and refer to "disk" blocks;
> >	BUFSIZ
> This is the stdio buffer size and varies from system to system, although
> it seems to be 1024 for most V.2 implementations - should be the same size 

UTS block sizes on our machines differ from "normal" VAX/sun/most things.

To this day I am not sure why we cannot use either bytes, Kbytes, Mbytes, etc.
instead of blocks.


Daryl Monge				UUCP:	...!ihnp4!ihcae!dlm
AT&T					CIS:	72717,65
Bell Labs, Naperville, Ill		AT&T	312-979-3603