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.
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!
- SUSE LLC's SUSE Manager
- Returning Values from Bash Functions
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- Tech Tip: Really Simple HTTP Server with Python
- Rogue Wave Software's Zend Server
- Parsing an RSS News Feed with a Bash Script
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