Crater is suing Lucent and needs access to some of 22,000 documents which Lucent has. The US Government declares that these documents can't be used because of "state secrets privilege".
In any other case Lucent had simply destroyed the documents or otherwise refused to make them available, the court would automatically presume/infer that whatever was in those missing documents were unfavourable to Lucent's case.
Shouldn't that be the same standard applied to cases where defendants hide behind the state secrets privilege? They get to use that privilege to prevent releasing documents, but the court can make some assumptions about what's in those documents. Sure it drives up the cost of being a contractor for the US Government, but that cost is passed on to the government and is a reflection of the value taken away from the rest of society by the "state secret privilege".
I spend much of my free time helping strangers with dumb computer problems on web forums instead of actually doing something useful with my knowledge, and I'm not happy with that. It's been six years since I left school because I didn't feel like I was learning anything, and now I want to go back.
It's not about the degree though (I can get work). I want to learn more than just how to do things. I want to learn why to do them, and I want to learn what can be done with them.
Absolutely go back. But be prepared that the answers you are seeking aren't readily found in the Computer Science department. Branch out into other fields like philosophy and the social sciences.
Why does the script that IBM provided (Exhibit B, page 19) refer to SCCS?
For example:
function DiffBySccs { (( ShellDebug )) && set -x SccsFile=$(Sourceid2vc $2) if [[ -f $SccsFile ]]; then echo "===> $1 $4 -> $3" sccsdiff -r$4 -r$3 $SccsFile else echo "===> $1 ($SccsFile) not found" fi }
Also check this quote on page 6:
IBM then matched those files names and identifiers to corresponding Source Code Control System ("SCCS") files. These SCCS files are the files maintained by IBM that provide the file development history since 1991 (or the inception of the file) for the particular corresponding source code file in the AIX operating system or related source code.
The paper http://www.cse.ucsd.edu/users/tkohno/papers/PDF/
shows that they were able to get less than 7 bits of identifying information when monitoring communications for 2 hours. So they would only be able to distinguish 1 out of 128 machines. That would only be useful if there was a very small set of candidate machines.
The
BBC transcript (about two thirds of the way down) explains that in the case of La Palma,
the risk is created by:
the shape of the volcano -- a long ridge
with a long fault line
the structure of the volcano --
one face held in place by friction,
a mixture of water-permeable rubble
and solidified-lava dykes
thoasands of years of
rain water accumulated in the
pockets of rubble creating
water pressure that
weakens the friction
along the fault
the inevitable future eruption
that will heat the water
and increase the water pressure
triggering a massive land slide
What I don't get is why I haven't seen anyone
propose draining the water out of the volcano.
Surely it would be possible to do horizontal
drilling into the critical pockets of water
and let the water drain out until the water
pressure is lowered sufficiently that the
risk is reduced.
I imagine you would be dealing with a fair amount
of water but not something unimaginable.
Say 10% of the rain that falls on the volcano
accumulates in the critical pockets.
You might want to drain off 500 years of accumulation in the next 10 years.
That would be the equivalent of 5 times the rainfall on the volcano, or approximately the drainage rate of several typical mountain rivers -- big engineering but certainly doable.
Use this cached version which doesn't try to load images from the slashdotted site:
http://www.google.com/search?q=cache:5p4B1xNAGXkJ: www.asktog.com/Bughouse/10MostPersistentBugs.html& hl=en&lr=&strip=1
Slashdot Mirror
http://signs-of-the-times.org/signs/friendly/signs _20060302_friendly.html
It is indeed very interesting.
Crater is suing Lucent and needs access to some of 22,000 documents which Lucent has. The US Government declares that these documents can't be used because of "state secrets privilege".
In any other case Lucent had simply destroyed the documents or otherwise refused to make them available, the court would automatically presume/infer that whatever was in those missing documents were unfavourable to Lucent's case.
Shouldn't that be the same standard applied to cases where defendants hide behind the state secrets privilege? They get to use that privilege to prevent releasing documents, but the court can make some assumptions about what's in those documents. Sure it drives up the cost of being a contractor for the US Government, but that cost is passed on to the government and is a reflection of the value taken away from the rest of society by the "state secret privilege".
Does anyone else find it strange that IBM's CMVC looks like it's built on top of SCCS? Now, that's a dated system!
The paper http://www.cse.ucsd.edu/users/tkohno/papers/PDF/ shows that they were able to get less than 7 bits of identifying information when monitoring communications for 2 hours. So they would only be able to distinguish 1 out of 128 machines. That would only be useful if there was a very small set of candidate machines.
What I don't get is why I haven't seen anyone propose draining the water out of the volcano. Surely it would be possible to do horizontal drilling into the critical pockets of water and let the water drain out until the water pressure is lowered sufficiently that the risk is reduced.
I imagine you would be dealing with a fair amount of water but not something unimaginable. Say 10% of the rain that falls on the volcano accumulates in the critical pockets. You might want to drain off 500 years of accumulation in the next 10 years. That would be the equivalent of 5 times the rainfall on the volcano, or approximately the drainage rate of several typical mountain rivers -- big engineering but certainly doable.
Use this cached version which doesn't try to load images from the slashdotted site: http://www.google.com/search?q=cache:5p4B1xNAGXkJ: www.asktog.com/Bughouse/10MostPersistentBugs.html& hl=en&lr=&strip=1