From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] /dev/draw and c, rc, ruby, python, go
Date: Mon, 11 Apr 2011 21:41:04 -0700 [thread overview]
Message-ID: <BANLkTim=9wjqYAyKFquYY2vfaL9mu2jYuw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTim76gxJX=ttb6AydKYgzox-OYcU_A@mail.gmail.com>
Even on Plan 9 proper (that is, bare hardware?
how about virtualized on qemu or VMWare, etc.)?
ak
On Sun, Apr 10, 2011 at 1:49 PM, ron minnich <rminnich@gmail.com> wrote:
> Hi, it's me, the repeating person (I almost said "broken record" but
> I'm not sure how many people know what that means any more :-)
>
> Suggest you run your command with ratrace
>
> ratrace - whatevercommandyouarerunning
>
> It can be very revealing.
>
> ron
>
>
next prev parent reply other threads:[~2011-04-12 4:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 17:53 Sergey Kish
2011-04-10 20:49 ` ron minnich
2011-04-12 4:41 ` Akshat Kumar [this message]
2011-04-13 22:16 ` erik quanstrom
2011-04-11 0:49 ` Anthony Martin
2011-04-11 1:09 ` Anthony Martin
2011-04-11 15:17 ` Sergey Kish
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='BANLkTim=9wjqYAyKFquYY2vfaL9mu2jYuw@mail.gmail.com' \
--to=akumar@mail.nanosouffle.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).