Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:11106 gnu.misc.discuss:15357 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!uwm.edu!spool.mu.edu!howland.reston.ans.net!pipex!sunic!news.uni-c.dk!iesd.auc.dk!news.iesd.auc.dk!abraham From: abraham@iesd.auc.dk (Per Abrahamsen) Newsgroups: comp.os.386bsd.questions,gnu.misc.discuss Subject: Re: Taylor UUCP on FreeBSD??? Date: 25 Jun 1994 15:50:15 GMT Organization: AUC Lines: 18 Message-ID: <ABRAHAM.94Jun25175015@verdande.iesd.auc.dk> References: <1994Jun13.040754.17764@kosman.uucp> <RSANDERS.94Jun22110639@hrothgar.mindspring.com> <1994Jun22.184617.10333@cm.cf.ac.uk> <RSANDERS.94Jun23005720@hrothgar.mindspring.com> <2ugieg$hh9@news.u.washington.edu> NNTP-Posting-Host: verdande.iesd.auc.dk Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit In-reply-to: tzs@u.washington.edu's message of 25 Jun 1994 06:22:08 GMT X-Newsreader: GNUS 4.1 >> Well, on a Unix filesystem, if a file has a long run of zeroes that >> touch both boundaries of one or mor blocks, it may be possible to >> represent that run of zeroes without actually allocating a block. In >>>>> "Tim" == Tim Smith <tzs@u.washington.edu> writes: Tim> That's not what a hole is on a Unix file system. Yes it is. Tim> A hole is a block of the file that has never contained data. A Tim> hole is created by seeking past the current end of the file and Tim> then writing. That too.