Red Hat CDE
Manufacturer: Red Hat
Price: $79.95 US
Reviewer: Don Kuenz
During the summer of 1997, Red Hat began shipping a version of the Open Group's Common Desktop Environment (CDE). CDE provides a Graphical User Interface (GUI) to the X Window System. As such, it shares some of the functionality offered by other window managers such as Feeble Virtual Window Manger (FVWM). A key difference between CDE and the others is that many of the leading Unix vendors provide a CDE package for their own native platform (AIX, Solaris, et al.) This means that users in a heterogeneous Unix environment need learn only one GUI, regardless of the underlying platform.
CDE's GUI is centered around a movable toolbar, which sits at the bottom of each of four workspaces. A workspace occupies one full screen and you can navigate between workspaces by clicking on a workspace panner, which is located in the center of the toolbar. CDE also features drag and drop functionality along with tear off menus.
Red Hat's Client Edition comes with a short Install booklet, a 300 page Advanced User's and System Administrator's Guide and a CD-ROM. The CD-ROM contains both software and lots of additional documentation. The User's Guide is well written with an elegance on par with Kernighan and Ritchie's The C Programming Language.
The Open Group bundles several new applications with CDE. Of these new applications, I use dtterm, dtpad and dtfile the most.
dtterm is meant to replace xterm and incorporates most of the functionality of xterm, adding a handy menu bar that allows you to cut, paste and set options. dtpad reminds me of Microsoft's Notepad. It uses ctrl-c, ctrl-v and Ctrl-x as hot keys to copy, paste and delete. If you spend any time using Windows, you should feel comfortable using dtpad. dtfile is a file manager that supports drag and drop as well as the normal options found in most file managers.
Running a simple script allowed me to perfectly install CDE over Red Hat Linux. But, CDE balked after I tried to slam-dunk (ignore all documentation, start the install script and press the enter key at each prompt) it over Slackware Linux. I'll take the blame for that failure, but it points out that you should carefully read the installation booklet if you install on a platform other than Red Hat.
In a CDE environment dtlogin replaces the command-line login. You enter your user ID with a password, and away you go—unless you are trying to login as root. In that case dtlogin denies the login. (See below for a workaround.) Red Hat needs to improve their install script to create a proper environment for root logins.
One other tiny improvement that Red Hat could make is to glue the User's Guide CD-ROM holder right side up. Somebody glued mine in upside-down.
The Open Group provides a generic login script, which causes some confusion in the Linux community. CDE sources a file named $HOME/.dtprofile to set up its environment. A comment at the bottom of .dtprofile implies that you can also source $HOME/.profile by setting DTSOURCEPROFILE=true, but that only works if you happen to use sh or csh as your shell. Unfortunately, most Linux distributions use bash, a shell that also sources $HOME/.profile.
The easiest way to handle this problem, especially on a stand-alone system, is to use Linux's virtual console. Most Linux distributions create four or more virtual consoles during the install process.
The only trick to using virtual consoles is knowing how to jump to them. To jump to the first virtual console, you press alt-F1. To jump to the second you press alt-F2 and so on. alt <- or alt -> cycles you through all of the consoles and displays, so to return to the CDE display you need to keep pressing one of those two combinations. With high resolution monitors, CDE requires a few seconds after you jump to it before it fires up. As you cycle through the screens, you can detect the CDE display because it's the only one that's blank—the remaining screens display a command-line prompt.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Google's SwiftShader Released
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Interview with Patrick Volkerding
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide