From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] cwfs64x+cryptsetup+mirror?
Date: Thu, 23 May 2013 15:25:36 +0100 [thread overview]
Message-ID: <9c26557c61a232e1fd3c1e7be8f15bb2@quintile.net> (raw)
In-Reply-To: <519e3095.AuaCJMQfupu4St6h%trebol55555@aol.com>
> Also, weeks ago I send a mail to contrib@plan9.bell-labs.com without response.
> I would like to share some ape ports and dictionaries for dict.
I don't believe that address is used much any more.
the usual technique is to email geoff at plan9..bell-labs.com
and ask for a contrib directory and an account.
Once you have this you can either put .tgz files on sources by hand:
9fs sources
cp package.tgz /n/sources/contrib/$user/
or even use the contrib package managment system built by fgb.
This can be bootstraped using:
9fs sources
/n/sources/contrib/fgb/root/rc/bin/contrib/install fgb/contrib
then look at the manual for contrib(1) for more info.
-Steve
next prev parent reply other threads:[~2013-05-23 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 15:07 trebol
2013-05-23 14:11 ` erik quanstrom
2013-05-23 14:25 ` Steve Simon [this message]
2013-05-25 13:06 trebol
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=9c26557c61a232e1fd3c1e7be8f15bb2@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
/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).