From: Ronald Natalie <ron@ronnatalie.com>
To: "Erik E. Fair" <fair-tuhs@netbsd.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Unix filesystem semantics history - files with holes
Date: Thu, 11 Apr 2019 01:28:57 -0400 [thread overview]
Message-ID: <0FA98B50-9800-48A8-8B19-D070D17767AF@ronnatalie.com> (raw)
In-Reply-To: <3993.1554950225@cesium.clock.org>
Define large? It appears that filesystems going back to Research V4 supported sparse files. The maximum file size went up from 2**24 in V6 to 2**32 in V7, and then broke that barrier in several of the subsequent file systems.
> On Apr 10, 2019, at 10:37 PM, Erik E. Fair <fair-tuhs@netbsd.org> wrote:
>
> When did the Unix filesystem add the semantics for "files with holes" (large,
> sparse files)?
>
> Just an idle question that was sparked by a conversation I had today.
>
> Erik <fair@clock.org>
next prev parent reply other threads:[~2019-04-11 5:29 UTC|newest]
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 [this message]
2019-04-11 15:57 Richard Tobin
2019-04-11 19:09 ` William Corcoran
2019-04-11 19:49 ` Bakul Shah
Reply instructions:
You may reply publicly 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0FA98B50-9800-48A8-8B19-D070D17767AF@ronnatalie.com \
--to=ron@ronnatalie.com \
--cc=fair-tuhs@netbsd.org \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).