Learn the hardware and software procedures for making MP3 and Linux get along. www.ssc.com/mirrors/LDP/HOWTO/MP3-HOWTO.html
When rebuilding kernels, make a backup of the last one that worked, and include a stanza in your /etc/lilo.conf to allow booting the working kernel. For example, with kernels found in /boot/vmlinuz and last known working kernel in /boot/vmlinuz.works, /etc/lilo.conf might look like:
boot=/dev/hda<\n> install=/boot/boot.b map=/boot/map vga=normal timeout=200 prompt read-only image=/boot/vmlinuz root=/dev/hda1 label=Linux read-only password=Vogons restricted image=/boot/vmlinuz.works root=/dev/hda1 label=Itworks read-only password=Vogons restricted
this will present a LILO prompt and wait 20 seconds for instructions as to which kernel to boot. The user may type
Itworksto select most recent build or most recent known good kernel. The “password” and “restricted” parameters prevent entry of additional boot parameters which might compromise security, without entry of the correct password. Make /etc/lilo.conf read/write to root, no permission to group or other.
Once a kernel is known to work, as root:
cp /boot/vmlinuz /boot/vmlinuz.works<\n> lilo
If you are using Linux and your system keeps crashing suspect the hardware, unless you are running some bleeding edge development kernel.
First, check the memory. There is a great program for memory check called memtest86 (http://reality.sgi.com/cbrady_denver/memtest86/).
The memtest program is an x86 boot sector. You can put it on a floppy and boot the suspect computer to memtest from a floppy drive. Or, my favorite is to load memtest from lilo as an operating system. Use an image clause in your lilo.conf file like this:
image=/vmlinuz #Your Linux kernel<\n> label=Linux read-only image=/memtest #Your copy of memtest label=Memtest
Sometimes CPU's just don't perform well at their rated speeds. You run into weird things like segmentation faults while using ls! Under clock your CPU. A good way to give your CPU a test is to run setiathome on your machine. See: http://setiathome.ssl.berkeley.edu/. This puts your CPU to work doing lots of fast Fourier transforms. Don't forget to join the Linux Journal setiathome group.
Still having problems? Lower the motherboard bus speed by a hair. If you see or smell smoke, shut off the power.
It happens often: an author sends a file created in DOS, which adds ^M throughout the text. To globally remove all ^Ms from a DOS file I use one of the following two options:
dos2unix <filename> bni:or
The ^M is produced by typing CTRL-V, then CTRL-M. Use them both—for a bit of variety!
“Linux happened without the help of deep pockets—how can we keep the magic?”
—Bruce Pehrens, posing a question to Michael Dell at LinuxWorld.
“Linux has to change the world more than the world needs to change Linux. Because IT sucks.”
Looking for a news site similar to Slashdot? Try: http://www.kuro5hin.org/. Reader's vote articles on or off!
Palm will soon be unveiling a new version of the Palm Vx—the Claudia Schiffer model! Try http://www.claudiaschiffer.com/ for more details.
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!
- Paranoid Penguin - Building a Secure Squid Web Proxy, Part IV
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- SourceClear Open
- SuperTuxKart 0.9.2 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