| 00:09.26 | *** join/#qi-hardware mth (ujhcjyos@82-168-42-142.ip.open.net) |
| 00:20.42 | *** join/#qi-hardware infobot (ibot@rikers.org) |
| 00:20.42 | *** topic/#qi-hardware is Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben/atusb 802.15.4 wireless, anelok and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware |
| 00:20.42 | *** mode/#qi-hardware [+v infobot] by ChanServ |
| 00:54.51 | *** join/#qi-hardware fiftysixc (ae351d5d@gateway/web/cgi-irc/kiwiirc.com/ip.174.53.29.93) |
| 00:55.52 | 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.13 | fiftysixc | he has a watercooling setup, is this the reason it crashed or unrelated? |
| 04:35.04 | *** join/#qi-hardware DocScrutinizer06 (~saturn@openmoko/engineers/joerg) |
| 05:50.59 | *** join/#qi-hardware luke-jr (~luke-jr@unaffiliated/luke-jr) |
| 06:18.15 | *** join/#qi-hardware ecloud (quassel@nat/qt/x-pswfjqpebrdvoogd) |
| 07:48.21 | *** join/#qi-hardware dandon (~dandon@88.151.75.36) |
| 07:53.26 | *** join/#qi-hardware ecloud (quassel@nat/qt/x-xtvzdjxndnwffamo) |
| 09:59.13 | *** join/#qi-hardware tavish (~tavish@unaffiliated/tavish) |
| 10:46.40 | *** join/#qi-hardware tavish (~tavish@unaffiliated/tavish) |
| 14:11.13 | *** join/#qi-hardware dandon (~dandon@88.151.75.36) |
| 15:41.01 | *** join/#qi-hardware wpwrak (~werner@13-145-231-201.fibertel.com.ar) |
| 16:35.57 | sb0 | DocScrutinizer05, https://github.com/systemd/systemd/issues/5644#event-1044786972 |
| 16:39.12 | *** join/#qi-hardware tavish (~tavish@unaffiliated/tavish) |
| 18:02.21 | 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 ? ;-) |
| 18:09.38 | *** join/#qi-hardware eintopf_ (~eintopf@unaffiliated/eintopf) |
| 18:22.53 | *** join/#qi-hardware arain (~alex@ssvlon5203w-lp130-02-70-50-41-128.dsl.bell.ca) |
| 19:34.43 | *** join/#qi-hardware arain (~alex@ssvlon5203w-lp130-02-70-50-41-128.dsl.bell.ca) |
| 19:57.53 | *** join/#qi-hardware tavish (~tavish@unaffiliated/tavish) |
| 21:43.53 | DocScrutinizer05 | sb0: thanks, already seen it :-) err >:-( |
| 21:45.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> pathetic |
| 21:46.25 | DocScrutinizer05 | [2017-04-16 Sun 21:10:01] <DocScrutinizer05> last comment is so to the point |
| 21:46.27 | 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.33 | DocScrutinizer05 | even better now: >> poettering locked and limited conversation to collaborators Apr 17, 2017<< |
| 21:56.04 | eintopf | :-( |
| 21:58.01 | wpwrak | at least he didn't lock and delete/hide it ;-) |
| 22:02.46 | whitequark | you can't easily do that on github can you? |
| 22:06.31 | DocScrutinizer05 | https://www.preining.info/blog/2017/04/systemd-again/ |
| 22:06.57 | *** join/#qi-hardware HardwareJefe (~pkennedy@104.236.150.108) |
| 22:08.07 | DocScrutinizer05 | http://without-systemd.org/wiki/index.php/Arguments_against_systemd#Absurd_Bugs_and_Responses |
| 22:20.53 | DocScrutinizer05 | https://www.preining.info/blog/2017/04/systemd-again/#comment-38174 |
| 22:25.29 | wpwrak | whitequark: i never felt the need to try ;-) but that would explain it ... |
| 22:59.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.36 | DocScrutinizer05 | didn't you claim git was exactly the tool to avoid such censorship? |
| 23:26.22 | 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.15 | DocScrutinizer05 | first of all you need git access to the git representation of the comments web frontend |
| 23:27.59 | wpwrak | sure |
| 23:28.11 | DocScrutinizer05 | git clone https://github.com/systemd/systemd; cd *; find . -iname *issue* -> http://paste.ubuntu.com/24423524 |
| 23:33.20 | DocScrutinizer05 | jr@saturn:~/x/systemd> grep -R "handover dev of this" ./.[^.]* |
| 23:33.22 | DocScrutinizer05 | jr@saturn:~/x/systemd> |
| 23:37.27 | DocScrutinizer05 | umm sorry, me's not awake yet |
| 23:39.20 | DocScrutinizer05 | anyway, this comment got censored for good |
| 23:39.30 | DocScrutinizer05 | for all I can tell |