Installer xorg-server avec Homebrew, apk, MacPorts, Nix, pacman, apt, dnf, zypper

Liens du projet

• Page d'accueil
• Dépôt
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• X
• Xephyr
• Xnest
• Xorg
• Xvfb
• gtf
• xvfb-run

Historique du projet

The Xorg manual says the server was derived by the X.Org Foundation from the XFree86 project's XFree86 4.4rc2 release; XFree86 itself came from the earlier X386 work contributed to X11R5. That lineage matters because the 2004 X.Org transition turned the de facto open Unix X server into a foundation-maintained project under the freedesktop.org development umbrella.

X.Org's X11R7.7 release notes explain the larger release history: X11's network protocol version was first released in 1988 and remained upward-compatible for decades, while the X.Org Foundation, founded in early 2004, issued releases from X11R6.7 onward. The server therefore carries both old X protocol compatibility and the post-XFree86 maintenance model.

A major turning point was modularization. X11R7.0, released in 2005, moved away from the old monolithic source tree into separately released modules. X.Org's version-numbering document notes that X11R7.0 included the xorg-server 1.0 module and that module versions became the most accurate way to track server development.

Historique d'adoption

X.Org Server rapidly became the standard open-source X server for Linux and BSD desktops after the XFree86 split. The Xorg manpage lists broad operating-system and architecture support, including Linux, FreeBSD, NetBSD, OpenBSD, Solaris, GNU Hurd, Mac OS X via Xquartz, and Win32/Cygwin via XWin.

The modular X.Org era also made distribution packaging more practical: servers, drivers, libraries, fonts, and applications could be released and updated independently. X.Org's release notes describe builders watching xorg-announce for individual module updates rather than waiting for a full window-system roll-up.

Even as Wayland became the modern Linux display-server direction, X.Org Server remained important through Xwayland compatibility, legacy Xorg sessions, nested servers, and headless tools. Xvfb and Xephyr in particular kept the package relevant beyond desktop login sessions: test suites, CI jobs, browser automation, and remote GUI debugging still depend on X server behavior.

Modes d'utilisation

On a traditional Unix-like desktop, Xorg is launched by a display manager or startx/xinit, loads video and input drivers, reads xorg.conf and xorg.conf.d configuration when needed, and brokers windows, drawing, and input for client applications.

In development and automation, Xvfb provides a virtual framebuffer for programs that require an X display without real hardware. Xephyr runs a full X server inside a window on another X display, useful for nested sessions, compositor testing, and isolating graphical experiments. Xnest serves a related nested-server role with different tradeoffs.

Administrators and package maintainers care about xorg-server because it is a convergence point for kernel device access, input stacks, graphics drivers, font paths, extension versions, and security policy. Small changes in this package can affect everything from terminal emulators to browser tests.

Pourquoi les passionnés de paquets s'y intéressent

Few packages have more historical gravity in Unix GUI stacks. xorg-server embodies the X11 split between server, clients, libraries, drivers, and protocol extensions, so packaging it correctly means understanding an entire ecosystem rather than a single executable.

It is also a classic example of infrastructure that became less visible as it got more mature. A user may never type Xorg directly, but the package can decide whether old CAD tools, Tcl/Tk apps, X11 forwarding, headless browser tests, and desktop sessions work at all.

The modularization story is a package-management lesson in itself: the X.Org stack moved from one large release artifact to many independently versioned modules, matching the way distributions and source package systems actually want to update fast-moving drivers and servers.

Chronologie

• 1988: X11 protocol version 11 is first released, according to X.Org release notes.
• Early 2004: The X.Org Foundation is founded and begins issuing X11 releases from X11R6.7 onward.
• 2004: X.Org Server is derived from XFree86 4.4rc2.
• 2005-12-21: X11R7.0 is released with the modular xorg-server 1.0 module.
• 2010-12-20: X11R7.6 adds xorg.conf.d directories, InputClass sections, udev support on Linux, improved documentation, and integrated xcb.
• 2012-06-06: X11R7.7 is released, adding multitouch input support, Sync fences, and pointer barriers.
• After X11R7.7: X.Org stops producing unified whole-stack releases and releases individual modules as needed.

Related projects

• XFree86 is the immediate source lineage from which X.Org Server was forked.
• Xwayland lets X11 clients run in Wayland environments and keeps Xorg code relevant in modern desktops.
• XQuartz and XWin are platform-specific X servers for macOS and Windows/Cygwin environments.
• Xvfb, Xephyr, and Xnest are specialized X servers shipped from the same server family for virtual and nested display use.

Sources

• https://gitlab.freedesktop.org/xorg/xserver
• https://www.x.org/Releases/
• https://www.x.org/releases/X11R7.7/doc/xorg-docs/ReleaseNotes.txt
• https://xorg.freedesktop.org/archive/X11R7.7/doc/xorg-docs/Versions.txt
• https://xorg.freedesktop.org/archive/current/doc/man/man1/Xorg.1.xhtml