From: forsyth@vitanuova.com forsyth@vitanuova.com
Subject: [9fans] My view of Plan 9 and it's future
Date: Mon, 22 May 2000 13:24:10 +0100 [thread overview]
Message-ID: <20000522122410.mi56RwJzvaAn3ezMPvSKypYoCgeTCnBhHOT6PrZmZc0@z> (raw)
>>with the current (hide at the end of the disk) system that has worked fine.
i'm a bit surprised, because i was fairly sure that kfs stored its metadeta
in machine-dependent form, which ought to confound attempts to read
little-endian pc structures on a big-endian sparc.
next reply other threads:[~2000-05-22 12:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-22 12:24 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-06 10:21 Christopher
2000-05-22 12:24 Bengt
2000-05-22 11:51 Bengt
2000-05-22 10:07 Will
2000-05-22 8:31 Bengt
2000-05-19 16:45 Tom
2000-05-19 16:19 Will
2000-05-19 16:06 Tom
2000-05-19 8:43 Bengt
2000-05-19 8:29 Christopher
2000-05-18 16:23 Douglas
2000-05-18 7:01 Richard
2000-05-17 12:40 Will
2000-05-17 11:56 Bill
2000-05-17 8:41 Douglas
2000-05-15 17:15 Tom
2000-05-15 16:47 Tom
2000-05-14 6:06 Jim
2000-05-14 3:57 /usr/rsc/lib/from.eecs
2000-05-14 0:58 Jim
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=20000522122410.mi56RwJzvaAn3ezMPvSKypYoCgeTCnBhHOT6PrZmZc0@z \
--to=forsyth@vitanuova.com \
/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).