From: "Anand Kumria" <wildfire@progsoc.org>
To: netdev@vger.kernel.org
Subject: Re: OLPC (One Laptop Per Child) Developer's program.
Date: Sun, 4 Jun 2006 13:17:16 +0000 (UTC) [thread overview]
Message-ID: <e5umgs$lfj$1@sea.gmane.org> (raw)
In-Reply-To: 1149335345.5053.177.camel@pmac.infradead.org
On Sat, 03 Jun 2006 12:49:05 +0100, David Woodhouse wrote:
> On Tue, 2006-05-30 at 17:42 -0400, Jim Gettys wrote:
>> As you know, we've said we were going to have a developer's program. You
>> can find more information, including how to apply for boards at:
>>
>> http://wiki.laptop.org/index.php/Developers_Program
>>
>> Note that these are bare PC prototype boards, not packaged machines.
>> Jim Gettys
>
> ObNetdev:
>
> One thing we really need is NAT-PT or an equivalent for allowing access
> to the Legacy Internet from IPv6-only hosts. As soon as I finish playing
> with JFFS2 improvements, I plan to start looking at that.
Wouldn't miredo mostly fit the bill? It won't get through Symmetric NATs
(by design) but those are supposed to be uncommon.
Cheers,
Anand
next prev parent reply other threads:[~2006-06-04 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 21:42 OLPC (One Laptop Per Child) Developer's program Jim Gettys
2006-06-03 11:49 ` David Woodhouse
2006-06-04 13:17 ` Anand Kumria [this message]
2006-06-05 9:07 ` David Woodhouse
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='e5umgs$lfj$1@sea.gmane.org' \
--to=wildfire@progsoc.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.