On Tue, 17.05.16 18:11, Michael Biebl (mbi...@gmail.com) wrote:
> I have to add, I don't quite understand, why the convenience libs are
> split up like this:
explained some in the other mail. To add to this:
>
>
> > libbasic.la
> > libshared.la
> > libfirewall.la
this one is separate as it
On Tue, 17.05.16 18:09, Michael Biebl (mbi...@gmail.com) wrote:
> 2016-05-17 10:36 GMT+02:00 Lennart Poettering :
> > On Mon, 16.05.16 04:24, Michael Biebl (mbi...@gmail.com) wrote:
> >
> >> Hi,
> >
> >> Any ideas, why simple tools like loginctl, busctl, hostnamectl
I have to add, I don't quite understand, why the convenience libs are
split up like this:
> libbasic.la
> libshared.la
> libfirewall.la
> libcore.la
> libsystemd-internal.la
> libsystemd-network.la
> libudev-internal.la
> libudev-core.la
> libjournal-core.la
> libsystemd-journal-internal.la
>
2016-05-17 10:36 GMT+02:00 Lennart Poettering :
> On Mon, 16.05.16 04:24, Michael Biebl (mbi...@gmail.com) wrote:
>
>> Hi,
>
>> Any ideas, why simple tools like loginctl, busctl, hostnamectl require 300K+
>> ?
>> What's up with systemd-analyze?
>
> it embedds much of
On Mon, May 16, 2016 at 12:06 PM, Martin Pitt wrote:
> Michael Biebl [2016-05-16 4:24 +0200]:
>> Any ideas, why simple tools like loginctl, busctl, hostnamectl require 300K+
>> ?
>> Could we move more common functionality into a shared, private library
>> to counter the
On Mon, 16.05.16 04:24, Michael Biebl (mbi...@gmail.com) wrote:
> Hi,
> Any ideas, why simple tools like loginctl, busctl, hostnamectl require 300K+ ?
> What's up with systemd-analyze?
it embedds much of PID1's logic actually, in order to do unit file
checking.
> Could we move more common
On Mon, May 16, 2016 at 11:06 AM, Martin Pitt wrote:
> Michael Biebl [2016-05-16 4:24 +0200]:
>> Any ideas, why simple tools like loginctl, busctl, hostnamectl require 300K+
>> ?
>> Could we move more common functionality into a shared, private library
>> to counter the
Am 16.05.2016 um 14:18 schrieb Michael Biebl:
2016-05-16 6:15 GMT+02:00 Auke Kok :
On Mon, May 16, 2016 at 04:24:25AM +0200, Michael Biebl wrote:
1,5M usr/bin/systemd-analyze
What's up with systemd-analyze?
It shouldn't be part of a base package, it's not even a
2016-05-16 6:15 GMT+02:00 Auke Kok :
> On Mon, May 16, 2016 at 04:24:25AM +0200, Michael Biebl wrote:
>> 1,5M usr/bin/systemd-analyze
>>
>> What's up with systemd-analyze?
>
> It shouldn't be part of a base package, it's not even a diagnostic tool, more
> like a
Michael Biebl [2016-05-16 4:24 +0200]:
> Any ideas, why simple tools like loginctl, busctl, hostnamectl require 300K+ ?
> Could we move more common functionality into a shared, private library
> to counter the constant growth?
Building src/shared/ into a private libsystemd-internal.so (which
On Mon, May 16, 2016 at 04:24:25AM +0200, Michael Biebl wrote:
> 1,5M usr/bin/systemd-analyze
>
> What's up with systemd-analyze?
It shouldn't be part of a base package, it's not even a diagnostic tool, more
like a performance measurement type of thing.
I don't think size is of a concern for
Hi,
systemd has a tendency to grow in size with each new release (and I
mean installed Mb on disk here).
Looking at the size of a couple of binaries, I'm really suprised they
are so huge:
36K bin/systemd-notify
36K usr/bin/systemd-cat
36K usr/bin/systemd-detect-virt
40K bin/systemd-escape
44K
12 matches
Mail list logo