I want to extend a gigantic thank you for the article in the May 2001 issue of Linux Journal on the GNU Boot loader, “Boot with GRUB”. It could not have arrived at a better time.
We have a Linux machine whose main (boot) hard-drive started giving us IDE bus resets and other attendant errors. It became unusable although we are pretty sure the files we need are probably still good.
I tried constructing a new system from scratch and then copying the needed files and applications to the new system. Unfortunately this didn't work.
After some effort I was able to clone the bad drive onto a similarly-sized replacement drive using Norton's Ghost program. However, the LILO booter was no longer functional.
With the use of the information in your article I was able to construct a boot floppy that would get the replacement drive booted, and then I ran LILO on it to get the boot configuration properly re-written onto the drive. It is now a booting system.
In the “Best of Technical Support” May 2001 a suggestion was made to use the command expect. The editor inserted a note that expect was described in an article published in the December 2000 Linux Journal but did not mention the specific article, author or page number. I relied on the Interactive Journal to find it. However, expect did not get picked up by your search engine. I ended up searching each article with my web browser's find feature and did locate the article: “Linux System Administration: A User's Guide” by Marcel Gagné. May I suggest that when referencing an earlier article that you use a fuller citation. Thanks.
In addition to Marcel's article, we've run two other articles on expect. One can be found in issue 54, “Automating Tasks with expect” and one in 68, “What Can You Expect?”
I would be more inclined to take Tobin Maginnis' infomercial on Sair Certification, “Why be Certified”, seriously, if his grasp of PC history wasn't as shaky as his understanding of Shakespeare (LJ May 2001).
When IBM introduced the original PC, it didn't “revolutionize the technology”. The design borrowed pretty heavily from the Apple II, and for the first few years of its life, it was a fairly pathetic machine. However, it had the one magic component, those three letters on the label. That made it socially acceptable in the office, even though it was distinctly inferior to the CP/M machines of the time. (On the positive side, it brought an end to the bewildering proliferation of floppy disk formats then current.)
Ever since Novell hit on the concept of certification as an extra cash cow, and corrupted the term “engineer” in the process, it's been making life easier for ignorant personnel (aka HR) types to sort resumes into piles, and I don't suppose that's going to go away. The only question is, to which pile will this certificate direct my resume?
I received the latest issue with the Training & Certification focus and was very disappointed to read that Red Hat's RHCE program was given essentially no print space, despite being widely recognized as the industry leader in Linux certification.
Having just completed the course, I can say that it is an accurate measure of a person's basic Linux systems administration skills, and even with 6+ years experience administering Linux, I found the class informative and the exam challenging.
I find the lack of mention of the course very disturbing, and I can only hope that this is not the beginning of a trend that will see LJ catering towards advertisers with deep pockets rather than accurately reporting on the Linux world.
—Cheyenne T. Greatorex, RHCE
Cheyenne, There certainly is no such trend. Between Sair, LCI and Red Hat I would have to say that the latter has the deepest pockets.
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
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- 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