Things went reasonably well, considering it was our first regular meeting in a new location. At one point, we had 12 people present, which was about the limit we could accommodate with the room arranged the way it was. I think I can make room for a few more folks with the tables arranged differently, so we'll try that next time.

I know that this is an incomplete list, but we didn't think about making a record of attendees until after several people had already left. Attendees included:

  • Ben, Bob, Daryl, Frank, Kevin, Ian, Joey, Louis, Robert, Shay

We had three speakers:

  1. Bob talked about the Linux/Unix File-system Hierarchy Standard, which covers file naming and directory structure that developers should adhere to in order that their programs might be more widely compatible.
  2. I showed the base Ubuntu system load that I have been loading on systems for the donation programs. It includes the Edubuntu educational package add-on, as well as a variety of games suitable for lower-end computers. Also I showed a sloth's handful of command-line tricks. Details will be in the meeting minutes on the ColaLUG website.
  3. Ben showed a couple of distributions starting up to various degrees with booting over the network. Unfortunately, the network we were using had some quirks that didn't allow the process to complete. We'll address the network issues before the next meeting.

For further details on the Filesystem standard, look here.

For further details on booting over the network, look here.

The command-line tricks shown included the following:

  1. start up a web server that will serve files from the current directory:
    • $ python -m SimpleHTTPServer

      This script is included with the base python install. It will start a web server on port 8000 which you can access like this: http://localhost:8000/ Or to access from another computer replace "localhost" with the ip address of the computer running the python script.

  2. When you go to execute a command that needs root privilege, and you forget to put "sudo" in front of it, just do this:
    • $ sudo !! This uses a shortcut for the bash history to fill in the text from the most recent command. A more generalized version would be $ sudo !-1 Where you could change the number to go back further to previous commands.
  3. When you are editing text in vi, and you discover that after you've made your changes, you had forgotten to put sudo on the vi command when you first started it, you can do this to save the file in vi:
    • :w !sudo tee % The ! executes the following text and passes the output of the :w command to the tee program, and the % gets filled in with the filename you're editing. So it behaves like a pipe to a privileged tee to save the file.