One of the first reactors in Switzerland was in Lucens. Construction was plagued with delays and cost blowouts. And when it was finished, it ran for a short time and then had a meltdown. Some accounts place the Lucens accident at a 4 on the INES scale, some at 4 or 5.
The key is to produce enough thrust with the wing to keep the aircraft flying at the required
forward velocity. This thrust is produced by placing the wing at a lower angle of attack,
relative to the local flow velocity, on the upstroke, and at a higher angle of attack on the
downstroke. It can be seen in the figure below that this results in a large amount of lift
and thrust on the downstroke and a small amount of lift and drag on the upstroke. The net
result is positive lift and positive thrust.
Throughout the stroke the wing must twist with the proper magnitude and phase to produce the
proper angles of attack. This is accomplished passively by designing the structure in such a
way that the aerodynamic and inertial forces produce the proper twist.
So, this is NOT merely a glider.
The up flap does NOT cancel out the down flap
The wings' movement is NOT purely vertical, there is a twist component.
It sounds like you've missed the latest turn in the sequence of the prosecutor flip flopping. Here's a recap:
20. August 2010: Duty prosecutor Maria Häljebo Kjellstrand decides it looks like rape
21. August 2010: Higher ranking prosecutor Eva Finné decides it doesn't
1. September 2010: Chief prosecutor Marianne Ny decides actually it does look like rape
> Rather, GPL is incompatible with anything else that can't be re-licensed as GPL, and > that includes GPL v2 and v3, which can't even be mixed among themselves.
Saying that GPLv2 and GPLv3 "can't even be mixed among themselves" is wrong and misleading.
Section 14 of GPLv2 specifically deals with the problem of later versions of the licence and sets out the options. A copyright holder can choose to allow work to be used with later versions, such as GPLv3, or can choose not to. There are also more complex options. The licence itself doesn't force the choice one way or the other.
Someone wrote a whole essay expanding on the above. A choice quote:
"These essays and this writing style are tempting to people outside the subculture at hand because of their engaging personal tone and idiosyncratic, insider's view. But after a while, you begin to notice that all the essays are an elaborate set of mirrors set up to reflect different facets of the author, in a big distributed act of participatory narcissism."
The whole essay, "Dabblers and Blowhards" is here:
> there's only a handful of applications we need
> [damn you, Texas Instruments! Where's your Linux
> version of Code Composer?
The code composer CD from December 2004 includes statically linked x86 linux binaries.
I use it every day and it works just fine. Admittedly, it doesn't include the GUI tools (simulator, debugger), but the compiler is there, and that's all I care about.
To what extent is google's policy determined by the technical staff? There are a bunch of things which have happened on google which suggest that there's some sort of body making policy decisions. Who makes these decisions?
Examples:
Pages can be manually removed from google for doing dubious things (e.g. cloaking). Someone must have actively decided that the benefits of this type of censorship exceeded the costs.
Someone decided to pull the anti-scientology pages, and then someone decided to put some of them back. Who?
Someone decided against making a list of removed sites so that we can all see what is being supressed by google.
I've got a Hauppauge Pixelview PV-BT878P+ which works fine for me. I had to find a newer version of the BT878 driver to make it work with the 2.17 kernel, it looks like 2.4 has everything the card needs. It took some fiddling with the driver's source to get the sound to work.
Interfaces
Tuner in. Needs an amplified signal, e.g. cable TV or a VCR. A normal aerial doesn't work.
S-video in. I think this is used by modern camcorders. I don't use it.
Composite video in. This is what my VCR emits.
Audio out.
Picture quality is fine for TV, the card can capture at up to 800x600. Supposedly the card works with every TV standard there is (PAL, NTSC, etc.) but I only have PAL so I don't know if the others actually work. The card puts the video directly in the graphics card's memory, so the CPU is hardly loaded at all if you're just watching TV (2% at worst).
Problems
The motherboard interferes with picture and sound on some channels. Sound is generally no problem unless I'm "doing something". If I compile the kernel, it sounds like there's an arcade game in the background of whatever's on TV. Similarly, some channels get a bit "stripy". Fine for watching TV, annoying when you want to capture pictures.
I didn't get the remote control to work. I didn't try very hard, just the maze of drivers and webpages explaining what to do wasn't worth trying to navigate.
My CPU (166MHz Pentium) is too slow to capture films. (I get 10 frames/s at 320x240)
Capturing films takes a heap of disk space because the card has no hardware compression.
I can't change the sound volume. I don't know if the card can do that or not. Doesn't matter---I just loop the sound through my sound card and set the volume that way.
For many applications, writing your own makes good sense. But even then you can get a flying start by using components made by others with high availability and reliability in mind. By building your own using fine-grained components you keep control over what you're building while also having some comfort in knowing that others have successfully done similar things using the same tools. And been happy with the results.
One example is the erlang programming language and libraries, which were developed specifically for writing high availability telephone systems. This is open source, available as tar.gz for solaris or in debian, red hat, BSD...
People have gone on to use these tools (both on Solaris and other OSes) to build high availability web systems (e.g. lodbroker) and robust email systems (e.g. bluetail).
I don't really agree with the idea of Linux in embedded systems. I think it makes much more sense to develop an OS for embedded systems that starts small and stays small rather than trying to adapt a much larger system for a smaller one.
Depends what your embedded system is.
The embedded system I work with is a single card with a 50MHz power PC and 32Mb of RAM, about the size of a compact disk. It's part of PABX (a small telephone exchange for small businesses).
50MHz and 32Mb. That sounds a lot like the linux system everyone had at home a couple of years ago, except that it has no hard disk. Linux takes about 800k and, with some realtime patches applied, has quite decent realtime behaviour.
Earlier we were running a "real" realtime OS called VxWorks. VxWorks has its nice points (such as more rigid realtime behaviour), but it's hard to argue with a familar environment, no "gotchas" for new developers, and no licence fees.
I used an old DEC monitor for a couple of years a while back. It worked fine. You basically have two options
1. Buy a video card specially made for fixed frequency monitors
2. Fiddle with your X config so that it runs at the frequency the monitor wants.
Option #2 is nice because it's free and works well, though ordinary text modes don't work. The main problem you're likely to have is that many fixed frequency monitors have 3 BNC connectors and expect sync signals mixed in with green. You can build a simple circuit to deal with this. Fiddling with X timings is tiring but eventually you get there.
Is driving on the right really the obvious majority standard?
There are some populous countries with left hand traffic, including India, Japan, Indonesia and, roughly, the southern half of Africa.
According to http://www.ar100123.demon.co.uk/signs/leftf.htm
Countries where driving on the left is normal:
Anguilla Antigua & Barbuda Australia Bahamas Bangladesh Barbados Bermuda Bhutan Bophuthatswana Botswana British Virgin Islands Brunei Cayman Islands Channel Islands Ciskei Cyprus Dominica Falkland Islands Fiji Grenada Guyana Hong Kong India Indonesia Ireland Jamaica Japan Kenya Lesotho Macau Malawi Malaysia Malta Mauritius Montserrat Mozambique Pakistan Papua New Guinea Seychelles Sikkim Singapore Solomon Islands Somalia South Africa Sri Lanka St Kitts & Nevis St. Helena St. Lucia Surinam Swaziland Tanzania Thailand Tonga Trinidad and Tobago Uganda United Kingdom Venda Zambia Zimbabwe St. Vincent & Grenadines Namibia Nepal New Zealand
Slashdot Mirror
One of the first reactors in Switzerland was in Lucens. Construction was plagued with delays and cost blowouts. And when it was finished, it ran for a short time and then had a meltdown. Some accounts place the Lucens accident at a 4 on the INES scale, some at 4 or 5.
Reference: http://en.wikipedia.org/wiki/Lucens_reactor
Reference: http://de.wikipedia.org/wiki/Reaktor_Lucens
Things work well in Switzerland, but they're not perfect either.
The project has a homepage: http://hpo.ornithopter.net/
Under "technical info", it says
The key is to produce enough thrust with the wing to keep the aircraft flying at the required
forward velocity. This thrust is produced by placing the wing at a lower angle of attack,
relative to the local flow velocity, on the upstroke, and at a higher angle of attack on the
downstroke. It can be seen in the figure below that this results in a large amount of lift
and thrust on the downstroke and a small amount of lift and drag on the upstroke. The net
result is positive lift and positive thrust.
Throughout the stroke the wing must twist with the proper magnitude and phase to produce the
proper angles of attack. This is accomplished passively by designing the structure in such a
way that the aerodynamic and inertial forces produce the proper twist.
So, this is NOT merely a glider.
The up flap does NOT cancel out the down flap
The wings' movement is NOT purely vertical, there is a twist component.
It sounds like you've missed the latest turn in the sequence of the prosecutor flip flopping. Here's a recap:
20. August 2010: Duty prosecutor Maria Häljebo Kjellstrand decides it looks like rape
21. August 2010: Higher ranking prosecutor Eva Finné decides it doesn't
1. September 2010: Chief prosecutor Marianne Ny decides actually it does look like rape
Source #1: http://www.thelocal.se/28704/20100901/
Source #2: http://www.aklagare.se/In-English/
> Rather, GPL is incompatible with anything else that can't be re-licensed as GPL, and
> that includes GPL v2 and v3, which can't even be mixed among themselves.
Saying that GPLv2 and GPLv3 "can't even be mixed among themselves" is wrong and
misleading.
Section 14 of GPLv2 specifically deals with the problem of later versions of the
licence and sets out the options. A copyright holder can choose to allow work to be used
with later versions, such as GPLv3, or can choose not to. There are also more
complex options. The licence itself doesn't force the choice one way or the other.
Matt
Someone wrote a whole essay expanding on the above. A
w hards.htm
choice quote:
"These essays and this writing style are tempting to people outside the subculture at hand because of their engaging personal tone and idiosyncratic, insider's view. But after a while, you begin to notice that all the essays are an elaborate set of mirrors set up to reflect different facets of the author, in a big distributed act of participatory narcissism."
The whole essay, "Dabblers and Blowhards" is here:
http://www.idlewords.com/2005/04/dabblers_and_blo
Matt
> there's only a handful of applications we need
> [damn you, Texas Instruments! Where's your Linux
> version of Code Composer?
The code composer CD from December 2004 includes
statically linked x86 linux binaries.
I use it every day and it works just fine. Admittedly, it doesn't include the GUI tools (simulator, debugger), but the compiler is there, and that's all I care about.
Matt
Whether you think it's a NIC card or not depends on whether you think NIC stands for network-interface-card or network-interface-controller.
Hardware people often think the latter, e.g. this
product sheet from Natsemi.
Matt
Examples:
Pages can be manually removed from google for doing dubious things (e.g. cloaking). Someone must have actively decided that the benefits of this type of censorship exceeded the costs.
Someone decided to pull the anti-scientology pages, and then someone decided to put some of them back. Who?
Someone decided against making a list of removed sites so that we can all see what is being supressed by google.
Matt
On my mozilla (build ID 2002051009, on linux), the default config seems to be that ctrl+pgup and ctrl+pgdn cycle through the tabs.
Matt
Interfaces
Picture quality is fine for TV, the card can capture at up to 800x600. Supposedly the card works with every TV standard there is (PAL, NTSC, etc.) but I only have PAL so I don't know if the others actually work. The card puts the video directly in the graphics card's memory, so the CPU is hardly loaded at all if you're just watching TV (2% at worst).
Problems
Matt
For many applications, writing your own makes good sense. But even then you can get a flying start by using components made by others with high availability and reliability in mind. By building your own using fine-grained components you keep control over what you're building while also having some comfort in knowing that others have successfully done similar things using the same tools. And been happy with the results.
One example is the erlang programming language and libraries, which were developed specifically for writing high availability telephone systems. This is open source, available as tar.gz for solaris or in debian, red hat, BSD...
People have gone on to use these tools (both on Solaris and other OSes) to build high availability web systems (e.g. lodbroker) and robust email systems (e.g. bluetail).
I don't really agree with the idea of Linux in embedded systems. I think it makes much more sense to develop an OS for embedded systems that starts small and stays small rather than trying to adapt a much larger system for a smaller one.
Depends what your embedded system is.
The embedded system I work with is a single card with a 50MHz power PC and 32Mb of RAM, about the size of a compact disk. It's part of PABX (a small telephone exchange for small businesses).
50MHz and 32Mb. That sounds a lot like the linux system everyone had at home a couple of years ago, except that it has no hard disk. Linux takes about 800k and, with some realtime patches applied, has quite decent realtime behaviour.
Earlier we were running a "real" realtime OS called VxWorks. VxWorks has its nice points (such as more rigid realtime behaviour), but it's hard to argue with a familar environment, no "gotchas" for new developers, and no licence fees.
Matthias
There's a FAQ at
http://www.devo.com/video/
I used an old DEC monitor for a couple of
years a while back. It worked fine. You basically
have two options
1. Buy a video card specially made for fixed
frequency monitors
2. Fiddle with your X config so that it runs
at the frequency the monitor wants.
Option #2 is nice because it's free and works
well, though ordinary text modes don't work.
The main problem you're likely to have is that
many fixed frequency monitors have 3 BNC connectors and expect sync signals mixed in with green. You can build a simple circuit to deal
with this. Fiddling with X timings is tiring but
eventually you get there.
Matthias
Is driving on the right really the obvious majority standard?
There are some populous countries
with left hand traffic, including India,
Japan, Indonesia and, roughly, the southern
half of Africa.
According to http://www.ar100123.demon.co.uk/signs/leftf.htm
Countries where driving on the left is normal:
Anguilla Antigua & Barbuda Australia Bahamas Bangladesh Barbados Bermuda
Bhutan Bophuthatswana Botswana British Virgin Islands Brunei Cayman
Islands Channel Islands Ciskei Cyprus Dominica Falkland Islands Fiji
Grenada Guyana Hong Kong India Indonesia Ireland Jamaica Japan Kenya
Lesotho Macau Malawi Malaysia Malta Mauritius Montserrat Mozambique
Pakistan Papua New Guinea Seychelles Sikkim Singapore Solomon Islands
Somalia South Africa Sri Lanka St Kitts & Nevis St. Helena St. Lucia
Surinam Swaziland Tanzania Thailand Tonga Trinidad and Tobago Uganda
United Kingdom Venda Zambia Zimbabwe St. Vincent & Grenadines Namibia
Nepal New Zealand