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] Bad Karma with old kit
Date: Sun,  5 Jun 2005 14:49:35 -0700	[thread overview]
Message-ID: <72a27d6c7aba3d47f462a0a6477e9e2f@collyer.net> (raw)
In-Reply-To: <9fad8e46180480a87bb08e10ebd3adcc@proxima.alt.za>

Usually if the block size is wrong, the magic number for the
configuration block is also wrong (since the configuration block is
then looked for at the wrong offset), which should cause a panic or
other drastic failure.

dat.h looks pretty much the same in the 64-bit fs.  The block size is
a truly fundamental constant of the file server implementation;
changing it currently requires recompilation because the block size,
and constants derived from it, are used in array declarations and the
like.  There are ways that one could work around it, with some
contortions in the code.  kfs does, after all, but kfs had to (or at
least did) change the on-disk representation to make this feasible.



      reply	other threads:[~2005-06-05 21:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-04 13:18 lucio
2005-06-04 22:26 ` geoff
2005-06-05 11:18   ` lucio
2005-06-05 21:49     ` geoff [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=72a27d6c7aba3d47f462a0a6477e9e2f@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).