From: Paige Thompson <erratic@yourstruly.sx>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] The future of linux, and Gentoo specifically now
Date: Fri, 21 Nov 2014 19:07:52 +0000 [thread overview]
Message-ID: <546F8D88.908@yourstruly.sx> (raw)
In-Reply-To: <546F78D3.90809@tampabay.rr.com>
On 11/21/14 17:39, wireless@tampabay.rr.com wrote:
> On 11/21/14 07:00, Rich Freeman wrote:
>> On Fri, Nov 21, 2014 at 2:32 AM, Canek Peláez Valdés
>> <caneko@gmail.com> wrote:
>>> It's actually a great thing for a lot of use cases. But it doesn't
>>> seem that Gentoo will change defaults soon, although systemd works
>>> great with it.
>>>
>>
>> My (personal) sense is that in the medium-term we may end up moving to
>> not having any default at all, just as with bootloaders, kernels,
>> syslog, crontab, mail, etc. That is pretty-much the Gentoo way
>> everywhere else when there are options.
>>
>> As you already pointed out, as long as somebody cares to maintain
>> openrc and write init scripts for it, there will be support for it.
>> Many init scripts and systemd units are contributed by outside users
>> already, and policy is that maintainers cannot block them from being
>> added to packages (though they do not have to write/maintain them
>> personally).
>>
>> Gentoo doesn't really tend to exclude anything, and inclusion is a
>> matter of whether somebody wants to put in the work.
>
>> Rich
>
> Very wall expressed and neutral. This is an "800 lb gorilla" that nobody
> seems to be talking about; that is embedded linux. Embedded linux now
> accounts for at least 20 times the number of deployments of linux than
> workstations and servers combined; some argue it is far more, others a
> bit less. Regardless, embedded linux is a force that is driving the
> semiconductor markets. There's not much margin on 32bit or less. etc etc.
>
> The main point of embedded linux is take what Rich has articulated above
> and multiply it by a billion. There is no such thing as standard
> embedded linux. If Systemd is successful, with very large embedded
> systems (dozens to hundreds of cores) then it has a future. If it
> fails in that space, it may survive, but not likely. It will old serve
> to isolate those distros that go down that path, exclusively, *imho*.
>
> Regardless, the smaller, cheaper embedded linux crowd is very unlikely
> to ever embrace systemd. Why? Glad you asks. Thousands of reasons, but,
> here are a few: It is very common in embedded (anything) to run
> multiple and often different rtos (real time operating system) on
> different embedded systems products, often to circumvent licenses,
> royalties, duplication, security and a plethora of other reasons.
> Furthermore, many embedded systems run simultaneous codes on a single
> core and systemd does not fit into that scheme of things, at all.
>
>
> So, even if gentoo becomes stupid and decides to abandon openrc. Many
> folks will just move to embedded (gentoo) linux and play "follow the
> leaders" with bootstrapping there cores.
>
> Rest easy as the devs fight this one out. I hope systemd survives
> and prospers. I can tell you one area of massive failure and that is
> clustering/cloud computing. Sure the "big dogs" with big buck are
> claiming to use systemd, but they only roll out binary offerings. When
> others try to use one of the commercial brands of linux and build a
> cluster/cloud from the source-codes up, there are all sorts of problems.
>
> Hmmmmmmmmmmmmmmmmmmmmmm. Very strange, batman. Very strange.
>
>
> What is going on, is wildly variant. YMMV. But, should I be a sporting
> man, my money is on the embedded folks deciding if something other than
> systemd survives. Why do I bet on embedded folks? Easy. I personally
> know of dozens of folks that code in machine, assembler all the way
> through any language they choose. They routinely build entire systems,
> custom on a wide bit of processors. Only a few of those folks are
> necessary to keep alternatives to systemd alive, prosperous and
> clearly documented. There are most likely tens of thousands of the
> folks around the world. Do the math. Each time one of these experts
> build an embedded
> (linux) system, it is usually optimized and so wonderful, that
> companies clone them in counts of thousands to millions of deployed
> linux systems. The fact that the majority rare require human tinkering,
> is both a testament to how well they run and the wisdon of these
> brilliant developers to keep the rank and file humanoids using winblows
> and OXlooser operating systems.
>
> A forking of the linux kernel would be the best thing to happen to
> opensource, in a very, very long time. The kernel development has become
> a "good ole boys club" imho.
>
> Embedded linux runs everywhere; so rest easy!
>
>
> peace,
> James
>
>
>
>
>
>
>
I hope for this to be the case
next prev parent reply other threads:[~2014-11-21 19:09 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ooQFA-1dS-23@gated-at.bofh.it>
[not found] ` <ooQYV-1BC-1@gated-at.bofh.it>
[not found] ` <ooV2x-7AP-13@gated-at.bofh.it>
2014-11-21 17:39 ` [gentoo-user] The future of linux, and Gentoo specifically now wireless
2014-11-21 18:20 ` Rich Freeman
2014-11-21 19:20 ` Paige Thompson
2014-11-21 19:07 ` Paige Thompson [this message]
2014-11-21 7:17 Paige Thompson
2014-11-21 7:31 ` Marc Stürmer
2014-11-21 18:17 ` Paige Thompson
2014-11-21 7:32 ` Canek Peláez Valdés
2014-11-21 11:57 ` Rich Freeman
2014-11-21 17:36 ` Philip Webb
2014-11-24 17:54 ` Marc Stürmer
2014-11-24 18:25 ` Gevisz
2014-11-24 19:13 ` Marc Stürmer
2014-11-25 17:44 ` Gevisz
2014-11-26 7:45 ` Marc Stürmer
2014-11-26 8:39 ` Gevisz
2014-11-26 20:39 ` Walter Dnes
2014-11-26 21:19 ` Marc Stürmer
2014-11-26 10:06 ` thegeezer
2014-11-26 10:14 ` Neil Bothwick
2014-11-24 21:05 ` Neil Bothwick
2014-11-25 4:53 ` Gevisz
2014-11-25 8:41 ` Neil Bothwick
2014-11-25 17:09 ` Gevisz
2014-11-25 17:37 ` Neil Bothwick
2014-11-25 17:55 ` Gevisz
2014-11-25 19:49 ` Neil Bothwick
2014-11-25 20:24 ` Gevisz
2014-11-25 22:42 ` Neil Bothwick
2014-11-25 23:35 ` Emanuele Rusconi
2014-11-26 0:56 ` Neil Bothwick
2014-11-26 6:43 ` Gevisz
2014-11-26 5:59 ` Gevisz
2014-11-26 9:32 ` thegeezer
2014-11-25 18:37 ` Gevisz
2014-11-25 18:21 ` Maxim Wexler
2014-11-25 18:46 ` Gevisz
2014-11-27 14:24 ` Tom H
2014-11-25 7:15 ` Gevisz
2014-11-25 9:45 ` Alan McKinnon
2014-11-25 10:23 ` Peter Humphrey
2014-11-25 17:03 ` Gevisz
2014-11-25 19:56 ` Alan McKinnon
2014-11-25 20:13 ` Gevisz
2014-11-24 18:51 ` Emanuele Rusconi
2014-11-27 11:00 ` Tom H
2014-11-27 14:43 ` Marc Stuermer
2014-11-27 15:22 ` Canek Peláez Valdés
2014-11-27 19:06 ` Marc Stürmer
2014-11-27 21:46 ` Canek Peláez Valdés
2014-11-27 22:56 ` Paige Thompson
2014-11-27 23:01 ` Paige Thompson
2014-11-28 1:13 ` Canek Peláez Valdés
2014-11-28 19:03 ` Paige Thompson
2014-11-28 19:14 ` Mick
2014-11-28 19:14 ` Michael Orlitzky
2014-11-21 18:37 ` Paige Thompson
2014-11-21 22:04 ` Marc Joliet
2014-11-24 12:18 ` Sid S
2014-11-24 12:20 ` Sid S
2014-11-23 17:44 ` Tanstaafl
2014-11-23 18:07 ` Canek Peláez Valdés
2014-11-23 19:02 ` Marc Joliet
2014-11-23 19:11 ` Tanstaafl
2014-11-23 20:23 ` Tanstaafl
2014-11-23 20:26 ` Tanstaafl
2014-11-27 14:21 ` Tom H
2014-11-27 14:53 ` Marc Stuermer
2014-11-23 20:34 ` Canek Peláez Valdés
2014-11-23 22:45 ` Tanstaafl
2014-11-27 14:21 ` Tom H
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=546F8D88.908@yourstruly.sx \
--to=erratic@yourstruly.sx \
--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