4 ms·
I am wondering if there are "Linux Insurgents", which are groups of people with a particular agenda that find small bits of data which can be made to serve thei
by ChuckMcM 12y ago
I am wondering if there are "Linux Insurgents", which are groups of people with a particular agenda that find small bits of data which can be made to serve their cause and expose them. Or maybe they just don't like DBus. Or maybe they just want to feel like they are having a larger debate.
If it is any consolation, while I worked at Sun in the kernel group and later, this sort of 'cherry pick a message to start a debate' technique was also present. Sometimes it is just someone who believes something is broken and they use the message to bolster their argument.
- nitrogen 12y agoI also wonder if the reverse happens, with people sabotaging the system by breaking things that work, making easy things harder, and replacing fast things with slower things.
- felixgallo 12y agoI don't think it's fair to call systemd or dbus sabotage. It's entirely possible to construct explanations that rely on blinkered, tasteless incompetence, naivete, and personality cults rather than maliciousness.
- nitrogen 12y agoI was thinking more along the lines of reimplementing the Windows registry in Samba...
- pcwalton 12y ago> I am wondering if there are "Linux Insurgents", which are groups of people with a particular agenda that find small bits of data which can be made to serve their cause and expose them. Or maybe they just don't like DBus. Or maybe they just want to feel like they are having a larger debate. D-Bus is related to systemd (in that systemd relies on it), so this issue seems to have garnered a fair bit of spillover from the larger systemd debate.
- ChuckMcM 12y agoNo doubt the spillover is real. Clearly highlights one of the challenges of Linux user land, I guess in the 'Bazaar' model this might be equivalent to trying to ban the selling of meat from endangered species amongst all the vendors.
- digi_owl 12y agoThe bazaar works in the sense that each vendor stick to their product. but with systemd one vendor is "branching out", and offering (tightly) interconnected products. And for a certain subset of customers, distro maintainers, this offer is tantalizing. Because it may make their life easier. Or maybe to go back to the meat, it is not the kind of meat thats the problem. But that now you have one vendor selling whole meals. And to stretch it a bit further, they are not selling it to the eater, but the chef. Say you have a favorite restaurant, and when you sit down you can combine this meat with that potato etc. But then one day you come in and you find the menu had changed to pre-set meal. Now if you want your favorite kind of meat you can only have it alongside a potato you barely tolerate (if not downright dislike). This because the restaurant switched supplier to one that only sell pre-packaged meals rather than individual components.
- kasabali 12y agoThis is the best analogy of systemd project I've seen so far.