From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] IDE FS failure
Date: Fri, 27 Sep 2002 16:17:07 +0200 [thread overview]
Message-ID: <200209271417.g8REH7r03233@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Fri, 27 Sep 2002 09:50:30 -0400." <299bf2fc58b57db82f3e4a16f9c59ffb@plan9.bell-labs.com>
> I think the allow command is documented somewhere, but
> I can't find it.
Also there is a patch to add ``allow'' to the list of fs commands,
so you don't have to reboot, to ``allow''.
I think it is part of the idefs patches/source at nemo's site.
Axel.
next prev parent reply other threads:[~2002-09-27 14:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-27 13:50 Russ Cox
2002-09-27 14:09 ` Lucio De Re
2002-09-27 14:17 ` Axel Belinfante [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-30 9:48 Fco.J.Ballesteros
2002-09-30 10:21 ` Lucio De Re
2002-09-27 14:18 Russ Cox
2002-09-25 22:40 Geoff Collyer
2002-09-27 12:32 ` Lucio De Re
2002-09-25 13:15 David Swasey
2002-09-25 13:36 ` Lucio De Re
2002-09-24 23:54 Geoff Collyer
2002-09-25 4:18 ` Lucio De Re
2002-09-24 10:54 Lucio De Re
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=200209271417.g8REH7r03233@zamenhof.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--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).