Well, FreeBSD's telnet also has security features (it supports Kerberos authentication and encryption). On the other hand, ssh provides many more features. For example, automated authentication, port forwarding, tunneling, connection sharing, working through proxies and so on. I haven't used telnet in this century. Even the typical use of telnet to check ports and debug protocols (e.g. telnet to port 25 for SMTP) works better with tools like netcat instead of telnet.And some still use telnet today, on environments where the added security features of ssh would not make any difference.
Please excuse me, but that's nonsense. In 1990, I started using X11 on various UNIX platforms (Sun, DEC, IBM), and it worked perfectly well. At that time, X was already 6 years old.It took about 10 years of experience for X to start to work.
nicely said, but it does not work on the latestNo, the old X protocol is going to die, sooner or later (hopefully sooner). It is 35 years old and was designed at a time when people didn't think much about security issues. Wayland fixes that and a bunch of other problems.
And please stop abusing this thread for your “BSD vs Linux” mission. As already stated, Wayland is an OS-independent display protocol.
I am fairly surprised to not see a libX11 "wrapper library" around Wayland.I hope, at least, that my favourite FVWM will somehow be ported. I've found a 2014 dated article about porting Motif to Wayland, but no traces of it dated by any later date... Anyway.
I'm sure there WAS (and probably still IS) such "layer". I used Ubuntu recently, up to 16.04, and it had this Wayland compatibility layer allowing to run X11-linked apps. But I must check with my Ubuntu installation that was upgraded recently.I am fairly surprised to not see a libX11 "wrapper library" around Wayland.
But then since Wayland does not have a united approach (it is really just a scatty band of separate non-standard compositor projects), it doesn't have a single underlying library. The closest is maybe wlroots but again, that is fairly non-standard.
Once Wayland gets serious and matures (or dies) and a library such as this appears, I am fairly sure we will see Motif, Gtk2 come fairly quick. Fvwm will also be great to see but since they have to develop an entire compositor (a window manager + 1/4 of Xorg), it might be a complex project.
Either way, most of the FOSS world is in limbo over waiting for Wayland. Innovation has completely stagnated whilst less than 7% actually use Wayland (Gnome/Sway) vs Xorg.
There is “XWayland” which acts as an X11 server that uses a Wayland compositor as its display backend. It allows traditional X11 clients to be displayed on a Wayland compositor. You can think of it as some kind of an X11-to-Wayland proxy.I'm sure there WAS (and probably still IS) such "layer". I used Ubuntu recently, up to 16.04, and it had this Wayland compatibility layer allowing to run X11-linked apps. But I must check with my Ubuntu installation that was upgraded recently.
In the same way that Xming is the way to go for X11 apps. If you have the choice, you should use the superior native technology. That is Xorg on FreeBSD.So then, Xwayland is the way to go for X11 apps?
No no, I'm talking about the hypothetical future where Xorg has been dropped and things not ported to Wayland.In the same way that Xming is the way to go for X11 apps. If you have the choice, you should use the superior native technology. That is Xorg on FreeBSD.
That is, unless of course you plan to run Wayland apps? Which ones are you interested in particular? I don't believe there are any.
The short answer is no. Wayland is limited in scope and individual compositors are very rough anyway.I still don't know what is Wayland in details and have one main question: Is it possible to run remote GUI applications with Wayland in the same way like Xorg? I.e. app running on server and open windows on X client with network transfer of GUI commands like "draw line" or "fill area". Not like TeamViewer or other tools for Windows where a whole screen/window is transmitted as bitmap.
Reaction score: 426
Step by step collecting all knobs and switches one needs to know. Thanks
It is basically libinput what trickles in first, causing a lot of people havingIn the 'latest' repository, the wayland option has been enabled by default since November. It will be the default in the upcoming quarterly update. It's only a 1Mb package, so not a big deal.
This also needs to be investigated.By the way, even if you unset the WAYLAND option when building ports, you will still get libinput because it is the default input driver for X.org on FreeBSD >= 12. Only on FreeBSD <= 11 the old legacy drivers are used (xf86-input-keyboard and xf86-input-mouse).
Actually, most of today’s X11 applications don’t use X11 protocol commands like “draw line” or “fill area” anymore. For example, when a web browser renders aI still don't know what is Wayland in details and have one main question: Is it possible to run remote GUI applications with Wayland in the same way like Xorg? I.e. app running on server and open windows on X client with network transfer of GUI commands like "draw line" or "fill area". Not like TeamViewer or other tools for Windows where a whole screen/window is transmitted as bitmap.
<HR>tag (for a horizontal rule on a web page), it draws that line itself and transfers the page as an image to the server.
It’s not specific for web browsers. Almost all X11 applications that I use do it exactly like that (various browsers, GIMP, InkScape, Scribus, mplayer, and others). The “old” X11 protocol commands are mostly not used anymore today; basically they only still exist so the X server passes the conformance test suite.I guess this is specific for web browser. It cannot predict how complex is a web page and prefer to render it locally and send it as image.