From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Fs Kernel
Date: Mon, 6 Jan 2003 17:33:31 +0000 [thread overview]
Message-ID: <4cbcf424f7cb6481ae2243bbb1009092@vitanuova.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 40 bytes --]
see /sys/src/fs/words
for a few hints
[-- Attachment #2: Type: message/rfc822, Size: 1389 bytes --]
From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Fs Kernel
Date: Mon, 6 Jan 2003 17:22:33 0000
Message-ID: <fa0a29ffa78d7a4f560ed841a58a2020@9fs.org>
> which kernel mkfile do I use for the file server?
> thanks
> will551
/sys/src/fs/*/mkfile
next reply other threads:[~2003-01-06 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 17:33 C H Forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-06 17:22 nigel
2002-11-14 16:47 [9fans] how to avoid a memset() optimization presotto
2002-11-19 7:38 ` Roman V. Shaposhnick
2003-01-06 10:18 ` Ralph Corderoy
2003-01-06 15:58 ` [9fans] Fs Kernel Conor Williams
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=4cbcf424f7cb6481ae2243bbb1009092@vitanuova.com \
--to=forsyth@vitanuova.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).