| 1 |
On Fri, Nov 21, 2014 at 12:39 PM, <wireless@×××××××××××.com> wrote: |
| 2 |
> |
| 3 |
> Regardless, the smaller, cheaper embedded linux crowd is very unlikely to |
| 4 |
> ever embrace systemd. Why? Glad you asks. Thousands of reasons, but, |
| 5 |
> here are a few: It is very common in embedded (anything) to run multiple |
| 6 |
> and often different rtos (real time operating system) on different embedded |
| 7 |
> systems products, often to circumvent licenses, royalties, duplication, |
| 8 |
> security and a plethora of other reasons. Furthermore, many embedded systems |
| 9 |
> run simultaneous codes on a single |
| 10 |
> core and systemd does not fit into that scheme of things, at all. |
| 11 |
> |
| 12 |
|
| 13 |
Embedded is a VERY broad term. I agree that systemd isn't applicable |
| 14 |
in all of these cases, but honestly in the cases where it doesn't |
| 15 |
apply I don't see something like openrc or even sysvinit being a great |
| 16 |
solution. |
| 17 |
|
| 18 |
For the more PC-like appliance something like systemd is fairly |
| 19 |
compelling once it matures, because it is basically a standardized |
| 20 |
collection of stuff designed to work together. You could look at it a |
| 21 |
bit like busybox in that regard. |
| 22 |
|
| 23 |
This argument is also a bit like saying that since most embedded |
| 24 |
devices don't have high-res displays, X11 and Wayland are dead-end |
| 25 |
technologies. |
| 26 |
|
| 27 |
The reality is that embedded tends to do things differently - it is |
| 28 |
related to your typical desktop distro, but not really in pure |
| 29 |
competition. |
| 30 |
|
| 31 |
Look at it another way - the most popular PID 1 on Gentoo-derived |
| 32 |
systems isn't even in the main portage repository. I'm speaking of |
| 33 |
course of Chromebooks, which run Upstart. |
| 34 |
|
| 35 |
-- |
| 36 |
Rich |
Archives