From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] nupas update
Date: Wed, 2 Sep 2009 19:29:57 -0700 [thread overview]
Message-ID: <3e1162e60909021929j79697867j9c4972d9501fe18@mail.gmail.com> (raw)
In-Reply-To: <6aaf2d79af665bf1905db13e44e194e5@quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
On Wed, Sep 2, 2009 at 7:16 PM, erik quanstrom <quanstro@quanstro.net>wrote:
> i've pushed an update of my nupas contrib
> package to sources. imap successful in use
> with apple mail (snow leper, too), iphone,
> outlook, opera, ff, upas/fs.
>
> note on installing:
> as devon pointed out, installation is still a
> big pain.
> 1. move /sys/src/nupas -> onupas
> 2. contrib/install quanstro/nupas
>
> if you want to go cold turkey nupas, then
> a. mv /386/bin/upas /386/bin/oupas
> b. mv /386/bin/nupas /386/bin/upas
> c. (opt) edit top-level mkfile to install in
> /386/bin/nupas.
>
> if you want to hedge your bets
> a. add "usenupas" to your profile
> b. edit cpurc as you see fit to use nupas
> binaries.
>
> cavet: i have not had a chance to retest the
> contrib package.
>
> as always, feedback welcome.
>
So when you say that it works with Snow Leopard too, are you meaning that
this works *on* snow leopard with something like FUSE 9p via plan 9 from
user space?
Just curious.
>
> - erik
>
>
[-- Attachment #2: Type: text/html, Size: 1609 bytes --]
next prev parent reply other threads:[~2009-09-03 2:29 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 2:16 erik quanstrom
2009-09-03 2:29 ` David Leimbach [this message]
2009-09-03 2:37 ` erik quanstrom
2010-05-15 23:17 ` Akshat Kumar
2010-05-15 23:45 ` erik quanstrom
2010-05-16 2:36 ` ron minnich
2010-05-16 4:15 ` erik quanstrom
2010-05-16 4:28 ` Akshat Kumar
2010-05-16 4:35 ` ron minnich
2010-05-16 4:39 ` erik quanstrom
2010-05-16 4:51 ` ron minnich
2010-05-16 4:57 ` Akshat Kumar
2010-05-16 5:44 ` ron minnich
2010-05-16 13:42 ` EBo
2010-05-16 14:03 ` erik quanstrom
2010-05-16 14:51 ` Ethan Grammatikidis
2010-05-16 15:37 ` EBo
2010-05-16 15:53 ` Ethan Grammatikidis
2010-05-16 16:02 ` ron minnich
2010-05-16 17:10 ` Ethan Grammatikidis
2010-05-16 17:19 ` EBo
2010-05-16 15:21 ` EBo
2010-05-16 15:42 ` Ethan Grammatikidis
2010-05-16 17:34 ` EBo
2010-05-16 17:47 ` hiro
2010-05-16 18:58 ` Corey
2010-05-16 19:29 ` EBo
2010-05-18 21:35 ` Georg Lehner
2010-05-18 22:07 ` ron minnich
2010-05-16 15:46 ` Jorden M
2010-05-16 15:59 ` Ethan Grammatikidis
2010-05-16 15:42 ` Jorden M
2010-05-16 18:24 ` erik quanstrom
2010-05-16 18:49 ` EBo
2010-05-16 20:44 ` erik quanstrom
2010-05-16 21:44 ` EBo
2010-05-17 1:17 ` erik quanstrom
2010-05-17 1:52 ` EBo
2010-05-17 1:58 ` erik quanstrom
2010-05-17 1:35 ` Akshat Kumar
2010-05-17 4:09 ` ron minnich
2010-05-17 4:19 ` erik quanstrom
2010-05-17 4:56 ` ron minnich
2010-05-18 23:50 ` Federico G. Benavento
2010-05-18 23:59 ` ron minnich
2010-05-19 0:40 ` Jorden M
2010-05-19 1:40 ` Robert Ransom
-- strict thread matches above, loose matches on Subject: below --
2009-08-06 15:23 erik quanstrom
2008-10-23 0:08 erik quanstrom
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=3e1162e60909021929j79697867j9c4972d9501fe18@mail.gmail.com \
--to=leimy2k@gmail.com \
--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).