I'm sure they're talking specifically about the virtualization features in the Vanderpool architecture, but it's worth noting that implementing VMs even with the current Intel x86 architecture implementations would be a lot easier if only the priviliged instructions behaved "properly" when executed in non-priviliged mode.
One of the biggest problems that a VM implementation under x86 has to solve is dealing with the fact that some priviliged instructions, critical to the proper operation of OSes, silently execute with no visible side-effects when executed in non-priviliged mode. Given that a VM essentially executes the guest OS as a non-priviliged "user application", it is critical that these instructions be trappable, but they're not, so various code analysis and single-stepping (ptrace) approaches are required.
The first is a command-line utility for processing the raw format images from a variety of cameras, including Nikon's NEF format and the second is a great plug-in for Gimp that integrates it with a GUI.
Linux-friendly heart rate monitors
on
Running for Geeks
·
· Score: 2, Interesting
Polar's heart rate monitors are nice and the protocol for their IR upload has been, errr, community-documented thanks to some open-source programming efforts. I keep my triathlon training log based on the software:
All complex periodic waveforms are constructed from a superposition of sine waves of different amplitudes, frequencies and phases. So, if simple sine waves can be reconstructed correctly, complex waveforms that are sums of sine waves can also be constructed correctly.
The original poster is correct. What you get with consumer digital cameras is a collection of sensors built into the CCD (or CMOS) imaging array, each of which has a built-in filter for a particular color. The total number of pixels reported (i.e. "X megapixels") is the sum of all red, green and blue sensitive sensors. You do not get "X megasensors", each of which is independently sensitive to red, green and blue. The ratios (and distribution) of the red, green and blue sensors are based on the sensitivities of the human eye to different spectral ranges.
It is indeed true that the Spirit camera is comparable to a 3 megapixel consumer camera, not 1 megapixel.
I really can't see how linus can claim copyright to the distribution of any source which happens to run with the linux kernel - but does not contain any part of it.
For device driver (and similar) modules that run within the kernel, the statement that they "don't contain any part of it [the kernel source]" can't be made so easily. To develop and compile the driver, the kernel header files are needed. Even putting aside structure definitions and the like, which are kernel sources, it is very easy to get whole functions subject to GPL be included in binary-only drivers by way of inlining (see the example of "static inline..." functions mentioned in the original discussion).
"A design which, if it breaks, opens a gash into the interior structure is thus a flawed design"
"As far as I recall, the shuttle does not have leading egde flaps. Thus it shouldn't be a reason for a 'split' design like the article describes, a solid leading edge panel made of reinforced carbon should be both possible and perhapes even less expensive"
You sound uninformed and are speculating without even attempting to research the subject. The RCC (Reinforced Carbon-Carbon) panels have gaps between them for a reason. The panels are mounted on floating joints to reduce the loads placed on them due to wing deflections. This also helps reduce the effects of mismatched thermal expansion coefficients between the aluminum wing structure and the carbon composite material they are made of. You can read more about the RCC panels and their attachment to the wing structure at:
Your comment that a design that causes a breach to the interior structure in case of failure is a flawed one doesn't make too much sense either. The TPS (Thermal Protection System) design is there specifically to protect the orbiter structures that cannot withstand the heat of reentry. Therefore, by design, if the TPS was not there, the structure would be breached. You should look for flaws in the design based on a lack of anticipation of possible external damage modes and not in that it was a very critical system whose loss results in an overall failure of the orbiter.
Slashdot Mirror
One of the biggest problems that a VM implementation under x86 has to solve is dealing with the fact that some priviliged instructions, critical to the proper operation of OSes, silently execute with no visible side-effects when executed in non-priviliged mode. Given that a VM essentially executes the guest OS as a non-priviliged "user application", it is critical that these instructions be trappable, but they're not, so various code analysis and single-stepping (ptrace) approaches are required.
Raw Digital Photo Decoding in Linux
RawPhoto GIMP-2.0 plug-in
The first is a command-line utility for processing the raw format images from a variety of cameras, including Nikon's NEF format and the second is a great plug-in for Gimp that integrates it with a GUI.
http://www.employees.org/~bozceri/training
and the link to the Polar heart rate monitor data download project:
http://daveb.net/s710/
All complex periodic waveforms are constructed from a superposition of sine waves of different amplitudes, frequencies and phases. So, if simple sine waves can be reconstructed correctly, complex waveforms that are sums of sine waves can also be constructed correctly.
The original poster is correct. What you get with consumer digital cameras is a collection of sensors built into the CCD (or CMOS) imaging array, each of which has a built-in filter for a particular color. The total number of pixels reported (i.e. "X megapixels") is the sum of all red, green and blue sensitive sensors. You do not get "X megasensors", each of which is independently sensitive to red, green and blue. The ratios (and distribution) of the red, green and blue sensors are based on the sensitivities of the human eye to different spectral ranges. It is indeed true that the Spirit camera is comparable to a 3 megapixel consumer camera, not 1 megapixel.
For device driver (and similar) modules that run within the kernel, the statement that they "don't contain any part of it [the kernel source]" can't be made so easily. To develop and compile the driver, the kernel header files are needed. Even putting aside structure definitions and the like, which are kernel sources, it is very easy to get whole functions subject to GPL be included in binary-only drivers by way of inlining (see the example of "static inline ..." functions mentioned in the original discussion).
"As far as I recall, the shuttle does not have leading egde flaps. Thus it shouldn't be a reason for a 'split' design like the article describes, a solid leading edge panel made of reinforced carbon should be both possible and perhapes even less expensive"
You sound uninformed and are speculating without even attempting to research the subject. The RCC (Reinforced Carbon-Carbon) panels have gaps between them for a reason. The panels are mounted on floating joints to reduce the loads placed on them due to wing deflections. This also helps reduce the effects of mismatched thermal expansion coefficients between the aluminum wing structure and the carbon composite material they are made of. You can read more about the RCC panels and their attachment to the wing structure at:
http://science.ksc.nasa.gov/shuttle/technology/sts -newsref/sts_sys.html#sts-rcc
Your comment that a design that causes a breach to the interior structure in case of failure is a flawed one doesn't make too much sense either. The TPS (Thermal Protection System) design is there specifically to protect the orbiter structures that cannot withstand the heat of reentry. Therefore, by design, if the TPS was not there, the structure would be breached. You should look for flaws in the design based on a lack of anticipation of possible external damage modes and not in that it was a very critical system whose loss results in an overall failure of the orbiter.