LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


View Poll Results: When will you switch to Wayland in Slackware?
As soon as it works 7 3.24%
As soon as it's stable 26 12.04%
Not before it is included by the dev team 115 53.24%
No plans to switch 68 31.48%
Voters: 216. You may not vote on this poll

Reply
  Search this Thread
Old 07-01-2013, 06:27 AM   #31
jtsn
Member
 
Registered: Sep 2011
Posts: 925

Rep: Reputation: 483Reputation: 483Reputation: 483Reputation: 483Reputation: 483

I will consider a display server, if ports to at least two other operating systems have been demonstrated. I won't use a windowing system, which only works exclusively on Linux. What these "desktop environment" guys are doing on their playgrounds doesn't interest me, it's irrelevant for the IT industry anyway.
 
Old 07-01-2013, 06:48 AM   #32
NonNonBa
Member
 
Registered: Aug 2010
Distribution: Slackware
Posts: 192

Rep: Reputation: Disabled
The main issue will be for the users that use one of the zillion available WMs (or, in a certain extent, the Gnome 2.x/KDE 3.x heirs). They won't work with Wayland, which requires to write a composer to talk to it (it goes without saying that it's far more complex than writing a WM). Plus, whereas X, Wayland does not draw, which also means you will have to bind to a toolkit to create taskbars, window decorations, menus and so.

To simplify things, it is question to implements them as plugins for the existing composers (Weston/Kwin). But all is still to do.

Quote:
Originally Posted by bartgymnast
The bug list is relative small compared to X. (the bugs that could not be solved in X are dealt with directly during development of Wayland)
Wayland also does less things than X, which may mean the bugs will just be highter in the "graphic stack" (it's saner, but does not imply the global solution will be more stable). Plus, it does not currently run in the wide wild world, where crazy things that were not meant to happen tend to find imperious reasons to finally happen.

So, I don't claim here Wayland will fail nor that the raised problems won't find some elegant solutions, but it's IMHO too soon to discuss the opportunity of a switch.
 
Old 07-01-2013, 08:58 AM   #33
bsdunixdb
Member
 
Registered: Jun 2009
Location: London, United Kingdom
Distribution: Slackware x86_64 Stable
Posts: 70

Rep: Reputation: 35
Quote:
Originally Posted by bsdunixdb View Post
Seems to me we are going a sort of systemd route.

Xorg does for me and if it ain't broke etc.
For my first statement, I can only apologize and say that it was a knee-jerk reaction. I unreservedly withdraw said statement.

As for my second statement, I will do more research.
 
Old 07-01-2013, 10:06 AM   #34
Soderlund
Member
 
Registered: Aug 2012
Posts: 185

Rep: Reputation: 81
I assume applications built on XLib will not work in Wayland. That will be an obstacle for adoption. And people are very addicted to their window managers.

Still, Høgsberg sounds like a Norwegian or Dane, and it's well known that all things Scandinavian are good (except for surströmming and C++), so it's at least very likely that Wayland is vastly superior to X.

Vølund is also Norse for Wayland, and although I don't know how Wayland MA got its name, it's definitely etymologically related. From Völundskvädet:

Quote:
Ensam satt Völund
i Ulvdalarne,
slog guldet röda
kring glimmande sten,
alla ringarna på lindebast
lyckte han väl;
sitt väna viv
väntade han så,
i hopp, att hon skulle
till honom komma.
Sounds promising. I see Debian Wheezy already has it. At the moment I don't see a reason to replace X though.
 
Old 07-01-2013, 02:35 PM   #35
thirdm
Member
 
Registered: May 2013
Location: Massachusetts
Distribution: Slackware, NetBSD, Debian, Sourcemage, 9front
Posts: 368
Blog Entries: 2

Rep: Reputation: Disabled
Not me. When I think of Wayland I remember getting lost buzzing around between Bedford and Framington searching in vain for a route that wasn't completely traffic clogged (Thoreau must be turning over in his grave) trying to visit an ex-gf. Bad associations all around.

Aside from that, by the time it's viable I'm hoping I've finally figured out how to get OpenBSD working on this laptop. Nothing against Slackware -- it's nice too -- but that's my home O/S, and I'll eventually return to it. I don't see OpenBSD ever supporting Wayland, particularly since one of their developers is a senior X person, on the board if I recall.
 
Old 07-01-2013, 02:50 PM   #36
Timothy Miller
Moderator
 
Registered: Feb 2003
Location: Arizona, USA
Distribution: Debian, EndeavourOS, OpenSUSE, KDE Neon
Posts: 4,018
Blog Entries: 27

Rep: Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523
Quote:
Originally Posted by thirdm View Post
Aside from that, by the time it's viable I'm hoping I've finally figured out how to get OpenBSD working on this laptop. Nothing against Slackware -- it's nice too -- but that's my home O/S, and I'll eventually return to it. I don't see OpenBSD ever supporting Wayland, particularly since one of their developers is a senior X person, on the board if I recall.
Actually, that's a good reason that OpenBSD WILL *eventually* support Wayland. Wayland is being devloped by many of the same x.org developers. As discussed earlier in the thread, the developers of x.org don't see a way to fix various security issues because of how x.org is designed, so they're designing wayland as a replacement for x.org.
 
Old 07-01-2013, 03:13 PM   #37
thirdm
Member
 
Registered: May 2013
Location: Massachusetts
Distribution: Slackware, NetBSD, Debian, Sourcemage, 9front
Posts: 368
Blog Entries: 2

Rep: Reputation: Disabled
Quote:
Originally Posted by Timothy Miller View Post
Actually, that's a good reason that OpenBSD WILL *eventually* support Wayland. Wayland is being devloped by many of the same x.org developers. As discussed earlier in the thread, the developers of x.org don't see a way to fix various security issues because of how x.org is designed, so they're designing wayland as a replacement for x.org.
Well, perhaps I should not speculate. I don't know what Matthieu Herrb's mind is, exactly, on the issue. There is this paraphrase of a small portion of his Feb 2013 fosdem talk that makes it sound like it may be a long time coming (or longer, as in infinite?) and that perhaps it's a headache for him and the very few others that do X server work in OpenBSD (anyone, anyone... Bueller?):
"Wayland will also be a mess for BSD and Solaris operating systems due to its dependence on kernel mode-setting, kernel input drivers, and Weston being designed with solely Linux in mind. " http://www.phoronix.com/scan.php?pag...tem&px=MTI5Njk
 
Old 07-01-2013, 09:40 PM   #38
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
Blog Entries: 2

Rep: Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886
Quote:
Originally Posted by NonNonBa View Post
The main issue will be for the users that use one of the zillion available WMs (or, in a certain extent, the Gnome 2.x/KDE 3.x heirs). They won't work with Wayland, which requires to write a composer to talk to it (it goes without saying that it's far more complex than writing a WM). Plus, whereas X, Wayland does not draw, which also means you will have to bind to a toolkit to create taskbars, window decorations, menus and so.
They will work with XWayland, but indeed, a better way would be to write a native plugin with the same functionality.
Quote:
I assume applications built on XLib will not work in Wayland. That will be an obstacle for adoption. And people are very addicted to their window managers.
Again: XWayland.
Quote:
Plus, it does not currently run in the wide wild world, where crazy things that were not meant to happen tend to find imperious reasons to finally happen.
It is planned as an option in Fedora 20 and as default in Fedora 21. Several phones are planned with it, using Sailfish and Tizen as OS, for example the Jolla phone. So having it running in the wild is coming in the near future.
Quote:
Wayland will also be a mess for BSD and Solaris operating systems due to its dependence on kernel mode-setting,
Kernel mode-setting is coming at least to the BSDs.
Quote:
kernel input drivers,
Sorry, don't know about that.
Quote:
and Weston being designed with solely Linux in mind.
Irrelevant. Weston is only the reference implementation of a Wayland compositor and not meant to be actually used (although it is possible).
 
