Timeline for Xephyr and xorg process
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 1, 2019 at 17:45 | comment | added | user313992 | Actually, you can replace Xvfb (the "dumb framebuffer" Xserver) with stock Xorg + xf86-video-dummy driver, but I don't think if you can do the same with Xorg + xf86-video-nested on a stock distro. Example for xf86-video-dummy: echo 'Section "Device" Identifier "dummy" Driver "dummy" EndSection' | PATH=/usr/lib/xorg:$PATH Xorg -config /dev/stdin :3 | |
| Jan 1, 2019 at 17:38 | comment | added | user313992 | Xorg and Xephyr share most of their code and are built from the same source, but ps ax will still print just the command line (the same thing you can get withtr '\0' ' ' </proc/PID/cmdline on linux). | |
| Jan 1, 2019 at 16:46 | comment | added | Irbis | I have thought that Xephyr runs a host xorg imeplementation but it looks like the Xephyr implements server protocol internally. | |
| Jan 1, 2019 at 13:31 | comment | added | user313992 | ps ax | grep xorg will match the command line like /usr/lib/xorg/Xorg :0 ..... What makes you believe that the command line you are running (Xephyr -ac ...) should match xorg despite not containing the xorg string anywhere? | |
| Jan 1, 2019 at 13:17 | history | asked | Irbis | CC BY-SA 4.0 |