SoylentNews is people
SoylentNews is powered by your submissions, so send in your scoop. Only 9 submissions in the queue.
SoylentNews
Debian Jesse is going to have Gnome3 as the default desktop.
The desktop re-qualification page, used to help choose which desktop will be default, has in the Jesse version a weight for systemd integration, and of course only Gnome3 does it (at least for now). This will surely make the systemd/gnome3 fanbase happy, but possibly will make others unhappy, as it [may] be seen as another step towards mono-culture, until we soon end up with all distros being redhat clones.
This discussion has been archived.
No new comments can be posted.
Integration with systemd Making Gnome3 the Default Debian Desktop
|
Log In/Create an Account
| Top
| 135 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Chess tonight.
(Score: 2, Informative) by schad on Wednesday September 24 2014, @11:46AM
Yep, that was my reaction to CentOS 7 as well. "Guess I'll run 6.x until they turn out the lights, and then migrate to... FreeBSD?"
I'm very frustrated by the current Linux server situation. If you want a server OS -- something that you can use on a couple hundred production servers -- you're pretty much shit out of luck right now. RHEL/CentOS, Ubuntu, Debian, SLES... all going, or already gone, systemd. Because those are all supported for a really long time we have a few years left. But just because they're getting patches, that doesn't mean they'll be getting new versions of software. And because so many developers and managers are brainless children obsessed with the latest and "greatest," it's going to be increasingly difficult to make those servers actually work while keeping them in a supported and supportable configuration.
It's so fucking infuriating. You know, you read the defenses of systemd. The real ones, the ones saying things like: "It's just too clumsy and unreliable to handle hardware connects/disconnects with SysV init." And that's a fair point. I can see why that could be a problem. But servers don't do any of that shit. They are configured at installation time and then not touched. Or, to be more precise, there is considerable process and procedure around how servers may be touched, and when, and who can do it, and so on. For a server, there is no use for systemd. None! It confers absolutely no advantages. Fuck, when we add a LUN to a server at work, we reboot the box even though we don't have to. It'll usually have been up for a couple hundred days by that point, so we take it as an opportunity to install kernel updates and make sure that everything that's supposed to start automatically does. And even on those occasions when we want to plug in some kind of external drive, we don't use USB. We use a NAS and plug it into one of the unused onboard NICs. (In practice, NFS over gigabit ethernet is usually faster and more reliable than direct-attached USB 3.0.)
Well, the nice thing about OSS is that if there's really a market for a truly server-only OS -- one where GNOME and the like aren't even installable options -- then someone will make it. Or, more precisely, someone probably already has made it, and it will just become more popular.