That is a nice peace of documentation, I worked with many 1500's but NT(3.51) installs. The newer machines (hmmm) like my 2500 uses a CD (smartstart) to boot and configure the hardware and Raid. I'm going to install Linux on my 2500 this weekend (first time on the Proliant platform) I'll document it as I go and attempt to match Joel's Document. I just had a thought about this type of Document. Should the TCLUG have some sort of document library for this kind of work people have done. Include the software for performing work and any trouble shooting along the way. Shell scripts would be an excellent addition to the library as well. Going a step farther I would keep it as simple as possible HTML and a downloads. A simple standard for document format would be good. Each person would keep the documents/downloads on their own website with the TCLUG website pointing to the documents/downloads. This way disk space wouldn't be an issue for TCLUG. Each document and the software could be added to a central repository and burned to CD. A distributed document system to refer to when things don't work as planned. A place for newbe's like me to go for information. This would build a library of information that would be invaluable to the community. Loosing documents like this would be a terrible thing to happen. I know I've deleted some things that I wish I had. Sam. Joel Schneider wrote: >On Mon, Aug 25, 2003 at 11:32:57AM -0500, Adam Maloney wrote: > > >>This is a rant. I'm not looking for help, just an outlet to vent. Please >>don't reply with fixes >> >> > >I once went through the entertaining (?) experience of setting up linux >on an old Compaq ProLiant 1500. The process ended up being a bit >complicated so I documented it on a web page: > >http://www.joelschneider.net/compaq_proliant_1500_debian_potato.html > > > _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list