From: crossd@gmail.com (Dan Cross)
Subject: [TUHS] Gnu/Stallman (was Bugs in V6 'dcheck')
Date: Mon, 2 Jun 2014 15:54:28 -0400 [thread overview]
Message-ID: <CAEoi9W7h+nGB3c917J01=wLPQe=vpRbwG0sj8KPH2cGpxURkSQ@mail.gmail.com> (raw)
In-Reply-To: <20140602193055.GC18282@mercury.ccil.org>
On Mon, Jun 2, 2014 at 3:30 PM, John Cowan <cowan at mercury.ccil.org> wrote:
> Dan Cross scripsit:
>
> > But nostalgia aside, something I find interesting (and frankly a bit
> > distressing) is what seems to me to simply be an acceptance that it's all
> > going to end with Linux. That is to say, no one ever seems to talk about
> > what will come *after* Linux. Will Linus's kernel truly be the last
> kernel
> > anyone works on seriously? Somehow I very much doubt that. And yet, you
> > don't see a lot of talk about evolutionary paths beyond Linux; it's a
> sort
> > of tunnel vision.
>
> This is like asking when there will be a new scientific discovery in some
> field.
Forgive me, but I think that's a bit of an odd analogy (or perhaps an
indication that I did not adequately explain what I meant). However, let
me run with it for a moment and rephrase my statement: there can only be a
discovery if one decides it's worth doing the sort of investigation that
would lead to a new discovery, and I wonder whether "we" still have that
kind of curiosity or drive. Or has Linux become so entrenched that no one
can imagine bothering anymore?
There will be a new kernel when someone decides, as Linus did, to
> write a new kernel. If it catches on, it may supplement or replace Linux.
To whit: it appears that "we" (for some large value of "we") have
collectively decided that it's not worth looking for a replacement for
Linux. If nothing else, I find that interesting.
- Dan C.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20140602/29ccb321/attachment.html>
next prev parent reply other threads:[~2014-06-02 19:54 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 2:09 Doug McIlroy
2014-06-02 2:24 ` John Cowan
2014-06-02 2:59 ` Warner Losh
2014-06-02 3:17 ` Greg 'groggy' Lehey
2014-06-02 3:37 ` John Cowan
2014-06-02 4:08 ` scj
2014-06-02 5:03 ` Greg 'groggy' Lehey
2014-06-02 12:31 ` Ronald Natalie
2014-06-02 4:04 ` Nick Downing
2014-06-02 4:43 ` John Cowan
2014-06-02 6:23 ` arnold
2014-06-02 17:35 ` John Cowan
2014-06-02 18:44 ` Warner Losh
2014-06-02 18:52 ` John Cowan
2014-06-02 3:18 ` John Cowan
2014-06-02 6:08 ` Steve Nickolas
2014-06-02 12:04 ` Clem Cole
2014-06-02 12:27 ` Ronald Natalie
2014-06-02 13:28 ` Clem Cole
2014-06-02 14:11 ` Tim Bradshaw
2014-06-02 14:25 ` Clem Cole
2014-06-02 14:41 ` John Cowan
2014-06-02 14:50 ` Armando Stettner
2014-06-02 18:27 ` Brantley Coile
2014-06-02 18:52 ` Dan Cross
2014-06-02 19:10 ` arnold
2014-06-03 1:45 ` Brantley Coile
2014-06-02 19:30 ` John Cowan
2014-06-02 19:54 ` Dan Cross [this message]
2014-06-02 23:37 ` John Cowan
2014-06-03 1:24 ` Dan Cross
2014-06-03 2:16 ` John Cowan
2014-06-03 2:18 ` Dan Cross
2014-06-02 19:47 ` Chris Nehren
2014-06-02 20:23 ` Dan Cross
2014-06-03 18:48 ` [TUHS] Evolutionary Paths (was Gnu/Stallman (was Bugs in V6 'dcheck')) scj
2014-06-04 1:10 ` Larry McVoy
2014-06-04 3:42 ` Greg Chesson
2014-06-05 0:43 ` Larry McVoy
2014-06-02 21:08 ` [TUHS] Gnu/Stallman (was Bugs in V6 'dcheck') Charlie Kester
2014-06-03 0:37 ` Tim Newsham
2014-06-02 20:06 ` Jacob Goense
2014-06-02 14:26 ` arnold
2014-06-02 14:30 ` John Cowan
2014-06-02 14:24 ` John Cowan
2014-06-02 14:29 ` Ronald Natalie
2014-06-02 14:37 ` Clem Cole
2014-06-05 7:31 ` Arno Griffioen
2014-06-05 8:24 ` emu
2014-06-05 9:17 ` Wesley Parish
2014-06-05 11:26 ` Brantley Coile
2014-06-05 13:34 ` Jesus Cea
2014-06-11 12:10 ` Michael Parson
2014-06-12 1:20 ` Wesley Parish
2014-06-05 15:07 ` Clem Cole
2014-06-05 18:26 ` Ronald Natalie
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='CAEoi9W7h+nGB3c917J01=wLPQe=vpRbwG0sj8KPH2cGpxURkSQ@mail.gmail.com' \
--to=crossd@gmail.com \
/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 NNTP newsgroup(s).