A dubs surprising history

If it doesn't relate to Debian, but you still want to share it, please do it here

A dubs surprising history

Postby Danielsan » 2017-04-08 13:33

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


:shock: :shock: :shock:
Last edited by Danielsan on 2017-04-09 13:07, edited 1 time in total.
If you can't fork then hold you in silence.
User avatar
Danielsan
 
Posts: 458
Joined: 2010-10-10 22:36

Re: A systemd windows-like disease

Postby arochester » 2017-04-08 13:52

Is that a question?

When you started the thread "It's time to move..." I thought that you might have moved to another distro.
"Something to be aware of: Debian is a core or source distribution. This means there are many Debian-based distributions. THEY ARE NOT DEBIAN."
arochester
 
Posts: 1029
Joined: 2010-12-07 19:55

Re: A systemd windows-like disease

Postby golinux » 2017-04-08 14:22

The question would be . . .

How could this possibly be a good thing?
May the FORK be with you!
User avatar
golinux
 
Posts: 1241
Joined: 2010-12-09 00:56
Location: not a 'buntard!

Re: A systemd windows-like disease

Postby Head_on_a_Stick » 2017-04-08 17:27

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:
No code is faster than no code.

Please read before posting How to report a problem
User avatar
Head_on_a_Stick
 
Posts: 6533
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: A systemd windows-like disease

Postby Danielsan » 2017-04-08 17:48

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:
If you can't fork then hold you in silence.
User avatar
Danielsan
 
Posts: 458
Joined: 2010-10-10 22:36

Re: A systemd windows-like disease

Postby dasein » 2017-04-08 17:57

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.
User avatar
dasein
 
Posts: 7775
Joined: 2011-03-04 01:06
Location: Terra Incantationum

Re: A systemd windows-like disease

Postby Danielsan » 2017-04-08 18:16

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:
If you can't fork then hold you in silence.
User avatar
Danielsan
 
Posts: 458
Joined: 2010-10-10 22:36

Re: A systemd windows-like disease

Postby sunrat » 2017-04-09 02:10

I'm getting older. Clearly systemd's fault. I was younger before it existed.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!
User avatar
sunrat
 
Posts: 1992
Joined: 2006-08-29 09:12
Location: Melbourne, Australia

Re: A systemd windows-like disease

Postby debiman » 2017-04-09 09:26

^ 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.
User avatar
debiman
 
Posts: 1173
Joined: 2013-03-12 07:18

Re: A dubs surprising history

Postby edbarx » 2017-04-13 10:52

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:
Debian == { > 30, 000 packages }; Debian != systemd
The worst infection of all, is a false sense of security!
It is hard to get away from CLI tools.
User avatar
edbarx
 
Posts: 5383
Joined: 2007-07-18 06:19
Location: 35° 50 N, 14 º 35 E

Re: A dubs surprising history

Postby Danielsan » 2017-04-14 19:36

Sorry now I will change the titles as:

A daemon scaring history


:mrgreen:
If you can't fork then hold you in silence.
User avatar
Danielsan
 
Posts: 458
Joined: 2010-10-10 22:36


Return to Offtopic

Who is online

Users browsing this forum: No registered users and 5 guests

fashionable