First off, I really did enjoy reading the article on replacing Microsoft Exchange with Linux [“Understanding and Replacing Microsoft Exchange” by Tom Adelstein, LJ, February 2003]. The article didn't explicitly state you were trying to replace Microsoft Exchange 5.5, but it was obvious to me that was the version you were working with. Microsoft's Exchange 5.5 was limited in the total size of the database, but that has changed in Exchange 2000 and Titanium. Exchange 2000's Exchange Storage Engine has been rewritten to allow much larger database sizes, which would be limited only to the total capacity of the hardware on which the database would reside. Also, I fail to understand the reasoning of why IMAP was provided as a connection mechanism. IMAP will provide you with a way to preview the e-mail message. Does your DLL plugin to Outlook provide a way for the message to remain on the e-mail server?
—Chris Lynch, Network Engineer
Tom Adelstein's reply: Thanks for your thoughtful letter. I appreciate your detailed understanding of Exchange. It is quite impressive. Our goal at Bynari was to create an RFC-compliant platform that allowed Microsoft Outlook to run in corporate workgroup mode. In the case of Outlook 2002, we wanted to provide calendar sharing and delegation.
I have been a happy LJ subscriber for many years now. I am usually not one to complain about things but the articles written by Marcel Gagné are getting irritating. His French Chef schtick is getting VERY old and detracts from his articles. Please consider having him stop that and simply write informative articles.
It is with much interest that I have read your editorial on clustering the previously unclustered [From the Editor by Don Marti, LJ, February 2003]. I seem to be unable to convince the powers that be at some CAD and CAD/CAM firms that this is an option. Therefore, I would very much like to get information on how to make programs that are not enabled for cluster technologies to work with cluster hardware configurations.
If you have one huge, slow process, you'll probably need to rewrite the software using a clustering library. However, if you need to make many processes cooperate, OpenMosix automatically will migrate some of them to idle nodes in the cluster. See openmosix.sf.net.
Thank you for excellent article on screen(1) [“Power Sessions with Screen” by Adam Lazur, LJ, January 2003]. Please persuade Adam Lazur to write a couple follow-up articles to this introductory one. I'm already starving for more.
In the March 2003 issue, there was an article on weblogs that led readers to believe that Geeklog is a fork of PHP-Nuke [“Building with Blogs” by Doc Searls and Dave Sifry]. Much respect needs to be given to PHP-Nuke for helping to spur the weblog phenomenon, and I think the article presented that respect. However, Geeklog is not a fork of PHP-Nuke. Also, the article should have mentioned www.opensourcecms.com. It has the most popular packages in a demo-able state for users to test them without having to download, install and configure.
Seth Schoen's column “Broadcast Flag: MPAA's Latest Attack on Linux” (LJ, March 2003) appears to be mistitled. Mr. Schoen did not provide evidence on the MPAA making any form of attack on Linux or on any free operating system in the article. On a side note, he wrote, “Reporters were barred from meetings, which had a $100-per-meeting admission fee.” Were reporters specifically barred or was it just that reporters would have to pay $100 per meeting?
Seth Schoen replies: Magazine editors have little space available for titles, so I could see where they would feel the need to condense “Broadcast Flag: MPAA's Latest Attack on the Right to Use Free Software to Lawfully Make and Interoperate with Recordings of Copyrighted Audiovisual Works” (which is what I would have called it) to “Broadcast Flag: MPAA's Latest Attack on Linux”. Reporters were specifically barred from meetings; they tried to participate, and they were kicked out.
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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
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