GPL Violation, Microtest's DiskZerver
Slashdot reader brtb reports:
About a year ago my employer, a local high school, purchased a couple MicroTest "DiskZervers," network-attached-storage boxes designed to cache CD images for LAN usage. We were mainly Netware-and-Win95 at that time, and the Zervers performed flawlessly in that configuration. But problems began when the district IT department made the decision to switch us over to an NT-domain setup. The Zervers, even with their advertised "Domain Integration" support, didn't seem to like this too well, so I dug a little deeper... imagine my surprise when I found out the boxes are actually embedded 486's with Linux and a whole slew of other GPL'ed software, mentioned nowhere in the manuals or on the accompanying software CD.
Apparently, Microtest (NAS division since sold to XStore) put together a mess of GPL software - a modified Linux kernel 2.0.27, Samba 1.9.x-ALPHA (!!!), the MARS_NWE netware emulator, and GNU C libraries (libc5), among others, stuffed them on a flash chip in a drive-bay-size embedded 486-based computer, and sold it as their "DiscZerver" product line. They also used some non-GPL packages, including Apache and Netatalk (macintosh server). Nothing wrong with their methods, but there's plenty wrong in their implementation.
The web interface and proprietary Windows front-end, the only given methods of configuring the device, refer to the various services generically, like "Web server," "SMB server," "NCP server," etc. - there's no mention anywhere, even in the manual, of the actual programs being used. Of course along with this is no accompanying source code or even the offer to provide any, as the GPL requires.
I can't even get any useful tech support from this company, much less someone to ask about getting the source code for the software and whatever modifications they made, which includes a flash file-system driver ("yaffs" - I think MicroTest wrote it, as I can't find any info on it) for the kernel. I did manage to hack out the hidden-from-customers root password; with that I found a shell prompt (Stand-alone Shell v1.0 - GPL? dunno) which only increased my determination as I could see exactly what programs they managed to steal, strip out identifying info, and use without credit.
I did contact the FSF with the limited information I had before I got shell access, and they did confirm the existence of a GPL violation, but were unable to do anything specific as they do not hold copyright on any of the programs I knew of at the time (and actually suggested I post to Slashdot to get some answers). xStore itself has not returned my emails or phone call. I have another e-mail in to the FSF, now that I know the machine includes glibc1.
So, right now I have a nice little piece of hardware, some mis-compiled (I think) software, and no idea what to do next. At the very least, I learned that my usual policy of disassembling and analyzing any new hardware we get is the right one; of course that doesn't help all the LAN users that need access to these CDs. I'd be happy if I could just get the code so I can fix SMBd/NMBd to work properly. I've thought about trying to make my own really-small distro to load on, but it's not really worth my time - I could just load the cached CD images (thankfully just standard .ISO's) off the Zerver's CD-storage hard drive into my other Linux server, compile and install Samba correctly (works great if you do it right) , and get on with life... but I really shouldn't have to do either. Any ideas?
GPL is moot when it comes to Embedded Systems!
You're not supposed to access the software on
these directly! Even Stallman admits as much
(check out the FSF philosophy pages)
If someone puts Linux on a toaster, he doesn't
have to supply you with source!
First:
... but [FSF] were unable to do anything specific as they do not hold copyright on any of the programs I knew of at the time ...
MicroTest could have done things simple just by printing a Readme-first documet stating that their system is built upon GPL'd software and printing the links to ftp-sites where it could be downloaded. Should sombody ask for the sourcecode it wouldn't be very hard having an ISO-image laying around with all the source on it. (One could say MicroTest acted a bit stupid.)
Second:
I would like to see the next version of the GPL including a clause granting FSF the right to sue on behalf of the copyrightholder(s.)
Look a monkey!
Their license states explicitly that THEY own all of the software on the device and that you may not attempt to reverse engineer the product.
So I guess they are saying that they wrote their own OS with utilities supporting all of the same file sharing mechanisms that Linux is known to support and that they own the whole ball of wax. That's a good one.
Sorry, I'd have cut and pasted the license in here but it was in PDF format.
-josh
And I'd be a Libertarian, if they weren't all a bunch of tax-dodging professional whiners.
Berke Breathed
That's a terrible analogy, and does not fit the situation at all. I can read GPL code learn how to do something and then write my own versions that do not use GPL code at all and it's free of the license. USING the code in my product is a completely different situation.
I'm the big fish in the big pond bitch.
Is the GPL parasitic and restrictive? Yes! So what?!?!?! If you don't like GPL software, don't use it!
Have you written any free software? If not, then you really don't have any right to criticise the GPL. The GPL is designed to protect both the creators and the users of free software evenly.
And the men who hold high places must be the ones who start
To mold a new reality... closer to the heart
If you write a book on fishing, and after reading it I invent a new maneuver that allows the catching of a larger type of bass, I shouldn't be forced to tell you how I did it.
With the GPL, you could invent a new way of fishing without telling anybody (remember, only redistribution is restricted). Your example should read:
"I write a book on fishing and give it to you for free, and after reading it you invent a new maneuver that allows the catching of a larger type of bass. You are *not* allowed to create a new book by copy-pasting my text, add your technique and sell it without giving me the same rights I gave you."
I think that's reasonable. You are also (under the GPL) allowed to write a new book which is equivalent to mine (but without copying mine verbatim).
Opus: the Swiss army knife of audio codec