The only "reasonable" alternative to strengthening laws and adding copy-protection to media is to give the media away, and make money with live appearances and peripheral tangible products, such as lunchboxes and t-shirts.
Why is this the only "reasonable" alternative? (And why is "reasonable" in quotes?)
As far as I can tell, no one has made any kind of effort to actually educate consumers on copyright law.
Re:Had to say it..
on
RMS Turns 50
·
· Score: 2, Insightful
The legal questions surrounding BSD in the early '90s may have had something to do with it too.
So, in other words, just because someone doesn't write a manual--because they don't have the necessary linguistic skills, or because they don't have the time, or they're catatonic, or a plethora of other legitimate reasons--the package is considered broken?
Yes. The Debian package is considered broken until someone, not necessarily the author of the underlying software, creates a man page. It's not a judgement of the underlying software.
If you weren't being sarcastic, you're vastly overestimating the intelligence of the average U.S. citizen. As unbelieveable as it may seem, the people in the U.S. who do vote are probably more intelligent and informed than the average citizen (generally speaking, of course).
...is why anyone would go into a business where they assume that all (or at least the majority) of their customers are thieves. If I were a venture capitalist, that business plan sure wouldn't impress me!
RAID5 is a different story, but RAID5 on IDE is a joke anyway.
Why?
I'm using 3 120GB IDE disks in a RAID-5 configuration (240GB usable) to store my FLAC'ed CD collection. Each drive is a master on one of two Ultra133TX2 cards.
This looks like it might be just what I'm looking for. I've been ripping all of my CDs to Ogg Vorbis and FLAC files, and toting my laptop around to play them is getting old. (Before you ask, I'll get rid of the Ogg Vorbis files when I find a player that can handle streamed Ogg FLAC files.)
Too bad the manuals are distributed in a format that requires a shareware program to decompress. Does anyone know of a free program that can handle these things?
I've always wondered what the legal basis for these BSA "audits" is. IANAL, but I'm 99% sure that there is no legal requirement for you to submit to one of them -- unless you've agreed to in a contract.
My gut tells me that a clause agreeing to such audits in a "shrinkwrap" EULA wouldn't be enforceable, but it would be enforceable if it were in an "enterprise" agreement, or other negotiated contract.
I'm sort of thinking out loud here, but I don't think that this is actually so hard to work around.
I'm pretty sure that the following are both true:
The IPID field's only real use is reassembling
fragmented packets.
It should be very easy to prevent any outgoing
packets from becoming fragmented on the local
network.
If this is the case, can't the gateway simply discard the IPIDs from the originating hosts and substitute its own? Internet hosts should still be able to reassemble any packets that are fragmented between the gateway and their final destination.
Where would the world be in companies had to take into account the needs of the people who love to criticise but never have any plans on purchasing their products?
I thought *real* load balancing used a first-come first-served approach and sent each client request to the least-used server.
That doesn't work for web applications that have some state stored on the web server. For those apps, you need to associate each client with a specific server for the duration of a session. This is usually done by IP address
Re:Tile damage vs autopilot software error.
on
Columbia Coverage
·
· Score: 1
My pet theory is somewhat similar.
Assume that the insulation from the tank did cause some damage to the tiles, damage that would not itself cause a catastrophic burn-through or uncorrectable drag. No one seems to be considering the effect that even minor damage would have on the plasma flow during reentry. Even minor damage has the potential to disrupt the normal flow pattern, creating "hot spots" that then cause more serious damage -- which causes more "hot spots", etc.
Eventually, you get either a catastrophic burn-through or more drag than the ship can handle. It seems like the preponderance of the evidence that we have is pointing to the latter -- too much yaw leading to complete disintegration.
If this really is a possibility, then the shuttle program has a serious problem. Any damage to a tile would have the potential to create such a cascade failure. And even if we had exact knowledge of the condition of every tile after a launch, I'm not sure that either the models or the compute power exist to check for this possibility.
And why the heck have we accepted fuel tanks that shed chunks of insulation during launch, anyway?
Slashdot Mirror
It's just my take on John Ashcroft's America.
Why is this the only "reasonable" alternative? (And why is "reasonable" in quotes?)
As far as I can tell, no one has made any kind of effort to actually educate consumers on copyright law.
Using sector 33 of your boot track!
I've heard bad things.
Yes. The Debian package is considered broken until someone, not necessarily the author of the underlying software, creates a man page. It's not a judgement of the underlying software.
(I believe it's from ancient Knurdic.)
Yes, using an LU6.2 session over Token-Ring.
Why?
I'm using 3 120GB IDE disks in a RAID-5 configuration (240GB usable) to store my FLAC'ed CD collection. Each drive is a master on one of two Ultra133TX2 cards.
Too bad the manuals are distributed in a format that requires a shareware program to decompress. Does anyone know of a free program that can handle these things?
My gut tells me that a clause agreeing to such audits in a "shrinkwrap" EULA wouldn't be enforceable, but it would be enforceable if it were in an "enterprise" agreement, or other negotiated contract.
So how did you acquire your software?
I'm pretty sure that the following are both true:
If this is the case, can't the gateway simply discard the IPIDs from the originating hosts and substitute its own? Internet hosts should still be able to reassemble any packets that are fragmented between the gateway and their final destination.
Am I missing something?
You mean like Red Hat?
That doesn't work for web applications that have some state stored on the web server. For those apps, you need to associate each client with a specific server for the duration of a session. This is usually done by IP address
Assume that the insulation from the tank did cause some damage to the tiles, damage that would not itself cause a catastrophic burn-through or uncorrectable drag. No one seems to be considering the effect that even minor damage would have on the plasma flow during reentry. Even minor damage has the potential to disrupt the normal flow pattern, creating "hot spots" that then cause more serious damage -- which causes more "hot spots", etc.
Eventually, you get either a catastrophic burn-through or more drag than the ship can handle. It seems like the preponderance of the evidence that we have is pointing to the latter -- too much yaw leading to complete disintegration.
If this really is a possibility, then the shuttle program has a serious problem. Any damage to a tile would have the potential to create such a cascade failure. And even if we had exact knowledge of the condition of every tile after a launch, I'm not sure that either the models or the compute power exist to check for this possibility.
And why the heck have we accepted fuel tanks that shed chunks of insulation during launch, anyway?
Which could be the subject of an interesting discussion. Sadly, this is Slashdot.