I agree with Gilbert,
Coming from centos 6 to 7, at first I was whoa, but after seeing how fast it booted I loved it.
Centos 6 started every thing sequentially, you had to wait one by one.
With systemd you tell your programs what to wait for, once that thing is started everything that was waiting for it gets started in parallel. My boots went from minutes to seconds always under a minute.
As for chrony and firewalld I went back to NTP because my system is always on, and iptables because I use QoS on my network connection
Why are users opposed to systemd? I personally like it.
I am a CentOS user and there was a big jump for me when moving from 6.x to 7.x with only one of those components being systemd. It was not systemd that made the transition difficult, but app changes (NTP, FIREWALL, etc) which were the problem. I not only had to learn systemd so I could start the apps, but had to learn how to program Firewalld and their new ntp program Chrony. I really believe that systemd is progress and makes things simpler to automate startup.
Gilbert
On 10/22/2015 10:42 AM, kitepilot@kitepilot.com wrote:
OK, I get it, I don't want systemd either.
So seems to feel most everyone.
But it looks like (sigh...) systemd is here to stay.
In 5 lines, what is it that I don't see?
Why are all the distros systemd(ing) disregarding the opposition?
What am I missing... :(
ET
Steve Litt writes:
On Wed, 21 Oct 2015 14:36:57 -0700---------------------------------------------------
Matt Graham <mhgraham@crow202.org> wrote:
On 2015-10-21 12:05, Steve Litt wrote:
> I recently switched over to Void Linux, a KISS principle distro much
> closer to Slack than to Ubuntu, but with an oustanding, full
> dependency handling package manager. So far, I really like it.
> I've put together a bunch of tips for installing and using Void, so
> that the next guy has an easier time than I did:
> http://troubleshooters.com/linux/void/voidtips.htm
Interesting. I guess this could be another alternative to the
creeping "systemd is everywhere" thing.
Yes. For those who prioritize keeping systemd off their machine, Void
is one of the few distros (along with Funtoo and Devuan and maybe
Slackware) who have stated unequivocally that they won't use systemd as
PID1 in the future. I've even heard various people in talking about
bringing systemd or a systemd like thing into FreeBSD.
It's also a nice place for people who don't like sysvinit. Every
program that could be used as a daemon installs a runit directory,
under /etc/sv, containing a tiny conf script (usually about 4 lines) and
a tiny run script (usually about 4 to 8 lines). Symlink that directory
to a same-named directory within /run/runit/runsvdir/current/ and the
daemon starts, and you're able to manage it with the sv command.
SteveT
Steve Litt October 2015 featured book: Thriving in Tough Times
http://www.troubleshooters.com/thrive
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss