1 |
On Sun, Sep 21, 2014 at 9:47 AM, Mark David Dumlao <madumlao@×××××.com> |
2 |
wrote: |
3 |
|
4 |
> |
5 |
> |
6 |
> On Sun, Sep 21, 2014 at 2:58 AM, Grant Edwards <grant.b.edwards@×××××.com> |
7 |
> wrote: |
8 |
> |
9 |
>> On 2014-09-20, Mark David Dumlao <madumlao@×××××.com> wrote: |
10 |
>> |
11 |
>> >> The only Linux systems where I care about boot time are embedded |
12 |
>> >> systems which are never going to have the resources needed to run |
13 |
>> >> systemd. |
14 |
>> > |
15 |
>> > You are mistaken. |
16 |
>> |
17 |
>> No, I am not. |
18 |
>> |
19 |
>> > I've helped a friend debug problems on a couple devices running a |
20 |
>> > custom Arch system with systemd. |
21 |
>> |
22 |
>> How does that contradict the statement I made that the systems where I |
23 |
>> care about boot times do not have the resources required to run |
24 |
>> systemd? |
25 |
>> |
26 |
> |
27 |
> You made a generic, catch-all statement about embedded systems which isnt |
28 |
> necessarily true. There are plenty of routers or NAS devices or ipcams, etc |
29 |
> that have the resources to run systemd. Pretty much everything that has the |
30 |
> space to fit the kernel and a a few MB has the resources to run it |
31 |
> |
32 |
|
33 |
Sorry I clicked somewhere onscreen and it sent immediately. An audit of 204 |
34 |
on debian shows that it's small to negligible, with a lot of optional |
35 |
components. |
36 |
|
37 |
https://people.debian.org/~stapelberg/docs/systemd-dependencies.html |
38 |
|
39 |
|
40 |
|
41 |
|
42 |
> |
43 |
> -- |
44 |
> This email is: [ ] actionable [ ] fyi [ ] social |
45 |
> Response needed: [ ] yes [ ] up to you [ ] no |
46 |
> Time-sensitive: [ ] immediate [ ] soon [ ] none |
47 |
> |
48 |
|
49 |
|
50 |
|
51 |
-- |
52 |
This email is: [ ] actionable [ ] fyi [ ] social |
53 |
Response needed: [ ] yes [ ] up to you [ ] no |
54 |
Time-sensitive: [ ] immediate [ ] soon [ ] none |