#qi-hardware IRC log for Thursday, 2017-04-20

--- Thu Apr 20 201700:00
fiftysixcMy 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, idle00:55
fiftysixche has a watercooling setup, is this the reason it crashed or unrelated?00:56
sb0DocScrutinizer05, https://github.com/systemd/systemd/issues/5644#event-104478697216:35
wpwraksb0: 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 ? ;-)18:02
DocScrutinizer05sb0: thanks, already seen it :-) err >:-(21:43
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> pathetic21:45
DocScrutinizer05[2017-04-16 Sun 21:10:01] <DocScrutinizer05> last comment is so to the point21: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:46
DocScrutinizer05even better now:  >> poettering locked and limited conversation to collaborators Apr 17, 2017<<21:50
eintopf:-(21:56
wpwrakat least he didn't lock and delete/hide it ;-)21:58
whitequarkyou can't easily do that on github can you?22:02
DocScrutinizer05https://www.preining.info/blog/2017/04/systemd-again/22:06
DocScrutinizer05http://without-systemd.org/wiki/index.php/Arguments_against_systemd#Absurd_Bugs_and_Responses22:08
DocScrutinizer05https://www.preining.info/blog/2017/04/systemd-again/#comment-3817422:20
wpwrakwhitequark: i never felt the need to try ;-) but that would explain it ...22:25
DocScrutinizer05wpwrak: 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?22:59
DocScrutinizer05didn't you claim git was exactly the tool to avoid such censorship?23:00
wpwrakwell, you can censor a repo. what you can't do is censor it without people who have an up to date copy noticing.23:26
DocScrutinizer05first of all you need git access to the git representation of the comments web frontend23:27
wpwraksure23:27
DocScrutinizer05git clone https://github.com/systemd/systemd; cd *; find . -iname *issue*  -> http://paste.ubuntu.com/2442352423:28
DocScrutinizer05jr@saturn:~/x/systemd> grep -R "handover dev of this" ./.[^.]*23:33
DocScrutinizer05jr@saturn:~/x/systemd> 23:33
DocScrutinizer05umm sorry, me's not awake yet23:37
DocScrutinizer05anyway, this comment got censored for good23:39
DocScrutinizer05for all I can tell23:39
--- Fri Apr 21 201700:00

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!