9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bruce Ellis <bruce.ellis@gmail.com>
To: Russ Cox <russcox@gmail.com>,
	Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: plan9port: recent changes
Date: Tue, 15 Feb 2005 07:31:04 +1100	[thread overview]
Message-ID: <775b8d1905021412313a0ec28d@mail.gmail.com> (raw)
In-Reply-To: <ee9e417a05021411094981aba7@mail.gmail.com>

i don't like autoindent ... it always seems to do what i don't
want it to do, the tab key is big, and i don't write deeply
nested code.  but if you do - fine ... make it an option (i hate
thousands of options too).

good to see a prolifertion of factota - the ozinferno one is even
simpler than the original, but loads modules on demand to do
the good stuff.

brucee

On Mon, 14 Feb 2005 14:09:34 -0500, Russ Cox <russcox@gmail.com> wrote:
> A few people have reported that running acme and exiting
> leaves behind a 9pserve process with the effect that you can't
> run acme a second time.  I believe I just checked in a fix to this bug,
> which I introduced trying to work around the pthread nonsense
> we were discussing last week.  After updating from CVS, you'll
> have to rebuild libthread and then 9pserve (or just use
> cd $PLAN9; ./INSTALL -- it's still much faster than compiling the
> Linux kernel).
>
> It's worth noting for everyone that you can't run two acmes in
> the same "name space" since they'll both want to post as the Unix
> socket `namespace`/acme.  If you want to start a new "name space"
> you can set $NAMESPACE manually, as in
>
>    mkdir /tmp/ns; NAMESPACE=/tmp/ns; export NAMESPACE
>
> and then you'll have a separate acme that is isolated from the
> first (and from the plumber that the first acme is using).
>
> Intro(4) has details.
>
> Setting $NAMESPACE also lets you run file servers before you
> start X and share them with your X session.  For example, in my
> .profile I have the following:
>
> # Logging in on tty1 sets up factotum and then runs X automatically
> if [ "`/bin/ls -l /proc/self/fd/0 2>/dev/null | awk '{print $NF}'`" =
> '/dev/tty1' ]
> then
>        NAMESPACE=/tmp/ns.`hostname`
>        export NAMESPACE
>        rm -rf $NAMESPACE; mkdir $NAMESPACE
>        9 factotum
>        eval `9 ssh-agent -e`
>        startx
> fi
>
> I have to start factotum and ssh-agent before X because I run
> stats to remote machines (via ssh) in my .xinitrc, and so that
> the $SSH_AUTH_SOCK variable is set in all my X windows.
>
> Russ
>


  reply	other threads:[~2005-02-14 20:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-14  0:41 [9fans] " Russ Cox
2005-02-14 19:09 ` [9fans] " Russ Cox
2005-02-14 20:31   ` Bruce Ellis [this message]
2005-02-14 20:49     ` Russ Cox
2005-02-14 21:03       ` Skip Tavakkolian
2005-02-15  3:28         ` Andrew Simmons
2005-02-15  3:39           ` Russ Cox
2005-02-15  7:20       ` Tiit Lankots
2005-02-15  9:51       ` David Tolpin

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=775b8d1905021412313a0ec28d@mail.gmail.com \
    --to=bruce.ellis@gmail.com \
    --cc=9fans@cse.psu.edu \
    --cc=russcox@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).