I've been experimenting with XML and XSLT lately. I've taken the examples from the Gentoo Linux web site and adopted my own XML schema. I plan to use it for internal department documentation.
I still have qualms on whether it's easy to use. Will the system administrators actually use the XML format, or will plain-text be more efficient? Given, the XML format will offer more flexibility in the future, but sometimes, it's easy to waste time with formatting XML.
Just my own two cents...
I taught two classes this week - "Introduction to UNIX". A good number (40) of people showed up and asked many questions. I covered the basics of the filesystem, directory navigation, and file maintenance; I was even able to explain permissions and the concept of indoes. I hope their heads weren't spinning by the time I was done.
I really enjoying teaching people the concepts of computing. Perhaps, this is why I'm great at creating documentation. I think the best way to encourage the open software movement is through education and positive influence. I certainly woudn't have known about Linux and the GNU movement if it hadn't been for that fateful day with my mentor.
There's a few projects that I would like to work on this week. I'd like to get an updated version of SeminarSite out before next month. A lot of people have made certain requests and I'd like to implement all of them and release the product. People can download the CVS version if they wish, I suppose.
Here at the School of Computer Science, we have a neat little system called the 'Depot'. The Depot comprises of various mounted drives on a multitude of servers and architectures. Each directory in the Depot is a symbolic link pointing to compilied binares on an unmounted disk. When a user requests this particular directory, the drive is automounted and the binaries for the specific architecture is retireved. The depot automatically mounts the appropriate software package in acordance to the architecture of the machine. This saves lots of time for the lazy system administrator. We don't have to install non-standard packages of software on every workstation and we can make updates from a single host.
The documentation for the depot system is in a state of disarray. I have been assigned to the task of sorting it out last year, but it has fallen downhill since then. I made a generic information file to be customized and inserted in each directory. A nightly script mounts each directory and retrieves the information and consolidates it into a single file. (I probably should use XML someday.) A couple PHP scripts interprets this data into easily navigatable web pages. I call it "DepotDoc".
Oh well, off to work I go!
No Hawaiian shirts today - it's the coldest day in Miami this year at thirty-seven (37) degrees. Because I'm from New England, I'm loving every minute of it while I watch my peers shiver.
One of my projects at work was to install and setup the Snort Intrusion Detection System. I wrote a whitepaper on it a few months ago. I also set up the amazing PHP project ACID to translate the information. My current project is to research and implement Bro into our network. Bro is a similar NIDS like Snort, but it's more powerful due to it's regular expression engine.
This is my first entry for Advogato. Recently, I finished a rather challenging data structures assignment which implemented circular doubly linked lists in Java. After a few hours, I've realized that the scope of my variables were incorrect, and everything worked.
My current open source projects listed below.
Keep up with the latest Advogato features by reading the Advogato status blog.