Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re:Pure Insanity (Score 1) 924

Changes like this make me wonder if the systemd developers even use Linux beyond their local development workstations ... cut (various "not how UNIX works)" cut ...

Ahhh yes, the common response, that systemd is for desktops. Sigh, for those in Red Hat who saw customers deploy Cluster Suite just to monitor services *and*, more importantly, resources (something Upstart doesn't do) for standalone, single system services, systemd does far, far more for servers than desktops. This is yet another. Customers not only desired systemd, but even the Debian vote exposed how many *major* (thousands of servers) Debian userbases wanted it too.

As someone who has extensive experience with LTSP and RHEV VDI, this was a long, requested change. Because multiuser environments absolutely need this. But ignorance is most common, especially those who haven't worked in 10,000 user Linux VDI environments, which is why get these types of responses. Same goes for the prior on PulseAudio, when the issue usually wasn't PulseAudio, but Ubuntu -- especially off-shoot, non GNOME/Unity Ubuntu -- integration issues.

As far as "how UNIX works," people should really change that to "how BSD works." Virtually all other UNIX implementations *do* have something with many systemd features and approaches.

Slashdot Top Deals

If this is a service economy, why is the service so bad?