12 ms·
Xorg doesn't really need a configuration file today; it's good at auto detecting hardware. But one of the things I really like about X is that you can have a co
by djsumdog 10y ago
Xorg doesn't really need a configuration file today; it's good at auto detecting hardware. But one of the things I really like about X is that you can have a config file and specify exactly which devices you want. In this way, you can connect two keyboards, two mice and two video cards to the same machine and have two totally different login screens. You can essentially have two people logged into the same machine as if they were using two different terminals (just do try to plug in a USB device if both users have automounters running).
Even on my current single user machine, I still run multiple X servers (one for my work related stuff and one for non-work. I work remotely so that way, I can just switch X servers at the end of the business day).
Can Wayland support multiple terminals on a single machine in the same way? Can you have two Wayland instances running like you can with X servers?
- stemc43 10y agoWith Wayland I can finally dock & undock my thinkpad without having to restart my laptop.
- lima 10y agoWhat configuration? Works fine for me with a Skylake ThinkPad on Fedora 24.
- krzyk 10y agoI can do the same with Xorg (also thinkpad), what kind of problems do you have in Xorg with docking?
- stemc43 10y agoScreen was freezing in Fedora. In Ubuntu it was working but took ~25 seconds for screen to come on. constant problems across several OS releases & versions.
- ChuckMcM 10y agoI know you are making an earnest comment but the idea of having one computer support multiple users each on their own terminal is really really well explored territory. So I chuckled a bit at how even old things can be new again. It does speak to having way more compute resources than you can consume at a given time.
- digi_owl 10y agoIts old yes, but the Freedesktop boys are doing it in a "new" way. This by using sofware to bundled a random set of devices into a single seat, and assigning said seat to a user on login based on the input device used. The old way was to hang dedicated hardware off serial ports and figure out the "seat" (if such a concept needed to be defined at all back then) that way.
- ChuckMcM 10y agoExactly right, the concept is timeless and the implementation choices change with the times. A similar moment of humor occurred when AT&T's U-verse product offering was bragging about sending your video signal to other TVs in your house wirelessly. So the next engineering question is "How does this make things we want to do, or have done, better or different?" I could imagine you could set up a very interesting pair programming setup that way, especially if you were projecting a common "third" monitor on the wall or something. That common monitor could show current status for both programmers like building/testing, source code state, etc.
- digi_owl 10y agoWayland (or more "correctly" the support plumbing that will surround it, but developed by the same team) will likely support all that, in time. Just that rather than manually configure it, it will be automatically (they hope) configured by combo of systemd, polkit and your DE of "choice".
- jff 10y agoSo once again freedesktop.org pushes out the new software with the promise that some day it will meet the capabilities of the current tools, honest, we pinky swear. They did it with systemd and they'll do it again with Wayland.
- coldtea 10y agoYeah, ignoring those seldom-used edge cases (multiple mice, keyboards, N people using the same computer at once, etc.) all the while solving several real issues and improving common uses cases in the process... Damn those freedesktop.org people!
- mixedCase 10y agoYes, we know the Gnome team (and by extension, most of Freedesktop) wants to reimplement macOS on Linux. But trust me, Miguel isn't coming back, the best course would be just going to macOS instead (or hell, Windows, he's a happy camper now, isn't he?) or do your work downstream. The rest of us just want our own systems to run as well or better for our own usecases as they currently do. Wayland is a great opportunity to rearchitect the Linux display system rather than organically grow it as X11 has over decades. But if you don't take into consideration those of us who use our Linux workstations as more than a Facebook machine with SSH preinstalled; you're just going to recreate the problem. People will start disregarding freedesktop, Wayland and so on and either stay in X or using a Wayland compositor that couldn't care less for standards and short-circuit every single convention and security protocol you have designed as long as it lets them get shit done, because at the end of the day, as beautiful as we like our code to be and our software to be architected; people want their systems to work for them.
- deleted 10y ago[deleted]