Excellent article [“Must-Have Zaurus Hardware and Software”, LJ, January 2003]! Very informative and a lot of detail. I have just bought my Zaurus, and I downloaded a lot of utilities and was able to set my Zaurus's configuration with the help of Guylhem Aznar's article. Thank you.
In “Playing with ptrace, Part II” [LJ, December 2002], Pradeep Padala talked about injecting code into a process and finding some “free space” to put it in to. It's worth noting that the space referred to is not really “free”; it's usually either the cleared space used for global storage in the executable and its shared libraries or the C library's heap storage area. In any case, writing over this data and not restoring it before allowing the execution to continue (as may seem reasonable at first) could cause all sorts of weird behaviour, including program crashes.
Just got my January 2003 issue of LJ and was quite surprised to see a FreeS/WAN article included—nice work! I was really happy to see you used the RSASigs in the examples instead of preshared secrets, a welcome change from the usual and insecure examples I've read in the past. I maintain www.freeswan.ca, an alternate source of information, patches and prepatched versions of FreeS/WAN for interoperation with many devices. Freeswan.org now ships RPMs for Red Hat 7.x and 8.x for all kernel combinations. These include only the ipsec.o modules and user-land tools and don't replace your vmlinuz and grub/lilo configs. Folks should update to 1.99, as there was a serious denial-of-service flaw that is now fixed.
Mick's reply: Thanks very much for your suggestions. Part II appeared in the February 2003 issue, and I doubt this is the last I'll write on the subject!
As a long-term LJ reader (fourth year), I am really surprised about the great January 2003 issue—it covers all the stuff that I am interested in without even knowing about it. The GCJ, Screen and DDD/quicksort articles shed more light into the daily use of our beloved Linux platform. Please keep us informed about developments in compilers, debuggers and other development tools to make us more effective in developing new stuff. Keep up the good work.
—Raphael Arlitt, Germany
What LUG meeting or BOF session would not be enhanced by penguin canapés and an igloo cheeseball? We humbly submit pseudo-code for building same and an image as proof that it's working code.
2 packages cream cheese1 cheeseball1 can large black olives, pitted1 can small black olives, pitted1 carrot1 packages toothpicks with yellow or orange fringecrackers1 tin kippered herring (optional symbolic offering to penguins)
#!/bin/bash while hungry; do (\ cut_cream_cheese_into_strips_and_cover_cheeseball;\ make_igloo_entrance_tunnel_from_cream_cheese_strip;\ use_toothpick_to_sculpt_snow_block_seams;\ peel_carrot_with_vegetable_peeler;\ cut_carrot_into_coin-sized_slices;\ cut_slender_wedge_from_each_carrot_slice_and_reserve_for_beak;\ slit_each_large_olive_and_stuff_with_cream_cheese;\ puncture_each_small_olive_and_insert_carrot_wedge_beak;\ skewer_small-olive_head_large-olive_torso_and_carrot-slice_feet_with_toothpick;\ arrange_olive_penguins_about_cheeseball_igloo_on_serving_dish;\ arrange_crackers_on_serving_dish_or_nearby;\ serve); done
Herring also can be served to set the scene. Herring are one of two things that make penguins contented. This recipe is a clean-room implementation developed by reverse engineering based on a study of olive penguins and a cheeseball igloo served at a party. We hope the process is not patented. In any case, we assert that the recipe is our own work, and we release it under the terms of the GNU Free Documentation License.
—Michael Callaham [penguins] and Jennifer Gentry [igloo]
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
- Returning Values from Bash Functions
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Rogue Wave Software's Zend Server
- Doing for User Space What We Did for Kernel Space
- 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