How else could NM update /etc/resolv.conf with the nameservers provided by the DHCP server? If you need static data in resolv.conf while using NM then add these in NM and they will be added to resolv.conf.

That is not what he said, he said that his backup was on a RAID6 not that he used RAID6 as a backup!

Better yet look at what they did to Gnome Terminal in 3.14, the tabs are not centered instead of left aligned which makes it hard to actually see how many tabs you have opened at the same time. And which tab is the active one is completely impossible to see visually.

No, because the key length of DES was public and thus people had no problem understanding what kind of effort and costs it would take to break it by using brute force. Once it was felt that that threshold was near, 3DES was strapped together and that one is still not reachable by any brute force machine the NSA has now or in the foreseeable future.

I know it's the answer to "should I run WIndows on my servers?" but how in hell do you find that as an acronym for Microsoft?

I wouldn't go so far as call it a killer feature but SSH support on Windows is a welcoming feature indeed. Hopefully they will also some day throw out their power shell and replace it with BASH, that would be the day!

So their employers donated that money then.

That is not the same thing as "the developers are not listening to people", it's simply the open questions from the code reviewers that needs to be addressed if kdbus will have a chance of being included. I.e business as usual.

And of course the devs are hell-bent to get it included, when was the last time that you wrote kernel code without caring if it would be included or not?

systemd is not in the kernel, it's part of userspace.

What didn't they listen to? AFAIK Linus will not merge kdbus if that where the case.

And the chance of that being implemented correctly is what, 1%? Now obviously MasterCard probably is better at this than random app-devloper considering that they have to pay the people whose cards are hacked, but since it's a closed app we only can speculate.

So post one of those easily reproductable steps then.

Of course it logs it to the journal that is there it sends all data from stderr, stdout and syslog. It even collects output from other processes that have with the daemon to do and stores them together, like systemd own actions.

For example for nptd, here we can see that ntpd shutdown since it couldn't reoslve the dns names and systemd restarted it, it's a common problem with ntpd that it doesn't retry itself. Several of these lines comes from stderr

fultra@ubuntu:~$ journalctl -u ntp
-- Logs begin at mån 2015-06-22 18:39:49 CEST, end at mån 2015-06-22 18:52:45 CEST. --
jun 22 18:40:07 ubuntu systemd[1]: Stopped LSB: Start NTP daemon.
jun 22 18:40:08 ubuntu systemd[1]: Starting LSB: Start NTP daemon...
jun 22 18:40:08 ubuntu ntp[925]: * Starting NTP server ntpd
jun 22 18:40:09 ubuntu ntpd[933]: ntpd 4.2.6p5@1.2349-o Mon Apr 13 17:00:14 UTC 2015 (1)
jun 22 18:40:09 ubuntu ntp[925]: ...done.
jun 22 18:40:09 ubuntu systemd[1]: Started LSB: Start NTP daemon.
jun 22 18:40:09 ubuntu ntpd[938]: proto: precision = 0.106 usec
jun 22 18:40:09 ubuntu ntpd[938]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
jun 22 18:40:09 ubuntu ntpd[938]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
jun 22 18:40:09 ubuntu ntpd[938]: Listen and drop on 1 v6wildcard :: UDP 123
jun 22 18:40:09 ubuntu ntpd[938]: Listen normally on 2 lo 127.0.0.1 UDP 123
jun 22 18:40:09 ubuntu ntpd[938]: Listen normally on 3 lo ::1 UDP 123
jun 22 18:40:09 ubuntu ntpd[938]: peers refreshed
jun 22 18:40:09 ubuntu ntpd[938]: Listening on routing socket on fd #20 for interface updates
jun 22 18:40:09 ubuntu ntpd[938]: Deferring DNS for 0.ubuntu.pool.ntp.org 1
jun 22 18:40:09 ubuntu ntpd[938]: Deferring DNS for 1.ubuntu.pool.ntp.org 1
jun 22 18:40:09 ubuntu ntpd[938]: Deferring DNS for 2.ubuntu.pool.ntp.org 1
jun 22 18:40:09 ubuntu ntpd[938]: Deferring DNS for 3.ubuntu.pool.ntp.org 1
jun 22 18:40:09 ubuntu ntpd[938]: Deferring DNS for ntp.ubuntu.com 1
jun 22 18:40:09 ubuntu ntpd[944]: signal_no_reset: signal 17 had flags 4000000
jun 22 18:40:11 ubuntu ntpd_intres[944]: host name not found: 0.ubuntu.pool.ntp.org
jun 22 18:40:11 ubuntu ntpd_intres[944]: host name not found: 1.ubuntu.pool.ntp.org
jun 22 18:40:11 ubuntu ntpd_intres[944]: host name not found: 2.ubuntu.pool.ntp.org
jun 22 18:40:11 ubuntu ntpd_intres[944]: host name not found: 3.ubuntu.pool.ntp.org
jun 22 18:40:11 ubuntu ntpd_intres[944]: host name not found: ntp.ubuntu.com
jun 22 18:40:15 ubuntu systemd[1]: Stopping LSB: Start NTP daemon...
jun 22 18:40:15 ubuntu ntp[1049]: * Stopping NTP server ntpd
jun 22 18:40:15 ubuntu ntpd[938]: ntpd exiting on signal 15
jun 22 18:40:15 ubuntu ntp[1049]: ...done.
jun 22 18:40:15 ubuntu systemd[1]: Stopped LSB: Start NTP daemon.
jun 22 18:40:24 ubuntu systemd[1]: Starting LSB: Start NTP daemon...
jun 22 18:40:24 ubuntu ntp[1457]: * Starting NTP server ntpd
jun 22 18:40:24 ubuntu ntpd[1465]: ntpd 4.2.6p5@1.2349-o Mon Apr 13 17:00:14 UTC 2015 (1)
jun 22 18:40:24 ubuntu ntpd[1467]: proto: precision = 0.175 usec
jun 22 18:40:24 ubuntu ntpd[1467]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
jun 22 18:40:24 ubuntu ntpd[1467]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
jun 22 18:40:24 ubuntu ntpd[1467]: Listen and drop on 1 v6wildcard :: UDP 123
jun 22 18:40:24 ubuntu ntpd[1467]: Listen normally on 2 lo 127.0.0.1 UDP 123
jun 22 18:40:24 ubuntu ntpd[1467]: Listen normally on 3 eth0 192.168.0.3 UDP 123
jun 22 18:40:24 ubuntu ntpd[1467]: Listen normally on 4 lo ::1 UDP 123
jun 22 18:40:24 ubuntu ntpd[1467]: Listen normally on 5 eth0 fe80::226:18ff:feae:582e UDP 123
jun 22 18:40:24 ubuntu ntpd[1467]: peers refreshed
jun 22 18:40:24 ubuntu ntpd[1467]: Listening on routing socket on fd #22 for interface updates
jun 22 18:40:24 ubuntu ntp[1457]: ...done.
jun 22 18:40:24 ubuntu systemd[1]: Started LSB: Start NTP daemon.

Why does this clearly wrong statements keep getting posted? It should be well known by know by everyone that systemd has captured stderr and uses the exit status since day one. In fact the old SysVInit was the one that didn't capture stderr at all or cared about the exit status.

So there is no public shared showers in Australian bath houses?