public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Grozdan Nikolov <microchip@chello.be>
To: Torsten Duwe <duwe@lst.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How innovative is Linux?
Date: Sat, 23 Jun 2007 18:19:43 +0200	[thread overview]
Message-ID: <200706231819.43556.microchip@chello.be> (raw)
In-Reply-To: <200706231812.02317.duwe@lst.de>

On Saturday 23 June 2007 18:12, you wrote:
> On Saturday 23 June 2007, Alan Cox wrote:
> > A few innovations that afaik first appeared the Linux kernel
> > - Making multiple hosts appear transparently as one IP address
> > - Futex fast hybrid locking
> > - Single pass checksum fragment and send fragments in reverse order
> > - Reiserfs - very innovative design, but innovation isn't neccessarily
> > success
> > - JFFS/JFFS2 - flash wear levelled file system avoiding all the problem
> > patents
> > - Loadable modules for a non-microkernel
>
> - ALSA framework and drivers
> - Direct Rendering Infrastructure
> - hotplugging
>

hmm, wasn't loadable kernel modules first implemented in SunOS 4.x together 
with the proc system ?

  reply	other threads:[~2007-06-23 16:19 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 [this message]
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
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=200706231819.43556.microchip@chello.be \
    --to=microchip@chello.be \
    --cc=duwe@lst.de \
    --cc=linux-kernel@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