=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/lyrics.html,v retrieving revision 1.57 retrieving revision 1.58 diff -u -r1.57 -r1.58 --- www/lyrics.html 2005/04/20 12:28:43 1.57 +++ www/lyrics.html 2005/09/27 04:31:13 1.58 @@ -20,6 +20,7 @@
+[Order OpenBSD 3.8 or other items] +OpenBSD 3.8 CD2 track 2 is an +uncompressed copy of this song. +MP3 song (4:24 minutes, 8.1MB) +OGG song (4:24 minutes, 5.6MB) +MP3 accoustic version (4:22 minutes, 8.0MB) +OGG accoustic version (4:22 minutes, 5.5MB) + + + + + + +For a multitude of (stupid) reasons, vendors often attempt to lock +out our participation with their customers by refusing to give our +programmers sufficient documentation so that we can properly support +their devices. + +Take Adaptec for instance. Before the 3.7 release we disabled support +for the +aac(4) +Adaptec RAID driver because negotiations with the Adaptec had failed. +They refused to give us documentation. Without documentation, support +for their controller had always been poor. The driver had bugs (which +affected some users more than others) which caused crashes, and of +course there was no RAID management support. Apparently most of these +bugs are apparently because the Adaptec controllers have numerous buggy +firmware issues which require careful workarounds; without documentation +we cannot solve these issues. + +The driver was written by an OpenBSD developer, who cribbed parts +of it from a FreeBSD driver written by an ex-Adaptec employee. But no +public documentation exists, and Adaptec has dozens of cards with +different firmware issues. All of this adds up to a very desperate +development model -- it becomes very hard for the principle of +"quality" to show its head. +
+RAID devices have two main qualities that people buy them for:
+
+Some vendors (or like the above Adaptec case, ex-employee) have +sometimes given us some documentation so that we could write drivers, +so that their devices could support Redundancy. But these vendors have +never given us any documentation for performing Repairs. + +Instead these vendors have tried to pass out non-free RAID management +tools. These are typically gigantic Linux binaries, or some crazy thing, that +is supposed to work through a bizzare interface in the device driver, which +we are apparently supposed to write code for without any documentation. + +And since we refuse to accept our users being forced into depending on +vendor binaries, we have reverse engineered the management interface for +the AMI controllers. + +There is no great "intellectual property" in this stuff, it is all +rather simple primitives. This is all that we need to implement +basic RAID management: +
+The AMI driver needed to support these small primitive operations. +And once we had that, we rely on something else which we know: Almost +all the RAID controllers would need the same primitives. + +Thus armed, we were able to write a generic framework which would later +work on other vendors' RAID cards, that is, once we get documentation +or do some reverse engineering for their products. + +But having been ignored for so long by these vendors, it is not clear when if +ever we will get around to writing that support for Adaptec RAID +controllers now. And Adaptec has gone and bought ICP Vortex, which +may mean we can never get documentation for the +gdt(4) +controllers. +The "Open Source Friendly liar" IBM owns Mylex, and Mylex has told us we +would not get documentation, either. +3Ware has lied to us and our users so many times they make politicians +look saintly. + +Until other vendors give us documentation, if you want reliable RAID +in OpenBSD, please buy +LSI/AMI +RAID cards. And everything + +will just work. +
+And keep pestering the other vendors.
+ |
+ + |
+Narrator:
+Welcome friends to the adventures of Puffiana Jones! + +Brought to you by the good people at OpenBSD! + +Whether braving jungles of wires, oceans of code, or hacking the most +treacherous of crypts, one fish fights for justice. With bravery and +morality like none other, one name rings true. Puffiana Jones, famed +hackologist and adventurer! + +Tracking down valuable artifacts and returning them to the public from +the steely grip of greed. Many a villain has he pummeled, many a vile +vendor has he thwarted, countless thugs, lawyers and kitties abound. + +Join us now in his latest adventure. Hackers of the Lost RAID! + + +Marlus: +Puffy, this mission will be dangerous. + +Puffy: +I'm a careful guy Marlus. + + +Puffy and Salmah: +They're hacking in the wrong place! + + +Beluge: +You will never get the documentation Jones! Ah ha ha ha ha! + +Puffy: +Now you're gettin' nasty. + + +Puffy: +SCSI's, why'd it have to be SCSI's? + +Salmah: +API's, very dangerous. You go first. + + +Narrator: +Through thick and thin our hero persists, until finally, +there before him +lies the answer of the ages. How to get OpenBSD, the world's most +secure operating system, +to communicate with the lost RAID. But alas, he is foiled once again by +the evil Neozis. Again he must chase the truth. Will our hero prevail? + +Triumphant again! Join us next time for the continuing adventures of +Puffiana Jones! + + + |
+ + |
+
+CD 2 track 2 is an audio track entitled "Hackers of the Lost RAID".
+Music composed by Ty Semaka and Jonathan Lewis.
+The Moxam Orchestra programmed and played by Jonathan Lewis.
+Vocals and Lyrics by Ty Semaka. Drums by Charlie Bullough.
+Recorded, mixed and mastered by Jonathan Lewis of Moxam Studios.
+(1-403-233-0350).
+
+
+
+
+