51–60 of 166 posts
Earlier quoted context omitted.
> when someone actually tries to hire an assassin What???
From the horse's mouth: Recently, people started collecting Bitcoins to hire a hitman for me (this really happened!). https://plus.google.com/+LennartPoetteringTheOneAndOnly/post...
Earlier quoted context omitted.
Same issue as #GamerGate in that game "journalism" really is completely broken but now you can't talk about that without being lumped in with a bunch of vocal minority crazed misogynists.
I don't think you're a misogynist based on this comment. I just think the minority is bigger than you might imagine.
Such actions are why I identify with neither the systemd opponents nor the proponents. Unfortunately, it does dilute arguments against systemd, because of immediate associations with fools who attack people and scream fallacies (even though the non-systemd camp is an amorphous blob more than anything). This in turn gives moral high ground to the proponents and any attempt at debate devolves into the same dead ends and non-arguments between equally clueless factions.
Yet as much as the entire display is abominable, it is sadly also completely predictable. For all the good things the systemd crew have done, their ideas are disruptive, in that they're trying to mold a cathedral out of what has been a rather adamantly bazaar-based community for over two decades now. Contrary to popular belief, simply developing your tools in one repository doesn't magically make you "more like the BSDs" - there's far more to the BSDs than that, and every time I see someone make that argument, I twitch.
We're in the midst of an unprecedented schism. But, for what it's worth, this isn't an issue with "open source". No, it's an issue with the Linux community in particular. It is particularly dysfunctional. I have no idea why Linux attracts so much drama and carnage amongst its constituents, but it does.
I'm pretty disappointed in all sides here. The people who attack systemd and its developers on completely false premises, and the people who are convinced it's the be all and the end all, and have been living under a sysvinit-based rock their entire lives. It's just so exhausting. It really is.
I don't know how this will end. But the irony is intense: an attempt at distro unification has led to a big divide. The best thing we can hope for is people doing a bunch of new experimentation in Unix process management. Projects like Epoch and nosh are up and coming. Hopefully we'll see more.
Earlier quoted context omitted.
Why does his gender matter?
Cops' lives (in a particularly uncharitable interpretation) revolve around reinforcing their own masculinity by winning fights and exerting dominance. Using that to protect damsels in distress from creepy male others/sexual predators is a highly masculinity-reinforcing, fatherly/brotherly and desirable thing to do. An effiminate man (using the again uncharitable notion that nerds with desk jobs are not manly in the e…
Earlier quoted context omitted.
Wish I could get over it. But every time some random process fails to start at boot time I...well I cry a little knowing this is what we are now stuck with.
"stuck" ? How was your init system choice enforced ? Did you have a gun pointed at your head ? Is there absolutely no working alternative ? You don't have to use systemd. If you keep using it when there are other working systems and you don't like it, the fault is entirely yours.
Whatever the original problem was or the top link that is just not a viable solution. It is like saying "you don't have use libc, write your own". Or "Fine, Linus is a jerk, don't use the kernel, install minix but stop criticizing linux".
Let's say I follow the advice and apt-get remove systemd from Ubuntu 14.10. It doesn't look good. It takes along with it gnome-session, gvfs, nautilus, network-manager, pulseaudio, ubunt-desktop, softare-center, update-manager, update-notifier and others. Have you tried doing, maybe I am doing something wrong and there is a easier way to replace it.
Earlier quoted context omitted.
Wish I could get over it. But every time some random process fails to start at boot time I...well I cry a little knowing this is what we are now stuck with.
With all of the valid criticisms of systemd, you've chosen an imaginary one. Systemd provides better process handling and failure reporting than the initscripts it replaces (and mostly better than upstart, as well).
I guess I can explain my 'imaginary' problems a bit. Like normal people, I had several random things thrown in rc.local(set drive power settings,disable blue tooth on laptops, set raid sync rates,ect).
The first issue was, systemd never even executed this file. I had to go do random googling just to get it to execute.
After that, it was hit or miss on whether everything within the file would even get successfully executed. I'm guessing because some dependencies or modules aren't loaded yet, which shouldn't matter since rc.local is normally ran last. Sure, I could take each individual command and make its own init file which is what systemd docs recommend over rc.local. But seriously, why should I have to go to that length to fix something that has been working fine for 15 years?
Earlier quoted context omitted.
Wish I could get over it. But every time some random process fails to start at boot time I...well I cry a little knowing this is what we are now stuck with.
"stuck" ? How was your init system choice enforced ? Did you have a gun pointed at your head ? Is there absolutely no working alternative ? You don't have to use systemd. If you keep using it when there are other working systems and you don't like it, the fault is entirely yours.
Earlier quoted context omitted.
Wish I could get over it. But every time some random process fails to start at boot time I...well I cry a little knowing this is what we are now stuck with.
With all of the valid criticisms of systemd, you've chosen an imaginary one. Systemd provides better process handling and failure reporting than the initscripts it replaces (and mostly better than upstart, as well).
I've very little to criticise it as an init system... My criticism falls more towards the issues of "why is this all in one process not task specific child processes launched by a core init process" and "why can't you make this work on BSD" and "why the f%*^# hell are you building kdbus... Please stop killing the kittens"
It's time for this crap to stop. systemd haters have gone Too Far. Get over it. It's childish and pathetic now. Death threats to the creator. Personal attacks to volunteers. You have carried a debate into the extreme to where it is no longer noble. Just leave. Just stop. You are not welcome anymore in the community.
I don't have a horse in this race, but isn't it a good idea to as they say: 'don't give them a reason to hate you'. From what I've seen the good intentions behind systemd were marred by the fact that when it was announced the (mostly skeptical) responses to it were met by systemd supporters who held the attitude 'we're saving nix, join us or nix dies', and this has created the current atmosphere of debate. While thes…
I can see that systemd as a piece of software has many benefits. However, as a software project, the attitude as you mention, is a major problem. In my one single minor interaction with systemd people, I already agree with this criticism:
"My experiences with systemd's Debian maintainers (and, indirectly, systemd's upstream) have been far from satisfactory in this regard. Instead of taking a flexible approach, and being willing to provide a range of glue facilities and approaches for different daemon upstreams, the systemd community seems doctrinaire. Daemon authors are expected to do as they are told by systemd upstream, rather than systemd upstream making things comfortable for daemon developers.
This is IMO the opposite of the proper attitude."
(from https://lists.debian.org/debian-ctte/2013/12/msg00182.html)
This counts as a "technical reason". Though not directly about the software itself, a project with such an attitude should not be relied on because the people in control do not have your best interests in the long run.
Earlier quoted context omitted.
The problem is that the decent people who dislike systemd don't deserve that criticism, and the deranged people who issue death threats will ignore it.
Same issue as #GamerGate in that game "journalism" really is completely broken but now you can't talk about that without being lumped in with a bunch of vocal minority crazed misogynists.