“One of the fun examples among all the copyright fuss is the extreme example of copyright claims made by AT&T some time in the 1980s. It’s the /bin/true program. This is a dummy’ library program whose main function is to make it easy to write infinite loops (while true do …) in shells scripts. The ‘true’ program does nothing; it merely exits with a zero exit status. This can be done with an empty file that’s marked executable, and that’s what it was in the earliest unix system libraries. Such an empty file will be interpreted as a shell script that does nothing, and since it does this successfully, the shell exits with a zero exit status. But AT&T’s lawyers decided that this was worthy of copyright protection.” Three blank lines. Copyrighted. You can’t make this stuff up.
Okay, fair enough, this is worthy of a small chuckle. But it certainly isn’t worthy of the anti-copyright rhetoric in this article.
What’s happened here? It’s obvious: They’ve simply run a script that appends their copyright message to the begining of every file in their source code.
Hardly an unusual thing to do.
The fact that it results in oddities like this is fairly irrelevant. And it certainly doesn’t imply anything about the concept of copyright.
Except the idea of a copyright on a empty file suggest THEY were not doing their due diligence on what they slapped their copyright onto.
This is the sort of thing you expect from SCO not AT&T. Plus it raises questions about how valid their other copyright statements are and companies like SCO can cause you to waste a ton of money because of a careless slip like this.
I love it…
😉
How can they copyright this in 1984 when the Amiga had this command also at that time frame?
Also while I don’t have my Micro magazines with me to check – did not OS9 also have this feature?
It’s a copyright, not a patent.
If you re-implement an existing program, you’re free to copyright your implementation. Obviously that copyright does not prevent others from re-implementing the same software, again.
IANAL, but as I recall (in the UK), a prosecution for breach of copyright won’t be upheld, if the accused can prove their work predates the copyright.
I’m pretty sure they just blanket applied the copyright header to all their files.
It’s not like they thought “Hey, we should copyright true”.
Reminds me of this.
http://www.theonion.com/articles/microsoft-patents-ones-zeroes,599/
But I’m sure someone once said “Hey, we should copyright more”, another well-known Unix command 🙂
Ironically, the FSF answer was to copyleft “less”! 😉
On my system, ‘true’ is a 16K ELF executable. From ‘man true’:
I’m confused now, who holds the copyright for truth? AT&T or FSF?
I’m sure false is copyrighted too.
Even the cp copy command is copyrighted :-p
I’d love to respond to this in a humorous, tongue and cheek fashion, but I’m afraid recent events have made me too aware that what I think is funny and absurd, others might think is a good idea to maximize revenue streams.
Sorry Sir, but I fear your comment re-used some patented expressions without express permission from their holders.
Please contact our lawyer with no delay.
PS: Welcome in 21th century. It sucks, you will love it!
So far, it still looks like it might suck much less than ~all centuries before it…
I was told that Justice hold truth copyright, but I could be getting too old…
Intersting, does adding text to the file make it derivative work? Should any text be considered to be derivative from it then? So protecting empty file with GPL automatically makes everything in the world GPL’ed?
If you take a file and add text to it, the resulting file is a derivative of the original file, yes.
No, copyright does not work like that: copyright protects against copying, but (unlike patents) not against others who independently come up with the same thing.
Can someone come up with the same empty file independently?
You can’t copyright an empty file. You can put a copyright header on an empty file but that means nothing.
In US Copyright law defines a computer program as …
“A “computer program†is a set of statements or instructions to be used directly or indirectly in a computer in order to bring about a certain result.”
Obviously, there are no statements or instructions in an empty file and even if there was just a single line copyright law would probably not protect the work because I could obviously come up with that line independently (which is perfectly ok to do under copyright law).
Edited 2012-01-30 23:38 UTC
Surely this is valid!
“…a set of statements or instructions…”
Does the empty set mean NOTHING anymore?
it’s just rename the GNU true to /bin/not_false or /bin/success
ln -s /bin/success /bin/true
tum dum tsss
1) /bin/true is copyright on all systems, including gnu/linux systems
2) you can’t copyright nothing (an old /bin/true script) so this is likely a doc bug in the old systems
3) your just making shit up to rant about – why don’t you just save the rage for ACTA which deserves it
I don’t see much ranting there, not from anybody you’d be probably addressing as “your just making shit up” – OTOH, when it comes to the larger quotation, I see it comes from an URL containing “humor”…
publishing whole copyrighted program source code in internets… lawers will like this