Old 07-01-2013, 09:42 PM   #39
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,564
Blog Entries: 15

Rep: Reputation: 2117Reputation: 2117Reputation: 2117Reputation: 2117Reputation: 2117Reputation: 2117Reputation: 2117Reputation: 2117Reputation: 2117Reputation: 2117Reputation: 2117
Wayland needs to prove itself before it should be used.

I'd suggest offering it as a /testing package ONLY. After the code has been stabilized for at least a 6-12 months time frame following the initial release date for adequate testing. This way the developers have worked out the bugs, security issues, etc.

I don't see Wayland taking over for X.Org for some time until all the UNICES out there can get a full port of Wayland created and stabilized. With Weston being possibly Linux only, chances are X.Org could be still co-developed alongside Wayland until Weston gets a successful port, clone, or ability to be commented out in favor of a BSD friendly compositor that is Wayland friendly, which remains to be seen.

Last edited by ReaperX7; 07-01-2013 at 09:44 PM.
 
Old 07-02-2013, 03:22 AM   #40
NonNonBa
Member
 
Registered: Aug 2010
Distribution: Slackware
Posts: 192

Rep: Reputation: Disabled
Quote:
Originally Posted by TobiSGD
They will work with XWayland, but indeed, a better way would be to write a native plugin with the same functionality.
They won't. X applications like xterm will work, because each will run in its own Xserver where it will fit the root window. It's explained there (§VI).

A WM is an application which filters the events between the X server and the root window's children (which means all the windows the different applications create in the same X session). So, the only thing you can expect with XWayland is an Xserver running a WM with nothing to manage. The window management in Wayland can't be anything but a component of a compositor.
 
Old 07-02-2013, 03:30 AM   #41
bartgymnast
Member
 
Registered: Feb 2003
Location: Almere, Netherlands
Distribution: slack 7.1 till latest and -current, LFS
Posts: 368

Rep: Reputation: 165Reputation: 165
Quote:
Originally Posted by ReaperX7 View Post
Wayland needs to prove itself before it should be used.

