9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Bence Fábián" <begnoc@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Can't start multiple copies of acme
Date: Sun, 15 Dec 2013 17:33:07 +0100	[thread overview]
Message-ID: <CAOCRf5X5LGD1ithoe_gT2eEqDmC5vORe9YGHoUqnbT8uO3_TuQ@mail.gmail.com> (raw)
In-Reply-To: <e5bd44a79dcfe0cf23324042620efad6@mikro>

[-- Attachment #1: Type: text/plain, Size: 702 bytes --]

I don't say it is very common, but I do run multiple acmes under
Plan 9 sometimes. With vastly different name spaces.


2013/12/15 erik quanstrom <quanstro@quanstro.net>

> On Sun Dec 15 10:23:13 EST 2013, blake@mcbride.name wrote:
>
> > I checked.  The following shell script does the trick:
> >
> >
> > #
> > mkdir /tmp/acme-$$
> > NAMESPACE=/tmp/acme-$$ acme "$@"
>
> this is swimming up stream.  acme's model is to run 1 copy of acme,
> and edit all files in it.  many things, such as plumbing, will work
> better with 1 copy of acme.
>
> by the way, this limitation is p9p specific.  but still it's no
> fun to have the same file get plumbed to every acme.
>
> - erik
>
>

[-- Attachment #2: Type: text/html, Size: 1205 bytes --]

  reply	other threads:[~2013-12-15 16:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-13 17:18 Blake McBride
2013-12-13 17:31 ` User &
2013-12-15 15:22   ` Blake McBride
2013-12-15 16:00     ` erik quanstrom
2013-12-15 16:33       ` Bence Fábián [this message]
2013-12-15 16:36       ` Blake McBride
2013-12-15 16:44         ` Bence Fábián
2013-12-15 17:13           ` Blake McBride
2013-12-13 17:37 ` Bence Fábián
2013-12-13 17:57   ` Aram Hăvărneanu
2013-12-16 10:15 ` dexen deVries
2013-12-14 14:54 Uvelichitel

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=CAOCRf5X5LGD1ithoe_gT2eEqDmC5vORe9YGHoUqnbT8uO3_TuQ@mail.gmail.com \
    --to=begnoc@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).