| 1 |
On Thu, Jan 22, 2015 at 1:06 PM, Tom H <tomh0665@×××××.com> wrote: |
| 2 |
> |
| 3 |
> Samsung's starting to release Tizen-driven phones, TVs, white goods, |
| 4 |
> etc. Tizen uses systemd and, given the size of Samsung, the number of |
| 5 |
> systemd embedded devices is going to skyrocket in the next few years. |
| 6 |
> Samsung wouldn't have chosen systemd for Tizen if it were too resource |
| 7 |
> hungry for its use case. |
| 8 |
> |
| 9 |
|
| 10 |
Embedded is a pretty broad term, and it impacts all aspects of a |
| 11 |
device's design. You can't really put a smartphone and a microwave in |
| 12 |
the same category. |
| 13 |
|
| 14 |
Phones actually have plenty of storage, RAM, and CPU by most embedded |
| 15 |
standards. The main issue is battery use, which is mostly about |
| 16 |
ensuring that your software isn't constantly waking up the CPU. If |
| 17 |
systemd is well-behaved in this regard I'd expect it to work on a |
| 18 |
phone just fine. |
| 19 |
|
| 20 |
The thing is that most devices that couldn't run systemd would |
| 21 |
probably be hard-pressed to run any kind of generic linux distro in |
| 22 |
any case. They might not even run linux, or if they did it might be a |
| 23 |
super-stripped-down build with an embedded initramfs containing |
| 24 |
nothing but a single executable built in C which runs as PID 1 (no |
| 25 |
need for even filesystem support, let alone stuff like /proc and so |
| 26 |
on). |
| 27 |
|
| 28 |
I'm genuinely curious as to how systemd and competing solutions are |
| 29 |
adopted in the embedded world, including phones but especially getting |
| 30 |
beyond this (huge) niche. |
| 31 |
|
| 32 |
I'm also curious as to where ChromeOS ends up going. It is based on |
| 33 |
Gentoo, but runs Upstart (which isn't used by just about anybody else |
| 34 |
now, and which isn't even in Gentoo's portage). |
| 35 |
|
| 36 |
-- |
| 37 |
Rich |
Archives