New Year Resolutions?
The time has come to gulp down the pumpkin pie and before you load up on Turkey, Ham, Roast Beef or a nice Vegetarian cuisine, to consider your goals and objectives for the year. Notice I didn't say resolutions. Of course, if you start off the resolution sentence with "I resolve to..." then that will work just fine along with your goals and objectives.
I'd like to share some of mine and see if you have any that fit yours. Then, I would like to invite the community to add any, one wishes to share. Here goes. I want to:
1. Write three howtos to benefit Linux users.
2. Make more money than I have since 2001.
3. Work only 40 hours a week at my day job.
4. Learn more about load balancing Apache web servers.
5. Incorporate an increased knowledge of load balancing into my work.
6. Contribute significantly to an under documented project.
7. Take a two week vacation out of the US.
8. Covert users of other operating systems to Linux desktops and servers.
9. Write positive comments.
10. Learn an open source programming language used in web services.
Now, some resolutions. I resolve to:
1. Stop criticizing comments people write in forums, after articles and on mailing lists.
2. Notice arrogance and bite my tongue figuratively.
3. End vitriolic comments.
4. Focus my support of Linux and open source projects to select ones and stick with it rather than hop from project to project.
5. Allow people to learn for themselves rather than jump-in and tell them how to do something.
6. Stop reciting my resume to people who disagree with me.
7. Treat others with respect and admiration even if they behave in ways I don't like.
8. Keep a job for a minimum of one year.
9. Not to leave a job if I don't like the technology they use.
10. Act appropriately toward people who think Linux is an air conditioning company.
I'd also like to get one of the vintage wrist watches I take apart to work when I put it back together. That's an important short-term objective. It has to do with expanding my horizons and stepping out of compulsive IT work. I think it gives me an "out of the box" perspective. Tinkering often leads to a break through even if one doesn't have an objective in mind.
What do I think of goals, objectives and resolutions? I believe that setting at the beginning of the year has some futility associated with it. Perhaps working with one of each in January might work. Then during the year, pick another and start working on that one.
I believe it's a good idea to write them all down today, so I have a record of them. Then as the year progresses, I can reflect on the things I considered when I wrote them. I often scratch several out and add another one or two. If I make progress on a couple during the year, I consider myself luck. At least I don't smoke now. That was a resolution I achieved twelve years ago. I think I keep that one for the rest of my life.
Here's looking at ja!
Happy New Year!
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!
- SourceClear Open
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Tech Tip: Really Simple HTTP Server with Python
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
- 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