Actually, I have one more suggestion.  For those using a laser printer (B&W type) it would be good to have another indicator of the dangerous commands.  Keep the color, but add something like a leading * or => or boldface or a different font.  Anything easily discernible without color.

On Thu, Jul 7, 2011 at 9:12 AM, Dennis Kibbe <dennisk@mesacc.edu> wrote:
I want to thank everyone who responded and let you all know that I just
uploaded the latest revised copies to S3.

https://s3.amazonaws.com/moodle_data/Linux+Commands.odt
https://s3.amazonaws.com/moodle_data/Linux+Commands.pdf

You may not see your suggestions in there yet, but I've made note of
every one (only had time to respond to a few) and will use as many as I
can find room for. Even if they don't show up on the sheet there is a
good chance I'll use them in class.

Special thanks to Joseph for the SOX PCI info. I do have student set
sudo on CentOS and I can now show them why in the real world they might
need an audit trail.

Now I need to put this aside and move on to getting AWS Route 53 set up
for Sahuaro.us.

Thanks again,

Dennis
--
Adjunct Faculty
Linux Operating System and System Administration
Business and Computer Information Systems
Mesa Community College

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss



--
Dazed_75 a.k.a. Larry

The spirit of resistance to government is so valuable on certain occasions, that I wish it always to be kept alive.
  - Thomas Jefferson