Novice to Novice
vim (3.0, on disk “AP”) stands for Vi IMproved. I've already stated that I'm not enthused about vi. Sadly, vim doesn't improve my opinion. It may be improvement over vi but it still doesn't make the commands any more intuitive or the vi idea any more palatable.
fpted is another clone. Unfortunately I couldn't really try it because it crashed. It looked like, at least, a help menu was easily available.
celvis required compiling, which produced a multitude of warnings. Yet it ran without any apparent problems. A unique aspect to this clone is that with the proper terminal you can write in Chinese.
vile and xvile for X-Windows are yet more vi clones. I liked these two because of the highlight bar at the bottom which, in part, clearly tells the command for help. I keep focussing on help because for novices it is perhaps the most important command to know. Considering that many of these programs do not include help files or tutorials, a menu bar saying that help is ^h-? or something is a great benefit.
nvi (1.03) is—guess what—yet another clone of vi but without a helpful menu bar at the bottom. [It's the official “new vi” from Berkeley—Ed]
xvi needed compiling which I passed on. My guess is this program is yet another variant on vi and will run under X-Windows.
jed (0.96, also on disk “AP”) is a program that I like. It uses the cursor keys for easy movement. There's a menu at the top and another available that appears at the bottom when you hit ^h-?. However, one warning about that: option 6 will not exit you from the secondary menu but from entire program! [Jed can also use Emacs, EDT, and Wordstar keys, and the curser keys work the same no matter what keyset you are using, so most people will be comfortable with it one way or another—Ed]
joe (2.2, disk “AP”) is a program I also like but not quite as much as jed. The screen is cleaner, not as cluttered with a help menu, just a simple bar at the top. joe uses Wordstar-like commands so I had no problems with cursor movement and other commands. The help was a bit tricky. ^k-h to turn it on but to page through required an awkward ^[-. or ^[-, (for backwards).
ed stands for “standard editor” and I couldn't stand it. This is a very small program with no obvious help command. In fact, to figure out the commands you have to read the source code; fine for hackers, not so good for novices. [Even most hackers avoid this like the plague. It complains about errors with only a question mark; the manual says, “Experienced users will usually know what is wrong.” —Ed]
ez (7.0, ATK 6.3.1) provides a clean X-Windows Word Processor that apparently can be used standalone or part of the larger Andrew system. This program was covered in Linux Journal, issues 4 (August, 1994) and 5 (September, 1994). ez certainly lives up to its name with mouse and cursor key control and a good word processor with multimedia options. Despite its ease it didn't have any obvious way to change fonts or type sizes, unusual for a program of this quality. I discovered a window that had the information about fonts and whatnot listed but again no obvious way to make changes.
[ez can edit documents of many different types transparantly. In order to access the word processing features, you have to open the right kind of document by giving the file the correct extension. Files ending in .d or .doc will turn on ez's word processing capability, which will show up in obvious menus; for instance, font changes are accessed through the “Font” menu—Ed]
crisp (v2.2e from the Sunsite CD) is an editor that is like emacs in that it has great expandability, obscure commands, and can be used for programming. Untarring the binaries produced a barrage of files including the two main executables cr and xcr (for the X-Windows version). Upon startup of either you get a window with an information bar at the bottom. For novices there is no obvious help command. ^-h didn't work. crisp was the last package I looked at and I was determined to at least figure some of it out. I used mc and finally discovered user and programmer help files under /usr/local/lib/crisp/help/org. The user.hlp file said Alt-h would give help but back in crisp it didn't; it gave gibberish that told me I probably had an emulation problem. Enough, enough, I resign. For Crisp this is apparently the last freebie version and they now have a snazzy graphical offering. I hope it has an obvious help command.
I probably missed a few spreadsheets and text editors while scrounging through the CD's. My general impression is that for the spreadsheets the level of the freeware is comparable to an early Lotus-123 or Excel. But the programs work and will get you through your basic spreadsheet needs.
There are quite a few choices of text editors available with the majority of them clones of either vi or emacs. My personal favorites are jed, joe, either X-Windows version of emacs, and Andrew's ez. They get the job done fairly easily and Emacs can apparently handle most anything. To conserve hard drive space, I would probably choose GNU Emacs over Lucid or maybe have both runnable off the CD. But to summarize my feelings: I guess I expected programs that were more for word processing and for that I gained disappointment. Maybe the WordPerfect demo would have met my expectation could I have installed the beast. For word processing I would stay with what I have in DOS or perhaps purchase a good commerical UNIX word processor. As a writer, I need advanced features and none of the above programs really satisfied that criterion, instead being better for producing ASCII files and for programming environments.
[Projects are now underway to provide more word processing programs. We will cover them in Linux Journal when they are ready for public consumption—ED]
Dean Oisboid, owner of Garlic Software, is a database consultant, Unix beginner, and avowed Diplomacy addict. He can reached at firstname.lastname@example.org.
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- My +1 Sword of Productivity
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
- 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