Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
|
01-27-2014, 01:56 PM
|
#1
|
Senior Member
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727
|
Looks like the missing SystemD support WILL BE a showstopper for using X.org 1.16...
Read and cry, my fellow die-hard Slackers!
http://lists.x.org/archives/xorg-dev...ry/040117.html
The response at question "WTF is that patch about?": X.org's DBUS is dead (i.e. kiss goodbye to plug and play mouses and keyboards), long live X.org's SystemD!*
My bet is on that SystemD support will arrive on X.org server version 1.16, which will be released on this summer...
BTW, I said that KDBUS (yep! you are right! It's about SystemD's D-BUS, at the kernel level) patches now wait on the Kernel.org RFCs?
----
* That is the sincere opinion of Hans de Goede, the patch author...
Last edited by Darth Vader; 01-27-2014 at 02:07 PM.
|
|
|
01-27-2014, 02:07 PM
|
#2
|
LQ Guru
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 11,351
|
It's a pull request. It hasn't been accepted yet.
As a rule, if the source of your news is a developer mailing list post, then it was reported prematurely. There have never been any exceptions, and there never will be. This is also one reason Phoronix is worse than useless.
Last edited by dugan; 01-27-2014 at 02:10 PM.
|
|
|
01-27-2014, 02:10 PM
|
#3
|
Senior Member
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727
Original Poster
|
Quote:
Originally Posted by dugan
It's a pull request. It hasn't been accepted yet.
|
Not yet, my friend, not yet...
But, I'm afraid that it hasn't been accepted yet, but will be...
My reason is that, now, how UDEV is just a part of SystemD, direct communication with the UDEV devices via SystemD, will be an appealing solution for X.org developers, also offering support for the "modern" authentication method.
Last edited by Darth Vader; 01-27-2014 at 02:16 PM.
|
|
|
01-27-2014, 02:59 PM
|
#4
|
Member
Registered: Aug 2012
Location: Ontario, Canada
Distribution: Slackware 14.2, LFS-current, NetBSD 6.1.3, OpenIndiana
Posts: 319
Rep:
|
Quote:
Originally Posted by Darth Vader
Not yet, my friend, not yet...
But, I'm afraid that it hasn't been accepted yet, but will be...
My reason is that, now, how UDEV is just a part of SystemD, direct communication with the UDEV devices via SystemD, will be an appealing solution for X.org developers, also offering support for the "modern" authentication method.
|
I think it's forky Mcfork fork time, I'm not letting that thing any where my X server, I don't care if I have to use free86 as a starting point and fix all those issues, atleast it won't be infected with that turd systemd.
|
|
2 members found this post helpful.
|
01-27-2014, 03:00 PM
|
#5
|
Member
Registered: Apr 2009
Distribution: Slackware
Posts: 543
Rep:
|
It's a virus! And a very arrogant one...
|
|
3 members found this post helpful.
|
01-27-2014, 03:09 PM
|
#6
|
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559
|
Please...
When you want to spread FUD, at least make sure you're backed up with facts otherwise it's just... FUD.
Let's read the commit message which accompanies the "config: drop the dbus API":
Code:
config: drop the dbus API
This API has been disabled by default since 1.4, the first release it came in.
There a no known users of it and even its direct replacement (HAL) has been superseeded by udev on supported platforms since 1.8.
This code is untested, probably hasn't been compiled in years and should not be shipped.
What was removed? Old unused code. Good for them!
Eric
Last edited by Alien Bob; 01-27-2014 at 03:51 PM.
|
|
13 members found this post helpful.
|
01-27-2014, 03:21 PM
|
#7
|
LQ Addict
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,257
Rep:
|
Only PV decides what's in Slackware anyway, so personally I'll just wait and see. I don't feel the need to worry about an event of which I don't know if it it will occur and when, especially if I have no way to prevent it nor to forecast its consequences
|
|
5 members found this post helpful.
|
01-27-2014, 03:47 PM
|
#8
|
Member
Registered: Aug 2012
Posts: 484
Rep:
|
After a lightning review of the patch-set, it appears an entirely optional (--enable-systemd-logind) layer. I then confirmed this by chatting with an Xorg dev.
Let's not forget Xorg still has to support non-systemd Linux, Solaris, BSDs, and others, so a hard dependency on systemd seems quite unlikely.
--mancha
|
|
8 members found this post helpful.
|
01-27-2014, 03:53 PM
|
#9
|
LQ Guru
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,564
|
Xorg can't remove dbus support or they'll destroy compatibility and piss off the entire Branded UNIX community that sponsors and financially supports most of their developments.
HP, Oracle, VMware and various other sponsors all heavily fund xorg to give proper x11 implementations. It'd be a shame to have all that funding dry up and force another fork of x11 over yet another bad decision. Plus if that funding dries up, then that would effectively kill wayland which is their biggest pending project.
If Xorg goes down, there's no tell who would pick up development, but for example if Oracle took over, chances are anything could happen, and who knows what could become of future UNIX, BSD, and Linux x11 related developments.
Quote:
Originally Posted by /dev/random
I think it's forky Mcfork fork time, I'm not letting that thing any where my X server, I don't care if I have to use free86 as a starting point and fix all those issues, atleast it won't be infected with that turd systemd.
|
I'd just take the existing code, clean out all the garbage, fix security issues, and relicense it in such a way that you become BDFL of the project, if possible.
Last edited by ReaperX7; 01-27-2014 at 04:09 PM.
|
|
|
01-27-2014, 04:11 PM
|
#10
|
Member
Registered: Aug 2012
Location: Ontario, Canada
Distribution: Slackware 14.2, LFS-current, NetBSD 6.1.3, OpenIndiana
Posts: 319
Rep:
|
Quote:
Originally Posted by mancha
After a lightning review of the patch-set, it appears an entirely optional (--enable-systemd-logind) layer. I then confirmed this by chatting with an Xorg dev.
Let's not forget Xorg still has to support non-systemd Linux, Solaris, BSDs, and others, so a hard dependency on systemd seems quite unlikely.
--mancha
|
Question is for how long? I have been around for a while and even I'm starting to see things I don't like. X.org should stay away from systemd, let Wayland take the fall. Poettering has showed ignorance towards anyone who opposes his "creations", even when at a conference where he is not the guest speaker. Funny how we allow tyrants like poettering to force his creations on us, but we openly reject a murderers creation that is functional and written very well. (Hans Reiser) I don't agree for what he did, but like it or not his filesystem is hundreds of orders of magnitude better then any of Poetterings creations, Poettering makes Reiser look like a god.
Basically if your an angel in the real world you have a license to destroy Linux/UNIX's heritage, but if you did something bad in the real world your code is banished for all eternity even tho it doesn't break any fundamentals. Good call guys, if this patch makes it through I'll be reverting any systemd related code that is thrown into xorg and I will be releasing it as a fork. it's time someone says no to being force fed the "creations" (if thats what you can call them) of Poettering.
Before someone asks if I am anti-systemd YES! very much so, in fact if there were an anti-system foundation I would probly be the founder!
I agree 1000000000000000% with this article.
http://slated.org/the_poetterisation_of_gnu_linux
|
|
4 members found this post helpful.
|
01-27-2014, 04:21 PM
|
#11
|
LQ Guru
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,564
|
I'd rather be locked in a room with Hans Reiser than Lennart Poettering any day. Lennart might not make it out alive... While me and Hans have coffee and chat over file system methodology.
I honestly think more of Hans than I do Lennart, more highly and respected too. Lennart even makes dumpster scum like Bill Gates looks decent, admirable, and praiseworthy.
|
|
2 members found this post helpful.
|
01-27-2014, 04:30 PM
|
#12
|
LQ Addict
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,257
Rep:
|
As pointed out by others, "the missing SystemD support WILL NOT BE a showstopper for using X.org 1.16...".
As a consequence I'd suggest that the OP mark this thread as [SOLVED] and that anyone who wants to share his or her thoughts about systemd and/or LP does so in another thread (and preferably in another forum than this one as the quota for this kind of discussion is clearly exceeded here :-)
Last edited by Didier Spaier; 01-27-2014 at 04:36 PM.
|
|
2 members found this post helpful.
|
01-27-2014, 04:39 PM
|
#13
|
LQ Guru
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 11,351
|
This is not the first time that Darth Vader has posted unfounded alarmism. I have not forgotten his Future of KDE thread from several years ago.
Last edited by dugan; 01-27-2014 at 04:49 PM.
|
|
1 members found this post helpful.
|
01-27-2014, 04:41 PM
|
#14
|
LQ Guru
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,564
|
I think too much FUD has been generated from the upstream at times that now it's starting to ooze it's way downstream and pollute things even if not implemented. Phoronix needs to full authenticate what it releases as news, or else they could be ignored for crying wolf too much.
|
|
|
01-27-2014, 04:44 PM
|
#15
|
LQ Guru
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 11,351
|
Quote:
Originally Posted by ReaperX7
Phoronix needs to full authenticate what it releases as news, or else they could be ignored for crying wolf too much.
|
It's too late for that. If there's a single person who isn't already ignoring Phoronix for posting outright fabrications on a regular basis, then I don't want to hear about it. Phoronix was the site that claimed that MS Office was being ported to Linux, and that Blizzard would be launching a game on Linux soon.
Last edited by dugan; 01-27-2014 at 04:46 PM.
|
|
2 members found this post helpful.
|
All times are GMT -5. The time now is 12:33 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|