From: "Chris Silva" <clowes@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Ken fs updated
Date: Sat, 18 Feb 2006 01:06:34 -0600 [thread overview]
Message-ID: <97154bb00602172306le1c6e19rc30ec516c2332890@mail.gmail.com> (raw)
In-Reply-To: <dc19c86465061f28dfaa377a7189f5bd@collyer.net>
Is there a install .iso? (last time I installed it was changed to fossil only)
On 2/18/06, geoff@collyer.net <geoff@collyer.net> wrote:
> As you've probably noticed if you've pulled today, the file server
> kernel, manual pages and paper have been updated to match my 64-bit
> file server kernel. I've removed /n/sources/contrib/geoff/fs64.tgz.
> /sys/src/fs/doc has some examples, advice and a list of changes.
>
> The emelie kernel is now called 9emeliefs. Examining port/portdat.h,
> you'll see that defining OLD will compile a 32-bit kernel compatible
> on disk with existing file systems. There's a little more noise at
> boot time (but the file server has always been chatty), including an
> announcement of the largest file size.
>
> Diffs against the previous kernel are voluminous, but mostly due to
> two things: type parameterisation and goto elimination.
>
> I'm running the 64-bit kernel and ran the 32-bit kernel from this tree
> during development. 9netics has one each (a 32-bit and a 64-bit
> kernel) and Kenji Okamoto is running the 64-bit kernel with filename
> components cranked up to 256 bytes maximum.
>
next prev parent reply other threads:[~2006-02-18 7:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-18 6:01 geoff
2006-02-18 7:06 ` Chris Silva [this message]
2006-02-18 7:18 ` geoff
2006-02-18 9:34 ` Russ Cox
2006-02-18 14:36 ` Brantley Coile
2006-02-18 15:37 ` Bruce Ellis
2006-02-18 10:39 ` Russ Cox
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=97154bb00602172306le1c6e19rc30ec516c2332890@mail.gmail.com \
--to=clowes@gmail.com \
--cc=9fans@cse.psu.edu \
/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).