00:55 <fiftysixc> My friend said he got a BSOD and now can't boot into windows. I looked at it and while in BIOS the cpu went up to 55~ celcius before capping out, idle

00:56 <fiftysixc> he has a watercooling setup, is this the reason it crashed or unrelated?

16:35 <sb0> DocScrutinizer05, https://github.com/systemd/systemd/issues/5644#event-1044786972

18:02 <wpwrak> sb0: force systemd down everyone's throat or try to understand how unix works. can't blame him for not having time for both, can we ? ;-)

21:43 <DocScrutinizer05> sb0: thanks, already seen it :-) err >:-(

21:45 <DocScrutinizer05> [2017-04-16 Sun 21:05:36] <DocScrutinizer05> https://github.com/systemd/systemd/issues/5644 [2017-04-16 Sun 21:19:56] <DocScrutinizer05> this points to a general problem and has some value to learn from it: >>It certainly doesn't help it isn't defined anywhere what path_is_safe means and for what it is "safe". << https://github.com/systemd/systemd/pull/5655 [2017-04-16 Sun 21:25:53] <DocScrutinizer05> pathetic

21:46 <DocScrutinizer05> [2017-04-16 Sun 21:10:01] <DocScrutinizer05> last comment is so to the point

21:46 <DocScrutinizer05> [2017-04-16 Sun 21:12:02] <golinux> I was just going to post that. Here it is! "maybe handover dev of this toy to someone with unix experience"

21:50 <DocScrutinizer05> even better now: >> poettering locked and limited conversation to collaborators Apr 17, 2017<<

21:56 <eintopf> :-(

21:58 <wpwrak> at least he didn't lock and delete/hide it ;-)

22:02 <whitequark> you can't easily do that on github can you?

22:06 <DocScrutinizer05> https://www.preining.info/blog/2017/04/systemd-again/

22:08 <DocScrutinizer05> http://without-systemd.org/wiki/index.php/Arguments_against_systemd#Absurd_Bugs_and_Responses

22:20 <DocScrutinizer05> https://www.preining.info/blog/2017/04/systemd-again/#comment-38174

22:25 <wpwrak> whitequark: i never felt the need to try ;-) but that would explain it ...

22:59 <DocScrutinizer05> wpwrak: well, how about finding the hidden git history to reveal the "maybe handover dev of this toy to someone with unix experience" comment and its censoring again?

23:00 <DocScrutinizer05> didn't you claim git was exactly the tool to avoid such censorship?

23:26 <wpwrak> well, you can censor a repo. what you can't do is censor it without people who have an up to date copy noticing.

23:27 <DocScrutinizer05> first of all you need git access to the git representation of the comments web frontend

23:27 <wpwrak> sure

23:28 <DocScrutinizer05> git clone https://github.com/systemd/systemd; cd *; find . -iname *issue* -> http://paste.ubuntu.com/24423524

23:33 <DocScrutinizer05> jr@saturn:~/x/systemd> grep -R "handover dev of this" ./.[^.]*

23:33 <DocScrutinizer05> jr@saturn:~/x/systemd>

23:37 <DocScrutinizer05> umm sorry, me's not awake yet

23:39 <DocScrutinizer05> anyway, this comment got censored for good

23:39 <DocScrutinizer05> for all I can tell