3 ms·

I assume that the video you are referring to is the durden demonstration playlist [1] and not the general project presentation? For durden alone, it's a bit ha

I assume that the video you are referring to is the durden demonstration playlist [1] and not the general project presentation? For durden alone, it's a bit hard to invite the comparison on a level other than feature, since I have to cover the bases that xrandr, xset and a whole lot of other x* tools provide - but current and planned features is tracked in the checklist if you scroll down in the readme at [2] [1] https://www.youtube.com/playlist?list=PLGqpKIeZOSp6quf6CmMOr91Tmj4UppyoR https://www.youtube.com/playlist?list=PLGqpKIeZOSp6quf6CmMOr... [2] https://github.com/letoram/durden https://github.com/letoram/durden

onli 10y ago
Durden confuses me a bit. Is arcan completely standalone, does it replace X? The screenshots for durden show normal applications in Windows. Does that mean it is possible to install linux, install arcan and durden, and then run normal applications without needing to install X (I assume of course only those that do not rely direcly or indirectly on Xlib or xcb)? How does it compare to Wayland? I guess I'm missing the positioning inside the existing linux-ecosystem. Feedback: Having to whitelist applications in a database before being able to launch it sounds like a pain in the ass, and I predict that would be a feature that will absolutely prevent adoption.
- crazyloglad 10y ago
  The 'you can install linux, arcan and durden and then run normal applications' assertion is correct. That's how I am using it. The screenshots were taken on OSX because that was the only handy thing I could do the video recording on at the time. It's possible to 'test it out' with X/libsdl as a backend. The actual setup is a bit hairy on most distributions because everything brings in X as a dependency, but I have both Alpine Linux and Ubuntu16.04 running it here without X (or dbus or pulseaudio or systemd or ...) Here [1] is some proof and [2] are my rough notes on how I did that. The whitelist part is entirely optional, it's only there for really security paranoid stuff later on (sandboxing policies and chain-of-trust starting). ARCAN_CONNPATH=durden /some/bin style 'launching' is entirely possible. The second to last slide goes into the relation with Wayland, but there will be support for connecting applications that speak wayland, and other protocols for that matter. [1] http://cubeupload.com/im/lmBeMk.png http://cubeupload.com/im/lmBeMk.png [2] https://github.com/letoram/arcan/wiki/linux-egl https://github.com/letoram/arcan/wiki/linux-egl
  - onli 10y ago
    Sounds incredible. I'll put it on my to-blog list, if I get it to run at least.

onli 10y ago

Durden confuses me a bit. Is arcan completely standalone, does it replace X? The screenshots for durden show normal applications in Windows. Does that mean it is possible to install linux, install arcan and durden, and then run normal applications without needing to install X (I assume of course only those that do not rely direcly or indirectly on Xlib or xcb)? How does it compare to Wayland? I guess I'm missing the positioning inside the existing linux-ecosystem. Feedback: Having to whitelist applications in a database before being able to launch it sounds like a pain in the ass, and I predict that would be a feature that will absolutely prevent adoption.

crazyloglad 10y ago
The 'you can install linux, arcan and durden and then run normal applications' assertion is correct. That's how I am using it. The screenshots were taken on OSX because that was the only handy thing I could do the video recording on at the time. It's possible to 'test it out' with X/libsdl as a backend. The actual setup is a bit hairy on most distributions because everything brings in X as a dependency, but I have both Alpine Linux and Ubuntu16.04 running it here without X (or dbus or pulseaudio or systemd or ...) Here [1] is some proof and [2] are my rough notes on how I did that. The whitelist part is entirely optional, it's only there for really security paranoid stuff later on (sandboxing policies and chain-of-trust starting). ARCAN_CONNPATH=durden /some/bin style 'launching' is entirely possible. The second to last slide goes into the relation with Wayland, but there will be support for connecting applications that speak wayland, and other protocols for that matter. [1] http://cubeupload.com/im/lmBeMk.png http://cubeupload.com/im/lmBeMk.png [2] https://github.com/letoram/arcan/wiki/linux-egl https://github.com/letoram/arcan/wiki/linux-egl
- onli 10y ago
  Sounds incredible. I'll put it on my to-blog list, if I get it to run at least.