From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Utilite
Date: Fri, 21 Feb 2014 12:16:33 -0800 [thread overview]
Message-ID: <CAJSxfmL5whUJU=zDJAdSkiOst+mPJuA=6KN4r=z9wND7rZqMjQ@mail.gmail.com> (raw)
In-Reply-To: <CAOr72miix+wtieTiOX0OdH0Ty-1nC-9gEDu4o81Ws59qSR6QBA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 347 bytes --]
it looks like it's a new CompuLab product based on their TrimSlice; so the
teg2 port should work.
On Fri, Feb 21, 2014 at 9:49 AM, Jeremy Jackins <jeremyjackins@gmail.com>wrote:
> I'm thinking of purchasing one of these:
> http://utilite-computer.com/web/home
> Just curious, has anyone tried to make one of them work on Plan 9?
>
[-- Attachment #2: Type: text/html, Size: 757 bytes --]
next prev parent reply other threads:[~2014-02-21 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 17:49 Jeremy Jackins
2014-02-21 20:16 ` Skip Tavakkolian [this message]
2014-02-21 22:04 ` Shane Morris
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='CAJSxfmL5whUJU=zDJAdSkiOst+mPJuA=6KN4r=z9wND7rZqMjQ@mail.gmail.com' \
--to=skip.tavakkolian@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).