1. http://irclogger.com/.alpine-devel/2015-12-10
  2. 09:35 <ncopa> kdbus work was initiated due to systemd (I assume)
  3. 09:36 <skarnet> not really
  4. 09:36 <skarnet> it was initiated because lots of people use D-Bus and found it was slow
  5. 09:36 <fabled> i think dbus people wanted it themselves
  6. 09:36 <skarnet> (including the authors themselves, yes)
  7. 09:36 <ncopa> now, systemd developers feels its obsolete even before it is included in mainline
  8. ...
  9. 09:37 <skarnet> and they thought "it's slow? then we need to put it in the kernel!"
  10. 09:37 <skarnet> not even thinking that it may be slow because they suck at coding
  11. 09:37 <skarnet> this bus1 thing is just them throwing a tantrum
  12. 09:37 <ncopa> systemd needed dbus to work
  13. 09:37 <skarnet> "we didn't get our toy included in the kernel? then we're gonna make a new one"
  14. 09:38 <ncopa> but since systemd is pid 1, dbus was not running early enough
  15. 09:38 <skarnet> that too
  16. 09:38 <skarnet> they don't know how to bootstrap either
  17. 09:38 <ncopa> "Kay Sievers"
  18. 09:38 <ncopa> the primadonna
  19. 09:38 <ncopa> :)
  20. 09:39 <ncopa> "Compared to KDBUS, BUS1 doesn't seem to be at least heavily based on D-Bus."
  21. 09:39 <skarnet> Red Hat should send those guys back to engineering school instead of paying them a salaty
  22. http://irclogger.com/.alpine-devel/2016-02-24
  23. 21:54 <ncopa> so
  24. 21:54 <ncopa> this is a bit fun
  25. 21:54 <ncopa> everyone tells you how modular systemd is
  26. 21:54 <ncopa> you can replace components
  27. 21:54 <coredumb> oh gosh
  28. 21:54 <ncopa> its almost like posix
  29. 21:54 <coredumb> please
  30. 21:55 <coredumb> not systemd
  31. 21:55 <ncopa> then when actually trying to do that
  32. 21:55 <skarnet> it's actually true: you can replace components. What they're not saying is that said components need to follow the exact same design
  33. 21:55 <ncopa> you get: "no its not that simple"
  34. 21:55 <skarnet> and they're not saying it because _they don't know_
  35. 21:55 <coredumb> a transcript of my conversation on #centos
  36. 21:56 <coredumb> me: "Hey, I'd like to know what's the best way to paint my car in red"
  37. 21:56 <skarnet> because nobody knows half a shit in software engineering and supports systemd
  38. 21:56 <skarnet> *nobody*
  39. 21:56 <coredumb> them: "mmmmmh I'm pretty sure you don't want your car being red"
  40. 21:56 <ncopa> coredumb: exactly
  41. 21:56 <ncopa> "why would you?"
  42. 21:56 <coredumb> them: "Why don't you start by telling us _why_ you think you want your car painted red"
  43. 21:57 <coredumb> me: "WTF!"
  44. 21:57 <skarnet> coredumb: and when you wouldn't get convinced, they called you a hater?
  45. 21:57 <coredumb> them: "Well you see, usually people think they want their car red, but actually they need it to be black"
  46. 21:58 <coredumb> skarnet: quite
  47. 21:58 <coredumb> for the record
  48. 21:58 <coredumb> my "car being red" was "how do I run something _last_ with systemd"
  49. 21:59 <coredumb> and the solution compared to echo "last command" >> /etc/rc.local
  50. 21:59 <coredumb> is nothing like "systemd made Linux easy"
  51. 21:59 <coredumb> gosh I really have to blog about it
  52. 21:59 <skarnet> why would you do that? I'm pretty sure you don't want to do that. Start by telling us *why* you think it would be useful.
  53. 22:00 <coredumb> skarnet: actually I had to go to #systemd and repeat the whole red car again to start getting informations on those damn targets >_<
  54. 22:00 <ncopa> yeah. please tell us why you think a red car would be useful
  55. 22:01 <coredumb> seriously the ppl on #centos... they must be s*cking RH devs for breakfast to be that lobotomized
  56. 22:01 <leo-unglaub> ncopa: your systemd thread is awesome
  57. 22:02 <skarnet> coredumb: think about it - a distribution that is just like RedHat, without even the creativity of RedHat
  58. 22:02 <skarnet> who do you think works on it
  59. 22:03 <coredumb> damn you did put creativity _and_ RedHat in the same sentence :O
  60. 22:03 <skarnet> they do have creativity
  61. 22:04 <skarnet> they don't have good engineering, but they make stuff. They come up with original, if bad, solutions.
  62. http://irclogger.com/.alpine-devel/2016-03-11
  63. 23:59 <skarnet> jirutka: the estimated time for the *beginning* of the work is towards the end of this year, something like Oct-Nov
  64. 23:59 <skarnet> and there will be a whole lot of prep work
  65. http://irclogger.com/.alpine-devel/2016-03-12
  66. 00:00 <skarnet> I want to do things right, with no compromise, and this takes time
  67. 00:01 <jirutka> one of things I’m miss in s6 are “soft” service dependencies like after/before in OpenRC
  68. 00:02 <skarnet> (to what extent do we take the separation between mechanism and policy? what are our exact needs in terms of dependency management? what does apk provide? if we need something apk doesn't provide, that requires adding stuff to apk first.)
  69. 00:03 <skarnet> jirutka: the equivalent of OpenRC is more s6-rc than s6. Is that what you're talking about? (Clarity is important.)

skarnet on systemd and s6 plans