About Me
My name is Andrew, and I am a LAMP developer with experience in plenty of other Linux areas. I have a pretty elaborate home lab setup, which helps me learn quite a bit in my areas of interest.
I am usually pretty proficient in documenting my labs, research, and general progress. I have it all in a private wiki, called “Intelligence” and powered by DokuWiki. The goal of this public site is to make some of my notes indexable on the ‘net.
Disclaimer
I am sharing these posts publicly with the hopes that they will be helpful to other people, but is provided with NO WARRANTY, explicit or implied. Several articles on this site involve installing operating systems, formatting drives, and deleting files. You are responsible for understanding the commands and procedures.
I understand that some articles may lack context that are outside of the objective of the specific article. If there is a command you don’t understand, please refer to the command’s man page or your favorite search engine.
Some Text Formatting Tips
When reading articles posted here, you will see commands, output, and text files being displayed. I will do my best for format them consistently, described below.
When I show a terminal command, it will look something like this.
[root]$ shutdown -h now
Make note of the user in []…while a lot of administrative tasks are ran as root, some can be ran as (any) user, identified like this.
[user]$ htop
Several commands will be listed in succession like this.
[root]$ ln -s /some/directory /var/www/link [root]$ service apache2 restart [root]$ service nagios restart
I realize that displaying the commands like this makes it difficult to copy and run several commands at once. That is by design, sorry. Run each command individually and understand what it does.
File contents or command output will also be displayed in the same markup, but without the sample bash prompt. Let’s say I want to show some output. It will look like this.
[root]$ tail /var/log/apache2/access.log 192.168.10.245 - - [18/Oct/2013:16:52:16 -0500] "GET / HTTP/1.1" 200 453 "-" "check\_http/v1.4.15 (nagios-plugins 1.4.15)" 192.168.10.245 - - [18/Oct/2013:16:57:16 -0500] "GET / HTTP/1.1" 200 453 "-" "check\_http/v1.4.15 (nagios-plugins 1.4.15)" 192.168.10.245 - - [18/Oct/2013:17:02:16 -0500] "GET / HTTP/1.1" 200 453 "-" "check\_http/v1.4.15 (nagios-plugins 1.4.15)" 192.168.10.245 - - [18/Oct/2013:17:07:16 -0500] "GET / HTTP/1.1" 200 453 "-" "check\_http/v1.4.15 (nagios-plugins 1.4.15)" 192.168.10.245 - - [18/Oct/2013:17:12:16 -0500] "GET / HTTP/1.1" 200 453 "-" "check\_http/v1.4.15 (nagios-plugins 1.4.15)" 192.168.10.245 - - [18/Oct/2013:17:17:16 -0500] "GET / HTTP/1.1" 200 453 "-" "check\_http/v1.4.15 (nagios-plugins 1.4.15)" 192.168.10.245 - - [18/Oct/2013:17:22:16 -0500] "GET / HTTP/1.1" 200 453 "-" "check\_http/v1.4.15 (nagios-plugins 1.4.15)" 192.168.10.245 - - [18/Oct/2013:17:27:16 -0500] "GET / HTTP/1.1" 200 453 "-" "check\_http/v1.4.15 (nagios-plugins 1.4.15)" 192.168.10.245 - - [18/Oct/2013:17:32:16 -0500] "GET / HTTP/1.1" 200 453 "-" "check\_http/v1.4.15 (nagios-plugins 1.4.15)" 192.168.10.245 - - [18/Oct/2013:17:37:16 -0500] "GET / HTTP/1.1" 200 453 "-" "check\_http/v1.4.15 (nagios-plugins 1.4.15)"
If I want to demonstrate changes to a file, I will show a command to edit the file in vim. You can replace it with the editor of your choice.
[root]$ vim /etc/network/interfaces
If I want you to add content to the file, it will look like this.
auto eth0
iface eth0 inet dhcp
post-up iptables-restore < /etc/iptables.up.rules
auto eth1
iface eth1 inet static
address 192.168.15.254
netmask 255.255.255.0
network 192.168.15.0
broadcast 192.168.15.255
Refer to the context of the article to see if I want to add those lines, delete those lines or replace the content of the file with these lines.
Latest Projects - Likely Future Posts
My latest projects have included LTSP, Debian preseed, Puppet, Kickstart, and KVM; with a side of Git (I know, I'm behind) and vim.