From: "Ethan Gardener" <eekee57@fastmail.fm>
To: "g_patrickb via 9fans" <9fans@9fans.net>
Subject: Re: [9fans] Help with Interpretation
Date: Thu, 16 Jan 2020 17:00:35 +0000 [thread overview]
Message-ID: <e5333e89-384f-4488-b758-87646cdeb489@www.fastmail.com> (raw)
In-Reply-To: <f6070a52-7f86-a06b-bc9e-8681970e6a39@fjrhome.net>
On Mon, Jan 6, 2020, at 12:19 AM, Frank D. Engel, Jr. wrote:
>
> I built the file server using a 32-bit 386 kernel but I think 64-bit
> CWFS was used?
64-bit CWFS just means it uses larger addresses for larger disks & files, it's nothing to do with the system architecture. If I remember right, smaller/older CWFS uses 56 bits, but that leaves me wondering why the change was made. (56 bits can address 72e15 bytes.)
prev parent reply other threads:[~2020-01-16 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 13:25 Frank D. Engel, Jr.
2020-01-05 15:56 ` [9fans] " Steven Stallion
2020-01-06 0:19 ` Frank D. Engel, Jr.
2020-01-16 17:00 ` Ethan Gardener [this message]
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=e5333e89-384f-4488-b758-87646cdeb489@www.fastmail.com \
--to=eekee57@fastmail.fm \
--cc=9fans@9fans.net \
/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).