public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] systemd and kernel developers cooperating to turn it into a global cgroup manager?
Date: Sun, 20 Oct 2013 10:42:32 -0400	[thread overview]
Message-ID: <5263EBD8.2010400@libertytrek.org> (raw)
In-Reply-To: <5263B5F3.9020604@sporkbox.us>

On 2013-10-20 6:52 AM, Daniel Campbell <lists@sporkbox.us> wrote:
> So they spend a lot of money hiring developers. The more important
> question is what is their agenda? What do they tell those developers to
> *make*? You don't hire people without a business plan in mind.

Well, once I understood their (Redhat's) motivation, which was/is 
enterprise/cloud/vm oriented (which is why they were so concerned about 
parallelism for startup, etc) - I dropped the conspiracy theory aspect 
of it all... it actually does make sense in that context.

And as long as Linus is at the helm of kernel development, I'm not too 
worried about the systemd guys doing too much damage there - I just 
can't see him letting it happen.

If I were the type to worry just for the sake of worrying, I'd be 
wondering what may happen down the road, if Linus were to suddenly lose 
interest in kernel development (for whatever reason) and walk away from 
it - who/what would take over the reins? But that would be pointless...


  parent reply	other threads:[~2013-10-20 14:43 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18  4:27 [gentoo-user] systemd and kernel developers cooperating to turn it into a global cgroup manager? Mark David Dumlao
2013-10-19 15:02 ` Daniel Campbell
2013-10-19 23:35   ` Volker Armin Hemmann
2013-10-20  6:34     ` Daniel Campbell
2013-10-20  7:37       ` Samuli Suominen
2013-10-20  9:24         ` Daniel Campbell
2013-10-20  9:55           ` Samuli Suominen
2013-10-20 10:47             ` Daniel Campbell
2013-10-20 13:02               ` Samuli Suominen
2013-10-20 14:01                 ` Tanstaafl
2013-10-20 14:03                   ` Samuli Suominen
2013-10-21  2:34                     ` Walter Dnes
2013-10-21  5:31                       ` Daniel Campbell
2013-10-21  7:34                         ` Samuli Suominen
2013-10-21  7:33                       ` Samuli Suominen
2013-10-20 14:05                   ` Samuli Suominen
2013-10-23 22:51           ` [gentoo-user] " Steven J. Long
2013-10-24  3:48             ` Daniel Campbell
2013-10-20  9:24       ` [gentoo-user] " Volker Armin Hemmann
2013-10-20 10:52         ` Daniel Campbell
2013-10-20 11:02           ` Volker Armin Hemmann
2013-10-20 11:18             ` Daniel Campbell
2013-10-21 20:33               ` Volker Armin Hemmann
2013-10-22  8:43                 ` Daniel Campbell
2013-10-20 14:42           ` Tanstaafl [this message]
2013-10-21  1:14             ` Mark David Dumlao
2013-10-21  9:55               ` Tanstaafl
2013-10-21 10:11                 ` Mark David Dumlao
2013-10-21 10:27                   ` Tanstaafl
2013-10-21 10:48                     ` Mark David Dumlao
2013-10-21 10:59                       ` Tanstaafl
2013-10-21 11:10                         ` Mark David Dumlao
2013-10-21 11:53                           ` Tanstaafl
2013-10-21 20:34                 ` Volker Armin Hemmann

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=5263EBD8.2010400@libertytrek.org \
    --to=tanstaafl@libertytrek.org \
    --cc=gentoo-user@lists.gentoo.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