From: andrey mirtchovski <mirtchovski@gmail.com>
To: fernanbolando@mailc.net,
Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9port openbsd 4.4
Date: Sun, 25 Jan 2009 19:42:41 -0700 [thread overview]
Message-ID: <14ec7b180901251842sdc9e102qa9d4653b4acd6d29@mail.gmail.com> (raw)
In-Reply-To: <1d5d51400901251734o5e7e74a9v13d30e65e5fd27f9@mail.gmail.com>
> rio seems to work fine, but I have been getting a few 9serve.core dumps.
that makes sense: p9p's rio (used to be 9wm) is written with X-windows
in mind. it's not a Plan 9 app.
next prev parent reply other threads:[~2009-01-26 2:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 1:34 Fernan Bolando
2009-01-26 1:41 ` Iruata Souza
2009-01-26 2:36 ` Fernan Bolando
2009-01-26 2:42 ` andrey mirtchovski [this message]
2009-01-26 5:13 ` sqweek
2009-01-26 16:04 ` Russ Cox
2009-01-26 18:01 ` Anthony Sorace
2009-01-29 14:43 ` Mechiel Lukkien
2009-01-26 18:28 ` Iruata Souza
2009-01-26 21:13 ` Fernan Bolando
2009-01-29 14:31 ` Fernan Bolando
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=14ec7b180901251842sdc9e102qa9d4653b4acd6d29@mail.gmail.com \
--to=mirtchovski@gmail.com \
--cc=9fans@9fans.net \
--cc=fernanbolando@mailc.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).