December saw the release of the latest major update to VirtualBox, Oracle's desktop virtualization tool. In its previous incarnation, it was voted as our readers' favorite virtualizer, so let's look at what 4.0 has to offer.
Upon launching the new VirtualBox, the first thing that becomes apparent is the new GUI layout. However, long-term VirtualBox users have little to fear as it remains a close relative of the original. The most obvious addition to the VM management part of the GUI is that there is now a thumbnail that gives a continuously updated view of a currently running GUI. It seems to have an update period of about once a second, so hopefully, it's not using up a lot of resources. Having said that, it's handy for people who just want to keep an eye on what's running.
Speaking of which, the VM windows themselves are now scalable. This means that you could have an OS running in, say, 1024x768 resolution but scaled to run in smaller window. Again, this is handy if you just want to keep an eye on things without sacrificing desktop space, and you can flip back to a full sized window with a key combination.
CLI junkie or GUI monkey? As with previous releases, VirtualBox 4.0 can be operated entirely via the GUI or from the command line, but the GUI continues to lag slightly behind in the case of some of the advanced features. For example, the new features of being able to set disk access bandwidth limits and the resizing of virtual hard disk images are only accessible via the command line. On the other hand, port forwarding now has a GUI dialogue. As some features are CLI only, it is important to have good documentation, and the good news is that the user manual has already been updated for the 4.0 features.
Under the hood, there have been some changes in the way that individual VMs store their settings. The settings file for each VM is now stored in the same directory as the HD image, and this, along with some other changes, makes transferring VMs between computers much easier. In addition, the file cleanup is more comprehensive when a machine is deleted.
Some may be disappointed with the volume of brand new features, given that this is a major version number change. What 4.0 offers over the most recent 3.x release is a new GUI and a few other improvements. A look through the release notes, makes it clear that there are a handful of smaller, although useful, new features in addition to the more noteworthy ones. I suspect that large minor version leap, from 3.2 to 3.5, would have given people a clearer idea of what the new release actually offers. However, this is a nitpick when we're talking about a such fine piece of free software as the OSE version of VirtualBox. Overall, it has some nice updates even though it lacks the earth shattering new innovations that people tend to expect from a full version number increment.
UK based freelance writer Michael Reed writes about technology, retro computing, geek culture and gender politics.
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!
- Stunnel Security for Oracle
- SourceClear Open
- 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!
- Google's SwiftShader Released
- Tech Tip: Really Simple HTTP Server with Python
- 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