At last, and article that's actually about Linux. I have blasted Mr. Katz in the past, but not today. Congratulations to him!
And more importantly, good article. There were some real thoughts in there. I felt the same thrill when I first delved into my own config files and wrote my first scripts (that was only a couple of months ago!)
It isn't binding if you haven't read it
on
Toshiba and EULA
·
· Score: 1
I read an article months ago that addressed this. Unfortunately I don't remember where, but there has been a test case.
Apparently there some kind of uniform commercial code, that has to do with implied warranties, the definition of a contract, and I'm sure many other things. Not all states have to agree to it, and not all states do- it's not federal law, simply an initiative by a bunch of states to regularize their business law and facilitate trade.
"Shrinkwrapped" licenses are a violation of this uniform commercial code. Which means that they're not binding in most states.
>He's a writer. He's writing. He's doing what he >does, and there's nothing >wrong with it
On the contrary. He's just writing about his own hardware problems rather and putting a Linux headline on it. This doesn't do anything to benefit Linux, Katz's readers, or anything but his own ego.
If this article is meant to entertain, it has a long way to go. If it's meant to inform, it has even further to go. Katz seems to like to see his work in print, but just because someone published it and many people read it, doesn't make him a good writer. Writing, like Linux, requires discipline. (That's why I have problems with both- but you don't see me posting Linux articles, do you?) This article hasn't been proofread, let alone purified by the crucible of revision.
Once he understands his subject, perhaps by actually installing and running Linux, he can probably write an entertaining and informative retrospective. Until then, he should be taking notes, not posting.
But on the chance that this newbie is legit, be warned: if you don't know what Linux is, you are probably not ready to try it. Yet. Read up on Unix basics and lurk on/. and newsgroups a while first. I would hate for someone's first experience with Linux to be traumatic due to lack of basic knowledge.
If you don't respect the copyright, that's a criminal offense. Can you say, "body cavity search?"
And I would point out that copyright, in principle, is not a problem. Extending copyright to the author's life +95 years is a problem, but one that can theoretically be resolved at the ballot box.
Slashdot Mirror
At last, and article that's actually about Linux. I have blasted Mr. Katz in the past, but not today. Congratulations to him!
And more importantly, good article. There were some real thoughts in there. I felt the same thrill when I first delved into my own config files and wrote my first scripts (that was only a couple of months ago!)
I read an article months ago that addressed this. Unfortunately I don't remember where, but there has been a test case.
Apparently there some kind of uniform commercial code, that has to do with implied warranties, the definition of a contract, and I'm sure many other things. Not all states have to agree to it, and not all states do- it's not federal law, simply an initiative by a bunch of states to regularize their business law and facilitate trade.
"Shrinkwrapped" licenses are a violation of this uniform commercial code. Which means that they're not binding in most states.
>He's a writer. He's writing. He's doing what he >does, and there's nothing
>wrong with it
On the contrary. He's just writing about his own hardware problems rather and putting a Linux headline on it. This doesn't do anything to benefit Linux, Katz's readers, or anything but his own ego.
If this article is meant to entertain, it has a long way to go. If it's meant to inform, it has even further to go. Katz seems to like to see his work in print, but just because someone published it and many people read it, doesn't make him a good writer. Writing, like Linux, requires discipline. (That's why I have problems with both- but you don't see me posting Linux articles, do you?) This article hasn't been proofread, let alone purified by the crucible of revision.
Once he understands his subject, perhaps by actually installing and running Linux, he can probably write an entertaining and informative retrospective. Until then, he should be taking notes, not posting.
But on the chance that this newbie is legit, be warned: if you don't know what Linux is, you are probably not ready to try it. Yet. Read up on Unix basics and lurk on /. and newsgroups a while first. I would hate for someone's first experience with Linux to be traumatic due to lack of basic knowledge.
If you don't respect the copyright, that's a criminal offense. Can you say, "body cavity search?"
And I would point out that copyright, in principle, is not a problem. Extending copyright to the author's life +95 years is a problem, but one that can theoretically be resolved at the ballot box.
I can see it now: I'm on the phone with the PC maker:
Me: "Can I get get it with a SCSI controller?"
Salesman: "Uh, I dunno. But you can get it in blue."