From: Paul Lalonde <paul.a.lalonde@gmail.com>
To: lucio@proxima.alt.za,
Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Trap in 5c compiling rc?
Date: Wed, 8 Dec 2010 04:18:25 -0800 [thread overview]
Message-ID: <AANLkTinaSnM0PpT+Cb0wUGVhkYyhqJDCO0OwqY960Tu-@mail.gmail.com> (raw)
In-Reply-To: <20101208061317.GB1904@fangle.proxima.alt.za>
[-- Attachment #1: Type: text/plain, Size: 1513 bytes --]
My application is home-control; I have an off-grid cabin that wants to run a
3G usb stick and a low-power cpu server to manage automation - pre-heating,
hot water, etc. This lets me geek a little at the same time.
Paul
On Tue, Dec 7, 2010 at 10:13 PM, Lucio De Re <lucio@proxima.alt.za> wrote:
> On Tue, Dec 07, 2010 at 09:25:37PM -0800, ron minnich wrote:
> >
> > I've gotten part of the way there. I set up a 9fat on the first
> > partition and I can boot the kernel from u-boot with the 9fat. But I'm
> > not quite done the rest.
> >
> The plug really needs fully hands-off booting and this does not seem to
> be the direction you're heading. I suppose my approach where the file
> server is on the network isn't great either, although it may be suitable
> for an auth server.
>
> What are the various eventual uses for a plug running P9? I can think of
>
> Stealth CPU server/AUTH server
> ARM development system (where's Go?)
>
> Can't think of anything else, but I'm not great on the imagination thing.
>
> I'm particularly fragmented now, but soon I'll want to focus on only a few
> projects, so I'm offering to help any sort of concrete goals. I have only
> an oldish plug, probably a year old now, but it's dedicated to Plan 9.
>
> Mind you, so is the YeeLoong and that doesn't seem to be going anywhere.
>
> ++L
>
>
--
I'm migrating my email. plalonde@telus.net will soon be disconnected.
Please use paul.a.lalonde@gmail.com from now on.
[-- Attachment #2: Type: text/html, Size: 2109 bytes --]
next prev parent reply other threads:[~2010-12-08 12:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 2:12 Paul Lalonde
2010-12-05 8:33 ` Bruce Ellis
2010-12-05 9:41 ` Charles Forsyth
2010-12-05 9:49 ` Charles Forsyth
2010-12-05 11:38 ` Bruce Ellis
2010-12-05 13:24 ` erik quanstrom
2010-12-05 16:16 ` Paul Lalonde
2010-12-05 16:42 ` Paul Lalonde
2010-12-05 18:02 ` Charles Forsyth
2010-12-05 18:15 ` ron minnich
2010-12-05 18:28 ` ron minnich
2010-12-07 1:08 ` Paul Lalonde
2010-12-07 1:14 ` ron minnich
2010-12-07 1:54 ` erik quanstrom
2010-12-07 3:51 ` ron minnich
2010-12-07 5:57 ` Paul Lalonde
2010-12-07 6:42 ` Lucio De Re
2010-12-07 13:34 ` erik quanstrom
2010-12-07 13:37 ` erik quanstrom
2010-12-07 15:32 ` Paul Lalonde
2010-12-07 16:26 ` ron minnich
2010-12-07 16:39 ` ron minnich
2010-12-08 4:26 ` Paul Lalonde
2010-12-08 0:33 ` Lucio De Re
2010-12-08 4:34 ` Paul Lalonde
2010-12-08 0:38 ` Lucio De Re
2010-12-08 5:25 ` ron minnich
2010-12-08 6:13 ` Lucio De Re
2010-12-08 6:21 ` ron minnich
2010-12-08 12:18 ` Paul Lalonde [this message]
2010-12-08 13:06 ` erik quanstrom
2010-12-08 19:26 ` Paul Lalonde
2010-12-05 17:08 ` erik quanstrom
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=AANLkTinaSnM0PpT+Cb0wUGVhkYyhqJDCO0OwqY960Tu-@mail.gmail.com \
--to=paul.a.lalonde@gmail.com \
--cc=9fans@9fans.net \
--cc=lucio@proxima.alt.za \
/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).