well...too sad ! SYSTEMD

Attached Thumbnails

 

I know.. I can't figure it out either.. our only hope is they are sucker punching M$/NSA.. into *thinking* this is going to be law.

I'm already seeing work arounds.. and lets face it, there are 7 billion of *us* and relatively few of the *them*.

Your news is late , it was made part of the standard install a couple months ago .

I do not understand why switching to systemd is a disgrace. No one forces you to switch (unless it is some package dependency, eg policykit), so you can stay to sysvinit if you wish.

Personaly, and having made the switch, I can not say things were easy, but they could be worse. And I can name at least 2 situations that made me upset...
I even made the switch to grub2 after the one to systemd and it bugs me more on some things.

I don't understandwhy it's so upsetting myself?
My system boots in 2mins., while wins takes about 4mins.
But, when I shutdown it's a few secs.
The only prob I had was having to move /usr back to /.

Today I had a breakthru after reading this post I went backt to my system & figured out why it took 2mins to boot.
For some reason there was another entry in my fstab for swap, I commented out the additional swap & it took 53secs to login screen &with slow typing password made a total of 1min 6secs to desktop.
To me that is cool enough.
That's systemd for you, I'm not at all mad.

I had my Debian computer, which ran in succession Lenny, Squeeze, Wheezy, and Sid through a succession of successful dist-upgrades over four years, happily configured to boot to the command line, the way Bob intended. When Systemd infected Sid, it mucked up my nice little configuration.

Even after I made changes to my sysv-rc-conf configuration to boot to a GDM and removed sysv-rc-conf, it would boot to the command line (the way Bob intended). Once I logged it, it would start the Gnome Display Manager, and I would have to log in again.

That machine is now running Slackware --Current.

I know this is my own problem, but I want my computers to do what I want them to do, not what some arrogant Red Hat employee wants them to do.

I do really like Debian, but I think they got this one wrong.

4 members found this post helpful.

Folks...always can use OpenRC...

https://wiki.debian.org/OpenRC

https://wiki.archlinux.org/index.php/OpenRC

http://wiki.gentoo.org/wiki/OpenRC

...

What stopped you from removing GDM and all accessibility packages?

This isn't even systemd related.
Orca is the default accessibility package for all debian "default" desktops and their login managers (note that defaults are important here).

I'm still booting in my prettified CLI (as bob intended, bob never had any accessibility issues though)

1 members found this post helpful.

I like systemd (big leap forward in my very personal opinion).
One of the things that made me switch to systemd is the huge amount of unhealthy, aggressive and utterly pointless anti systemd/Lennart topics, ... like this one.

Thank you for helping me switch to systemd

I'd change 'Fedora' for Red Hat !!!

btw nice taste

The dream of many including mine!

OK, you seem to dislike systemd.
But how should I read the disgrace in the screenshot you have posted? What exactly is wrong?

I am not sure yet whether I like or dislike systemd. I am still running Wheezy. But last weekend my son installed Jessie and dist-upgraded to Sid. When he had problems with X I helped him out -- and discovered his system was running systemd. So I looked up a wiki page and did whatever I had to do. Yes, right you have to use a tool to see if a service did start.

I am not in favor of making things more complicated. I dislike the automated Xorg.conf, can grab udev, hate Grub2. And I like /etc/init.d/foo start. But on the other hand the Debian maintainers are an order of magnitude smarter than I am, so ...

And again, please explain what is so terrible about the screenshot you posted.

jlinkels

The system also includes startpar, I didn't notice until yesterday

This threads about NOT wanting systemD, and how to work without it.

However this thread is now under threat, obviously by Microsoft, US Federal Government, and other assorted systemD supporters.

People should stop responding to these 'pro-systemD' posts, since there is voluminous information on why old school Unix dudes, including Linus, are either dead set against what this cancer is doing, or on the verge of neutering it.

Can you point me to a link where Linus is 'dead set against' or 'on the verge of neutering' systemd?