On 11/21/14 18:20, Rich Freeman wrote:
> On Fri, Nov 21, 2014 at 12:39 PM,  <wirel...@tampabay.rr.com> wrote:
>> 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.
>>
> Embedded is a VERY broad term.  I agree that systemd isn't applicable
> in all of these cases, but honestly in the cases where it doesn't
> apply I don't see something like openrc or even sysvinit being a great
> solution.
>
> For the more PC-like appliance something like systemd is fairly
> compelling once it matures, because it is basically a standardized
> collection of stuff designed to work together.  You could look at it a
> bit like busybox in that regard.
>
> This argument is also a bit like saying that since most embedded
> devices don't have high-res displays, X11 and Wayland are dead-end
> technologies.
>
> The reality is that embedded tends to do things differently - it is
> related to your typical desktop distro, but not really in pure
> competition.
>
> Look at it another way - the most popular PID 1 on Gentoo-derived
> systems isn't even in the main portage repository.  I'm speaking of
> course of Chromebooks, which run Upstart.
>
> --
> Rich
>
I'm actually familiar with android / Qualcomm stuff and QuRT as well as
OKL4. Honestly if it meant a substitute for QuRT could be made available
to the public I'd say use whatever-- I'll never buy another device until
then. Besides, I'm not sure at which point it became okay to buy a $400+
device use it for 6 months and then throw it in the trash and buy
another but I won't be a part of that.

Reply via email to