The advantage with the D-He3 reaction is that it is theoretically aneutronic, but in any D-He3 fusion-capable environment you're going to have enough D-D fusion to have to worry about neutrons anyway...
I've seen estimates that the Neutron production should be about 100X less for a D-He3 reaction mixture than for the D-T reaction. That by itself can make a big difference in the economics of a fusion reactor as there would be a lot less neutron damage to the first wall. In the late 70's, Kulcinski was estimating that each atom in the first wall would be knocked out of its lattice position 10 times during the life of the first wall. Kulcinksi was at UCB for a few weeks in mid-1978 and gave some talks on the state of fusion reactor design.
There are a couple of other advantages to D-He3. One is that most of the energy from the reaction is in the ejected proton - easier to keep in the plasma. The other is that He3 is non-radioactive and isn't as useful in nuclear weapons as Tritium.
OTOH, I recently asked a friend with "a little bit of experience with moon rocks" about the idea of He3 mining - she was rather dubious about the idea - mainly in extracting sufficient amounts of He3 from the lunar soil.
The SFU NFS client did follow symlinks when the target was on the same device, but it didn't seem to follow a symlink to another device. I tried making targets of c:\temp and \\host\share, but even though Windows Explorer could see the target directly, when Windows Explorer browses the remote NFS Network the the symlink target did not resolve. (A trace shows the NFS server returning the right target name to the SFU NFS client.)
If I'm reading your post correctly, the SFU NFS client is working correctly. NFS only allows one filesystem to be exported in a single share. For example, if I'm exporting/export/home/foo and have another filesystem mounted at/export/home/foo/bar, then/export/home/foo/bar has to be exported separately. Symlinks would presumably follow the same pattern.
One of the beefs Novell had with SCO was SCO's deal with Sun and MS about the one time payments in royalties. Both Sun and MS would benefit from not having to pay a per copy royalty. Sun is again offering Solaris x86 as a free download, and now MS is offering SFU for free.
Would be fun to check out the NFS client - it's a much cleaner protocol than SMB.
The first computer I got to work with was a CDC-1700 at CDC's La Jolla facility. Used a coding pad to write out the programs, followed by keypunching, and finally fed the deck to the card reader. Compilation speed for FORTRAN was about 1 card per second. Was exposed to an 1108 and a PDP-8 shortly thereafter, but still have a soft spot for the CDC-1700.
Bought my first computer 11 years later, an SCP 8086 system, followed 4.5 years later by a Deskpro 386.
Still have my HP-45 kicking around - the young-uns on/. wouldn't comprehend what a change the HP-35/45 represented.
That movie was nominated for a "Razzie" which was presented by Robert Conrad (who asked to be the presenter).
I was a fan of the series, especially the first two years. Just never warmed up to the idea of Will Smith as James West...
The TV-movie of TWWW (1980) was pretty decent, especially with the producers misunderstanding what Ross Martin meant when he wanted to do a part "in drag" (Ross wanted to something in disguise - the producers assumed the more modern meaning of the phrase).
apple screwed the pooch by being overly proprietary back in the early 80's. they were just too damn expensive for mass penetration.
You mean that apple wouldn't let anyone else screw the pooch?? (OTOH, the pooch would be looking like the goatse guy).
ibm being dipshits about ms-dos. they could have had the rights for chump change.
Ummm, no. When MS got the rights to 86-DOS, Seattle Computer got rights to MS-DOS, OTOH, if IBM dealt directly with SCP, then...
in 1949, we had a state fo the art bomber, the YB-49. it could fly farther, faster, stealthier, etc. and, check this out, it was a flying wing. based on a design from the horten bros. in germany. discovered after the war, and developed by jack northrup.
Ummm, no again. The YB-49 was the XB-35 with 8 jet engines replacing the 4 Wasp Majors + contra-rotating props. The XB-35 was a scale-up of the Northrop (note "o" not "u") N9M which was flying in the early 40's. The B-35 and B-36 were both results of an RFP for a bomber with a 10,000 mile range and a 10,000 pound bombload that came out in early 1941. The USAAF wanted a plane capable of bombing Berlin from the NE US.
It is interesting to note that the B-2 has a wingspan almost identical to that of the B-35/49.
The Horten aircraft was specifically designed with low radar cross section in mind, the low RCS of the B-49 was a happy accident. There was an incident where the B-49 was being tested off the coast of Calif and it frequently disappeared from the radar screens.
The first US stealth aircraft was the Lockheed A-12/F-12/SR-71. The Blackbird was often called the A-11 because LBJ read AMI as A-11, and the recce bird was originally the R/S-71 (following the R/S-70 nee XB-70), but LBJ screwed that up again.
Call me too lazy to look it up, but a quantitative study I read (put out by Cato, I believe) said replacing the oldest 5% of cars on the road will do more for air quality than kicking the SUVs off the road.
You could get the same results by replacing the dirtiest 1% of the cars on the road. In California, at least 10% of the pollution comes from small gas engines, i.e. lawn mowers, leaf blowers, etc. - and narrowly avoided losing the right to regulate small gas engines.
It was at one point clear (DOS/Win3.1), but then the GUI started to "own" many features (net support, and even CD-ROM access!) from 95 on - and they finally did away with the separated "core system" from ME on.
The earliest versions of Win NT kept the GUI code out of the kernel, but that was changed in later versions of NT to improve performance. Bear in mind that NT was much more of a resource hog than OS/2.
More importantly is the corporate culture - M$ has played fast and loose with programming in the past, e.g. the original IBM PC and their first software for the Mac.
IBM PC - Intel's databooks for the 8086 specifically stated that interrupts below 20H were reserved for future versions of the 8086 family - IBM and M$ then proceed to use those interrupts for the BIOS routines.
Mac - Apple had many programming guidelines that were intended to allow migration to future versions of the 68000 family (e.g. don't use the upper 8 bits of addressing for flags). When Apple came out with a 68020 version of the Mac, a lot of the M$ software was broken by the upgrade.
Sun? SuSE? Funny, I seem to remember hearing Sun had their own OS in development. Called Sol-something... I think it'll be big.
64-bit Linux for AMD64 is out now (mainly since GCC supports AMD64). The rumors are that Solaris AMD64 should be out Summer 2004 (at least summer in the northern hemisphere). The wait is due to developing AMD64 support for Sun's compiler collection (Solaris was written for Sun's C compiler).
Having Solaris support the Opteron may help Sparc sales as it could increase the market for 64 bit software on Solaris - should be a very simple re-compile to prt from one platform to the other.
The only real problem is memory technology hasn't kept up. 1GB DIMMs can be had at almost reasonable prices but 2GB density ones are out of range of most everyone. 4GB are on the distant horizon.
Crucial is listing their CT51272Y265 DIMM's for a measly $6999 - these are 4GB PC2100 registered with ECC. The price (ahem) may be a bit high, but if you really need the memory...
Hal Computers had an interesting "benchmark" back in the late 90's. Their Sparc box was capable of handling 3 GB (at close to 80 grand per GB), one chip simulation took 40 hours with 2 GB and 1.5 hours with 3 GB.
One of my favorite short stories was And he buily a Crooked House which I first read in A.C. Clarke's Time Probe anthology.
I also like Blowups Happen, one of the best (if not the best) predictions of a nuclear power plant I've seen (especially since it was written in 1940). There are some errors, for example RAH didn't know about delayed neutrons (nor did anyone else at the time), but the errors reflect the times more than RAH's ability.
Reading the review was timely, as I picked up a copy of the book last night - did like the 1930's style for the cover.
Think the editors did make at least one mistake - the area where Perry crashed is Torrey Pines
notTorrey Fines. I'll have to ask a co-worker (who graduated from La Jolla High in '47) about the roads through that area.
Slashdot Mirror
I've seen estimates that the Neutron production should be about 100X less for a D-He3 reaction mixture than for the D-T reaction. That by itself can make a big difference in the economics of a fusion reactor as there would be a lot less neutron damage to the first wall. In the late 70's, Kulcinski was estimating that each atom in the first wall would be knocked out of its lattice position 10 times during the life of the first wall. Kulcinksi was at UCB for a few weeks in mid-1978 and gave some talks on the state of fusion reactor design.
There are a couple of other advantages to D-He3. One is that most of the energy from the reaction is in the ejected proton - easier to keep in the plasma. The other is that He3 is non-radioactive and isn't as useful in nuclear weapons as Tritium.
OTOH, I recently asked a friend with "a little bit of experience with moon rocks" about the idea of He3 mining - she was rather dubious about the idea - mainly in extracting sufficient amounts of He3 from the lunar soil.
If I'm reading your post correctly, the SFU NFS client is working correctly. NFS only allows one filesystem to be exported in a single share. For example, if I'm exporting /export/home/foo and have another filesystem mounted at /export/home/foo/bar, then /export/home/foo/bar has to be exported separately. Symlinks would presumably follow the same pattern.
Would be fun to check out the NFS client - it's a much cleaner protocol than SMB.
Bought my first computer 11 years later, an SCP 8086 system, followed 4.5 years later by a Deskpro 386.
Still have my HP-45 kicking around - the young-uns on /. wouldn't comprehend what a change the HP-35/45 represented.
I was a fan of the series, especially the first two years. Just never warmed up to the idea of Will Smith as James West...
The TV-movie of TWWW (1980) was pretty decent, especially with the producers misunderstanding what Ross Martin meant when he wanted to do a part "in drag" (Ross wanted to something in disguise - the producers assumed the more modern meaning of the phrase).
You mean that apple wouldn't let anyone else screw the pooch?? (OTOH, the pooch would be looking like the goatse guy).
ibm being dipshits about ms-dos. they could have had the rights for chump change.
Ummm, no. When MS got the rights to 86-DOS, Seattle Computer got rights to MS-DOS, OTOH, if IBM dealt directly with SCP, then...
in 1949, we had a state fo the art bomber, the YB-49. it could fly farther, faster, stealthier, etc. and, check this out, it was a flying wing. based on a design from the horten bros. in germany. discovered after the war, and developed by jack northrup.
Ummm, no again. The YB-49 was the XB-35 with 8 jet engines replacing the 4 Wasp Majors + contra-rotating props. The XB-35 was a scale-up of the Northrop (note "o" not "u") N9M which was flying in the early 40's. The B-35 and B-36 were both results of an RFP for a bomber with a 10,000 mile range and a 10,000 pound bombload that came out in early 1941. The USAAF wanted a plane capable of bombing Berlin from the NE US.
It is interesting to note that the B-2 has a wingspan almost identical to that of the B-35/49.
The Horten aircraft was specifically designed with low radar cross section in mind, the low RCS of the B-49 was a happy accident. There was an incident where the B-49 was being tested off the coast of Calif and it frequently disappeared from the radar screens.
The first US stealth aircraft was the Lockheed A-12/F-12/SR-71. The Blackbird was often called the A-11 because LBJ read AMI as A-11, and the recce bird was originally the R/S-71 (following the R/S-70 nee XB-70), but LBJ screwed that up again.
You could get the same results by replacing the dirtiest 1% of the cars on the road. In California, at least 10% of the pollution comes from small gas engines, i.e. lawn mowers, leaf blowers, etc. - and narrowly avoided losing the right to regulate small gas engines.
The earliest versions of Win NT kept the GUI code out of the kernel, but that was changed in later versions of NT to improve performance. Bear in mind that NT was much more of a resource hog than OS/2.
More importantly is the corporate culture - M$ has played fast and loose with programming in the past, e.g. the original IBM PC and their first software for the Mac.
IBM PC - Intel's databooks for the 8086 specifically stated that interrupts below 20H were reserved for future versions of the 8086 family - IBM and M$ then proceed to use those interrupts for the BIOS routines.
Mac - Apple had many programming guidelines that were intended to allow migration to future versions of the 68000 family (e.g. don't use the upper 8 bits of addressing for flags). When Apple came out with a 68020 version of the Mac, a lot of the M$ software was broken by the upgrade.
64-bit Linux for AMD64 is out now (mainly since GCC supports AMD64). The rumors are that Solaris AMD64 should be out Summer 2004 (at least summer in the northern hemisphere). The wait is due to developing AMD64 support for Sun's compiler collection (Solaris was written for Sun's C compiler).
Having Solaris support the Opteron may help Sparc sales as it could increase the market for 64 bit software on Solaris - should be a very simple re-compile to prt from one platform to the other.
Crucial is listing their CT51272Y265 DIMM's for a measly $6999 - these are 4GB PC2100 registered with ECC. The price (ahem) may be a bit high, but if you really need the memory...
Hal Computers had an interesting "benchmark" back in the late 90's. Their Sparc box was capable of handling 3 GB (at close to 80 grand per GB), one chip simulation took 40 hours with 2 GB and 1.5 hours with 3 GB.
I also like Blowups Happen, one of the best (if not the best) predictions of a nuclear power plant I've seen (especially since it was written in 1940). There are some errors, for example RAH didn't know about delayed neutrons (nor did anyone else at the time), but the errors reflect the times more than RAH's ability.
Reading the review was timely, as I picked up a copy of the book last night - did like the 1930's style for the cover.
Think the editors did make at least one mistake - the area where Perry crashed is Torrey Pines
not Torrey Fines. I'll have to ask a co-worker (who graduated from La Jolla High in '47) about the roads through that area.