If you watch the video you'd understand why they named the file that.
They nicknamed the image that because it looked like it could have come from a movie.
They also go into detail that they show the unretouched nasa photos and then the enhanced ones.
Additionally for some of these images there were multiple satellites involved. Absolute proof that there was a real object not a CCD fault (well I suppose it is possible that the CCD's in the 2 sats failed at the same time, showing the same false image.. yea.. right..)
Put the SP-2812 story in context:
>Brian Kendig asked a side question that bears answering: "How will I be able to work with Microsoft without appearing to be biased?" Another question asked about how I would deal with the monster egos at Microsoft.
He was showing that he HAS worked with the egos at Microsoft successfully in the past. And it was in a situation where the person in question would have vigorously defended the document.
It wasn't a boast as much as a "I was in this situation where I could have been a slacker and done nothing. Instead I took the hard road and did the right thing."
To me it seems like this guy would do well in the oversight job.
If you look at the facts this is a good deal for everyone.
Dmitri gets to go home.
He gets to testify about writing a legal program in Russia.
The DMCA test case becomes US vs ElcomSoft.
Unfortunately, I doubt the chilling effect on presenting scientific/research papers will get explored. Although he would be able to persue a judgement like Felton went for and not get it thrown out like his was.
I think most people would have a problem with the first M.. You know the Massively part.
MMORPG
Massively Multiplayer Online Role Playing Game
vs
MORPG
Multiplayer Online Role Playing Game
Most people don't consider 64 people Massively.
Empire and Muds (Mush/Muck/Mage/Diku/LPMUD/MudOS/etc) could all support that many people. I don't ever remember anyone calling any of those MMORPG.
In looking at the lawsuit, it looks like to me that it hinges on the facts that the click thru agreement did not apply if you never had any intention to try to collect the reward. If that is held up in court. Does your legal counsel believe that the RIAA's fallback assertion of we (RIAA) never meant to sue you hold up in court?
Or is it more likely that the judge will actually tackle the real issue of the DMCA stifling research (and now foreign visitors presenting papers re: Sklyarov)
I believe the "fair" part they are talking about relates to time shifting and media conversion.
It's fair use to copy an LP to cassette so you can play it in your car.
It's fair use to copy a CD to cassette so you can play it in your car.
It's fair use to convert a CD to mp3 so you can play it in your computer/mp3 player.
The fair use part is that you bought it once. You shouldn't have to buy it for every media type on the planet.
Even under the "license" model. The person has purchased a license to listen to a piece of music. The media in which it is stored is irrelevant. Of course if the RIAA ever switched to a convoluted EULA like MS's...
For those that have long memories this was completely expected.
MS said back then that one possible avenue of attack was patents.
Patent a core piece of the system.. Something that can't be missing or implemented differently. Then whoever implements must pay the MS tax umm.. I mean licensing fees..;)
All perfectly legal too. Charge everyone $x per installation of the system. Closed source can afford to pay, open source can't...
RSA did the same thing for years.. Which greatly crippled the adoption of crypto.
We can only hope that MS's decisions greatly cripple.NET in a similar way.
I'm just guessing here.. But wouldn't a failure in one of these things most likely be in the magnetic containment?
100M degree Kelvin plasma would melt through the walls of the reactor real quick once a section of the magnetic field collapsed. And probably squirt out and melt anything nearby.
Since it's hydrogen fusion there wouldn't be any highly radioactive elements. Helium and possibly Beryllium (sp?) isotopes, nothing like plutonium. So cleanup wouldn't be that bad I suppose.
Anyway, I just wonder how damaging a containment failure would be on a full sized reactor.. a 6 inch hole in the reactor and things up to 5 feet away melted.. Or everything within a mile vaporized?
They were most likely assuming that no one would ever use the internet for more than 8 hrs a day.
9.7*3 comes to 29.1k.
Re:What's the Source doing connected to the Net?
on
Microsoft Cracked
·
· Score: 1
You just answered it.
If you have *any* machines that have access to the internal network AND to the internet then your screwed. A trojan sitting on that machine can act as a gateway. The way I read this was you went to a workstation connected to both and copied it from the server to the workstation.
Now if it's completely seperate (seperate hubs and the files have to be moved physically via zip disk or something) your fairly safe. However most networks are designed for "user friendly" rather than security. Most people don't put the servers on the net.. But put the workstations on both the net and the internal network.
Also telecommuting is pretty popular in our industry. You have to be able to get to these things via the net or some dialup access if your allowing your developers to telecommute.
MS got screwed by their own "user friendly" SW. Myself, I'm going to be looking for the laugh track over the next few weeks (aka MS PR spin doctoring/damage control teams)
A method and system for generating email addresses which would only be valid for a certain time period. A computer system (server) or similar technology generates an email address given an expiration date and time. This email address will automatically stop functioning ("begin bouncing") once that time has passed. The email addresses would be valid for any email program (client) or similar technology. They would vary in length and format so that the receivers of the email address ("spammers") would not be able to tell that is was a time limited email address. The system would also ensure that the receivers of the email address ("spammers") would not be able to infer, deduce or discover the real email adddress of the user.
IIRC I was 9 when I started to learn how to hunt. (Rabbit/Squirrel with a.410 shotgun).
Way back when everyone had guns. They had to have them to eat.. I don't remember too many mass killings by kids with guns being discussed in my history class.
IMO it's not the video games. Those in and of themselves don't make good kids bad.. However what all the violence does do is make some bad kids far worse..
It falls to the parents to decide if their child(ren) are mature enough to handle something.
If someone is 15 and as mature as a normal 18 yo they should be given the extra responsibility.
If someone is 18 and only mature as a normal 15yo then they should be treated like the 15yo.
Sometimes I wonder if the "Licensed Parent before being allowed to have kids" idea doesn't have some merit. It'll never happen but I think it would solve alot of problems.
I've done some larger projects (aka "The Death March") and consulting work..
Usually documentation can only speak to 1 audience. If it's for the lusers.. I mean Users the techies say their isn't enough detail. If you include enough detail the users get bored to death, come back at the end and say I didn't know it said that I thought it said....
Here are some of the thoughs I have on project management.. Not really a process though.
1. All users are morons. Untrained monkeys can understand the system but our users can't. 2. Users never say what they mean. They expect you to be psychic. 3. Talk to the Users NOT the managers of the users. Standard biz philosophy says "Managers don't need to know anything about what they are managing." And true to the philosophy they usually don't. 4. Make the involved parties sign off on what the project is. The document is probably wrong but at least you have something to change. (Verbal/Mental designs mutate with no controls.) 5. A project schedule that is highly detailed and inflexible is always wrong after a short number of days. Stick to a functional points in a sequence and an estimate of days. Be willing to change it when it hits the fan. 6. Break up the project into manageable bits.. 5 days for a person at most. Have a done, work in progress and to be started list. Watch your "critical path" for changes because of slippages/changes and adapt as needed. (if it's more than 5 days then you haven't broken it up enough.. I used to not believe that but it's true) 7. Project Management is kinda like when they had to fire the rocket on Apollo 13 with no guidance computer. Keep the earth (end of project) in the window and hang on.
As for the crux of the original question.. Any documentation is better than no documentation. Find something that works and use it. Source Control is an assumed. Those that do without it are just ignorant of it. Teach them and they will use it. (I had to do that once.. After a year they said I don't know how we ever got by without it) Force all changes to documentation to go through a review and sign off. If someone can goto an individual (programmer/manager/etc) and change something with no review you are doomed.
-Jerry (and now back to our regularly scheduled interruptions)
I've got various linux boxes here with everything from 486's to PII's.
For giggles I decided to run the test on my 34G IDE stripeset (2 17G drives). I used a 100M file instead of 10M since I have 64M of ram.
Everything checked out 100% okay after 40 sums.
I would say change BIOS settings / CPU Clock speed to something very conservative and re-run your reliability test. Once everything checks out then you've fixed your problem. Then you can start bring speeds, etc up to find out what breaks what.
I've seen problems like this before a few years ago.. Intermittent failures on a news server I ran.. Started with Linux, went to FreeBSD and finally built a brand new box and the problems went away. I would say that your problems are *definitely* hardware. Overclocking your cpu/memory or failing cpu/memory/drives.
Also IHMO, using Windows 95 as a test of hardware is like using an 85 year old lady to test drive an indy car.. Of course nothings going to go wrong at that speed.;)
Slashdot Mirror
If you watch the video you'd understand why they named the file that.
They nicknamed the image that because it looked like it could have come from a movie.
They also go into detail that they show the unretouched nasa photos and then the enhanced ones.
Additionally for some of these images there were multiple satellites involved. Absolute proof that there was a real object not a CCD fault (well I suppose it is possible that the CCD's in the 2 sats failed at the same time, showing the same false image.. yea.. right..)
Put the SP-2812 story in context:
>Brian Kendig asked a side question that bears answering: "How will I be able to work with Microsoft without appearing to be biased?" Another question asked about how I would deal with the monster egos at Microsoft.
He was showing that he HAS worked with the egos at Microsoft successfully in the past. And it was in a situation where the person in question would have vigorously defended the document.
It wasn't a boast as much as a "I was in this situation where I could have been a slacker and done nothing. Instead I took the hard road and did the right thing."
To me it seems like this guy would do well in the oversight job.
-Jerry
If you look at the facts this is a good deal for everyone.
Dmitri gets to go home.
He gets to testify about writing a legal program in Russia.
The DMCA test case becomes US vs ElcomSoft.
Unfortunately, I doubt the chilling effect on presenting scientific/research papers will get explored. Although he would be able to persue a judgement like Felton went for and not get it thrown out like his was.
-Jerry
I think most people would have a problem with the first M.. You know the Massively part.
MMORPG
Massively Multiplayer Online Role Playing Game
vs
MORPG
Multiplayer Online Role Playing Game
Most people don't consider 64 people Massively.
Empire and Muds (Mush/Muck/Mage/Diku/LPMUD/MudOS/etc) could all support that many people. I don't ever remember anyone calling any of those MMORPG.
-Jerry
In looking at the lawsuit, it looks like to me that it hinges on the facts that the click thru agreement did not apply if you never had any intention to try to collect the reward. If that is held up in court. Does your legal counsel believe that the RIAA's fallback assertion of we (RIAA) never meant to sue you hold up in court?
Or is it more likely that the judge will actually tackle the real issue of the DMCA stifling research (and now foreign visitors presenting papers re: Sklyarov)
-Jerry
I believe the "fair" part they are talking about relates to time shifting and media conversion.
It's fair use to copy an LP to cassette so you can play it in your car.
It's fair use to copy a CD to cassette so you can play it in your car.
It's fair use to convert a CD to mp3 so you can play it in your computer/mp3 player.
The fair use part is that you bought it once. You shouldn't have to buy it for every media type on the planet.
Even under the "license" model. The person has purchased a license to listen to a piece of music. The media in which it is stored is irrelevant. Of course if the RIAA ever switched to a convoluted EULA like MS's...
-Jerry
For those that have long memories this was completely expected.
;)
.NET in a similar way.
MS said back then that one possible avenue of attack was patents.
Patent a core piece of the system.. Something that can't be missing or implemented differently. Then whoever implements must pay the MS tax umm.. I mean licensing fees..
All perfectly legal too. Charge everyone $x per installation of the system. Closed source can afford to pay, open source can't...
RSA did the same thing for years.. Which greatly crippled the adoption of crypto.
We can only hope that MS's decisions greatly cripple
I'm just guessing here.. But wouldn't a failure in one of these things most likely be in the magnetic containment?
100M degree Kelvin plasma would melt through the walls of the reactor real quick once a section of the magnetic field collapsed. And probably squirt out and melt anything nearby.
Since it's hydrogen fusion there wouldn't be any highly radioactive elements. Helium and possibly Beryllium (sp?) isotopes, nothing like plutonium. So cleanup wouldn't be that bad I suppose.
Anyway, I just wonder how damaging a containment failure would be on a full sized reactor.. a 6 inch hole in the reactor and things up to 5 feet away melted.. Or everything within a mile vaporized?
Hmm.. Wouldn't Micros~1 lose all rights to IE then?
They were most likely assuming that no one would ever use the internet for more than 8 hrs a day.
9.7*3 comes to 29.1k.
You just answered it.
If you have *any* machines that have access to the internal network AND to the internet then your screwed. A trojan sitting on that machine can act as a gateway. The way I read this was you went to a workstation connected to both and copied it from the server to the workstation.
Now if it's completely seperate (seperate hubs and the files have to be moved physically via zip disk or something) your fairly safe. However most networks are designed for "user friendly" rather than security. Most people don't put the servers on the net.. But put the workstations on both the net and the internal network.
Also telecommuting is pretty popular in our industry. You have to be able to get to these things via the net or some dialup access if your allowing your developers to telecommute.
MS got screwed by their own "user friendly" SW. Myself, I'm going to be looking for the laugh track over the next few weeks (aka MS PR spin doctoring/damage control teams)
-Jerry
A method and system for generating email addresses which would only be valid for a certain time period. A computer system (server) or similar technology generates an email address given an expiration date and time. This email address will automatically stop functioning ("begin bouncing") once that time has passed. The email addresses would be valid for any email program (client) or similar technology. They would vary in length and format so that the receivers of the email address ("spammers") would not be able to tell that is was a time limited email address. The system would also ensure that the receivers of the email address ("spammers") would not be able to infer, deduce or discover the real email adddress of the user.
-Jerry (jasegler@gerf.org)
IIRC I was 9 when I started to learn how to hunt. .410 shotgun).
(Rabbit/Squirrel with a
Way back when everyone had guns. They had to have them to eat.. I don't remember too many mass killings by kids with guns being discussed in my history class.
IMO it's not the video games. Those in and of themselves don't make good kids bad.. However what all the violence does do is make some bad kids far worse..
It falls to the parents to decide if their child(ren) are mature enough to handle something.
If someone is 15 and as mature as a normal 18 yo they should be given the extra responsibility.
If someone is 18 and only mature as a normal 15yo then they should be treated like the 15yo.
Sometimes I wonder if the "Licensed Parent before being allowed to have kids" idea doesn't have some merit. It'll never happen but I think it would solve alot of problems.
-Jerry (jasegler@gerf.org)
I've done some larger projects (aka "The Death March") and consulting work..
....
Usually documentation can only speak to 1 audience. If it's for the lusers.. I mean Users the techies say their isn't enough detail. If you include enough detail the users get bored to death, come back at the end and say I didn't know it said that I thought it said
Here are some of the thoughs I have on project management.. Not really a process though.
1. All users are morons. Untrained monkeys can understand the system but our users can't.
2. Users never say what they mean. They expect you to be psychic.
3. Talk to the Users NOT the managers of the users. Standard biz philosophy says "Managers don't need to know anything about what they are managing." And true to the philosophy they usually don't.
4. Make the involved parties sign off on what the project is. The document is probably wrong but at least you have something to change. (Verbal/Mental designs mutate with no controls.)
5. A project schedule that is highly detailed and inflexible is always wrong after a short number of days. Stick to a functional points in a sequence and an estimate of days. Be willing to change it when it hits the fan.
6. Break up the project into manageable bits.. 5 days for a person at most. Have a done, work in progress and to be started list. Watch your "critical path" for changes because of slippages/changes and adapt as needed. (if it's more than 5 days then you haven't broken it up enough.. I used to not believe that but it's true)
7. Project Management is kinda like when they had to fire the rocket on Apollo 13 with no guidance computer. Keep the earth (end of project) in the window and hang on.
As for the crux of the original question..
Any documentation is better than no documentation.
Find something that works and use it.
Source Control is an assumed. Those that do without it are just ignorant of it. Teach them and they will use it. (I had to do that once.. After a year they said I don't know how we ever got by without it)
Force all changes to documentation to go through a review and sign off. If someone can goto an individual (programmer/manager/etc) and change something with no review you are doomed.
-Jerry (and now back to our regularly scheduled interruptions)
That's funny...
/x" on NT and you'll see them.
I can still type cd \progra~1 and have it work on NTFS...
Actually do a "dir
"True Long Filenames" would be a filesystem with 1 filename per file.. Not 2.
E2FS has "True Long Filenames" 8)
-Jerry (jsegler@gerf.org)
I've got various linux boxes here with everything from 486's to PII's.
;)
For giggles I decided to run the test on my 34G IDE stripeset (2 17G drives). I used a 100M file instead of 10M since I have 64M of ram.
Everything checked out 100% okay after 40 sums.
I would say change BIOS settings / CPU Clock speed to something very conservative and re-run your reliability test. Once everything checks out then you've fixed your problem. Then you can start bring speeds, etc up to find out what breaks what.
I've seen problems like this before a few years ago.. Intermittent failures on a news server I ran.. Started with Linux, went to FreeBSD and finally built a brand new box and the problems went away. I would say that your problems are *definitely* hardware. Overclocking your cpu/memory or failing cpu/memory/drives.
Also IHMO, using Windows 95 as a test of hardware is like using an 85 year old lady to test drive an indy car.. Of course nothings going to go wrong at that speed.
-Jerry (jasegler@gerf.org)