Quoting KatolaZ (kato...@freaknet.org):
> or, just use debfoster :P
Words of wisdom. ;->
Excerpts follow from the package-operations notes for the team managing
www.svlug.org for Silicon Valley Linux User Group. (A long-ago nitwit
LUG vice-president chose Ubuntu Server for the system, and
On Tue, Feb 13, 2018 at 09:33:38AM -0800, Rick Moen wrote:
> Quoting Steve Litt (sl...@troubleshooters.com):
>
> > Urban, back in 2013 I faced a sort of mini-systemd situation: I kicked
> > every KDE executable and library off my system, on the theory that if
> > any KDE code got run, it could do
Quoting Steve Litt (sl...@troubleshooters.com):
> Urban, back in 2013 I faced a sort of mini-systemd situation: I kicked
> every KDE executable and library off my system, on the theory that if
> any KDE code got run, it could do heaven knows what to my system,
> because KDE is a hairball of monoli
On Tue, 13 Feb 2018 14:39:26 +
KatolaZ wrote:
> Unless you really believe in *ghosts*, and accept as an act of faith
We believe in zombies, don't we?
We even *rely* on daemons... ;-)
(Sorry, I could'nt resist :)
Luciano.
--
/"\ /Via A. Salaino, 7 - 20144 Milano (It
On Tue, 13 Feb 2018 15:35:42 +0100
Irrwahn wrote:
> J. Fahrner wrote on 13.02.2018 14:55:
> > Am 2018-02-13 13:50, schrieb Irrwahn:
> > But wouldn't it be nice to have a patch-script,
> > which locates all known files containing "systemd" and patches them
> > to remove this systemd stuff after
On Tue, Feb 13, 2018 at 02:55:12PM +0100, J. Fahrner wrote:
> Am 2018-02-13 13:50, schrieb Irrwahn:
> >That message can safely be ignored.
> >
> >This is caused by the dbus startup from script(s) /etc/X11/Xsession.d/ .
> >It basically means that dbus did not find systemd upon launch, which is
> >to
J. Fahrner wrote on 13.02.2018 14:55:
> Am 2018-02-13 13:50, schrieb Irrwahn:
>> That message can safely be ignored.
>>
>> This is caused by the dbus startup from script(s) /etc/X11/Xsession.d/
>> .
>> It basically means that dbus did not find systemd upon launch, which is
>> to be expected on a D
On Tue, 13 Feb 2018 13:41:40 +0100, J. wrote in message
<022bc517b4f405d3419202c35b0b1...@fahrner.name>:
> Am 2018-02-13 13:30, schrieb J. Fahrner:
> > My .xsession-errors has the following warning
> >
> > dbus-update-activation-environment: systemd --user not found,
> > ignoring --systemd
> >
Am 2018-02-13 13:50, schrieb Irrwahn:
That message can safely be ignored.
This is caused by the dbus startup from script(s) /etc/X11/Xsession.d/
.
It basically means that dbus did not find systemd upon launch, which is
to be expected on a Devuan system that by definition comes w/o systemd.
I
J. Fahrner wrote on 13.02.2018 13:30:
> My .xsession-errors has the following warning
>
> dbus-update-activation-environment: systemd --user not found, ignoring
> --systemd
> argument
>
> Any ideas what's causing this? Is there some wrong config file around?
That message can safely be ignored
Am 2018-02-13 13:30, schrieb J. Fahrner:
My .xsession-errors has the following warning
dbus-update-activation-environment: systemd --user not found, ignoring
--systemd
argument
Any ideas what's causing this? Is there some wrong config file around?
Found 2 files in /etc/X11/Xsession.d which
My .xsession-errors has the following warning
dbus-update-activation-environment: systemd --user not found, ignoring
--systemd
argument
Any ideas what's causing this? Is there some wrong config file around?
Jochen
___
Dng mailing list
Dng@lists.dyn
12 matches
Mail list logo