Quoting Alessandro Selli (alessandrose...@linux.com):
[supporting what you said]
> What could they possibly do of any harm to your system systemd unit
> files, that is plain ASCII config files?
I've said it before: If worried about such detritus files (or about
libsystemd0), any sysadmin is
Am 11. Oktober 2018 15:21:17 MESZ schrieb Alessandro Selli
:
> And I wish we were living in a world where the
> only struggle was advancing science,
> knowledge, free software and landing on far
> away planets and explore the galaxy. Reality
> is quite a different story, though, and it's not
On 10/10/18 at 15:23, Enrico Weigelt, metux IT consult wrote:
> On 25.07.2018 10:20, Joel Roth wrote:
>
> Hi,
>
>> Most of those "alarming" files are just systemd units files, put there> by
>> daemons/packages/utilities who "also" support systemd in a way or another.
>> So they are not alarming
On 25.07.2018 10:20, Joel Roth wrote:
Hi,
> Most of those "alarming" files are just systemd units files, put there> by
> daemons/packages/utilities who "also" support systemd in a way or>
another. So they are not alarming but just *totally* *harmless* if you>
don't have a running systemd as PID
On 25.07.2018 09:11, Hleb Valoshka wrote:
> It's required just to notify systemd that sshd is running, so in
> systemd-less system it's nop. So mostly libsystemd0 is harmless.
Is it that the original libsystemd0, which tries to talk to systemd
via desktop-bus ?
Or is it a patched version, where
Am Freitag, 27. Juli 2018 schrieb KatolaZ:
> On Fri, Jul 27, 2018 at 11:37:57AM +0200, Dr. Nikolaus Klepp wrote:
> [...]
> > Well, yes, but the wole point of removing libsystemd0 would be to get rid
> > of anything systemd, not to magle the systemd sources to do nothing (which
> > would be a
On 2018-07-27 05:18, Lars Noodén wrote:
On 07/27/2018 01:00 PM, KatolaZ wrote:
[...] I need to specify here that a *maintainer* is a person who
follows the changes happening upstream to the packages he/she is
maintaining on a daily basis, and rebuilds those packages as
necessary, keeping them
On Fri, 27 Jul 2018 12:00:05 +0200
KatolaZ wrote:
> Unfortunately, most of the great people that helped stripping
> libsystemd deps in Jessie, just disappeared soon after
One of the tricks is to get a disliked project up and running to make
it the de facto alternative, then either pulling out
On Fri, Jul 27, 2018 at 01:18:41PM +0300, Lars Noodén wrote:
[cut]
>
> Can you please (re-)post the link to the new Devuan build process?
>
Dear Lars,
it's under "Deveopment":
https://devuan.org/os/development
and the relevant link is the fourth one:
On 07/27/2018 01:00 PM, KatolaZ wrote:
> [...] I need to specify here that a *maintainer* is a person who
> follows the changes happening upstream to the packages he/she is
> maintaining on a daily basis, and rebuilds those packages as
> necessary, keeping them updated. And commits herself to do
On Fri, Jul 27, 2018 at 11:37:57AM +0200, Dr. Nikolaus Klepp wrote:
> Am Freitag, 27. Juli 2018 schrieb KatolaZ:
> > On Fri, Jul 27, 2018 at 12:05:54AM +0200, Dr. Nikolaus Klepp wrote:
> > > Sorry, this may break the thread but I already deleted the original
> > > message.
> > >
> > > To make
Am Freitag, 27. Juli 2018 schrieb KatolaZ:
> On Fri, Jul 27, 2018 at 12:05:54AM +0200, Dr. Nikolaus Klepp wrote:
> > Sorry, this may break the thread but I already deleted the original message.
> >
> > To make things short: this a minimal "libnosystemd" for sshd on ascii. It
> > basicly does
On Fri, Jul 27, 2018 at 12:05:54AM +0200, Dr. Nikolaus Klepp wrote:
> Sorry, this may break the thread but I already deleted the original message.
>
> To make things short: this a minimal "libnosystemd" for sshd on ascii. It
> basicly does nothing at all. To be more specific, it does exactly the
Am Freitag, 27. Juli 2018 schrieb Dr. Nikolaus Klepp:
> Sorry, this may break the thread but I already deleted the original message.
>
> To make things short: this a minimal "libnosystemd" for sshd on ascii. It
> basicly does nothing at all. To be more specific, it does exactly the same
> that
Sorry, this may break the thread but I already deleted the original message.
To make things short: this a minimal "libnosystemd" for sshd on ascii. It
basicly does nothing at all. To be more specific, it does exactly the same that
libsystemd0 does, which is nothing.
Unpack where you like,
Quoting Luciano Mannucci (luci...@vespaperitivo.it):
> Wasn't there something called uselessd that had this very goal some
> time ago? It was promising but died, I don't know why ...
The anonymous author felt his initial versions (through 2014's
uselessd-8) had successfully made his point --
Steve Litt wrote on 26.07.2018 18:17:
> On Thu, 26 Jul 2018 13:17:21 +0200
> Irrwahn wrote:
>> What's more, I'd
>> go even further and say I wouldn't mind at all if every daemon
>> package came with support for all init systems in current use
>> (rc-style sysv|openrc, runit, ... , systemd), as
On Thu, 26 Jul 2018 13:17:21 +0200
Irrwahn wrote:
> Hendrik Boom wrote on 26.07.2018 12:35:
> > On Wed, Jul 25, 2018 at 06:50:43PM +0200, Irrwahn wrote:
> >> Hendrik Boom wrote on 25.07.2018 17:59:
> >> [cut]
> >>> Package dependencies are of the form
> >>> Install X if Y is installed
>
On Thu, 26 Jul 2018 16:45:29 +0200
info at smallinnovations dot nl wrote:
> systemd is in principle
> nothing new in functionality but provides an uniform API for some
> information you otherwise have to program yourself. We can serve them
> the same information without serving systemd this way.
On 26-07-18 16:34, Steve Litt wrote:
> On Thu, 26 Jul 2018 12:45:53 +0200
> info at smallinnovations dot nl wrote:
>>
>> Of course does the libsystemd API not provide it, but we can. First
>> call to libsystemd API == systemd installed? If no, call to
>> libnosystemd API which init system ==
On Thu, 26 Jul 2018 12:45:53 +0200
info at smallinnovations dot nl wrote:
> On 26-07-18 12:15, KatolaZ wrote:
> >
> > The libsystemd API does not provide any way to check *which* init
> > system is running (ehm...for "obvious" reasons, right?). But we
> > could put in place a mechanism that
On Thu, 26 Jul 2018 12:15:13 +0200
KatolaZ wrote:
> This would in principle allow people to "catch" systemd-related events
> and "translate" them to events for any other init system, using a
> simple mechanism.
Sounds like a great idea. The daemon phones home to what it thinks is
systemd to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Do den 26. Jul 2018 um 14:23 schrieb Lars Noodén:
> Looking at the DSC files, it seems that the culprit is either gnome or
> ssh-askpass-gnome or both.
>
> Is there an alternative ssh-askpass-* graphical utility likely to be
> more portable
On 07/26/2018 04:01 PM, Klaus Ethgen wrote:> Hi,
>
> Am Mo den 23. Jul 2018 um 14:24 schrieb Rolf Schmidt:
>> I would ask, if it is true, that the openssh-server still needs
>> libsystemd0 in ascii?
>
>> Can I expect e fix?
>
> If you trust me ( :-D ) you can use my package[0].[snip]
Looking at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Am Mo den 23. Jul 2018 um 14:24 schrieb Rolf Schmidt:
> I would ask, if it is true, that the openssh-server still needs
> libsystemd0 in ascii?
>
> Can I expect e fix?
If you trust me ( :-D ) you can use my package[0].
It is the debian
Hi,
KatolaZ writes:
> On Thu, Jul 26, 2018 at 12:45:53PM +0200, info at smallinnovations dot nl
> wrote:
>> On 26-07-18 12:15, KatolaZ wrote:
>> >
>> > The libsystemd API does not provide any way to check *which* init
>> > system is running (ehm...for "obvious" reasons, right?). But we could
>>
Hi,
Joel Roth writes:
> Katolaz wrote on March 2, 2018:
>
>> leloft wrote:
>
>>
>> I issued $locate systemd
>> and got 200 lines of output, including
>> /etc/systemd/system/* (23 files)
>> /lib/systemd/system/* (60 files)
>> /lib/x86_64-linux-gnu/libsystemd.so.0 (and 0.17.0)
>> /usr/lib/systemd
On Thu, Jul 26, 2018 at 12:45:53PM +0200, info at smallinnovations dot nl wrote:
> On 26-07-18 12:15, KatolaZ wrote:
> >
> > The libsystemd API does not provide any way to check *which* init
> > system is running (ehm...for "obvious" reasons, right?). But we could
> > put in place a mechanism that
Hendrik Boom wrote on 26.07.2018 12:35:
> On Wed, Jul 25, 2018 at 06:50:43PM +0200, Irrwahn wrote:
>> Hendrik Boom wrote on 25.07.2018 17:59:
>> [cut]
>>> Package dependencies are of the form
>>> Install X if Y is installed
>>> Too bad it doesn't handle
>>> Install X it Y and Z are
On 26-07-18 12:15, KatolaZ wrote:
>
> The libsystemd API does not provide any way to check *which* init
> system is running (ehm...for "obvious" reasons, right?). But we could
> put in place a mechanism that allows to shell out the calls to
> libsystemd functions to a set of scripts with
On Wed, Jul 25, 2018 at 06:50:43PM +0200, Irrwahn wrote:
> Hendrik Boom wrote on 25.07.2018 17:59:
> [cut]
> > Package dependencies are of the form
> > Install X if Y is installed
> > Too bad it doesn't handle
> > Install X it Y and Z are installed.
> > I suspect, though, we don't wand to
On Thu, Jul 26, 2018 at 12:01:54PM +0200, info at smallinnovations dot nl wrote:
> On 26-07-18 10:00, KatolaZ wrote:
> >
> > The main problem is that those packages need to be maintained, and not
> > just stripped of the libsystemd0 dependency once, and then forgotten,
> > which is what happened
On 26-07-18 10:00, KatolaZ wrote:
>
> The main problem is that those packages need to be maintained, and not
> just stripped of the libsystemd0 dependency once, and then forgotten,
> which is what happened with most of the Jessie packages that were
> forked for that reason.
>
> The medium-term
Simon Hobson wrote on 25.07.2018 23:25:
> KatolaZ wrote:
>
>> Replace 'links2' with 'openssh-server' and 'libfbdirect' with
>> 'libsystemd0', and you should see what I mean. Most of the De??an
>> installations actually have tons of libraries that are never used, or
>> are just used to probe for
On Wed, Jul 25, 2018 at 10:25:32PM +0100, Simon Hobson wrote:
> KatolaZ wrote:
>
> > Replace 'links2' with 'openssh-server' and 'libfbdirect' with
> > 'libsystemd0', and you should see what I mean. Most of the De??an
> > installations actually have tons of libraries that are never used, or
> >
KatolaZ wrote:
> Replace 'links2' with 'openssh-server' and 'libfbdirect' with
> 'libsystemd0', and you should see what I mean. Most of the De??an
> installations actually have tons of libraries that are never used, or
> are just used to probe for a certain functionality that is not
> available.
On Wed, Jul 25, 2018 at 11:59:06AM -0400, Hendrik Boom wrote:
> On Tue, Jul 24, 2018 at 10:20:56PM -1000, Joel Roth wrote:
>
> > Katolaz wrote on March 2, 2018:
> >
>
> >
> > Most of those "alarming" files are just systemd units files, put there
> > by daemons/packages/utilities who "also"
Hendrik Boom wrote on 25.07.2018 17:59:
[cut]
> Package dependencies are of the form
> Install X if Y is installed
> Too bad it doesn't handle
> Install X it Y and Z are installed.
> I suspect, though, we don't wand to have to embed a SAT solver into the
> package manager. It's already
On Tue, Jul 24, 2018 at 10:20:56PM -1000, Joel Roth wrote:
> Katolaz wrote on March 2, 2018:
>
>
> Most of those "alarming" files are just systemd units files, put there
> by daemons/packages/utilities who "also" support systemd in a way or
> another. So they are not alarming but just
On Wed, Jul 25, 2018 at 02:41:52AM -0500, goli...@dyne.org wrote:
> On 2018-07-25 02:11, Hleb Valoshka wrote:
> > On 7/23/18, Rolf Schmidt wrote:
> >
> > > I would ask, if it is true, that the openssh-server still needs
> > > libsystemd0 in ascii?
> >
> > Yes.
> >
> > > Can I expect e fix?
> >
On 2018-07-25 02:11, Hleb Valoshka wrote:
On 7/23/18, Rolf Schmidt wrote:
I would ask, if it is true, that the openssh-server still needs
libsystemd0 in ascii?
Yes.
Can I expect e fix?
It's required just to notify systemd that sshd is running, so in
systemd-less system it's nop. So
On 7/23/18, Rolf Schmidt wrote:
> I would ask, if it is true, that the openssh-server still needs
> libsystemd0 in ascii?
Yes.
> Can I expect e fix?
It's required just to notify systemd that sshd is running, so in
systemd-less system it's nop. So mostly libsystemd0 is harmless.
Currently
Hello,
I would ask, if it is true, that the openssh-server still needs
libsystemd0 in ascii?
Can I expect e fix?
Fine regards
Rolf
signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
43 matches
Mail list logo
