X.Org Server 1.16 Brings XWayland, GLAMOR, Systemd Integration 226
An anonymous reader writes The much anticipated Xorg Server 1.16 release is now available. The X.Org "Marionberry Pie" release features XWayland integration, GLAMOR support, systemd support, and many other features. XWayland support allows for legacy X11 support in Wayland environments via GL acceleration, GLAMOR provides generic 2D acceleration, non-PCI GPU device improvements, and countless other changes.
The systemd integration finally allows the X server to run without root privileges, something in the works for a very long time. The non-PCI device improvements mean System-on-a-Chip graphics will work more smoothly, auto-enumerating just like PCI graphics devices do. As covered previously, GLAMOR (the pure OpenGL acceleration backend) has seen quite a bit of improvement, and now works with Xephyr and XWayland.
Re:Systemd? Not on my system... (Score:5, Interesting)
Anyone thinking about defending systemd should read this [pappp.net].
Mod parent up.
As a primarily linux user: (Score:5, Interesting)
I can tell you I feel similiarly.
But until and unless a large percentage of the community starts coughing up money to directly pay devs otherwise, they're going to do what their corporate masters (primarily redhat, but also other tech incumbents) choose to do.
It's the same reason lots of other tech has made it into the linux kernel but taken years to a decade to make it into BSD. If the community isn't ponying up the cash to keep the development in a direction they desire, then some corporation will coopt it and pervert it into something we hate.
It's not the first nor last piece of software we'll see this happening with.
Re:What about non-Linux users? (Score:4, Interesting)
I am displeased with the trend towards all of the primarily Linux dependencies for a lot of software - GNOME 3, Wayland, X11
We had a GNOME 3 dev on here a while ago. Apparently they've been working hard to get the features of GNOME3 working without systemd.
As for X11, it also has this feature to run rootless in Windows. However, that doesn't affect me as a Linux user. I think adding integration with more systems is generally done well on Xorg.
Re:Systemd? Not on my system... (Score:2, Interesting)
Anyone thinking about defending systemd should read this [pappp.net].
Interesting read, but my "defense" of systemd is usually an "systemd could be the devil himself and you'd still sound like a paranoid asshat." I don't care if people don't want to use systemd. but shouldn't they be putting effort into collaborating on a set of remove-systemd-dependancy patches instead of bitching on the internet about the inevitable?
"An anonymous reader writes" (Score:0, Interesting)
FUCK OFF MICHAEL LARABEL
Re:Soon... (Score:4, Interesting)
ML removed the old stale obsolete Apple-branded X11.app. It did not uninstall XQuartz. And XQuartz is quite actively maintained. Does the average kid running GarageBand need it? No.
It's been an optional install from the beginning because most folks don't need X11 apps. Native mac ports of apps are much nicer most of the time and pretty easy to find. Running legacy X11 apps is not something most people need. But if the need arises, you can, and it works REALLY well. LOTS of people run command-line FOSS tools under OSX though.
Apple solved the crappy UNIX desktop environment problem. They just didn't give away the source. I don't care if software is FOSS or not however. If it's good, I'll use it. If the price is too high, there's plenty of ways around that issue that any 14-yr-old kid with a web browser can find.
Re:Systemd? Not on my system... (Score:5, Interesting)
Here's a true story. I was in a CentOS 7 system via chroot and trying to troubleshoot some problems. If it were CentOS 6 I would just run "service rsyslog start" and have syslog running in the chroot so I can get the diagnostics I was expecting, but since systemd wasn't actually running I couldn't do that. I had to launch rsyslog directly by command-line, but then it didn't listen on /dev/log like it's supposed to and I had no logging. After all, it's systemd integrated now and gets its listen socket a different way. And this is just the most recent incident.
Systemd may be technically better than sysvinit but the latter is just shell scripts which are sufficiently independent of anything else and just work. Systemd takes over your machine and wants to get its hands into everything to the point that you can't even use it anymore without systemd. This is what we're worried about what will happen to X.Org and other software.