BTW: This is an example of the philosophical difference between FreeBSD and Linux. Linux distributions lost the KISS principle. It really hurts to have a server system with a multitude of "to difficult to explain, to difficult to understand, just trust me" services running. It is not reliable and it is not safe because the admin looses the ability to understand what's going on - and the system is never just as complex as necessary. My servers do not need a lid closed, don't scan for wireless, don't wait for a USB stick coming in.. simply said: I do not need event-driven hardware management. They also do not boot five times the day. If I need it, there could be tools to _replace_ parts of it to serve _another_ purpose (e.g. your laptop). Fine. But instead Linux went the way of having tools designed for GUI, reoccurring boots and laptop users now running on every server in this universe. What is the share of desktops running Linux/Gnome? 2 or 3 percent. What is the share of servers running Linux? More than 50 percent in some areas I guess. How many of them need polkit/systemd/dbus/NetworkManager..? None. This is simply not explainable by stupidity anymore.. Who has interest in complex and therefor unsafe Internet servers, embedded systems etc..? Regards Peter On Thu, Aug 6, 2015 at 11:45 AM, Tim Connors <tim.w.connors@gmail.com> wrote:
On Wed, 5 Aug 2015, Rick Moen wrote:
Quoting Andrew McGlashan (andrew.mcglashan@affinityvision.com.au):
I am convinced, systemd want to control everything, including power doesn't it?
Nah, upower wants to control power.
PolKit wants to control process permissions. systemd-logind wants to control login and 'seat' access to consoles. D-Bus wants to control chatter among processes. udisks2 wants to control access to storage. pm-utils and HAL want to control suspend/resume.
And all of them want to convince you that all the others are essential because they're all part of the Freedesktop.org stack. But they won't hurt you if you don't believe in them.
Won't hurt? Getting a laptop to do any action upon lid close used to be so easy - pop a script in /etc/acpi somewhere. Power removed and want to spin the HD down more aggressively? Trivial!
But then some idiots came along, who though gnome was the entire world, and now it's impossible to not get it to stomp on your feet when you want to tell suspend-on-lid-close to fsck right off to where it belongs.
-- Tim Connors _______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main