Re:Obstacles for kdbus
by sho_hn on Thursday April 23, 2015 @04:42PM
(#9429662)
A LWN subscription is a must for anyone serious about the open source systems infrastructure in place today. While overall Linux-centric, a lot of the content in LWN's Weekly Issue deals with the greater community context (policy, legal, etc.) or with tooling also in use by others (e.g. toolchains, or culture enablement stuff like Nathan Willis' tremendously great coverage of the typography / font stack / localization engineering beat). It's not just a must because reading it is worth your time, but also because it's a venue worth supporting for the continued health of the ecosystem a lot of us exist in.
Re:Obstacles for kdbus
by Spidler on Thursday April 23, 2015 @06:07PM
(#9430204)
I must say that I agree, and I'm personally _very_ fond of their business model.
Having the articles become free no matter what, and having articles of a level of quality that they _Repeatedly_ get referenced in papers on computer science, is a great feat.
Are there any other magazines online that have a good, weekly/bi-weekly posting schedule of multiple, high-quality and on-topic articles? I've seen ones related to photography, but not that have the same focus and high quality as LWN.
Re:Obstacles for kdbus
by RustyRussell on Thursday April 23, 2015 @07:21PM
(#9430544)
Heh, I came here to do exactly the same. I figure one free link per year on HN is about right for Manic Supporter level subscription, but you beat me to it.
Re:Obstacles for kdbus
by bandrami on Friday April 24, 2015 @02:37AM
(#9431744)
I have stayed away from the systemd hatred - is it still a huge issue?
Not for me, I use Slackware and don't want dbus or a QR code generator linked in to my init system.
I think the misadventures of udev set a whole lot of people off to start looking for every possible conspiracy theory they could find. Personally, I don't "hate" systemd; it's a probably-interesting solution to problems I just don't have.
Re:Obstacles for kdbus
by digi_owl on Friday April 24, 2015 @01:03PM
(#9434582)
The "major" issue is the tighter and tighter coupling between init and desktop login thanks to systemd-logind+"bunch of Freedesktop.org kits"+gnome (and with Wayland +KDE).
Eventually you have to go back to using FVWM for your GUI needs if you don't want to do a wholesale userspace-ectomy on a perfectly functional distro.
Never mind avoiding anything GTK or Qt based, as they are likely to depend on some lib form Gnome or KDE that in turn depend on something tied to the hip of systemd.
Seriously people, logind is at present in charge of handling the likes of laptop lid closure. If that does not bring out the WTFs, i dunno what will.
Re:Obstacles for kdbus
by bandrami on Friday April 24, 2015 @01:32PM
(#9434779)
Seriously people, logind is at present in charge of handling the likes of laptop lid closure.
It's sure as hell not for me; I still have never booted with systemd. If people choose a distribution in which it does, I wish them luck with that. It probably does solve multiple problems; like I keep saying they are just problems I don't have.
Re:Obstacles for kdbus
by bitwize on Monday April 27, 2015 @05:02AM
(#9445086)
The point is that even if you haven't booted with systemd -- you will. Tge desktop and GUI software of the future will depend on the integration it provides.
Re:Obstacles for kdbus
by anonbanker on Friday April 24, 2015 @03:52AM
(#9431949)
when systemd/networkmanager/pulseaudio are involved, the freedesktop.org brigade comes to defend the honor of their favorite developers, and the discussion is effectively ruined. We can now probably add kdbus to the above list of volatile apps.
Re:Obstacles for kdbus
by bitwize on Friday April 24, 2015 @09:55AM
(#9433268)
I think it's more like when systemd/networkmanager/pulseaudio are involved, the hater horde comes out to tear down the hard work of developers without offering any viable alternatives.
Dbus is the future of system integration in Linux. Period. The Unix philosophy sucks; real integration is done with the COM philosophy of looking up and invoking services by name and sending messages and calling methods on them as they run.
The reason why we even have a systemd is to integrate the essential system bits -- startup, device and service management, user login and session management, etc. with the dbus fabric, providing application developers with an API to call into them. Unfortunately it meant rewriting fucking everything, but Lennart, Kay, and company rolled up their sleeves, did the work, and got it pushed into mainstream distros. What the fuck have you done lately?
Re:Obstacles for kdbus
by jude- on Friday April 24, 2015 @12:53PM
(#9434502)
> hater horde comes out to tear down the hard work of developers without offering any viable alternatives.
No comment on the "haters," but your argument precludes the possibility that some users are happy with their current installations, and do not want an alternative.
> What the fuck have you done lately?
I'm writing a udev replacement [1]. Not because I want to re-invent the wheel, but because the wheel I was using got taken away.
Re:Obstacles for kdbus
by anonbanker on Monday May 04, 2015 @11:24AM
(#9486715)
Thank you for the hard work you are doing. Not very many are directly opposing Red Hat's dominance, but each one of you that do are making great strides in keeping linux (and GNU) free.
Re:Obstacles for kdbus
by ehvatum on Friday April 24, 2015 @11:19AM
(#9433915)
If I were Lennart, Kay, and company, I would not want the sort of "support" you are offering, here. If they do enjoy and encourage it, something is very wrong.
Re:Obstacles for kdbus
by anonbanker on Sunday April 26, 2015 @10:29PM
(#9444134)
wow. you pretty much hit on all the standard systemd/Lennart-supporting talking points. The future supporters should use your template as a fantastic starting point.
as for what I'm doing lately, I'm lurking in #systemd, watching you guys organize these reply-a-thons.
Re:Obstacles for kdbus
by anonbanker on Friday April 24, 2015 @03:33AM
(#9431892)
the users are collectively not happy with the choices their representatives are making. Especially when this choice compromises the GPL itself (Non-free software/modules/derivatives communicating over RPC to GPL'd libraries via systemd is a violation of the license), and GNU principles.
I have high hopes for Devuan and other non-systemd distros, but I never discount the docility of linux users en masse, and hold the opinion that once systemd got into debian, it would never get out again.
I am personally running a systemd-free arch linux install, and am switching all my machines to either Gentoo or OpenBSD, depending on use, in order to avoid systemd (or NetworkManager, or PulseAudio) being installed. I'm a tad more militant than most, though.
Re:Obstacles for kdbus
by bandrami on Friday April 24, 2015 @02:34AM
(#9431737)
Systemd is why kdbus is even being talked about (personally, I think it's a crazy idea, but then I don't use dbus even on my desktop), and the two projects share a lot of developers.
Re:Obstacles for kdbus
by username223 on Thursday April 23, 2015 @11:19PM
(#9431248)
Um, wow [1]...
> The only insult in that incoherent pile of metaphors is the fact that we belong to the same species. And since you cause _that_ offence simply by being yourself, well... everyone got used to it by now.
This is the internet, so I'm used to adults behaving like 5th graders sometimes, but when those same adults -- Al Viro -- write core infrastructure, something's seriously wrong.
Re:Obstacles for kdbus
by anonbanker on Friday April 24, 2015 @03:45AM
(#9431923)
you should have posted the parent post, from Jóhann B. Guðmundsson, a systemd/kdbus dev[1]:
> Last time I made reference to you living in a glass house you did not have the mental capacity to understand it so I sincerely doubt that your slowly growing senile brain can comprehend it now.
Al Viro was responding to something far more vitriolic. His response was understandable. Though, when arguing with a poisonous person, from enough distance, nobody can tell which is the poisonous one.
Re:Obstacles for kdbus
by username223 on Friday April 24, 2015 @08:15PM
(#9436635)
> His response was understandable.
His response was childish. The sane thing for a middle-aged man in a semi-respected position to do would be to say nothing. But this is the Land of Drepper, so you may be right.
http://lwn.net/SubscriberLink/641275/43136cb3c973ec6c/
Consider subscribing to LWN!
Having the articles become free no matter what, and having articles of a level of quality that they _Repeatedly_ get referenced in papers on computer science, is a great feat.
Are there any other magazines online that have a good, weekly/bi-weekly posting schedule of multiple, high-quality and on-topic articles? I've seen ones related to photography, but not that have the same focus and high quality as LWN.
Not for me, I use Slackware and don't want dbus or a QR code generator linked in to my init system.
I think the misadventures of udev set a whole lot of people off to start looking for every possible conspiracy theory they could find. Personally, I don't "hate" systemd; it's a probably-interesting solution to problems I just don't have.
Eventually you have to go back to using FVWM for your GUI needs if you don't want to do a wholesale userspace-ectomy on a perfectly functional distro.
Never mind avoiding anything GTK or Qt based, as they are likely to depend on some lib form Gnome or KDE that in turn depend on something tied to the hip of systemd.
Seriously people, logind is at present in charge of handling the likes of laptop lid closure. If that does not bring out the WTFs, i dunno what will.
It's sure as hell not for me; I still have never booted with systemd. If people choose a distribution in which it does, I wish them luck with that. It probably does solve multiple problems; like I keep saying they are just problems I don't have.
Dbus is the future of system integration in Linux. Period. The Unix philosophy sucks; real integration is done with the COM philosophy of looking up and invoking services by name and sending messages and calling methods on them as they run.
The reason why we even have a systemd is to integrate the essential system bits -- startup, device and service management, user login and session management, etc. with the dbus fabric, providing application developers with an API to call into them. Unfortunately it meant rewriting fucking everything, but Lennart, Kay, and company rolled up their sleeves, did the work, and got it pushed into mainstream distros. What the fuck have you done lately?
No comment on the "haters," but your argument precludes the possibility that some users are happy with their current installations, and do not want an alternative.
> What the fuck have you done lately?
I'm writing a udev replacement [1]. Not because I want to re-invent the wheel, but because the wheel I was using got taken away.
[1] https://git.devuan.org/pkgs-utopia-substitution/vdev/blob/ma...
as for what I'm doing lately, I'm lurking in #systemd, watching you guys organize these reply-a-thons.
I have high hopes for Devuan and other non-systemd distros, but I never discount the docility of linux users en masse, and hold the opinion that once systemd got into debian, it would never get out again.
I am personally running a systemd-free arch linux install, and am switching all my machines to either Gentoo or OpenBSD, depending on use, in order to avoid systemd (or NetworkManager, or PulseAudio) being installed. I'm a tad more militant than most, though.
http://lists.freedesktop.org/archives/systemd-devel/2013-Mar...
> The only insult in that incoherent pile of metaphors is the fact that we belong to the same species. And since you cause _that_ offence simply by being yourself, well... everyone got used to it by now.
This is the internet, so I'm used to adults behaving like 5th graders sometimes, but when those same adults -- Al Viro -- write core infrastructure, something's seriously wrong.
[1] https://lwn.net/Articles/640643/
> Last time I made reference to you living in a glass house you did not have the mental capacity to understand it so I sincerely doubt that your slowly growing senile brain can comprehend it now.
Al Viro was responding to something far more vitriolic. His response was understandable. Though, when arguing with a poisonous person, from enough distance, nobody can tell which is the poisonous one.
1. https://lwn.net/Articles/640636/
His response was childish. The sane thing for a middle-aged man in a semi-respected position to do would be to say nothing. But this is the Land of Drepper, so you may be right.