From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fs config problem status update (still unsolved)
Date: Thu, 28 Feb 2002 16:09:07 -0500 [thread overview]
Message-ID: <6f1e535b5006a4d39a822acbd26f140e@plan9.bell-labs.com> (raw)
> Is the ide-patched fs kernel 'compatible' with the plan9pc one?
> Or do the on-disk structures differ (w.r.t. 'using 16K blocks')
it's just a compile-time constant; you can recompile, right?
next reply other threads:[~2002-02-28 21:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 21:09 Russ Cox [this message]
2002-02-28 21:17 ` Axel Belinfante
-- strict thread matches above, loose matches on Subject: below --
2002-03-01 13:16 Fco.J.Ballesteros
2002-03-01 8:09 Fco.J.Ballesteros
2002-03-01 10:35 ` Axel Belinfante
2002-02-28 21:19 forsyth
2002-02-28 21:59 ` Axel Belinfante
2002-02-22 12:37 [9fans] fs config problem: accidental config deletion? forsyth
2002-02-22 12:55 ` Axel Belinfante
2002-02-22 18:39 ` [9fans] fs config problem status update (still unsolved) Axel Belinfante
2002-02-28 21:06 ` Axel Belinfante
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=6f1e535b5006a4d39a822acbd26f140e@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).