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.
|Speed Up Your Web Site with Varnish||Jun 19, 2013|
|Non-Linux FOSS: libnotify, OS X Style||Jun 18, 2013|
|Containers—Not Virtual Machines—Are the Future Cloud||Jun 17, 2013|
|Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer||Jun 12, 2013|
|Weechat, Irssi's Little Brother||Jun 11, 2013|
|One Tail Just Isn't Enough||Jun 07, 2013|
- Containers—Not Virtual Machines—Are the Future Cloud
- Non-Linux FOSS: libnotify, OS X Style
- Linux Systems Administrator
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Validate an E-Mail Address with PHP, the Right Way
- Technical Support Rep
- Senior Perl Developer
- UX Designer
- Introduction to MapReduce with Hadoop on Linux
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?