Letters to the Editor
I'd like to make a short comment on the Product Review (December '95 pg. 34): Caldera Network Desktop.
I agree with Roger Scrafford “It's slick...” etc., but if Caldera could separate the commercial stuff from the free parts they would be playing more on the “team of FSF and Linux”.
I would be willing to pay for products like the full-blown CRiSP editor (Yes I love it, being a Brief user way back) or WordPerfect 6.1 with HTML.
But a student or hacker could download the Caldera Desktop for free.
As Linus Torvalds says (and I fully agree): “...the future is the desktop...”---meaning that what Caldera is doing for Linux is very important.
With this separated distribution method, maybe the Caldera Desktop could be a big success (like Netscape?).
O.J. -> Ole J. Utnes (Ole.J.Utnes@hive.no)
P.S. Keep up the good work with LJ.
To answer your first point: Caldera does separate them, very carefully. It makes it very clear in the manual which parts are free, and which are commercial, and makes it clear that you can install only the free parts on as many machines as you wish.
The desktop application is one of the commercial pieces they licensed from someone else, just like the font server, backup.unet, and the NetWare connectivity tools.
However, the Caldera Network Desktop is based on Red Hat Commercial Linux, and all the free pieces of CND are in Red Hat, which is available for FTP from many sites on the internet, including ftp.caldera.com, so your wish is granted.
That is, your wish is granted unless you specifically want them to give away their desktop application. Linus wasn't talking about a desktop metaphor like Looking Glass when he said that the future is in the desktop. He was talking about machines that sit on the desktop, as opposed to servers that live in a “glass house” and are administered by all-knowing gurus.
I think the index should:
Quietly appear in every December issue.
Be printed on the last pages of the issue (like in science journals).
And, by the way, I think my father's TeX'ed index is better. But that's my own biased opinion. I think he e-mailed you about it just because you printed yours...
Peter Galbraith, research scientist email@example.com Maurice-Lamontagne Institute, Department of Fisheries and Oceans Canada
You will be glad to know that the index is scheduled to appear in every December issue, covering the previous year.
It will probably not be printed on the last pages of the issue. We've sold that advertising space, and we can't just take it back for a month.
Your father's index is different—it's more like the index to a book; ours is more like an extended table of contents. We may end up providing his index via the WWW and/or FTP.
You might also check out our index on our WWW site (http://www.ssc.com/). When we have all our articles on-line, that should be capable of a full-text search; it's currently capable of a keyword search.
First I said: “Oh, a possibly boring issue...” from the titles on the cover. But no! You had a really good article on find, and I knew I'd learn something in that Linux System Administration article on adding a new disk.
One question to all of you: The find article uses cpio to copy a directory tree and the Administration article uses tar. I typically use:
tar cf -> ./ | (cd TARGET_DIRECTORY; tar xvf ->)
so I learned about the ->C DIRECTORY tar option from Aileen's article. But should I be using cpio? What's best?
Also, a note on “Hints for splitting Linux across two disks”. I use her method of moving directories and pointing soft links to them as a last resort. Isn't it better to mount the second disk under /usr (or something) to begin with and then safely fully install Linux? Then at least everything is where is should be with a minimum of (sometimes confusing) links on the system.
Thanks for another good issue,
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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
- 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