It is official; Scientists confirm: *saurs are dead
One more crippling bombshell hit the already beleaguered *saur community when scientists confirmed that *saur population has dropped yet again, now down to less than a fraction of 0 percent of all animals. Coming on the heels of a recent MIT survey which plainly states that *saurs have lost more population, this news serves to reinforce what we've known all along. *saurs are collapsing in complete disarray, as fittingly exemplified by falling dead last in the census of all animals.
You don't need to be a Kreskin to predict *saurs's future. The hand writing is on the wall: *saurs face a bleak future. In fact there won't be any future at all for *saurs because *saurs are dead. Things are looking very bad for *saurs.
Stegosaurus is the most dead of them all, having lost 100% of its core breeding population. The sudden and unpleasant departures of long time stegosaurus breeders Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: Stegosaurus is dead.
Nothing short of a miracle could save them at this point in time. For all practical purposes, *saurs are dead.
You know, I filter the string "ImageReady slices" in my incoming email, and it's never hit on anything that isn't spam. I never knew it was an Adobe product, I always thought it was some sort of spam program.
Well if it's dead, and the data isn't very important, time for drastic measures.
It sounds like a mechnical problem, a head crash that went as far as pulling the head right off the arm, and wedging it between the platters, or the bearings died.
Freezing it won't hurt anything, but beware condensation when you take it out of the freezer.
I'd recommend getting in the cleanest room you can, preferably with high humidity to reduce dust.
Take off the cover and look for metal shavings in the inside. If there are no metal shavings visible, then the bearings have gone, and you might as well give up.
If there are metal shavings, then there's a chance you can recover data. Try to move the platters/heads, if the heads aren't in the landing zone, then this WILL damage the platters (a little).
If the top head is the bad one, you are lucky. Try to rig it in a way so the platters can turn again. If it's a head between other platters, you are going to have to pull the platters out, which is not easy at all.
Anyway, if the data is worth more than $1000 to you, then send it to a professional recovery service. I don't think an electronics board swap will help anything in your case. It would only waste time and money.
Doing any and all of the above things may damage the disk more than it already is. You've been warned.
The problem might come when GPL source is being sent with code produced from a proprietary app. This code could be pretty intermingled, and sure doesn't comply with the GPL, since the user never knows they had any rights under the GPL, if indeed they did.
Well what about what lots of people do, send email through their ISPs web server, and use the email address of where they get mail, which may not be their ISP?
I do this all the time, I send mail through whatever SMTP server for the ISP I'm currently connected to, but my email address is always the same, and the email domain is my hosting provider, which is not my ISP.
They better not fuck things up for people that don't always use their ISPs email address, or have more than one ISP.
Heh, I've had a running argument with my wife about whether it would damage a baby to put it in a microwave for 1 second. (This discussion came about after a news story of a schitzophrenic woman who microwaved her baby to death).
I'm a ham radio guy so I know a little about RF. I argue that it wouldn't cause any damage, the magnetron would barely get warmed up in 1 second, and even if you assume it generates full output for that second, I still don't think it would damage anything.
Her sister who is a doctor says "there might" be damage. The only think I could think of would be retinal damage.
BMW doesn't do it on all their cars either. I know my friend's BMW is electric only.
One annoying thing BMW does do is that if you push the lock in manually on the door, there's no way to pull it back out! Took me a minute to figure out that pulling on the door opening level automatically unlocks the door the first time you pull it, then the second time it opens the door.
If inflation is a tax, then someone as apparently liberal as yourself should like it a lot!
It's a tax on those who have money saved and invested, and a refund to those who are in debt. Robbing from the rich and giving to the poor! It's like an invisible social program!
I don't think error messages could ever be considered under this problem, because it would be very difficult to argue an error message was "code", in any way.
Regarding the DHTML thing, it gets fuzzy. The lines between executable code and data are fuzzy. Is HTML a programming language? Most would say no.
But postscript, something that is often considered "data", is most definitely a programming language.
I think the best thing would be for people that create GPL apps that might generate pieces of static source code in output, just make an exception to BSD style license any outputted code. The wording could get sticky though, if you put in an exception, then someone creates a derivative work that just sends the entire GPLed source to stdout, could it then be BSD licensed? You'd have to be careful.
As I said, this is much more of a problem with scripts, than with compiled works.
A company being able to use open source software without fear of copyright violation should be a given, since the GPL places no restrictions on mere use.
The problem is coming when mere use could also constitute redistribution of GPL covered code, because of some output generated that gets sent down the wire to the client, output that may be part of the source code of the app itself (especially with scripts).
I think it's obvious that the spirit of the GPL is to not require everyone who uses the software to be bound to it. The GPL intends to cover only redistribution.
The GPL works best with compiled software, because the separation between code and binary and input and output are clear. In a script that generates HTML, much of it copied verbatim out of the "source", whether this is distribution of GPL software or not is not clear at all.
If it is distribution, then there's no way to merely use the software without complying with the GPL.
My bank has never said to me that I can come in and demand gold (or anything else) for my cash. If your bank has, I suggest you find a less scammy one.
Are you sure you are both talking about the same kind of ASP here? (Active server pages vs Application service provider)
The way I understand the problem, a GPL server-side app might send out pieces of itself, either in the form of static HTML which is GPLed, or snippets of what could be considered executable code (Javascript, etc), which are also GPLed.
If this counts as distribution of GPLed code, then many people who make modified works of GPLed server-side web apps might be in violation of the GPL by not distributing the rest of the source. It seems to be a gray area right now.
It's really not a good idea to leave out the "or higher" part.
If they GPL is somehow found to be invalid, any code that is GPL 2.0 only licensed will automatically become undistributable. Those projects will die instantly, and any projects that are based off them will die too.
If the FSF has to, they could make an emergency higher version of the GPL, to circumvent a court ruling that struck down part of the existing GPL, or a court made a ruling that the current GPL means something other than the intention.
If the FSF comes out with a new version, you and your users are still free to use the older versions of the GPL.
Slashdot Mirror
Since no one who's replied has answered your question, instead choosing to talk about unrelated things, I have to say that I'd go with the Bitscope.
Visit #electronics (our electronics+open source channel) on irc.freenode.net if you want to discuss.
It is official; Scientists confirm: *saurs are dead
One more crippling bombshell hit the already beleaguered *saur community when scientists confirmed that *saur population has dropped yet again, now down to less than a fraction of 0 percent of all animals. Coming on the heels of a recent MIT survey which plainly states that *saurs have lost more population, this news serves to reinforce what we've known all along. *saurs are collapsing in complete disarray, as fittingly exemplified by falling dead last in the census of all animals.
You don't need to be a Kreskin to predict *saurs's future. The hand writing is on the wall: *saurs face a bleak future. In fact there won't be any future at all for *saurs because *saurs are dead. Things are looking very bad for *saurs.
Stegosaurus is the most dead of them all, having lost 100% of its core breeding population. The sudden and unpleasant departures of long time stegosaurus breeders Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: Stegosaurus is dead.
Nothing short of a miracle could save them at this point in time. For all practical purposes, *saurs are dead.
Fact: *saurs are dead
You know, I filter the string "ImageReady slices" in my incoming email, and it's never hit on anything that isn't spam. I never knew it was an Adobe product, I always thought it was some sort of spam program.
I see you still are stuck in the Windows world, where you only have one desktop.
It's easy enough to make a new desktop and put the Gimp on it by itself.
Well if it's dead, and the data isn't very important, time for drastic measures.
It sounds like a mechnical problem, a head crash that went as far as pulling the head right off the arm, and wedging it between the platters, or the bearings died.
Freezing it won't hurt anything, but beware condensation when you take it out of the freezer.
I'd recommend getting in the cleanest room you can, preferably with high humidity to reduce dust.
Take off the cover and look for metal shavings in the inside. If there are no metal shavings visible, then the bearings have gone, and you might as well give up.
If there are metal shavings, then there's a chance you can recover data. Try to move the platters/heads, if the heads aren't in the landing zone, then this WILL damage the platters (a little).
If the top head is the bad one, you are lucky. Try to rig it in a way so the platters can turn again. If it's a head between other platters, you are going to have to pull the platters out, which is not easy at all.
Anyway, if the data is worth more than $1000 to you, then send it to a professional recovery service. I don't think an electronics board swap will help anything in your case. It would only waste time and money.
Doing any and all of the above things may damage the disk more than it already is. You've been warned.
The problem might come when GPL source is being sent with code produced from a proprietary app. This code could be pretty intermingled, and sure doesn't comply with the GPL, since the user never knows they had any rights under the GPL, if indeed they did.
How would it be different, if it could "run exactly the same thing Intel chips can", isn't that the definition of compatible?
Well what about what lots of people do, send email through their ISPs web server, and use the email address of where they get mail, which may not be their ISP?
I do this all the time, I send mail through whatever SMTP server for the ISP I'm currently connected to, but my email address is always the same, and the email domain is my hosting provider, which is not my ISP.
They better not fuck things up for people that don't always use their ISPs email address, or have more than one ISP.
Yeah, and what if spinning quickly will make you fly?
Or... Or. What if mixing up Coke and Pepsi will make an intoxicating drink??
Well?????
BTW- The FBI wouldn't handle any "real" terrorists, only internal threats.
They claim to have sold a handful to unnamed companies.
I think Darl said something like "we solicited 14 companies and over 40% of them licensed it" So I guess that means about 5 companies.
Heh, I've had a running argument with my wife about whether it would damage a baby to put it in a microwave for 1 second. (This discussion came about after a news story of a schitzophrenic woman who microwaved her baby to death).
:)
I'm a ham radio guy so I know a little about RF. I argue that it wouldn't cause any damage, the magnetron would barely get warmed up in 1 second, and even if you assume it generates full output for that second, I still don't think it would damage anything.
Her sister who is a doctor says "there might" be damage. The only think I could think of would be retinal damage.
So what do you think?
You just need a SuperTech Gonad Shield!
(Scroll to bottom of page)
BMW doesn't do it on all their cars either. I know my friend's BMW is electric only.
One annoying thing BMW does do is that if you push the lock in manually on the door, there's no way to pull it back out! Took me a minute to figure out that pulling on the door opening level automatically unlocks the door the first time you pull it, then the second time it opens the door.
If inflation is a tax, then someone as apparently liberal as yourself should like it a lot!
It's a tax on those who have money saved and invested, and a refund to those who are in debt. Robbing from the rich and giving to the poor! It's like an invisible social program!
I don't think error messages could ever be considered under this problem, because it would be very difficult to argue an error message was "code", in any way.
Regarding the DHTML thing, it gets fuzzy. The lines between executable code and data are fuzzy. Is HTML a programming language? Most would say no.
But postscript, something that is often considered "data", is most definitely a programming language.
I think the best thing would be for people that create GPL apps that might generate pieces of static source code in output, just make an exception to BSD style license any outputted code. The wording could get sticky though, if you put in an exception, then someone creates a derivative work that just sends the entire GPLed source to stdout, could it then be BSD licensed? You'd have to be careful.
As I said, this is much more of a problem with scripts, than with compiled works.
I believe the standard you are looking for is "reasonable suspicion", to merely stop and request ID.
I do think they would need probable cause to actually detain someone against their will.
IANAL.
Have you ever asked a blind man to describe what "red" look like?
That's the answer to the guy who trotted out the "if you have nothing to hide" line.
They can do it because no one fights back.
Yes, that's exactly the issue. I hope the FSF does something we can all live with.
That is very much not clear.
A company being able to use open source software without fear of copyright violation should be a given, since the GPL places no restrictions on mere use.
The problem is coming when mere use could also constitute redistribution of GPL covered code, because of some output generated that gets sent down the wire to the client, output that may be part of the source code of the app itself (especially with scripts).
I think it's obvious that the spirit of the GPL is to not require everyone who uses the software to be bound to it. The GPL intends to cover only redistribution.
The GPL works best with compiled software, because the separation between code and binary and input and output are clear. In a script that generates HTML, much of it copied verbatim out of the "source", whether this is distribution of GPL software or not is not clear at all.
If it is distribution, then there's no way to merely use the software without complying with the GPL.
My bank has never said to me that I can come in and demand gold (or anything else) for my cash. If your bank has, I suggest you find a less scammy one.
Writing code is easy. Reading someone else's code is the real test.
I stick to Bash for most things involving text processing.
Mandows... The Freshmaker!
Are you sure you are both talking about the same kind of ASP here? (Active server pages vs Application service provider)
The way I understand the problem, a GPL server-side app might send out pieces of itself, either in the form of static HTML which is GPLed, or snippets of what could be considered executable code (Javascript, etc), which are also GPLed.
If this counts as distribution of GPLed code, then many people who make modified works of GPLed server-side web apps might be in violation of the GPL by not distributing the rest of the source. It seems to be a gray area right now.
It's really not a good idea to leave out the "or higher" part.
If they GPL is somehow found to be invalid, any code that is GPL 2.0 only licensed will automatically become undistributable. Those projects will die instantly, and any projects that are based off them will die too.
If the FSF has to, they could make an emergency higher version of the GPL, to circumvent a court ruling that struck down part of the existing GPL, or a court made a ruling that the current GPL means something other than the intention.
If the FSF comes out with a new version, you and your users are still free to use the older versions of the GPL.