Caldera Network Desktop 1.0
The Caldera Network Desktop (CND) is not just another Linux distribution. Some people will be very happy to hear this; others will be disappointed. Rather than an in-depth product review, this article offers some first impressions and talks about where CND is a good fit.
Starting in Fall 1993, with the first Yggdrasil release, Linux has been evolving in the commercial arena. That is, prior to that time, most newcomers found Linux on the Internet or in the hands of a friend and worked from there. Yggdrasil changed that, and other vendors (including Walnut Creek, CraftWorks, and Red Hat) continue to offer commercial products.
Like Yggdrasil, a pioneer that took Linux into a different arena, Caldera has done it again, expanding the possible Linux market into a whole new area. What needs to be addressed is: what is this new market, and who, along with Caldera, will need to get involved to service this market? But before we get into that, here are my initial experiences with installation.
When I opened the package I found a manual, a CD in a jewel case, a very skinny mouse pad (that gets mixed reviews in our office), and two floppy disks. I was pleased to find the floppies but very surprised there were only two, since Red Hat (which Caldera is based on) uses two root disks plus a boot floppy that you must select from 72 possible choices.
It turns out Caldera is using a new installation system and only one floppy is required. One of the two is for standard computers, the other is for laptops with PCMCIA cards.
I quickly thumbed through the manual as I searched for some free disk space on biggie, the machine I have used to load and test most of the Linux distributions on the planet. The documentation looks good, covering most of what you need to know without becoming a text for techno-nerds.
I slipped in the boot disk and CD and booted up the system. It came up to a boot screen where I entered my one required boot-time parameter so my SCSI controller could be found. All worked well and I was ready to start answering questions.
Without going into great detail, LISA (Linux Installation and System Administration) is a text-mode installation system that was very easy to use and asked the right number of questions. By that I mean, if something needs to be asked, it is, but users aren't pelted with questions about things they might not care about or understand.
All went well until the X installation. At that point the system refused to believe I had an S3-based video board and kept defaulting to VGA mode. The board I have is a brand-X, but I have it running fine under Slackware, Red Hat and Yggdrasil.
I finally gave up and changed to a name-brand video board that was one of the choices on the X configuration menu and all worked fine. The X server is X Inside, which is, I understand from talking to others, very good and fast. While it supports cards that are not supported by the free server (like the Matrox line) it has a reputation for not liking some clone cards.
At this point, I decided I needed to try installing CND on another computer to see how well it worked. I chose my Toshiba T3600 notebook which is currently running Slackware 2.3. I plugged in a New Media BusToaster card and SCSI CD-ROM drive and booted it up from the PCMCIA floppy. After booting, it asked me to insert my PCMCIA card, wait five seconds and press return. I did. It successfully identified the card, but then died because the module to talk to the card was not on the boot disk. While I could have found the module, made another boot disk, and tried again, I decided to quit and hope that version 1.1 addresses that problem.
On boot after installation, all came up fine. My only complaint is that it starts about every possible server and daemon in the world. While this does make it easy for people who don't know what they want, it also means editing rc files for those who need to streamline their system.
Once CND is up and running, it offers a drag and drop desktop. But, you already know that from the reviews of the preview version and the Caldera ads. So, once again, I wanted to make it do all the stuff I had been doing with other Linux distributions, and my first effort was to get my PPP link back up and running.
There was no GUI-based setup for PPP, so I looked in the manual. Sure enough, PPP was in the index. The reference basically said to read the PPP HOWTO (which is on the CD). This wasn't fatal, as I merely copied the PPP stuff I had under Slackware over and it worked fine. But again, there was nothing easier about setting it up under CND.
|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|
|Introduction to MapReduce with Hadoop on Linux||Jun 05, 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
- Senior Perl Developer
- Technical Support Rep
- 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?