Ordinary ECC will correct any single-bit error in a 64 bit word, and detect all 2 bit and most other errors. Chipkill ECC (same RAM, fancier memory controller) spread the codes across multiple words and is stronger still.
Average soft error rates for DRAM are about 1 bit flip/gigabyte/month (sea level up to about 10x that in Denver), mostly due to cosmic rays.
the jump-to-edge syndrom is due to poor autocalibration of the trackpad. At least on mine, it's easily cured by forcing it to recalibrate. Just hit the keys in all 4 corners of the keyboard, Fn last (so esc-frame-right-Fn) to force a new calibration.
Specifically, if you shut down fast from high power output (a.k.a. an unexpacted stop like this), you leave the reactor core full of neutron-absorbing byproducts of the reaction. At high power these didn't interfere too badly, because you had lots of neutrons. But when you're trying to restart, they keep you from getting a self-sustaining chain reaction. So you basically have to wait for them to decay before you can restart.
A planned stop (maintence, fueling, etc) would have slowly tapered down the output so that it finished saturating these chemicals with neutrons the total quantities of reaction produce gradually dropped. That leaves the core pretty clean for a restart, but in an unplanned shutdown you just don't take chances - get it stopped, figure out why you stopped, then worry about how to get it started again:-P
Close - they don't need it, but it's (one of) the backups, and by policy they won't run without it. Once things start going awry, better to shut down while you're still in control than wait for something else to make it a serious incident...
I can't say for sure that Apple did this, but do note that randomizing it once per computer (e.g. ramdomize it *while* prebinding) is very nearly as effective as randomizing it every time. It still means someone can't write exploit shellcode that works on all (or even a significant fraction) of machines. This is the approach glibc's prelink uses.
Sure, it's possible (unlike, say, doing it with soybeans at 40 gallons/acre where you need more than 3 times the total arable land of the US!). But if completed, these algae ponds would have as much surface area as Lake Michigan! That's a *very* serious undertaking...
And impressive as that sounds, it's 3% solar efficiency (photocells are about 11%) ((1.5kW/m^2)/(10kW*hr/l)). So the thermodynamic situation certainly seems within the realm of possibility, and vast tracts of algae ought to cost less to build than similar-sized photovoltaic installations (not to mention less maintenance, *much* less energy needed to manufacture them, etc)
What's the math for that 525mi^2 figure? The numbers I've seen put US consumption at about 60billion gallons/year diesel and 120 billion gallons/year gasoline). Given that diesel engines are about 30-odd percent more efficient than gas ones, we'll say 150billion gallons/year combined could replace both (after a period of vehicle replacement). That gives a needed space of about 23000 mi^2 for this algae process (or 10000 mi^2 if we're only replacing current diesel and not gas - which won't work, because you get some of each when refining crude).
Which numbers that I'm using are different from yours?
If it doesn't take it out, it's a pretty crappy filter. Chlorine in solution with water isn't very stable, and comes out pretty easily.
The really easy way to get it out is to let the water stand for 24 hours. I just keep a pitcher of water in the fridge. The chlorine has time to work, time to work it's way out of the pitcher, and it's cold. Pretty simple.
Now, your waterworks might use chloramine instead of straight chlorine, and that's harder. Just letting it stand won't remove that. There are products that will remove it (usually sold for fish-tank water and the like), and most filtration systems that have any chemical portion will get it, but it's not quite as much a given as it is for chlorine.
Re:Will their tools stay free?
on
TrollTech to IPO?
·
· Score: 2, Informative
actually, they do. It's not part of the GPL (obviously) but it is a separate contractual agreement.
For one thing, many of the measures taken since the 80's to decrease emissions (NOx, particulates, unburned hydrocarbons, etc) have significant negative impacts on fuel economy; NOx limits especially, since the main way to combat that pollutant is to run cooler, which is less efficient. Carburetors weren't terribly inefficient, just dirty.
For another, the Prius is a bigger (4.5m vs 3.8m)and higher-performance(76+67hp, 0-60 10s vs. 55hp, 0-60 18s seconds) car than your Geo Metro. kudos for coming up with one of the very few cars where that's true.
FWIW, Cars like the Jetta TDI also get 50-ish MPG. The secret to doing it conventionally is what it's always been - trade off performance. The Prius is interesting because it gets into that efficiency league (perhaps not to the front, but certainly in the running) *without* being tiny or sluggish. This means it may be possible to sell the tech the unwashed masses, espescially with high gas prices (see how well it works for Europe).
FWIW, professional bicycle racing is somewhere around 400W. An uphill race (ala the Tour de France mountain stages or something) is ~500W if you want to win. Obviously not many can do this, and fewer still for very long:-)
Your local athletic friend who bikes a lot, but not commpetively, is probably in the vicinity of 200W. I don't think too many people would have trouble substaining 60W for a while (though I guess this *is* slashdot).
It is a nice way to put the numbers in perspective though, good example!
Well then, in the interest of forcing audiophiles to make up some new words, let's come up with some concrete definitions for these. To start us off, here's how I would read some of these terms. I doubt any self-respecting audiophile would agree with me:-)
soundstage is, as you suggested, stereo separation. I might also include the presence of very high-frequency response in it, since there's some evidence frequencies we don't perceive conciously still affect our ability to place the source.
extended is easy, lots of frequency range on both ends.
detailed, I would read as the ability to produce quick, quiet broadband effects well, even when playing a much louder main harmonic (think guitar frets). This basically boils down to the ability to put a small step/square-wave into a larger-magnitude waveform.
congestion makes me think of the sort of pre-echo sound of a piece that's been transformed into freq domain using an FFT, then resynthesized. This causes frequencies found in a short burst to get spread out in time, over the full length of the FFT window that detected them. This is a very characteristic artifact of digital compression, particularly MP3, but not something a player should normally struggle with.
liquid... I can't think of something for this w.r.t layback, but in a piece of music I might use it to describe a section played with a slightly irregular tempo (just a little bit rubato). If my playback gear is producing this effect, I doubt I will like it:-)
I took a physics exam using a sliderule a few years back, when the HP48's batteries gave out about 15 mins into it (d'oh!). The monitor didn't recognize it and challenged me, luckily the professor was older and did. I think he got a chuckle out of it too:-)
No, I won't comment on why I had the sliderule in my bag. There was a perfectly good reason, I assure you...
It's a Douglas Adams quote from Chapter 15 of Life, the Universe, and Everything. And yes, DNA definitely has a "whoa, that's some strong stuff" vibe going on:-)
I had to put it at a URL, as describing obfuscated perl without pissing off the lameness filter is hopeless. Maybe it's trying to tell me something...
Re:Major Features Dropped From GCC 4.0
on
GCC 4.0 Preview
·
· Score: 1
Basically GCC is not to emit or accept any standardized IL sufficient to separate backend from frontend completely. This is intended to ensure that a proprietary backend cannot benefit from GCC's language support, nor a proprietary language from GCC's optimizers and CPU targets; you must instead integrate with GCC-specific internal structures, ensuring that you are politely compelled to GPL your addition if you want to use the rest of GCC.
Of course, if you assume that only market discipline keeps print encyclopaedia's honest, then the argument that the majority's opinion matters more than the truth applies quite as much to them as well.
Do you run mythtv? I finally figured out that that's where some of the stranger ones were coming from - they're out of show descriptions on the weirder cable tv channels:-)
I've definitely had the experience of WINE being faster than 'native' WinXP performance. But I wasn't doing gaming or other driver-intensive things, I was running some FPGA layout and simulation software. Running my testsuite in the simulator didn't work in windows; I let it go for over an hour and then it crashed. In wine it took ~5minutes:-)
Now, in all fairness, I'll attribute that to at least 2 factors: - in Linux, my machine has 2 processors, and both were getting used. XP home only sees one, and I've never cared enough to pay additional microsoft tax to solve that. - The simulation run needed significantly more memory than I have; WinXP basically thrashed itself to death and then eventually the process crashed on an allocation failure. I have linux setup with swap on the second hard drive (and thus separate from the data files).
So windows was playing with double handicap, because I don't usually do real work in windows:-)
However, I do think the real deciding factor was the kernel's VM layer; linux had an advantage in having the swap on a separate spindle, but it also was doing a better job at managing the working set, and wasn't degenerating into random thrashing.
ACK. The highest standard mode I know of on ye olde D-sub is QXGA (2048Ã--1536px) @85Hz, which is about 4x the data rate of 1080p @30fps.
I even had a monitor that could run it... took pretty spendy cables though :-)
Ordered data is the ext3 default. Did you mean journalled data?
Err, the Dark Knight *was* PG-13 (IMDB).
No, watts are correct. The thing that's special about this battery isn't the capacity, it's the rapid charge/discharge.
Qt Designer is part of the core package, and is excellent.
Correct. And e-ink displays (like the Kindle) would be subtractive displays.
Ordinary ECC will correct any single-bit error in a 64 bit word, and detect all 2 bit and most other errors. Chipkill ECC (same RAM, fancier memory controller) spread the codes across multiple words and is stronger still.
Average soft error rates for DRAM are about 1 bit flip/gigabyte/month (sea level up to about 10x that in Denver), mostly due to cosmic rays.
the jump-to-edge syndrom is due to poor autocalibration of the trackpad. At least on mine, it's easily cured by forcing it to recalibrate. Just hit the keys in all 4 corners of the keyboard, Fn last (so esc-frame-right-Fn) to force a new calibration.
http://wiki.laptop.org/go/Recalibrating_Touchpad
Specifically, if you shut down fast from high power output (a.k.a. an unexpacted stop like this), you leave the reactor core full of neutron-absorbing byproducts of the reaction. At high power these didn't interfere too badly, because you had lots of neutrons. But when you're trying to restart, they keep you from getting a self-sustaining chain reaction. So you basically have to wait for them to decay before you can restart.
:-P
A planned stop (maintence, fueling, etc) would have slowly tapered down the output so that it finished saturating these chemicals with neutrons the total quantities of reaction produce gradually dropped. That leaves the core pretty clean for a restart, but in an unplanned shutdown you just don't take chances - get it stopped, figure out why you stopped, then worry about how to get it started again
Close - they don't need it, but it's (one of) the backups, and by policy they won't run without it. Once things start going awry, better to shut down while you're still in control than wait for something else to make it a serious incident...
I can't say for sure that Apple did this, but do note that randomizing it once per computer (e.g. ramdomize it *while* prebinding) is very nearly as effective as randomizing it every time. It still means someone can't write exploit shellcode that works on all (or even a significant fraction) of machines. This is the approach glibc's prelink uses.
Sure, it's possible (unlike, say, doing it with soybeans at 40 gallons/acre where you need more than 3 times the total arable land of the US!). But if completed, these algae ponds would have as much surface area as Lake Michigan! That's a *very* serious undertaking...
And impressive as that sounds, it's 3% solar efficiency (photocells are about 11%)
((1.5kW/m^2)/(10kW*hr/l)). So the thermodynamic situation certainly seems within the realm of possibility, and vast tracts of algae ought to cost less to build than similar-sized photovoltaic installations (not to mention less maintenance, *much* less energy needed to manufacture them, etc)
What's the math for that 525mi^2 figure? The numbers I've seen put US consumption at about 60billion gallons/year diesel and 120 billion gallons/year gasoline). Given that diesel engines are about 30-odd percent more efficient than gas ones, we'll say 150billion gallons/year combined could replace both (after a period of vehicle replacement). That gives a needed space of about 23000 mi^2 for this algae process (or 10000 mi^2 if we're only replacing current diesel and not gas - which won't work, because you get some of each when refining crude).
Which numbers that I'm using are different from yours?
If it doesn't take it out, it's a pretty crappy filter. Chlorine in solution with water isn't very stable, and comes out pretty easily.
The really easy way to get it out is to let the water stand for 24 hours. I just keep a pitcher of water in the fridge. The chlorine has time to work, time to work it's way out of the pitcher, and it's cold. Pretty simple.
Now, your waterworks might use chloramine instead of straight chlorine, and that's harder. Just letting it stand won't remove that. There are products that will remove it (usually sold for fish-tank water and the like), and most filtration systems that have any chemical portion will get it, but it's not quite as much a given as it is for chlorine.
actually, they do. It's not part of the GPL (obviously) but it is a separate contractual agreement.
p hp
http://www.kde.org/whatiskde/kdefreeqtfoundation.
For one thing, many of the measures taken since the 80's to decrease emissions (NOx, particulates, unburned hydrocarbons, etc) have significant negative impacts on fuel economy; NOx limits especially, since the main way to combat that pollutant is to run cooler, which is less efficient. Carburetors weren't terribly inefficient, just dirty.
For another, the Prius is a bigger (4.5m vs 3.8m)and higher-performance(76+67hp, 0-60 10s vs. 55hp, 0-60 18s seconds) car than your Geo Metro. kudos for coming up with one of the very few cars where that's true.
FWIW, Cars like the Jetta TDI also get 50-ish MPG. The secret to doing it conventionally is what it's always been - trade off performance. The Prius is interesting because it gets into that efficiency league (perhaps not to the front, but certainly in the running) *without* being tiny or sluggish. This means it may be possible to sell the tech the unwashed masses, espescially with high gas prices (see how well it works for Europe).
FWIW, professional bicycle racing is somewhere around 400W. An uphill race (ala the Tour de France mountain stages or something) is ~500W if you want to win. Obviously not many can do this, and fewer still for very long :-)
Your local athletic friend who bikes a lot, but not commpetively, is probably in the vicinity of 200W. I don't think too many people would have trouble substaining 60W for a while (though I guess this *is* slashdot).
It is a nice way to put the numbers in perspective though, good example!
Well then, in the interest of forcing audiophiles to make up some new words, let's come up with some concrete definitions for these. To start us off, here's how I would read some of these terms. I doubt any self-respecting audiophile would agree with me :-)
:-)
soundstage is, as you suggested, stereo separation. I might also include the presence of very high-frequency response in it, since there's some evidence frequencies we don't perceive conciously still affect our ability to place the source.
extended is easy, lots of frequency range on both ends.
detailed, I would read as the ability to produce quick, quiet broadband effects well, even when playing a much louder main harmonic (think guitar frets). This basically boils down to the ability to put a small step/square-wave into a larger-magnitude waveform.
congestion makes me think of the sort of pre-echo sound of a piece that's been transformed into freq domain using an FFT, then resynthesized. This causes frequencies found in a short burst to get spread out in time, over the full length of the FFT window that detected them. This is a very characteristic artifact of digital compression, particularly MP3, but not something a player should normally struggle with.
liquid... I can't think of something for this w.r.t layback, but in a piece of music I might use it to describe a section played with a slightly irregular tempo (just a little bit rubato). If my playback gear is producing this effect, I doubt I will like it
I took a physics exam using a sliderule a few years back, when the HP48's batteries gave out about 15 mins into it (d'oh!). The monitor didn't recognize it and challenged me, luckily the professor was older and did. I think he got a chuckle out of it too :-)
No, I won't comment on why I had the sliderule in my bag. There was a perfectly good reason, I assure you...
It's a Douglas Adams quote from Chapter 15 of Life, the Universe, and Everything. And yes, DNA definitely has a "whoa, that's some strong stuff" vibe going on :-)
Almost right. It does rm -rf ~ instead, which is perhaps worse as it's more likely to work :-)
decomposed in detail for the morbidly curious: http://puetzk.org/projects/perl-sig-trojan.txt
I had to put it at a URL, as describing obfuscated perl without pissing off the lameness filter is hopeless. Maybe it's trying to tell me something...
Basically GCC is not to emit or accept any standardized IL sufficient to separate backend from frontend completely. This is intended to ensure that a proprietary backend cannot benefit from GCC's language support, nor a proprietary language from GCC's optimizers and CPU targets; you must instead integrate with GCC-specific internal structures, ensuring that you are politely compelled to GPL your addition if you want to use the rest of GCC.
Of course, if you assume that only market discipline keeps print encyclopaedia's honest, then the argument that the majority's opinion matters more than the truth applies quite as much to them as well.
Do you run mythtv? I finally figured out that that's where some of the stranger ones were coming from - they're out of show descriptions on the weirder cable tv channels :-)
I've definitely had the experience of WINE being faster than 'native' WinXP performance. But I wasn't doing gaming or other driver-intensive things, I was running some FPGA layout and simulation software. Running my testsuite in the simulator didn't work in windows; I let it go for over an hour and then it crashed. In wine it took ~5minutes :-)
:-)
Now, in all fairness, I'll attribute that to at least 2 factors:
- in Linux, my machine has 2 processors, and both were getting used. XP home only sees one, and I've never cared enough to pay additional microsoft tax to solve that.
- The simulation run needed significantly more memory than I have; WinXP basically thrashed itself to death and then eventually the process crashed on an allocation failure. I have linux setup with swap on the second hard drive (and thus separate from the data files).
So windows was playing with double handicap, because I don't usually do real work in windows
However, I do think the real deciding factor was the kernel's VM layer; linux had an advantage in having the swap on a separate spindle, but it also was doing a better job at managing the working set, and wasn't degenerating into random thrashing.