Linux.Conf.Au - Day One
My flight from Wellington to Sydney can be easily chalked up as one of the most painful experiences of my life - alongside military service, breaking a bone, and supporting Windows 98. Things improved markedly when, after approximately three hours standing in line, my colleague and I boarded our flight from Sydney to Hobart.
We were playing spot-the-conference-attendee - a Linux cap here, a summer of code shirt there - when Linus Torvalds boarded our plane, looking a little sheepish at all the adoring stares. I ran into him again after we disembarked - standing in my way at the baggage carousel. I forgave him. After all, I've heard he's a KDE fan.
The University turned out to be a very expensive but scenic twenty minute taxi ride from the airport. Hobart is nestled in thickly forested hills with stunning ocean views. The University itself is set to a backdrop of stately Australian bush, with a view of the city and the water from my room. The accommodation is better than any year I can remember - I and four others are sharing a spacious modern apartment with a very pleasant living and kitchen area.
After a pleasant Italian meal and a good night's sleep, I started my conference experience by alternating between the Sysadmin and Kernel miniconfs. Matthew Garrett's talk 'How I learned to stop worrying and love ACPI' was entertaining and informative, as expected. I counted no less than 10 instances of the word 'magic' during his explanation of how ACPI suspend happens. After my misspent youth digging into making Linux go on laptops I fully believe him that magic is involved. Dark magic. Involving animal sacrifice. Possibly the animal operating the computer.
On the systems administration side of things, I listened to Richard Keech talk on "Rapid, repeatable provisioning of Linux systems" using the Red Hat kickstart framework. There were some very good points to this talk, but my colleagues and I agreed we thought our current methods were better. Perhaps we should get around to putting in a talk for next year's conference. Devdas Bhagat's presentation on "Automating system administration" was great, looking at the people as well as the technical aspects and discussing how to make the business case for spending time on building these frameworks. I've felt the truth of his comment in the past, that "... any sysadmin can blow up a box, but to blow up an entire bunch of machines takes a sysadmin with a configuration management system."
So far the highlight of the conference for me came in my schwag bag. This is my Tasmanian devil-tux. Yes, that's a penguin beak strapped on with string. He's adorable, but I confess to an uneasy feeling that he's trying to get in amongst the penguins for nefarious reasons. There's something a little too smug about that expression.
Tomorrow I plan to again alternate, this time between the Security, Systems Administration, and Virtualisation and Management miniconfs. For now, tassy-tux and I are going to go and see what happened to our pizza delivery we ordered an hour ago. He looks hungry.
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 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