From: Jeff Osier-Mixon <jefro@jefro.net>
To: chris@2net.co.uk
Cc: linux-embedded <linux-embedded@vger.kernel.org>
Subject: Re: History of embedded Linux
Date: Tue, 4 Sep 2012 10:28:15 -0700 [thread overview]
Message-ID: <CA+YB3rYMyO+qoCX234anCbjucigMEL4zJ_aDDo1Git3J7bpfUQ@mail.gmail.com> (raw)
In-Reply-To: <500D66F5.5030906@2net.co.uk>
Looks like an excellent start. I think it would be good to add
OpenEmbedded and the Yocto Project - I'll try to get some key dates
together.
On Mon, Jul 23, 2012 at 8:00 AM, Chris Simmonds
<chris.simmonds@2net.co.uk> wrote:
> Hi,
>
> This is a little off-topic, but I have a bee in my bonnet about documenting
> where "embedded Linux" came from. As a starting point, I have written up a
> time line of key events, which is here
>
> http://embedded-linux.co.uk/embedded-history
>
> I am aware that there is a lot that I have missed, or misunderstood, so if
> you have a few minutes to spare perhaps you could have a look at it and tell
> me what I have got wrong. I am not sure where I am going with this, but I
> would like to use it as the basis of a longer document/web site/garden shed
> on the topic of the evolution of Linux as an embedded operating system.
>
> Oh, one last thing. If someone has some reasonably reliable figures of the
> numbers of Linux products shipped, that would be nice. Ideally I would like
> a graph that goes from zero in 1995 to NNN million in 2012. I know, its a
> dream, can't be done...
>
> Bye for now,
> Chris Simmonds
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-embedded" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Jeff Osier-Mixon http://jefro.net/blog
Yocto Project Community Manager @Intel http://yoctoproject.org
prev parent reply other threads:[~2012-09-04 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 15:00 History of embedded Linux Chris Simmonds
2012-09-04 17:28 ` Jeff Osier-Mixon [this message]
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=CA+YB3rYMyO+qoCX234anCbjucigMEL4zJ_aDDo1Git3J7bpfUQ@mail.gmail.com \
--to=jefro@jefro.net \
--cc=chris@2net.co.uk \
--cc=linux-embedded@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).