I'd suggest offering it as a /testing package ONLY. After the code has been stabilized for at least a 6-12 months time frame following the initial release date for adequate testing. This way the developers have worked out the bugs, security issues, etc.

I don't see Wayland taking over for X.Org for some time until all the UNICES out there can get a full port of Wayland created and stabilized. With Weston being possibly Linux only, chances are X.Org could be still co-developed alongside Wayland until Weston gets a successful port, clone, or ability to be commented out in favor of a BSD friendly compositor that is Wayland friendly, which remains to be seen.
There are currently 2 major components in active development that is changing the whole DE's.
Wayland in combination with systemd is very powerfull for the desktop experience, and would bring linux desktops closer to apple and microsoft desktops in the way of user experience.

Both these components are still in their child shoes (wayland being more mature imo)
Both these components are developed with different parts of the system.
Kernel additions, glibc changes, dbus changes, probably alot more.

When it comes to BSD, they are just saying it doesn't work on BSD.
Instead they should be working with wayland to make this work.
Also systemd is here an option, as they have their own kernel the can work with the devs of systemd to make this work.

PS. I see systemd having only benefits in a desktop enviremont at the moment.
wayland can be used also as a remote desktop server. (No more seperate VT's for each user)
 
Old 07-02-2013, 11:32 AM   #42
jtsn
Member
 
Registered: Sep 2011
Posts: 925

Rep: Reputation: 483Reputation: 483Reputation: 483Reputation: 483Reputation: 483
Quote:
Originally Posted by bartgymnast View Post
Wayland in combination with systemd is very powerfull for the desktop experience, and would bring linux desktops closer to apple and microsoft desktops in the way of user experience.
Hey, I didn't choose Slackware to have the worse Apple and Microsoft "user experience".
 
5 members found this post helpful.
Old 07-02-2013, 12:52 PM   #43
thirdm
Member
 
Registered: May 2013
Location: Massachusetts
Distribution: Slackware, NetBSD, Debian, Sourcemage, 9front
Posts: 368
Blog Entries: 2

Rep: Reputation: Disabled
Quote:
Originally Posted by bartgymnast View Post
There are currently 2 major components in active development that is changing the whole DE's.
When it comes to BSD, they are just saying it doesn't work on BSD.
Instead they should be working with wayland to make this work.
Also systemd is here an option, as they have their own kernel the can work with the devs of systemd to make this work.
Does wayland need to be everywhere? At least on OpenBSD mailing lists, I've never seen any sign of anyone with plans to work on wayland support. The people doing real work there already have long TODO lists, I suspect. If the toolkits support both Wayland and X11, is there a need for BSD application porters to care about what's going on in the GNU/Linux display server world?
 
Old 07-02-2013, 02:47 PM   #44
zsd
Member
 
Registered: Dec 2005
Location: Nova Scotia
Distribution: Slackware
Posts: 97

Rep: Reputation: 57
Quote:
Originally Posted by jtsn View Post
Hey, I didn't choose Slackware to have the worse Apple and Microsoft "user experience".
Well said. Whenever someone says something about wanting the M$ or OS-X gui experience, I have no idea what they are wanting, unless it is (useless to my needs) eye candy.

Last edited by zsd; 07-03-2013 at 07:05 AM.
 
Old 07-02-2013, 03:24 PM   #45
ttk
Senior Member
 
Registered: May 2012
Location: Sebastopol, CA
Distribution: Slackware64
Posts: 1,038
Blog Entries: 27

Rep: Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484
I second this sentiment, and then some. Every time I've had to touch a windows machine at work, or my wife's Macbook at home, it really impresses upon me that X11-based UI is more sophisticated, and more powerful.

Compare and contrast copy-and-pasting text segments from an almost-screen-sized window to another window:

Under Windows or MacOSX, the source window's text is not always selectable (also true under X11, but less frequently), the destination window is not always capable of taking the paste, the destination window has to be brought to the foreground for the paste to happen, and sent back to the background to make the source window entirely visible again, and highlighting text is insufficient to actually copy the text (a control-key sequence is necessary, or clicking on a menu).

Under X11, the destination window remains behind the source window, and it's just left-button to copy + middle-button to paste. zip zip zip, all done.

I know there are WM's which emulate the click-to-focus behavior of Windows and MacOSX, but these are broken. Do not use them.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Wayland - Beyond X LXer Syndicated Linux News 1 02-14-2012 01:59 PM
Future !X ? Wayland : X - what is wayland? serafean Linux - General 5 03-04-2011 12:09 PM
Iptables + Forwarding + Vlan + OpenVPN & L2 junk switch /L3 extreme networks switch feloniousj Linux - Networking 3 03-15-2010 10:27 PM
thread switch results in kernel stack switch superstition Linux - General 1 05-18-2005 12:48 AM
set up DSL thru SWITCH - winXp connected to SWITCH too husz Linux - Newbie 5 04-22-2004 01:08 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:28 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration