Page 1 of 1

A dubs surprising history

Posted: 2017-04-08 13:33
by Danielsan

Code: Select all

A reboot is required to replace the running dbus-daemon.
Please reboot the system when convenient.
:shock: :shock: :shock:

Re: A systemd windows-like disease

Posted: 2017-04-08 13:52
by arochester
Is that a question?

When you started the thread "It's time to move..." I thought that you might have moved to another distro.

Re: A systemd windows-like disease

Posted: 2017-04-08 14:22
by golinux
The question would be . . .

How could this possibly be a good thing?

Re: A systemd windows-like disease

Posted: 2017-04-08 17:27
by Head_on_a_Stick
Danielsan wrote:

Code: Select all

A reboot is required to replace the running dbus-daemon.
Please reboot the system when convenient.
This message has *nothing* to do with systemd and was in fact printed out in wheezy under sysvinit...
bugs.debian.org wrote:dbus-daemon has never had this feature
https://bugs.debian.org/cgi-bin/bugrepo ... bug=805449

Now please FUD off :mrgreen:

Re: A systemd windows-like disease

Posted: 2017-04-08 17:48
by Danielsan
Please take it easy... 8)

If I would start a complain I would have opened it in the general section. However if you still continue to read the mailing list is clearly a problem connected with systemd as both rely each others because the former.

I was surprised because I have never seen dbus requesting to restart with sysv-init, for me is not a big issue restart a computer but a for a cluster of server might it be a serious pain.

Peace :wink:

Re: A systemd windows-like disease

Posted: 2017-04-08 17:57
by dasein
arochester wrote:Is that a question?
Nah. Just more troll-fodder from FDN's most persistent systemd troll.
arochester wrote:I thought that [Danielsan] might have moved to another distro.
We aren't that lucky.

Re: A systemd windows-like disease

Posted: 2017-04-08 18:16
by Danielsan
And probably I will continue until a new init system, however epistemologically speaking it is clearly fault of systemd beacuse at the time when dbus was designed the former doesn't exist so changing the conditions it changes also the effects... :mrgreen:

Re: A systemd windows-like disease

Posted: 2017-04-09 02:10
by sunrat
I'm getting older. Clearly systemd's fault. I was younger before it existed.

Re: A systemd windows-like disease

Posted: 2017-04-09 09:26
by debiman
^ sunrat, i couldn't have phrased it better.
yet the urge to rant is strong in me:
This message has *nothing* to do with systemd and was in fact printed out in wheezy under sysvinit...
Now please FUD off :mrgreen:
yep.
danielsan, please change thread title.
unless you actually like the sort of unrest this falsity is going to create.

according to some, every (vaguely administration- and service-related) problem that crops up, is systemd's fault.
every actual real bug in systemd is proof of it being - the devil's masterplan to destroy all linux.

anyhow, on topic (if there is one):
in windows reboot, in linux be root
- is a really nice pun, but my experience has always been that in many situations it's much easier to log out/in or even reboot, than to look up the right (root) commands.

Re: A dubs surprising history

Posted: 2017-04-13 10:52
by edbarx
What is "dubs"? Please change it to "dbus".

Yes, rebooting a machine is considered an obvious trick to use by many, irrespective of the fact that Linux could do anything without requiring it. A reboot can be avoided even when a kernel is upgraded given the kernel is patched for such a functionality, but nevertheless, the great great masses out there, want a reboot, as that is what they are used to.

Danielsan, don't be shocked if you also discover your system grinding to a halt during shutdown... Updates during shutdown must be cool these days... To hell, if you happen to be in a hurry.

Enough trolling for today... :roll:

Re: A dubs surprising history

Posted: 2017-04-14 19:36
by Danielsan
Sorry now I will change the titles as:
A daemon scaring history
:mrgreen: