#qi-hardware IRC log for Tuesday, 2016-06-07

DocScrutinizer05https://lists.dns-oarc.net/pipermail/dns-operations/2016-June/014965.html   krrhrr >> Which in general was my problem when I met the systemd people to talk about this. My use cases were simply ignored as not relevant.<<06:02
DocScrutinizer05start here: https://lists.dns-oarc.net/pipermail/dns-operations/2016-June/014964.html06:02
kyakwhy do i have the feeling that there is some evil master plan behind systemd?06:29
larscthe evil master plan is to improve the Linux ecosystem06:41
DocScrutinizer05rather redhat's ecosystem aka favourable balance06:46
DocScrutinizer05kyak: maybe because you're right?06:47
DocScrutinizer05also:   https://lists.dns-oarc.net/pipermail/dns-operations/2016-June/014967.html  >>[$Poetteringware fails on XY,] Which is exactly what $Poetteringware was supposed to solve....<<  I smell a recurring annoying pattern06:49
DocScrutinizer05even more annoying: often this doesn't change even *years* after introduction of the "new leete shit"06:50
DocScrutinizer05on a more general paraphrased quote: "When your usecase doesn't work with systemd then your usecase is wrong. Systemd is great and there's absolutely no valid alternative to it"06:56
DocScrutinizer05I hope it's obvious that I beg to differ06:57
DocScrutinizer05what really puzzles the shit outa me are those frequent statements like "I completely trust my distro maintainer to handle this for me"06:59
DocScrutinizer05heck, I'd rather trust M$ regarding such stuff, than a distro maintainer making money only from providing support for those professional enterprise grade users that simply can't afford all the educational workshops anymore to keep pace with that avalanche of "new leete stuff that 'usually works' OOTB"07:02
infobot[freee] http://www.youtube.com/watch?feature=player_detailpage&v=ZTdUmlGxVo0&t=329607:05
DocScrutinizer05(trust distro maintainers) actually it's rather the usual case that stuff like e.g. systemd comes up with new defaults that break shit for a significant number of users, and the distro maintainers don't give a flying F* to fix that07:17
DocScrutinizer05au contraire your local custom settings in preferences are relentlessly nuked during installation of that new stuff. See for example sysreq keys07:19
DocScrutinizer05and when you complain, the answer is "your usecase is, and always been, wrong - to start with. So WONTFIX"07:20
DocScrutinizer05in case of sysreq keys "the user isn't supposed to be able to do this" KTNXBY07:21
kyakbut that's quite true! average use is not supposed to be able to do that :)07:37
DocScrutinizer05but when I deliberately enabled it on my system, who's bold enough to tell me I did wrong and he's entitled to fix it and educate me?07:42
DocScrutinizer05not even microsoft got away with fixinf default browser each time MS Explorer got started07:47
DocScrutinizer05or the insane "when you don't provide a working resolver/DHCP config, Systemd will be more helpful than dhcpd or any other daemon so far, and defaults to for you"07:49
DocScrutinizer05or cron which "was broken so far, but systemd fixed that for you, now replaying all events old cron would have missed due to e.g. system suspended at the scheduled time" - which provokes the answer "so far the `killall poettering` job was scheduled to a time where I'm supposed to have my system suspended, unless I'm gone insane over all that new crap"07:53
DocScrutinizer05NB they *could* have done The Right Thing[TM], implement a default-off config option for that behavior, like "anacron=1", and even add a new parameter to crontab syntax to deal with jobs that actually want to use the replay feature. But nooooooo.07:59
whitequarklarsc: you mean "destroy"09:03
whitequarkit's going on quite well, there is so much new fun fragmentation...09:03
wpwrakwhitequark: let's turn this around: if you're opposing systemd, your are fomenting division and fragmentation !11:56
wpwrakbut we have to hand it to poettering that, where init and such used to be a mainly technical area, he succeeded in politicizing it. if he's not out of steam yet, maybe he could lawyerize it in the next iteration. then we would have recovered syntony with overall societal development. :)12:01
larschaving to accept the EULA before a deamon starts13:27
wpwrakthings like this: http://www.pidjin.net/2016/05/18/i-just-wanna-see/13:35
kristianpaulso cruel 18:28
kristianpaul:o anelok.com that hovering features is quite handy 18:32
kristianpaulbit of 404 still but not bad18:32
wpwrakkristianpaul: 404 ? where ?19:26
kristianpaulwpwrak: https://anelok.com/TOUCH 21:51
kristianpaulbut i read the Under Construction sign so..21:52
wpwrakoh, right. i actually noticed these, too. they're weird, because all the things that are supposed to be there, are. lemme see what produces this ...22:07
wpwrakah, links i planned to use at some point in the future :) i never noticed because i never even tried, but i saw crawlers try them - and now you :)22:10
wpwrakhmm no, it's actually more subtle. it's a side-effect of how i implemented the hovering back then. meanwhile, i'm using a much nicer mechanism, suggested by hellekin, for block diagrams. but i never got around to upgrading this bit (which later inspired the block diagrams)22:30
kristianpauloh lol22:40
wpwrakthough the block diagram solution doesn't apply 1:1 either, because there i use pop-ups (a bit like on xkcd's "what if", which is actually where i stole that idea), while the anelok front page replaces the image. the latter should be easier, but the difference means that i can't just reuse the same scripts.22:59
wpwrakwell, i guess that's a battle for another day then :) needs a bit of planning.23:00
--- Wed Jun 8 201600:00

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