You could just wipe the hard drive before you send it. Just b/c Microsoft says it's an OEM version, doesn't mean you can't keep the license and the media as long as you don't send the box with that copy of Windows still on it.
You weren't going to give the machine with all of your data to the charity anyway, we're you?
Re:Titanium is also very flexible.
on
The Sexiest Metal
·
· Score: 1
Here's a place you can buy all the Ti cookware you'll ever need (for your backpack)!
Here's a stupid one:
The basic idea is a <gasp> global variable (a class more specifically) which needs construction. Its constructor will be called before main runs. In fact, even if you use the default constructor for a global class, it will get called before main, but it just doesn't do much.
#include <iostream>
class A
{
public:
A() ;
~A() {}
private:
int foo;
};
A::A()
{
cout<< "In A Ctor" <<endl;
foo=1;
}
static A sA;
int main()
{
cout<<"In main"<<endl;
A a;
cout<<"After A decl"<<endl;
return 0;
}
ariel(119)$ g++ -v
Reading specs from/vol/gnu/gcc/2.95.3/lib/gcc-lib/i686-pc-linux-gnu/ 2.95.3/specs
gcc version 2.95.3 20010315 (release)
ariel(116)$ g++ -o test test.C
ariel(117)$./test
In A Ctor
In main
In A Ctor
After A decl
I know a self-reply is taboo.....
But, I thought I'd mention noweb as well. If you're not doing literate programming in a language independent way for a major, multi-person programming challenge, you're doing it the hard way.
For the record, I also prefer:
Imagine for a minute that you don't know what problem you want to solve yet. You know that that you want to apply a Galerkin Finite Element Method (for instance, though this particular method isn't required) to a whole class of problems on unstructured grids on a whole class of distributed and shared memory parallel computers. Imagine that you want your user base to be able to specify their equations like they would in LaTeX or some other markup language. Now try imagining that you have only FORTRAN77. Not a pretty picture.
We're in the process of completing a rewrite of major sections of our parallel code to do exactly this. Our code started out (7 years ago) as an extremely efficient parallel (3D) C/F77 code for Navier-Stokes + Heat Transfer and is quickly growing into a multi-purpose, multi-physics code written largely in C++.*
We extract considerable advantage form C++'s ability to hide implemenations so that as long as interfaces don't change the guts can. We also make good use of the ability to run code before main() in order to register the exisitence of routines (hash tables are your friend). If the routine isn't there you can't call it, but the code still compiles and runs otherwise. We also make use of base class/derived class relationships and polymorphism to allow, for instance, one base mesh class for the rest of the code to interact with, but with two separate derived classes: one to generate meshes internally, and one to read meshes from other programs. Etc., etc.
I'm not sure our website can take the/.'ing, but you can look here for some hints.
* I say largely b/c there's a few struct's still left over from the code's C days, but all the F77 is gone. There are still calls to assembly coded (vendor supplied) BLAS routines, though.
you better have a 100Mbit network between endpoints since it's a huuuge bandwidth hogger
I've been using VNC over my cable modem (< 2Mb/s d/l, 256 Kb/s u/l) through an ssh tunnel for 6 or 8 months with no complaints. It's _much_ faster than a plain X connection over the same link. You might be right about the CPU requirements, but VNC seems to do a good job for me on the bandwidth side.
When one section of the superconductor stops superconducting Ohmic heating kicks in. If the current densities/magnetic fields are low then catastrophic failure can be avoided. But when they are high (O(1-10) Tesla, say) the Ohmic heating is usually fast enough so that the resistence continues to rise, the wire melts, the coolant boils, the safety valves come off, and you have a room full of LN2 or LHe. They call this a "quench".
Do you have a network card? Do a network install. As I'm sure you know, the Vaio BIOS will boot off the USB disk just fine, so just do a network install.
Yeah, but think about it this way: For a century or more companies have been willing to buy the risk for diseases that will/have turned out to be genetic. Do you think that they will significantly lower prices if allowed to screen everyone's genes for all of the known genetically linked diseases? It seems clear that they probably would not. So governments will attempt to protect us from them but keeping the playing field the same.
The knowledge of risk may be changing here, but I doubt that the pricing will follow.
Perhaps governments will allow special pricing for those willing to be tested, who knowns.
Actually X suppots two mice at the same time without any problems. They just end up driving the same pointer, so far. I'm sitting here in front of my laptop which has a touchpad built-in and a Logitech optical USB mouse plugged-in.
Anyway, I can't imagine that it would take much work to make the X server add another pointer to the screen getting input from the nth-mouse. It might be difficult to have most applications do anything different with it though. (However, it is amazing what you can do with your.Xresources file.)
If you need encryption that'll keep you safe from the government, you're probably doing something illegal.
Why is it that this argument persists in societies that value free speach? There are some things that are illeagal and still not wrong.
Besides the 4th Amendment protects me from incriminating myself. One might argue that this extends to the files I have stored away. My private diary, the one I store on my computer, should be kept away from the government at all costs. And courts in the USA would probably support this idea, but in the UK there is no Bill of Rights (constitutionally at least) to protect its citizens from the government.
This new OS is designed for them. For people in a place where there is a law that punishes people for not (possibly) incriminating themselves by handing over encryption keys under court order.
This OS certainly won't help those who are sending out incriminating emails to their friends, but it will keep the prying eyes of the government out of their private computer files.
(BTW, is using 'incriminating' four times in one short post too many?)
One good sign of LaTeX being misused is the use of 'eqnarray'. I've used latex for 3 years, written >400 pages in it, and never used it once.
Hmm...I'm curious why you think 'eqnarray' is a bad LaTeX environment. I've been using LaTeX and TeX for 6 or 7 years, written >1k pages, and have had plenty of opportunities for it's use. Please explain to me what the big problem with 'eqnarray' is.
...because they've upped the memory bandwidth soooo much. I've seen some performance numbers from Intel's optimized BLAS (Basic Linear Algebra Subroutines) for the P4, and they are stellar. In particular the FLOP rate for matrix-vector products (just one here guys, no reuse of the matrix or vector at a nearby, cache useful step) which our code spends 90+% of its time doing, has quintupled. And since I've verified Intel's P3 matvec numbers, I tend to be hopeful about their P4 numbers.
The basic idea is that a player that currently claims to be SDMI compliant will stop working and request the user to upgrade its firmware the first time an SDMI watermarked file is downloaded into the player.
Wrong. The applications run on these machines are ususally tightly coupled parallel PDE solvers. If they were embarrassingly parallel, DOE would not have commissioned such a machine; they would have just bought a bunch of PCs and thrown they code at them.
...if your program is anywhere near memory bandwidth limited the extra processor (or three!) will buy you nothing. We see performance gains in the single digit percentages when the problems we solve are maxing the memory bandwidth.
The answer to your question is clearly based on what kind of problem you happen to be solving, though. If you're just banging registers together, then use MPI or one of the MPI w/SMP packages available (see other posts).
Of course, if you're interested in using Java or Haskell, your probably not maxing out the memory bus or the processor's resources, so the extra local processors will probably buy you a lot. In the case of Java use threads and RMI or somesuch.
Actually the the new President will have been elected by then, but he doesn't take office until some time in mid-January. There won't be any shake-ups at DOJ until after that.
It really depends on your codes. If you're set up to use the shared memory then you should continue in that direction. If your codes are really distributed memory parallel running on a shared memory machine, then you should talk to SGI about getting a T3E. There is actually some shared memory available there, too (SHMEM is supported on the Origin and the T3E). If you are at all memory bandwidth limited then you should avoid the Origin at all costs. Our (heavily-optimized) code's performance goes in half when we go beyond half of the machine on an O2K! I.e. when you start to use the second processor on the same board (2 procs share a pool of memory on each proc board in the O2K, but you knew that). If you haven't seen this already on the O2K then you will probably not see it on the newer Origin either .
Most importantly don't get a machine to which you can't port your code reasonably. BTW, why the hell can't you run your codes under Linux? Is this a commercial app like Fluent, FIDAP, Inca, etc?
You weren't going to give the machine with all of your data to the charity anyway, we're you?
Are there MPI bindings for Java?. (I'd hate to have to do the socket calls myself.) :)
Here's a stupid one:
/vol/gnu/gcc/2.95.3/lib/gcc-lib/i686-pc-linux-gnu/ 2.95.3/specs
./test
The basic idea is a <gasp> global variable (a class more specifically) which needs construction. Its constructor will be called before main runs. In fact, even if you use the default constructor for a global class, it will get called before main, but it just doesn't do much.
#include <iostream>
class A
{
public:
A() ;
~A() {}
private:
int foo;
};
A::A()
{
cout<< "In A Ctor" <<endl;
foo=1;
}
static A sA;
int main()
{
cout<<"In main"<<endl;
A a;
cout<<"After A decl"<<endl;
return 0;
}
ariel(119)$ g++ -v
Reading specs from
gcc version 2.95.3 20010315 (release)
ariel(116)$ g++ -o test test.C
ariel(117)$
In A Ctor
In main
In A Ctor
After A decl
Hope this helps.
Bill.
emacs
autoconf
make
and a few other things.Imagine for a minute that you don't know what problem you want to solve yet. You know that that you want to apply a Galerkin Finite Element Method (for instance, though this particular method isn't required) to a whole class of problems on unstructured grids on a whole class of distributed and shared memory parallel computers. Imagine that you want your user base to be able to specify their equations like they would in LaTeX or some other markup language. Now try imagining that you have only FORTRAN77. Not a pretty picture. We're in the process of completing a rewrite of major sections of our parallel code to do exactly this. Our code started out (7 years ago) as an extremely efficient parallel (3D) C/F77 code for Navier-Stokes + Heat Transfer and is quickly growing into a multi-purpose, multi-physics code written largely in C++.* We extract considerable advantage form C++'s ability to hide implemenations so that as long as interfaces don't change the guts can. We also make good use of the ability to run code before main() in order to register the exisitence of routines (hash tables are your friend). If the routine isn't there you can't call it, but the code still compiles and runs otherwise. We also make use of base class/derived class relationships and polymorphism to allow, for instance, one base mesh class for the rest of the code to interact with, but with two separate derived classes: one to generate meshes internally, and one to read meshes from other programs. Etc., etc. I'm not sure our website can take the /.'ing, but you can look here for some hints.
* I say largely b/c there's a few struct's still left over from the code's C days, but all the F77 is gone. There are still calls to assembly coded (vendor supplied) BLAS routines, though.
F-PROT anyone?
Used to be the best in the world, may still be.
I've been using VNC over my cable modem (< 2Mb/s d/l, 256 Kb/s u/l) through an ssh tunnel for 6 or 8 months with no complaints. It's _much_ faster than a plain X connection over the same link. You might be right about the CPU requirements, but VNC seems to do a good job for me on the bandwidth side.
When one section of the superconductor stops superconducting Ohmic heating kicks in. If the current densities/magnetic fields are low then catastrophic failure can be avoided. But when they are high (O(1-10) Tesla, say) the Ohmic heating is usually fast enough so that the resistence continues to rise, the wire melts, the coolant boils, the safety valves come off, and you have a room full of LN2 or LHe. They call this a "quench".
:).
It can be quite exciting/expensive
Do you have a network card? Do a network install. As I'm sure you know, the Vaio BIOS will boot off the USB disk just fine, so just do a network install.
Yeah, but think about it this way: For a century or more companies have been willing to buy the risk for diseases that will/have turned out to be genetic. Do you think that they will significantly lower prices if allowed to screen everyone's genes for all of the known genetically linked diseases? It seems clear that they probably would not. So governments will attempt to protect us from them but keeping the playing field the same.
The knowledge of risk may be changing here, but I doubt that the pricing will follow.
Perhaps governments will allow special pricing for those willing to be tested, who knowns.
Actually X suppots two mice at the same time without any problems. They just end up driving the same pointer, so far. I'm sitting here in front of my laptop which has a touchpad built-in and a Logitech optical USB mouse plugged-in.
.Xresources file.)
Anyway, I can't imagine that it would take much work to make the X server add another pointer to the screen getting input from the nth-mouse. It might be difficult to have most applications do anything different with it though. (However, it is amazing what you can do with your
Why is it that this argument persists in societies that value free speach? There are some things that are illeagal and still not wrong.
Besides the 4th Amendment protects me from incriminating myself. One might argue that this extends to the files I have stored away. My private diary, the one I store on my computer, should be kept away from the government at all costs. And courts in the USA would probably support this idea, but in the UK there is no Bill of Rights (constitutionally at least) to protect its citizens from the government.
This new OS is designed for them. For people in a place where there is a law that punishes people for not (possibly) incriminating themselves by handing over encryption keys under court order.
This OS certainly won't help those who are sending out incriminating emails to their friends, but it will keep the prying eyes of the government out of their private computer files.
(BTW, is using 'incriminating' four times in one short post too many?)
Hmm...I'm curious why you think 'eqnarray' is a bad LaTeX environment. I've been using LaTeX and TeX for 6 or 7 years, written >1k pages, and have had plenty of opportunities for it's use. Please explain to me what the big problem with 'eqnarray' is.
...because they've upped the memory bandwidth soooo much. I've seen some performance numbers from Intel's optimized BLAS (Basic Linear Algebra Subroutines) for the P4, and they are stellar. In particular the FLOP rate for matrix-vector products (just one here guys, no reuse of the matrix or vector at a nearby, cache useful step) which our code spends 90+% of its time doing, has quintupled. And since I've verified Intel's P3 matvec numbers, I tend to be hopeful about their P4 numbers.
(or somesuch).
The basic idea is that a player that currently claims to be SDMI compliant will stop working and request the user to upgrade its firmware the first time an SDMI watermarked file is downloaded into the player.
kinda sucks, huh?
Wrong. The applications run on these machines are ususally tightly coupled parallel PDE solvers. If they were embarrassingly parallel, DOE would not have commissioned such a machine; they would have just bought a bunch of PCs and thrown they code at them.
They're usually called PE's on massively parallel machines (processing entities).
A politely worded commemnt to him may have better results.
...if your program is anywhere near memory bandwidth limited the extra processor (or three!) will buy you nothing. We see performance gains in the single digit percentages when the problems we solve are maxing the memory bandwidth.
The answer to your question is clearly based on what kind of problem you happen to be solving, though. If you're just banging registers together, then use MPI or one of the MPI w/SMP packages available (see other posts).
Of course, if you're interested in using Java or Haskell, your probably not maxing out the memory bus or the processor's resources, so the extra local processors will probably buy you a lot. In the case of Java use threads and RMI or somesuch.
Actually the the new President will have been elected by then, but he doesn't take office until some time in mid-January. There won't be any shake-ups at DOJ until after that.
Beta tetsters do this for many products already, we just don't hear as much about it. (Think NDA, et. al.)
It really depends on your codes. If you're set up to use the shared memory then you should continue in that direction. If your codes are really distributed memory parallel running on a shared memory machine, then you should talk to SGI about getting a T3E. There is actually some shared memory available there, too (SHMEM is supported on the Origin and the T3E). If you are at all memory bandwidth limited then you should avoid the Origin at all costs. Our (heavily-optimized) code's performance goes in half when we go beyond half of the machine on an O2K! I.e. when you start to use the second processor on the same board (2 procs share a pool of memory on each proc board in the O2K, but you knew that). If you haven't seen this already on the O2K then you will probably not see it on the newer Origin either .
Most importantly don't get a machine to which you can't port your code reasonably. BTW, why the hell can't you run your codes under Linux? Is this a commercial app like Fluent, FIDAP, Inca, etc?