Peter Larsen will talk about boot loaders on Linux. We'll cover how booting works, how the boot loader fits into this process, and cover how to do basic customization and diagnostics on the boot loader.
We'll focus mainly on the legacy boot mode, but will shortly cover uEFI booting too (the default on "newer" hardware).
I have a lot of respect for AMD because over the years they have come up with a number of true innovations, leaving Intel (sometimes the whole industry) to play catch-up for a bit. The x86-64 architecture (a.k.a. AMD64) provided backwards compatibility to the 32-bit x86 instruction set when Intel was ready to move on with Itanium. AMD followed up by baking the memory controller in the CPU. When paired with HyperTransport, this gave multiple CPU servers significant performance enhancements while still providing memory coherency.
Their current line of processors -- dubbed APUs -- merge the CPU and GPU into a single chip, trying to leverage that integration to better performance. Up until now, the two might live on the same silicon, but there was still a high wall between them. In the latest generation, codenamed Kaveri, AMD has merged the GPU and CPU in a tightly unified architecture called HSA.
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.