Thought you might be interested in this picture I took across from the main train station in Taipei, Taiwan. It is a very large Linux penguin, dressed up for Chinese New Year. I just finished up with Apricot (the Asian networking conference), and Linux had a large presence in the IPv6 appliances on display, as well as the research being presented. The research lab I work in has many Linux systems. The software engineers do most of their work on Linux and FreeBSD.
I just read the article “Linux for a Small Business” by Gary Maxwell [LJ, April 2003]. He states that when you pay for a book, you debit your cash account and credit your expense account. I believe it should be the other way around. In accounting, debit refers to the left side of a T-account and credit refers to the right side of a T-account. The words are of Latin derivation meaning left and right. They don't mean decrease or increase. Depending on the type of account, a debit can either increase it or decrease it. The same applies to credits. I think this is probably the source of most non-accountants' confusion about double-entry accounting.
Thanks for the great article listing rdesktop, Marcel [Cooking with Linux, LJ, April 2003]. In a heterogeneous environment, rdesktop works nicely for getting to Windows machines. I have also found tsclient (www.gnomepro.com/tsclient), a GNOME 2 front end to rdesktop that looks and acts exactly like the Windows Terminal Services client. For those of us who must work in this environment, it helps things a little bit.
To Jon “maddog” Hall: I am Brazilian and would like to let you know that I agree with your response to Bruno Trevisan's letter about the “Landless Workers' Movement”, Movimento dos Trabalhadores Rurais Sem Terra (MST) [LJ, February 2003]. I sincerely thank you for bringing out the facts. MST is addressing the very basic needs of landless people in Brazil in a conscious, organized and effective way. MST has shown results—tons of results. The land issue in Brazil is a serious one, and Trevisan's statements show a total lack of respect toward people in need of basic things, people in poverty, people that die from hunger. Former President Cardoso never had his farm destroyed. The Brazilian army was always securing his properties because of the lack of response of local police. A few years ago, in the Brazilian state of Para, in the Amazon region, the state police cowardly murdered dozens of rural workers. It took a very long time to bring the police officers to trial. A few years ago, in the state of S. Paulo, the state police invaded a prison and murdered 111 prisoners. Again, it took a very long time to put the responsible ones on trial.
The term wardialing was in use in 1979-80. It was used to describe either linear or random dialing of phone numbers and keeping tabs on the modem carrier detects (CDs) received. Wardialing also was used interchangeably to signify using those numbers, getting the codes from the long-distance carriers, or if you were lucky, a PBX connect to trunk calls and make party lines. Nothing too intelligent, just brute force. Not that I ever did any of that. I think the term war was that you were at “war” with the phone company doing this. Think of it as carpet bombing the telco switch. Eventually, you'll hit something. There were a lot of turf wars like they have now, and essentially, the biggest “list” wins. The movie Wargames (1983) had nothing to do with it whatsoever.
I disagree strongly with your description of GNOME 2 as “an excellent choice for first-time and nontechnical users” [“The GNOME 2 Desktop Environment”, LJ, April 2003]. I used GNOME 1 and persuaded my wife to use it too, but when I installed Red Hat 8 with GNOME 2 we found things had gone backward.
Under GNOME 1, with the Sawfish window manager, I set up all sorts of keyboard shortcuts. This was reasonably easy. There was a decent keyboard shortcuts tool, which allowed you to set the context (global, window, title) and then set shortcuts like Alt-MOUSE3, etc., with a long list of commands to assign them to. Now under GNOME 2, I find a very primitive “keyboard shortcuts editor” that offers a much smaller number of predefined commands and does not allow you to specify the context. Why adopt a worse new window manager without offering the choice of keeping the old one?
We wanted to have some programs run on GNOME startup. I looked in the menus for something like “startup”. It took ages: I finally found the required functionality in a program that runs when you click on Extras-->Preferences-->Sessions. Well hidden!
My wife found GNOME 2 unusable and unfriendly. I found it shockingly weak on everyday functionality, compared with GNOME 1. Overall, the point of a desktop is to make the computer more usable, but I see no sign of any user-sensitivity in the GNOME desktop. It feels like a half-baked programming project, not a user-oriented functional tool.
—Dr Mark Alford
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|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader 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