Motif 1.2.3 Runtime and Development System for Linux
I found mwm to perform very well on my system.
I did check its memory usage, and found that it used 1460KB of memory (according to TOP), while fvwm used only 296KB. Clearly, if you are trying to conserve memory, fvwm is the better way to go. As mentioned earlier, there is no virtual mwm, so if you like having a larger than screen desktop, you'll want to stick with fvwm. However, in terms of a solid consistent sharp look-and-feel, mwm has a slight edge.
fvwm in top:
PID USER PRI NI SIZE RES SHRD STAT %CPU %MEM TIME COMMAND 67 dal 2 0 160 296 296 S 0.8 4.1 0:25 fvwm
mwm in top:
980 dal 3 0 344 1460 608 S 1.7 20.3 0:01 mwm
I was impressed by Sequoia's port of Motif for the Linux platform. They have done a fine job bringing the industry standard to Linux. If portability is a concern for you or you want to use the same tools as the rest of the industry, then I recommend this product.
[Ed: Since this review was written, GUI, Inc. has taken over responsibility for the SWiM Motif distribution, and has released a new version of SWiM based on Motif 1.2.4. GUI is responsible for support, including upgrades, for SWiM. More details will be available in the review of GUI's SWiM Motif 1.2.4 which will be published in a future issue of Linux Journal.
Dale A. Lutz can be reached at (email@example.com)
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!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
- 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