Interesting, I've never seen that at all.. and I've been using different builds (nightlies and stable) for quite some time. Since people also seem to be saying that a refresh fixes the problem, there must be some rather odd interaction happening there.
Of course, the bug report mentions that the problem is fixed in the trunk, so it may be gone next release...
It's pretty irresponsible to bring up your corporate servers before those of your clients.
1) It's quite possible that the corporate servers didn't need special attention to bring up... or, didn't need large amounts of attention.
2) Where are customers going to go for updates, tickets, etc? Most likely, the corporate servers. Given the choice between the phone ringing off the hook while trying to concentrate on disaster recovery and having other forms of communication flashing around on the network, I'd pick the second any time. Unless there are large numbers of people sitting around to answer phones who would be absolutely useless in the recovery efforts, it's far more effecient to rely on text communication (and much easier to sort the useful people out from those who just want an ETA every five minutes). There's nothing worse for productivity than being forced to stop every five minutes to spend ten minutes convincing someone that you're working on problems as quickly as possible (and no, there isn't an eta, because it's likely something else is broken that won't be visible until the current thing you're working on is fixed..)
Oh, and I love how you say you're not qualified to comment, and then proceed anyways...
That is why he has already delegated authority to other people in the development process. There are a LOT of things these people could have done rather than send the email directly to Linus.
I dunno about you, but the last thing I would want is a legal climate where security bugs are punished through the courts. What's next.. coder's malpractice insurance? What will that do to OSS?
Much safer to get the word out that Microsoft is bad at handling these issues, and that their EULA specifically protects them from any responsibility. Luckily, they seem to be doing a very good job of doing that on their own..
tiasi54ffcb44334bcvxw53ezz3wr@gmail.com ,r as in really,
Wow, not only do you make it really difficult to memorize, you also spell it wrong when you give it out! Pure genius! I'll bet you never have to worry about any mail!
If some idiot decides to bring in his warezed copy of Sound Forge because he doesn't want to go to the trouble of putting in a purchase order for the real thing, does that make Microsoft complicit in piracy?
Try using that logic in a BSA audit and see how far it gets you.
Why for example is it a GOOD idea for AVAST's real time scanner to tell me it found a virus and then not doing anything about it? It knows it's there, kill the damn thing. Don't give me a message popup from the system tray telling me you found it.
Two words for you: False positives.
It's bad enough when an AV scanner accidently triggers and displays a message about a valid program. It would really drive people nuts if it kept immediately deleting valid programs as soon as they were installed...
I think the question is... how many con artists out there are going to take the time to set up an identity that people will buy from, pay the money in bandwidth fees, design all the rest of the stuff that goes into the 'identity' of a software publisher, and then risk it all and much, much more by blatently violating copyright laws. All it takes is for one of the recipients to notice the similarity to cause trouble.
Have you looked at the penalties for copyright violation lately? Now tack on fraud on top of that.
You asked how many people have succesfully been sued... the answer is very few, but the reason is that almost every discovered violator has quickly caved in when faced with the penalties of what they're doing.
As for identifying violations.. the logistics of it become much more reasonable when you realize how few applications of each kind there actually are out there. In your example... there are only so many CAD applications available, and any serious buyer of a CAD program most likely has experience with several.
1. A small, light object will also have a much smaller surface area for the beam to push against, so it will pick up much less accelleration (the article mentions that the speed applied to the ship is very dependant on the width of the beam).
2. The beam is only planned to be on for a short time.
3. Any items wandering into the beam will have a velocity of their own to start with, which would cause it to travel off at an angle. The further away the craft is, the lower the chances of anything being able to enter the beam at the proper angle and speed to be pushed towards the ship.
Well, in preview, that first "here" was a link for this. Not sure what happened to it, but now I'm thinking this might have been a better choice anyways.
It does allow a spammer to change their nameserver real fast, however.
I've seen one spammer who liked to set up a redirector on an innocent-looking account on a server, then set the DNS that was under his control to point to it for short periods of time while sending out loads of spam. The redirector would remove itself after the time was up. Took months to get SPEWS to remove the listing for one server that he pointed the domain to for 15 minutes, even though the server was shut down minutes after complaints came rolling in and not brought back up until the reason was figured out.
Now, since SPEWS will sometimes blacklist nameserver IPs as well...
There's also SCO's ability to threaten people who don't make all the certifications demanded in the letters they sent out to all their customers... the DC case pretty much killed that one, though SCO is still able argue that they should have gotten an answer in 30 days or less if they want to. *snicker*
Slashdot Mirror
"...except at occasional intervals, when it was checked by a violent cease-and-desist which swept up the server racks..."
Interesting, I've never seen that at all.. and I've been using different builds (nightlies and stable) for quite some time. Since people also seem to be saying that a refresh fixes the problem, there must be some rather odd interaction happening there.
Of course, the bug report mentions that the problem is fixed in the trunk, so it may be gone next release...
Oddly enough, I've never had problems with Slashdot on Firefox. I'm still trying to figure out precisely what the bug is supposed to be.
Perhaps you're talking about this story, about copyrighted building codes in a city in Texas?
It's pretty irresponsible to bring up your corporate servers before those of your clients.
1) It's quite possible that the corporate servers didn't need special attention to bring up... or, didn't need large amounts of attention.
2) Where are customers going to go for updates, tickets, etc? Most likely, the corporate servers. Given the choice between the phone ringing off the hook while trying to concentrate on disaster recovery and having other forms of communication flashing around on the network, I'd pick the second any time. Unless there are large numbers of people sitting around to answer phones who would be absolutely useless in the recovery efforts, it's far more effecient to rely on text communication (and much easier to sort the useful people out from those who just want an ETA every five minutes). There's nothing worse for productivity than being forced to stop every five minutes to spend ten minutes convincing someone that you're working on problems as quickly as possible (and no, there isn't an eta, because it's likely something else is broken that won't be visible until the current thing you're working on is fixed..)
Oh, and I love how you say you're not qualified to comment, and then proceed anyways...
That is why he has already delegated authority to other people in the development process. There are a LOT of things these people could have done rather than send the email directly to Linus.
I dunno about you, but the last thing I would want is a legal climate where security bugs are punished through the courts. What's next.. coder's malpractice insurance? What will that do to OSS?
Much safer to get the word out that Microsoft is bad at handling these issues, and that their EULA specifically protects them from any responsibility. Luckily, they seem to be doing a very good job of doing that on their own..
tiasi54ffcb44334bcvxw53ezz3wr@gmail.com
,r as in really,
Wow, not only do you make it really difficult to memorize, you also spell it wrong when you give it out! Pure genius! I'll bet you never have to worry about any mail!
Oh, sure.. I'd love to see an installer that can gracefully and intelligently fail from a corrupted download and bugs imposed by outside software.
Next step after that: the Firefox installer becomes self-aware....
Here they are, flaunting this "code signing", and all it does is decide whether the Evil Bit is set or not!
I don't think HP qualifies as competition for themselves.
"HP notes that LightScribe is likely to show up eventually on such consumer electronics products as[...]"
The article you pointed out does mention Yamaha's DiscT@2 briefly, but doesn't give much detail.
Survey says....
Hmm.. looks like a tie between "What's Logan's Run?" and "Cowboy Neal".
"If you need the standard GNU tool set - buy the professional edition!"
Is it just me, or does something seem rather backwards about that statement?
Finally some realistic humans
n s_6113062.html?page=10
http://www.gamespot.com/pc/action/halflife2/scree
I'll say. That one looks exactly like my boss! Oh, wait, I can scroll this picture over a bit...
If some idiot decides to bring in his warezed copy of Sound Forge because he doesn't want to go to the trouble of putting in a purchase order for the real thing, does that make Microsoft complicit in piracy?
Try using that logic in a BSA audit and see how far it gets you.
Why for example is it a GOOD idea for AVAST's real time scanner to tell me it found a virus and then not doing anything about it? It knows it's there, kill the damn thing. Don't give me a message popup from the system tray telling me you found it.
Two words for you: False positives.
It's bad enough when an AV scanner accidently triggers and displays a message about a valid program. It would really drive people nuts if it kept immediately deleting valid programs as soon as they were installed...
I think the question is... how many con artists out there are going to take the time to set up an identity that people will buy from, pay the money in bandwidth fees, design all the rest of the stuff that goes into the 'identity' of a software publisher, and then risk it all and much, much more by blatently violating copyright laws. All it takes is for one of the recipients to notice the similarity to cause trouble.
Have you looked at the penalties for copyright violation lately? Now tack on fraud on top of that.
You asked how many people have succesfully been sued... the answer is very few, but the reason is that almost every discovered violator has quickly caved in when faced with the penalties of what they're doing.
As for identifying violations.. the logistics of it become much more reasonable when you realize how few applications of each kind there actually are out there. In your example... there are only so many CAD applications available, and any serious buyer of a CAD program most likely has experience with several.
Three things you're overlooking:
1. A small, light object will also have a much smaller surface area for the beam to push against, so it will pick up much less accelleration (the article mentions that the speed applied to the ship is very dependant on the width of the beam).
2. The beam is only planned to be on for a short time.
3. Any items wandering into the beam will have a velocity of their own to start with, which would cause it to travel off at an angle. The further away the craft is, the lower the chances of anything being able to enter the beam at the proper angle and speed to be pushed towards the ship.
Well, in preview, that first "here" was a link for this. Not sure what happened to it, but now I'm thinking this might have been a better choice anyways.
So long as it's actually news of some sort. Here you go, and here's another one.
Food? We've got that too.
I suppose you getting laid after a meal you didn't have to pay for might be news, but it'd be a bit more difficult to push that one to the editors.
I'd love to see a system that lets you fix a messed up video driver without the command line.
It does allow a spammer to change their nameserver real fast, however.
I've seen one spammer who liked to set up a redirector on an innocent-looking account on a server, then set the DNS that was under his control to point to it for short periods of time while sending out loads of spam. The redirector would remove itself after the time was up. Took months to get SPEWS to remove the listing for one server that he pointed the domain to for 15 minutes, even though the server was shut down minutes after complaints came rolling in and not brought back up until the reason was figured out.
Now, since SPEWS will sometimes blacklist nameserver IPs as well...
I can't think of so many words strung together in such a meaningless way.
What, didn't you get your Buzzword Bingo card on your way in? You'll never win with an attitude like that!
No, no.. firemen set fire to books, not houses.
There's also SCO's ability to threaten people who don't make all the certifications demanded in the letters they sent out to all their customers... the DC case pretty much killed that one, though SCO is still able argue that they should have gotten an answer in 30 days or less if they want to. *snicker*