Create a unique Linux experience with the Unix Desktop Environment

This article is part of a special series of 24 days of Linux desktops. If you're in the mood for something completely unique, then UDE is the desktop you need to try.
83 readers like this.
Top 5 Linux pain points in 2017

Internet Archive Book Images. Modified by CC BY-SA 4.0

When the UDE project started in 1996, the developers took on a bold name—Unix Desktop Environment (UDE)—and held high hopes of reinventing what a desktop could be. They weren't just trying to redefine Unix desktops; they were trying to change the way users interacted with applications on their system. Windows 95 had just come out, so the idea of managing a make-believe "desktop" filled with "folders" and "windows" meant to mimic a real-world desktop had not won all computer users' mindshare (it still hasn't, but it does at least seem to be a reliably stable option now). There was still room for experimentation in computer user interfaces (UIs), and the UDE project introduced some truly innovative ideas.

One of UDE's most intriguing concepts is that its windows have no title bars or handles. All window control is performed with a hex menu that appears when a window border is clicked. Windows are moved with a middle-click and resized with a right-click.

Unix Desktop Environment

If you're in the mood for something completely unique, then UDE is the desktop you need to try.

Installing UDE

Your distribution probably doesn't have UDE in its software repository, but it's relatively easy to compile for someone who's used to building software from raw source code.

I installed UDE on Slackware 14.2, but it doesn't rely on any libraries other than standard Xlibs, so it should work on any Linux or BSD system. The compile process requires build tools, which ship by default on Slackware but are often omitted on other distributions to save space on the initial download. The names of the packages you must install to build from source code vary depending on your distro, so refer to the documentation for specifics. For example, on Debian-based distributions, you can learn about build requirements in Debian's BuildingTutorial doc, and on Fedora-based distributions, refer to Fedora's Installing software from source doc. Once you have the build tools installed, you can build UDE the standard GNU Automake way:

$ ./configure
$ make -j2
$ sudo make install

The default location for installation is /usr/local, but you can adjust the paths during the configuration step.

Xinitrc and UDE

The easiest way to get up and running with UDE is to let Xorg do the bulk of the work. First, you must create a $HOME/.xinitrc file. I adapted this from scripts bundled in Slackware:

# $XConsortium: xinitrc.cpp,v 1.4 91/08/22 11:41:34 rws Exp $


# merge in defaults and keymaps

if [ -f $sysresources ]; then
    xrdb -merge $sysresources

if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap

if [ -f $userresources ]; then
    xrdb -merge $userresources

if [ -f $usermodmap ]; then
    xmodmap $usermodmap

# window manager
exec /usr/local/bin/uwm

According to this file, the default action for the startx command is to launch the uwm window manager (which houses UDE). However, your distribution may have other ideas about what happens when your graphic server is launched (or killed to be restarted), so this file may do you little good. On many distributions, you can add a .desktop file to /usr/share/xsessions to have it listed in the GDM or KDM menu, so create a file called uwm.desktop and enter this text:

[Desktop Entry]
Comment=UNIX Desktop Environment

Log out from your desktop session and log back into UDE. By default, your session manager (KDM, GDM, or LightDM, depending on your setup) will continue to log you into your previous desktop, so you must override that before logging in.

With GDM:

With SDDM:

Launching with brute force

If UDE fails to start, try installing XDM, a lightweight session manager that doesn't look at /usr/share/xsessions and instead just does whatever the authenticated user's .xinitrc prescribes.

Desktop tour

When UDE first launches, you may find yourself staring at a black screen. That's the default primary desktop for UDE, and it's blank because no background wallpaper has been set. You can set one for yourself with the feh command (you may need to install it from your repository). This command has a few options for setting the background, including --bg-fill to fill the screen with your wallpaper of choice, --bg-scale to scale it to fit, and so on.

$ feh --bg-fill ~/Pictures/wallpapers/mybackground.jpg

Interacting with the desktop

The next task is to launch an application. UDE provides an application menu, which you can bring up at your mouse pointer's position with a right-click on the desktop. Because you haven't customized the menu yet, your best bet is to launch an xterm window so that you can issue arbitrary commands.

Once you have an xterm window open, you might notice that there's no window decoration. This is the central idea behind UDE: windows are manipulated primarily with a "honeycomb" or hex menu that appears when you left-click on the border of any window.

UDE honeycomb menu

Clockwise from the top hex, the options are:

  • Close
  • Kill (confirm by selecting the pop-up hex that appears upon mouseover)
  • Make sticky or send to a different desktop
  • Maximize
  • Send behind other windows
  • Minimize

Most of them are self-explanatory, but the minimize option can be confusing because there's no place for windows to be minimized to because there's no taskbar, no docklet, and no desktop icons. To retrieve a minimized window, middle-click on the desktop.

UDE middle-click menu

This presents a menu of virtual desktops, one of which is your current desktop and therefore contains even your minimized applications. Select the minimized application to restore it to your screen.

There are example and default config files in /usr/local/share/uwm/config, including one for the right-click application menu configuration. The syntax for the menu is simple and well-documented at the top of the file. This code sample changes the browser option from Netscape to Firefox:

% ITEM "Netscape":"netscape";
ITEM "Firefox":"firefox";

To see your changes, restart UDE from the left-click menu. The uwmrc configuration files dictate the layout of UDE, including the size of window borders, fonts, and other stylistic choices. They are

also well-documented in comments, so look through them and make changes to experiment and find what works best for you.

Old innovations, new again

UDE's interface is strange and new and—if you're intrigued by UI design—very exciting. UDE's design exemplifies the advantages and disadvantages of creating standards in computing. On the one hand, something like UDE is so alien to most users that it's bound to get in the way, yet on the other hand, it's fresh and different and forces users to re-evaluate their workflows, which may result in several unexpected improvements. The reaction you probably have when trying UDE is the same one you're likely to see when you introduce a friend to Linux: What's an old, familiar GNOME or KDE desktop to you is a puzzle to them. But deep down, most of us know the potential benefits of changing the way we look at something we take for granted.

That said, UDE is unquestionably an experiment, not a finished project. It probably isn't going to be your primary desktop, but it's well worth exploring. This is innovation. It's sometimes messy, sometimes slow, sometimes tumultuous. But it's important, bold, and a heck of a lot of fun.

What to read next
Seth Kenlon
Seth Kenlon is a UNIX geek, free culture advocate, independent multimedia artist, and D&D nerd. He has worked in the film and computing industry, often at the same time.

Comments are closed.

Creative Commons LicenseThis work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License.