9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil speed
Date: Thu, 27 Jan 2005 20:08:32 -0800	[thread overview]
Message-ID: <dbcbb771ed2fdb08094bf99e22ad7da2@collyer.net> (raw)
In-Reply-To: <568ba9e3d5e7d0a4f1031424662d5f89@granite.cias.osakafu-u.ac.jp>

It is possible to generate file server kernels exactly compatible with
existing ken fs on-disk file systems, but you get none of the benefits
of the new file server if you do that.  It does however let you build
old and new file server kernels from the same sources.

If you want to get the benefits of the new file server (64-bit file
sizes, offsets and block numbers; smarter IDE code ported from the cpu
kernel; larger file name components; indirect blocks beyond
double-indirect; etc.), you have to build a new file server kernel
that will not be compatible on disk with existing file systems (it
will however speak 9p2000 compatibly, though not 9p1, because 9p1
depends crucially on NAMELEN being 28; 9p1 is disabled in the new file
server kernels, but it turns out that nothing needs 9p1 any more [old
drawterm uses it, but it never connects to file servers directly]).

I decided that I could live without the history on my old file server,
so just copied its main file system to a new file server.  It's nice
to not need lnfs any more.


  reply	other threads:[~2005-01-28  4:08 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-26  2:00 [9fans] browse /sys/src YAMANASHI Takeshi
2005-01-26  2:27 ` Kenji Okamoto
2005-01-26  2:31   ` Michael H. Collins
2005-01-26  2:45     ` boyd, rounin
2005-01-26  3:50     ` Russ Cox
2005-01-26  4:28       ` Kenji Okamoto
2005-01-26  4:39         ` Kenji Okamoto
2005-01-26  8:49         ` Skip Tavakkolian
2005-01-26 10:00           ` Matthias Teege
2005-01-26 21:32       ` [9fans] fossil speed rog
2005-01-26 21:36         ` andrey mirtchovski
2005-01-26 22:09           ` Charles Forsyth
2005-01-26 22:18           ` andrey mirtchovski
2005-01-26 22:22           ` andrey mirtchovski
2005-01-26 22:48             ` rog
2005-01-26 22:26           ` rog
2005-01-26 22:13             ` Charles Forsyth
2005-01-26 22:15               ` Charles Forsyth
2005-01-26 22:40             ` andrey mirtchovski
2005-01-27  2:47               ` Russ Cox
2005-01-27 19:20                 ` rog
2005-01-27  7:51             ` Fco. J. Ballesteros
2005-01-27 21:09               ` geoff
2005-01-27 21:23                 ` andrey mirtchovski
2005-01-27 21:35                   ` Russ Cox
2005-01-27 22:28                   ` geoff
2005-01-28  2:11                     ` Kenji Okamoto
2005-01-28  4:08                       ` geoff [this message]
2005-01-28  4:39                         ` Kenji Okamoto
2005-01-28  4:54                           ` geoff
2005-01-27  3:39         ` boyd, rounin
2005-01-26  9:55 ` [9fans] browse /sys/src Fco. J. Ballesteros

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=dbcbb771ed2fdb08094bf99e22ad7da2@collyer.net \
    --to=geoff@collyer.net \
    --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).