The Unix Heritage Society mailing list
 help / Atom feed
From: Bakul Shah <>
To: The Eunuchs Hysterical Society <>
Subject: Re: [TUHS] Unix filesystem semantics history - files with holes
Date: Thu, 11 Apr 2019 12:49:34 -0700
Message-ID: <> (raw)
In-Reply-To: <>

On Apr 11, 2019, at 8:57 AM, Richard Tobin <> wrote:
>> When did the Unix filesystem add the semantics for "files with holes" (large,
>> sparse files)?
> It was there in the first edition:

You still had to read all those unallocated blocks as zeroes
if you wanted to copy such a "holey" file. I believe it was
Solaris (may be just for zfs?) that added SEEK_HOLE and
SEEK_DATA lseek whence values.

This could've been hidden if only mmap was allowed on files.
Or alternately read/write buffering was done by the kernel
or the {network,file}-server - which can avoid copying in
cases where it makes sense. 

      parent reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11  2:37 Erik E. Fair
2019-04-11  5:28 ` Ronald Natalie
2019-04-11 15:57 Richard Tobin
2019-04-11 19:09 ` William Corcoran
2019-04-11 19:49 ` Bakul Shah [this message]

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

The Unix Heritage Society mailing list

Archives are clonable: git clone --mirror

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox