On Wed, 30 Nov 2016, Klaus Ethgen wrote:
> No, it worked well for decades and it was exactly why you have small
> root and resizable /usr on other medias.
It worked because of extraordinary effort by DDs to continuously migrate
libraries from /usr to / any time a binary or library in /bin, /sbin,
On Wed, Nov 30, 2016 at 09:45:08AM +0100, Klaus Ethgen wrote:
> Am Mi den 30. Nov 2016 um 9:36 schrieb Julian Andres Klode:
> > In your imagination, that is (yes, I too can write stupid replies
> > without any arguments - but I actually can provide arguments too,
> > see below).
>
> Thanks for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Mi den 30. Nov 2016 um 9:36 schrieb Julian Andres Klode:
> In your imagination, that is (yes, I too can write stupid replies
> without any arguments - but I actually can provide arguments too,
> see below).
Thanks for insulting me. (I do not
Hello Martin,
Martin Steigerwald [2016-11-30 9:20 +0100]:
> Also agreed to that… libsystemd is almost one third of the size of libc6.so
> here… and it seems upstream basically stuffes *everything* into it, including
> reading process attributes that IMHO would be a task for a *different*
(Huh, all emails are CCing listmaster - let's drop them for this
subthread for now.)
On Wed, Nov 30, 2016 at 07:46:31AM +0100, Klaus Ethgen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi Martin,
>
> Am Di den 29. Nov 2016 um 22:36 schrieb Martin Pitt:
> > Cristian
Am Mittwoch, 30. November 2016, 07:46:31 CET schrieb Klaus Ethgen:
> > Also, *if* you want to make this about systemd vs. SysV again:
> Well, systemd, or better the religiosity, systemd is spread, is part of
> this particular problem. Exactly that is the case, why so many users
> oppose systemd.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Martin,
Am Di den 29. Nov 2016 um 22:36 schrieb Martin Pitt:
> Cristian Ionescu-Idbohrn [2016-11-29 22:16 +0100]:
> > Eversince systemd came about into debian, you've shown direct or
> > indirect disrespect, IMO, to people objecting against
Hello Christian,
Cristian Ionescu-Idbohrn [2016-11-29 22:16 +0100]:
> Eversince systemd came about into debian, you've shown direct or
> indirect disrespect, IMO, to people objecting against screwing up
> their systems, where they want to keep sysv instead of adopting
> systemd world domination.
On Sun, 27 Nov 2016, Michael Biebl wrote:
> Am 27.11.2016 um 12:32 schrieb Klaus Ethgen:
> > Am So den 27. Nov 2016 um 11:56 schrieb Michael Biebl:
> >> We no longer support a split /usr which is not pre-mounted in the
> >> initramfs.
> >
> >> So you either have two options:
> >> 1/ Don't use a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am So den 27. Nov 2016 um 11:56 schrieb Michael Biebl:
> We no longer support a split /usr which is not pre-mounted in the initramfs.
>
> So you either have two options:
> 1/ Don't use a split /usr
> 2/ Use an initramfs to mount /usr
1. I do not
There are several fields that a process can have that are obtained from the
systemd library. man ps and search for systemd shows them all but the ones
I noticed were machine, lsession, ouid, seat and slice that come to mind.
On Sun, Nov 27, 2016 at 9:41 PM Klaus Ethgen wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Craig,
Am So den 27. Nov 2016 um 11:12 schrieb Craig Small:
> There is a reason for linking to libsystemd and it is to do with accessing
> the systemd type parameters that can be applied to a process.
But what has ps to do with such a
reassign 845480 libsystemd0 232-6
retitle 845480 libsystemd links to libraries in /usr
affects 845480 procps
thankyou
Hi,
I received a report saying that ps fails to run if /usr is separate.
The reason for this is ps links to libsystemd which in turn links to
liblz4 which is found on /usr
I'm
There is a reason for linking to libsystemd and it is to do with accessing
the systemd type parameters that can be applied to a process.
- Craig
On Sun, Nov 27, 2016 at 8:28 PM Klaus Ethgen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi Craig,
>
> Am Mi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Craig,
Am Mi den 23. Nov 2016 um 23:15 schrieb Axel Beckert:
> Craig Small wrote:
> > Actually its not ps, its libsystemd that is pulling this dependency in. ps
> > is linked to libsystemd which is in /lib and
> > $ ldd
Control: found -1 2:3.3.12-2
On 2016-11-26 09:44:44 +1300, Ben Caradoc-Davies wrote:
> I think that this bug affects only systems that have /usr on a separate
> filesystem.
>
> I upgraded procps on a system in which /usr is on the root filesystem and
> encountered no problems at boot time.
>
>
I think that this bug affects only systems that have /usr on a separate
filesystem.
I upgraded procps on a system in which /usr is on the root filesystem
and encountered no problems at boot time.
Please consider adjusting the title of this report for the benefit of
your apt-listbugs readers
Hi Craig,
Craig Small wrote:
> Actually its not ps, its libsystemd that is pulling this dependency in. ps
> is linked to libsystemd which is in /lib and
> $ ldd /lib/x86_64-linux-gnu/libsystemd.so | grep usr
> liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 (0x7fa2cf30)
>
> There is
Actually its not ps, its libsystemd that is pulling this dependency in. ps
is linked to libsystemd which is in /lib and
$ ldd /lib/x86_64-linux-gnu/libsystemd.so | grep usr
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 (0x7fa2cf30)
There is also this on the systemd bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Package: procps
Version: 2:3.3.12-3
Severity: critical
ps is depending on /usr/lib/x86_64-linux-gnu/liblz4.so.1. As udev needs
ps to be started, it cannot make the devices available where /usr is on
so the boot fails completely.
Please make ps not
20 matches
Mail list logo