I think we should have another argument over systemd we haven't had one in a while.
|
Quote:
|
Replying to the original post - as the OP has not responded since:
Quote:
The comment is just opinion from someone who is most likely not in full possession of the facts. Quote:
Quote:
|
Quote:
|
Quote:
Before this fiasco, projects were going along at a steady pace and developing things without any standard par to aim for. Things were ready and done, when they were ready and done. Since systemd came along, everything that was abandoned for systemd was either forked out, redeveloped, or fresh starts were made, some which made it, some which are ongoing, and some that faltered, but development had to be ramped up to get on par with systemd or be left behind, but there was no excuse that all of this could have been avoided in the first place by not trying to drag anything and everything into systemd trying to force, coerce, and bully users, administrators, and system developers into a single locked in and locked down system they'd have little to no control over. If the shoe fits, then yes, they are completely responsible for creating this mess. If they didn't want to be held responsible for their actions, they shouldn't have attempted this crap in the first place, but no, they have too many people trying to make up excuses for them to put the blame on everyone but them. |
Quote:
wow, this thread has grown so fast - once again :rolleyes: |
i havent really commented on anything...as i know very little...just reading comments here. i am a total newb who completed linux+ earlier thus year and have moved onto Red Hat certification...
i guess we/i will be stuck with systemd for some time...and its in the course the next question is how much should you know? can anybody give me some key points on things i should be learning to do with systemd...i know its to stop and start services etc...but i know it can do a heck of a lot more...from what i read its moved from being an init system to handle more management roles...correct? and from what i read systemctl is a very popular command with systemd...some exercises would be great... i dont even know what logind is...will do some reading thanks |
What is vdev?
Don't tell me its a "son of udev"! If udev ever fails me I wouldn't have a hope of fixing it - its monolithic, but not as monolithic as systemd.:rolleyes: |
Quote:
|
There is no systemd in my boxes.
Code:
~ $ equery u sys-apps/dbus |
Quote:
|
Quote:
|
Quote:
Then you have specialized stuff like timedatectl for setting the clock/date and timezones or machinectl for handling virtual machines, containers and sessions. What you learn is up to you, if you don't have a need for virtual machines or containers than their is not much sense in learning how to use machinectl, for example. In the end, if you really need something that you don't know about yet, all the info is only one manpage away. Regarding logind, you shouldn't need to care a lot about that, have a look at the configuration in /etc/systemd/logind.conf if you want (you can for example set up the number of TTYs you want to get on boot or set actions that should be run when pressing the power management keys on your keyboard), but mostly it is just used by display managers and you don't have to care. |
Quote:
|
Quote:
Quote:
Better question, where did all the loudmouth hipsters go recently who were spouting systemd this and systemd that? Answer, they'll all using Windows 10 trying to make it a trendy thing, saying it's cool, and trash talking anything but Windows 10 is the best OS ever. |
All times are GMT -5. The time now is 04:32 PM. |