From: Carlo Wood <carlo@alinoe.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Grozdan Nikolov <microchip@chello.be>, linux-kernel@vger.kernel.org
Subject: Re: How innovative is Linux?
Date: Sun, 24 Jun 2007 00:02:22 +0200 [thread overview]
Message-ID: <20070623220222.GB13907@alinoe.com> (raw)
In-Reply-To: <20070623164608.05dc5c30@the-village.bc.nu>
On Sat, Jun 23, 2007 at 04:46:08PM +0100, Alan Cox wrote:
> Now if you want really innovative OS work go look in the lab or at
> projects most people have never heard of and don't run.
Hey, I heard of one. I got a few friends that are sitting
in an IRC channel and have been working on a complete new
OS from scratch for like 10 years now (kernel, filesystem,
graphics drivers, libraries - everything). I consider them
to be totally nuts of course. When I ask them why are you
still doing this? Can't you use linux? Then the answer is
that there are still companies interested in operating
systems like that, precisely because they are not well-
known. It would be pretty hard to exploit vulnerabilities
in such a system (or that is their explanation anyway).
--
Carlo Wood <carlo@alinoe.com>
next prev parent reply other threads:[~2007-06-23 22:02 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 12:17 How innovative is Linux? Grozdan Nikolov
2007-06-23 14:43 ` Alan Cox
2007-06-23 15:22 ` Grozdan Nikolov
2007-06-23 15:46 ` Alan Cox
2007-06-23 16:12 ` Torsten Duwe
2007-06-23 16:19 ` Grozdan Nikolov
2007-06-23 16:42 ` Torsten Duwe
2007-06-23 16:54 ` Matthew Jacob
2007-06-23 17:30 ` jimmy bahuleyan
2007-06-23 17:49 ` Diego Calleja
2007-06-23 19:23 ` Alan Cox
2007-06-23 21:02 ` Al Viro
2007-06-23 22:13 ` Alan Cox
2007-06-23 18:12 ` Jan Engelhardt
2007-06-23 19:44 ` Alan Cox
2007-06-23 17:38 ` Benny Amorsen
2007-06-23 19:18 ` Jeffrey V. Merkey
2007-06-23 18:36 ` Grozdan Nikolov
2007-06-24 4:31 ` Rik van Riel
2007-06-23 22:02 ` Carlo Wood [this message]
2007-06-23 22:16 ` David Kane
[not found] ` <345c044f0706231513u46d870es6539bdf5797b305b@mail.gmail.com>
2007-06-23 22:27 ` Alan Cox
2007-06-25 9:39 ` Hiro Yoshioka
2007-06-25 22:57 ` Adrian Bunk
2007-06-24 21:36 ` Nikita Danilov
2007-06-23 18:02 ` Satyam Sharma
2007-06-23 18:17 ` Grozdan Nikolov
2007-06-23 17:53 ` Bernd Petrovitsch
2007-06-23 18:15 ` Grozdan Nikolov
2007-06-23 18:54 ` jimmy bahuleyan
2007-06-23 19:06 ` Grozdan Nikolov
2007-06-23 23:15 ` Jesper Juhl
2007-06-25 15:12 ` Lennart Sorensen
2007-06-25 15:15 ` Jan Engelhardt
2007-06-25 16:37 ` Randy Dunlap
2007-06-25 16:42 ` Jan Engelhardt
2007-06-25 17:51 ` jimmy bahuleyan
2007-06-26 12:26 ` Helge Hafting
-- strict thread matches above, loose matches on Subject: below --
2007-06-23 17:43 Al Boldi
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=20070623220222.GB13907@alinoe.com \
--to=carlo@alinoe.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=microchip@chello.be \
/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