Letters to the Editor
I read your article about The Linux Appliance (“From the Publisher”, Issue #36, April 1997, page 12) with interest. Right offhand, I can't help but ask myself:
How can such an appliance compete with a “pure Java” system as an appliance? What kind of marketing technique might be used to offset the power of Microsoft? How might we get some major hardware makers (like Sony, Panasonic, etc.) interested?
Is there anything I can do, or anyone I might contact, to help this along (purely on a part-time basis; I have a full-time job as a mainframe/NT system support analyst; if it became a money-maker, I could quit, of course)?
I don't have any business or manufacturing experience, but I have wanted to contribute something good to Linux for a long time. This might be a possibility. —Chuck
I'm not the person ready to manufacture and market this appliance so I am hoping someone else will seriously address these points, but here is my input.
A pure Java system might be a winner, but it could also be a dead end. An addition to Java or a move to something other than Java would result in an obsolete system. On the other hand, a programmable computer makes it easy to follow software changes. In addition, upgrading from an Internet Appliance to a useful computer for word processing and such is also possible.
As for the power of Microsoft, the sales approach is what could make the difference. Anyone can buy a PC/Microsoft system from a catalog or retail store but for many, this is a scary proposition. While computers have come a long way toward being easy to set up and use, offering the necessary support with a system like this could make a big difference. Much like getting a price break on a cellular phone when you purchase air time, ISPs could offer a price break on these systems with connectivity contracts. The ISP would then be there to support it.
As for the possibility of Sony or Panasonic getting interested, if you know the right people to talk to, point them at me. The idea of Linux on the Sony Playstation has already been suggested. —Phil Hughes email@example.com
I appreciated your review of Applixware in the April 1997 issue of the Linux Journal. I do feel obligated to point one large error—Applix data is NOT provided with the 4.3 release, according to Lisa Sullivan at Red Hat.
There are some people (Cameron Newham, firstname.lastname@example.org) working on interfaces to databases that do exist on Linux, but the full-fledged Applix Data interface is not likely to exist in the near future, a victim of lack of support from the big-3 database vendors—at least, that is the reason in my opinion.
Applixware has a chance to do either a lot of good or a lot of harm to the Linux community. It is not quite ready to replace MS Office. Filters and data access, as well as performance with embedded graphics, are areas that need work.
If people expect it to do everything, try it, and are disappointed, they may end up dismissing Linux as junk—a tragic mistake. —Cary O'Brien email@example.com
Dear Terry Dawson,
I just wanted to thank you for your article “A 10-Minute Guide for Using PPP to Connect Linux to the Internet” that appeared in Issue 36 of Linux Journal.
I bought Slackware 2.3 (kernel version 1.2.8) in September of 1995, loaded it on my Micron Pentium-90 and have been experimenting with it ever since. Being more experienced with DOS/Windows, I wasn't successful in getting my PPP connection to work from Linux. I read Matt Welsh's Running Linux and Patrick Volkerding's Linux Configuration and Installation as well as the PPP HOWTO but had no success until your article. Since then, I've gotten ftp, rlogin, telnet, lynx 2.3 and Netscape Navigator 1.1 to run. Next, it's e-mail (I'm sending you this from my DOS/Windows partition). —Steve Tjensvoldstjen firstname.lastname@example.org
I read your article in this month's LJ with much interest. In the March 10th issue of Computerworld magazine, Mr. Charles Babcock wrote about building his own network computer from scratch. From the sound of his article, Mr. Babcock had no previous experience with Linux, yet that was the OS he chose for his NC.
Mr. Babcock was not able to keep the price of his NC below $500. However, it is not clear whether he used many resources towards getting the best prices available. Clearly, anyone venturing into this on a large scale would be able to better his price—$1200.
What interests me most about both articles is the fact that such a system already exists—and has existed for over a year. IGEL, LLC has a line of systems called Etherminals—they were even advertised in LJ for a while. (That's where I learned of them)
I left a full-time position as a Unix Systems Engineer in August of '95 to help my wife with the acquisition of the veterinary hospital where she had worked (as a veterinarian). One of my first responsibilities was to install a computer network.
That's when I discovered the Etherminals. The model 3x was IGEL's current offering—386sx-40 w/ 8MB RAM, on-board Ethernet (all 3 media types) and the standard compliment of 2 serial and 1 parallel ports. What made these machines so attractive to me was that they booted Linux and X Windows from ROM/NVRAM. These units had no drives—not a floppy, not a hard drive, nothing.
I went out on a limb and bought three of them. Once they arrived, I connected them to the Ethernet I'd run (with the help of a couple of good friends) the week before. In a little over an hour I had everything working like a charm. I think it helped more than a little that the server was running Linux as well. (This was something that I insisted on—it even became a point of contention with two potential vendors of veterinary office applications.)
In the end, we chose a vendor whose application was (and still is) DOS-based. DOSEMU now runs multiple sessions on the server and uses X to redirect the I/O to the Etherminals. It's an acceptable solution—DOS being the weakest link.
The most important point of this whole message is that this solution was arrived at over a year ago. No need to wait for SUN or ORACLE. It's here today. —Chuck Stickleman email@example.com
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
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Rogue Wave Software's Zend Server
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