From: "Tiit Lankots" <t.lankots@aprote.ee>
To: "Matthias Teege" <mteege@gmail.com>,
"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] install new 9load
Date: Sat, 30 Oct 2004 12:05:58 +0300 [thread overview]
Message-ID: <opsgod780e3anw4g@tiitl.aprote.com> (raw)
In-Reply-To: <88a47756041030020149ad479e@mail.gmail.com>
> chmod gives me "can't wstat /n/9fat/9load: permission denied"
> Matthias
dossrv(4)
Your 9load is messed up. prep(8)
prev parent reply other threads:[~2004-10-30 9:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 17:28 Matthias Teege
2004-10-26 18:01 ` Alberto Cortes
2004-10-26 18:09 ` Alberto Cortes
2004-10-26 19:13 ` boyd, rounin
2004-10-26 21:50 ` Russ Cox
2004-10-28 2:10 ` Rajendran A
2004-10-28 3:04 ` andrey mirtchovski
2004-10-28 3:30 ` Vester Thacker
2004-10-28 16:31 ` Rajendran A
2004-10-28 16:40 ` Steve Simon
[not found] ` <86209de9e9812a23c76766c108e29bfc@quintile.net>
2004-10-28 18:30 ` Rajendran A
2004-10-30 9:01 ` Matthias Teege
2004-10-30 9:05 ` Tiit Lankots [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=opsgod780e3anw4g@tiitl.aprote.com \
--to=t.lankots@aprote.ee \
--cc=9fans@cse.psu.edu \
--cc=mteege@gmail.com \
/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).