From: Chris Simmonds <chris.simmonds@2net.co.uk>
To: linux-embedded <linux-embedded@vger.kernel.org>
Subject: History of embedded Linux
Date: Mon, 23 Jul 2012 16:00:05 +0100 [thread overview]
Message-ID: <500D66F5.5030906@2net.co.uk> (raw)
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
next reply other threads:[~2012-07-23 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 15:00 Chris Simmonds [this message]
2012-09-04 17:28 ` History of embedded Linux Jeff Osier-Mixon
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=500D66F5.5030906@2net.co.uk \
--to=chris.simmonds@2net.co.uk \
--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).