How do you test Linux?
How do you build your own distribution?
How do you build code to run on another machine?
In this lecture, I plan to answer these questions by introducing the theory and practice of cross compilation and virtualization, as well as discuss the ingredients and questions to ask for creating your own Linux distribution. All of the examples use free, open source software (FOSS) that is readily available in many existing distributions. But, since Linux is very much a hobbyist community, this lecture will focus on a doing-it-yourself (DIY) approach (this doesn't have to mean _by_ yourself).
On Saturday, 11 January 2014, the regular monthly meeting of NoVALug started, as usual, with an interactive monologue by Greg, bringing us up to speed on various current events topics. Most notable was the recent establishment of an association between Red Hat and CentOS. Greg filled us in on his take on the “What's in it for Red Hat?” side of the discussion, with input from Peter and others in the group. Then we got on to the main topic of the meeting – Inkscape.
Over the next few months, we'll be upgrading the NoVaLUG website to Drupal 7. As part of that update, we'll be looking at the everythign from the look and feel of the site to the features on the site to integration with other services.
As part of that update, we'd like some feedback from you, the NoVaLUG community, about what is good about the site and what is not so good, what you find useful, and what you find to be lacking.
This survey has five free response questions. You may answer any or all of them.
We are looking for a logo. Please submit your ideas. If you aren't artistic, talk with a friend who is. We will use the logo on the website and make it available for purchase on items (at cost).
One of our junior sys admins told me he was trying to figure out how to modify his monitoring script during maintenance windows (the monitoring script is called automatically by the monitoring agent on the box.) I told him to use a "stop file."
At or near the top of your script (a simple bash script,) put a block like this:
if test -f /tmp/do_not_run
Then, during maintenance windows, create the /tmp/do_not_run file and the script will simply exit without attempting to perform any actions against the system. When the maintenance window is over, remove the file and everything goes back to normal.