On 12/02/2014 06:47 AM, Paul W. Frields wrote:
On Tue, Dec 02, 2014 at 09:40:53AM +0100, Lars E. Pettersson wrote:
On 12/02/14 02:45, Rahul Sundaram wrote:
Well, it was originally meant to be default in Fedora 14 and there were
many discussions about it. it is been years since that point. Perhaps
people didn't pay attention to it and didn't realize it but it wasn't
snuck in when people weren't looking. There were literally hundreds of
mails on the subject before it become default.
Well, to be frank, it was sold to solve the issue of start up time of
computers. It has then evolved to almost transfer the GNU/Linux concept to
systemd/Linux. And this is something that has to be addressed, even on on a
users list. Users use Fedora too, you know :) and might have usable (users)
views on the subject.
This is incorrect. The actual problems systemd was meant to solve
include but are not limited to:
* Properly sorting dependencies of services
Well, they sure missed on that one. If anything, this has become a real
quagmire with systemd.
* Simplifying startup configuration
Simplifying startup? What an utter and complete misread. Startup is
INCREDIBLY more complex now. Over 6MB of config files in four or five
directories scattered all over hell and gone? They call that simplifying
startup configs? Really?
Just try to sort out a frozen boot sometime. You have NO idea what the
hell's going on because there are multiple processes running and
there's no way to tell what's locked up. On top of that, journalctl
stuffs everything useful into a bloody database so it's difficult to see
what's what. We used to be able to boot to single user mode and look
at the logs. Not anymore. Sheesh!
* Allowing arbitrary levels of startup
I might allow this, but was there really any need to do this? That's
what rc.local was for.
* Allowing sysadmins more control over resource utilization
I really fail to see how that's the case. If anything, this
parallelization crud uses MORE resources, not less.
The fact that the parallelization in systemd permits faster startup
time was a side benefit.
And a piss-poor benefit. If you're rebooting so often that this is a
problem, then you have other issues that need sorting before dealing
with this perceived bottleneck.
<soap>
I've said this before and I will continue to say it: systemd (and
journalctl's horrible abomination of stuffing logs into databases) are
solutions to problems that never existed. They are unnecessarily
complex, fraught with race conditions and dependency issues, resource
hogs, and just really, really stupid ideas in general. It appears that
the people who have forced these beasties on us are all ex-government
officials ("We know what's best for you...you're too stupid to deal
with it.")
</soap>
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
- -
- IGNORE that man behind the keyboard! -
- - The Wizard of OS -
----------------------------------------------------------------------
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
