Using Linux in a Training Environment
For connectivity, a generic NE-2000 compatible card works rather nicely. I have had good experiences with 3COM 3C509 cards, as well as the Intel Etherexpress cards. If you are setting up a full network, be sure to purchase network cards which match any existing or planned wall connections. Don't run out and save a bundle on a rack of AUI-based cards, if you have twisted pair connections in the wall already.
We use and recommend the Trio64, S3-based cards from Number 9. These cards have proven to be quite reliable and versatile under X Windows. This is a tricky area, due to the fact that XFree86 only supports cards with certain chip sets. Other good choices include cards sporting a Tseng-4000-based chip set.
Our students are not in the graphic design business, nor are we. A low-end, LaserJet-compatible unit works nicely for source code printing and other small jobs. In fact, even a low-end printer can generally support postscript or PCL raw formats, so working with programs like ghostscript and TeX can be facilitated easily. I think our printers are coming on-line at around $400 per unit—not bad.
While installing, configuring and maintaining our Linux host machines can be somewhat time consuming, the same procedures, when performed on our student workstations, take considerably less time. Depending on which training branch you visit, our student workstations range from older 486/33 machines to newer Pentium 90 desktop models. For a simple TELNET connection, even older XT/AT or 286 machine is capable of running NCSA's freely available implementation of TELNET.
For X Windows and Motif development, a more robust platform is required. Most of our workstations have around 500MB of storage and 8 to 16MB of RAM. DCI is an Authorized Microsoft Technical Education Center (ATEC). As such, we also instruct a number of non-Unix related courses, such as Windows NT development. These courses require considerably more resources on the workstation side. The only common denominator is really the network cards used in the workstations, which are also of the NE-2000 variety.
As far as workstation tools go, we use the following software packages on each of our workstations:
NCSA's TELNET Package has truly been a gift from the heavens. It has performed reliably over a sustained time period and is quite configurable on the workstation side. With it, our students are able to maintain multiple TELNET sessions, as well as the occasional FTP to the host to upload their lab work.
X/Appeal from Xtreme S.A.S. (Italy) is a remarkable, surprisingly inexpensive X Server for DOS. It supports a number of different video chip sets, as well network configurations. A 30 day trial version of X/Appeal can be obtained at ftp://oak.oakland.edu/.
Microsoft Windows for Workgroups v3.11? In a Unix-based training room? Surprised? Not at all. One of the nice things about our setup, is that we use the freely available Samba package to allow Linux to provide shared directory and printer services to our DOS/Windows based workstations. The bulky Windows products used in some of our other courses (PowerBuilder, Visual Basic, Visual C++, etc.) can be installed directly onto the Linux host, freeing up valuable disk storage on the workstations. In fact, we even share the CD-ROM which is installed on the host machine. The student workstations can then access the CD-ROM at any time.
While there are a number of advantages to using Linux as a training solution, a number of drawbacks also manifest themselves over time. Do the benefits outweigh the drawbacks? I'll let you be the judge.
Free. End of story. As mentioned earlier, the price of a stable Linux distribution on CD-ROM is exponentially cheaper than obtaining a commercial solution, such as SCO or Unixware. In fact, with the extra cash you have left over, you can afford to subscribe to Infomagic's quarterly Developer's Resource 4 CD set for the rest of your life.
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
- Tech Tip: Really Simple HTTP Server with Python
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Returning Values from Bash Functions
- Doing for User Space What We Did for Kernel Space
- Rogue Wave Software's Zend Server
- Google's SwiftShader Released
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