If your software runs on a generic Un*x system and compiles with e.g. gcc, and is properly written and documented, you shouldn't need to worry much about migrating to a new platform, it'd just involve possibly some code tweaking and recompiling, right?
Most of the time I download a program from Sourceforge, the README file lists about 20 different environments it'll compile in.
However,/. cannot get into the belief that software piracy is *not* a bad thing. Especially when it is commercial piracy (shrink wrapping copied/conterfeit products).
Isn't counterfeiting a *bad* thing? Isn't it directly *stealing* from the publishers by intercepting their *paying* customers and redirecting the money into the counterfeiters' wallets?
Really. If you really insist on getting a pirated piece of software, copy it from a friend or download it. Don't *ever* buy pirated software. You *don't* want to know where the money ends up.
Weird. I could've sworn that just a few minutes ago, the Parent-link had cid=0 in its destination, meaning the Re: Slashdotted already child comment was effectively a root comment.
(This has been happening a lot lately, which is why it didn't surprise me much, and I didn't investigate it much further.)
Actually, if a law isn't enforced, it's unlikely to be removed as it's not being challenged either. If they were really consequent in applying the law, sooner or later someone with really deep pockets will end up challenging it.
Second, the junior engineer there, a year out of UNH, made a point of running over the senior engineers toes many times. No injury, he was walking around fine.
Well, if they provide source, and it compiles into a 3K binary, and the source isn't unnecessarily obfuscated, it's very unlikely there's a trojan inside!:-)
Actually, this doesn't nullify the original poster's concern. Deleting files won't introduce a trojan, but what about this new, patched cd_clink.dll file?
Is it a patched version of the original? Is it a new program that got compiled by the author? (If so, he should open the sourcecode so those concerned could compile their own.) Or does it, as the original poster feared, contain other malicious code?
Make sure you don't EVER use equipment from the company you work for to make anything for your own company, or they might successfully sue you for the IP you created on THEIR machines.
If your software runs on a generic Un*x system and compiles with e.g. gcc, and is properly written and documented, you shouldn't need to worry much about migrating to a new platform, it'd just involve possibly some code tweaking and recompiling, right?
Most of the time I download a program from Sourceforge, the README file lists about 20 different environments it'll compile in.
Now that's future-proofing!
They haven't taken into consideration the existence of AMD CPUs :-)
Well, a font is basically a collection of images, and images are copyrightable.
No, I don't think that is what you were saying. I interpret it as:
Slashdot [users] do not believe software piracy is a good thing.
Where:
Isn't counterfeiting a *bad* thing? Isn't it directly *stealing* from the publishers by intercepting their *paying* customers and redirecting the money into the counterfeiters' wallets?
Really. If you really insist on getting a pirated piece of software, copy it from a friend or download it. Don't *ever* buy pirated software. You *don't* want to know where the money ends up.
No, he's using a P90, so I wouldn't exactly call it demilitarized ;-)
Weird. I could've sworn that just a few minutes ago, the Parent-link had cid=0 in its destination, meaning the Re: Slashdotted already child comment was effectively a root comment.
(This has been happening a lot lately, which is why it didn't surprise me much, and I didn't investigate it much further.)
Apparently, the post disappeared, as do many toplevel posts, for unknown reasons. Maybe it's a bug?
What? You want a pirate copy of RedHat? Go ahead.
Actually, if a law isn't enforced, it's unlikely to be removed as it's not being challenged either. If they were really consequent in applying the law, sooner or later someone with really deep pockets will end up challenging it.
I'm actually better at reading Perl ;-)
You mean they didn't retaliate? ;-)
Well, if they provide source, and it compiles into a 3K binary, and the source isn't unnecessarily obfuscated, it's very unlikely there's a trojan inside! :-)
Well, sue the guy, then!
Actually, this doesn't nullify the original poster's concern. Deleting files won't introduce a trojan, but what about this new, patched cd_clink.dll file?
Is it a patched version of the original?
Is it a new program that got compiled by the author? (If so, he should open the sourcecode so those concerned could compile their own.)
Or does it, as the original poster feared, contain other malicious code?
What if I get my cat to click the Agree button? Although he doesn't seem to interested in the mouse ;-)
Make sure you don't EVER use two tables with names nearly equal, save for two characters exchanged ;-)
Make sure you don't EVER use equipment from the company you work for to make anything for your own company, or they might successfully sue you for the IP you created on THEIR machines.
Last week, some troll moderated five of my score 1 posts overrated.
No, he must've been thinking about those toads ;-)
This page isn't a derivative of Slashcode, it's a derivative of the comments.
E.g. if I burn a piece of wood, the ashes are not a derivative of fire, but of wood.
Well, that does explain that Fritz Hollings link in Lendrick's post ;-)
(No, really, you shouldn't click it.)
He does need alcohol, to power his fuel cells.
The "Introducing the Baen Free Library" article explains precicely what the most vocal Slashdot readers have been saying all along.
Go on, Americans, put your money where your mouth is, and make them a success! That is, if you like their books.
"Thanks for the definition. I, and others, have no ability to look up words. You're insightful." -- AC in the current Schadenfreude poll.