I don't think so. You have to be in shifting prgram S6 and DSC (whatever that is) deactivated, push the shift lever forward and hold it, press the accelerator pedal (aka 'gas') down to the floor!! [you'll hear the engine rev' up] and then release the shift lever to activate the "race start" or "burnout" modes. This can't happen accidently - or in other words: The car doesn't behave in a way you wouldn't expect even if you don't know about these modes because you haven't read the manual.
IMHO the actions to activate these modes are quite intuitive and very much like manually performed "race starts" - hold down clutch, shift in first gear, rev up engine (though you wouldn't put the pedal to the metal on a normal car of course), release clutch.
> i ment is it 100% like RISC, that there isn't anything that is jinxed or
There's no standard that defines what 100% RISC is or not. RISC just means "reduced instruction set computer" but that term is often missused. So (marketing) people want you to know that Pentium-whatever or other X86-compatible CPUs have "RISC inside" and other stupid nonsense. RISC is (was) a design philosophy - no feature.
> partially incompatible to the way other RISC cpus handle sosme thing...
Err - RISC CPUs don't have to be compatible at all (instruction set wise) - a SPARC CPU won't process software written vor ARM CPUs. And how things are handled internally doesn't matter for users and software developers.
And what about 1800MHz? GSM (in europe and maybe elsewhere) uses both bands and most (all?) GSM cellphones available here nowadays are so-called 'dualband' i.e. can deal with 900 and 1800MHz frequencies.
> Freedom can be bad. Suppose you make really cheap guns that work really well, and you decide to > give them away completely free. Then some terrorist comes along and takes a few thousands of > your guns, for free.
Yeah, you are right. I should sell those cheap weapons to those evil terrorists and make money that way. And I should do the same with the cheap bread I made to feed the hungry.
Sorry, I can't take someone serious who writes up such stupid unrelated nonesense like you. (I stopped reading after the second paragraph BTW).
Common myth. Let's look at the geostationary orbit (where most TV, telecom and weather satellites nowadays are) which is ~36000 km above the surface, i.e. it has an diameter of nearly 85000km and a length of over 265000km. So even if you require a minimum safety distance of 50km between satelites in geostationary orbit, there's place for over 5000 satellites.
Currently there are less than 300 AFAIK. (Here's a list of most of them). Please note that satellites which that are put put out of service usually will be parked in a "graveyard orbit" above the geostationary orbit - if there's still enough fuel and the motors still work of course.
The lower orbits (LEO, ~150-500km), where most military satellites, GPS, GLONASS, IRIDIUM and the like are placed is less problematic, since they are 'self cleaning' from old satellites: Objects there will deorbit sooner or later (the larger the sooner) since those orbits aren't very stable (due to earth's irregular shape) and the very thin atmosphere there reduces the orbital speed. That's why spacestations like Mir or ISS have to be boosted from time to time to higher orbits by a docked spacecraft.
The space debris problem is not caused by dead satellites, it's caused by all those tiny nuts and bolts left over from stage seperations, solar panel releases and so on which are affected much less by those deorbiting effects. Satellite and launch system designers nowadays take more care of this as they used in the 60-70s, e.g. the parts of the fairing which protects the payload of a launcher, are kept together connected by a wire or something after the fairing is ejected - the fairing just used to be blown up in seperate pieces by small pyros before.
Actually this is the #1 reason I don't think she was hit by this meteorite - it's a common missconception that meteorites are hot when they hit the earth. There's an FAZ article about common myths about meteorites.
The #2 reason: Even a small piece of iron/rock like this, falling from more than 100m height surely would break a girl's foot if it hits it.
My guess: She bought the meteorite via internet and maybe it fell on her foot when she opened the package...
> From the DirectFB web-site [directfb.org], they support Matrox [...]
But only on Linux. XFree should be an OS independent project and I really disklike the attemps from the linux camp to change that with the dependency of certain features on weird linux kernel modules and the like.
AFAIK it's worse since it's not possible at all to get an IRIX license seperate from any hardware from any dealer (see here) and if you go to SGI directly and say "can I have IRIX 6.2 for my old Indy?" - well, good luck! (I bet they will tell you to ask your local dealer;-)
The MD5 checksum mentioned in the weblog is *NOT* stored alongside the distribution file. It comes from the package system (or 'ports' in FreeBSD jargon). The package system fetches the tarball from the distribution system and compares its own MD5 checksum against the one calculated from the fetched file.
Slashdot Mirror
I don't think so. You have to be in shifting prgram S6 and DSC (whatever that is) deactivated, push the shift lever forward and hold it, press the accelerator pedal (aka 'gas') down to the floor!! [you'll hear the engine rev' up] and then release the shift lever to activate the "race start" or "burnout" modes. This can't happen accidently - or in other words: The car doesn't behave in a way you wouldn't expect even if you don't know about these modes because you haven't read the manual.
IMHO the actions to activate these modes are quite intuitive and very much like manually performed "race starts" - hold down clutch, shift in first gear, rev up engine (though you wouldn't put the pedal to the metal on a normal car of course), release clutch.
> i ment is it 100% like RISC, that there isn't anything that is jinxed or
There's no standard that defines what 100% RISC is or not. RISC just means "reduced instruction set computer" but that term is often missused. So (marketing) people want you to know that Pentium-whatever or other X86-compatible CPUs have "RISC inside" and other stupid nonsense.
RISC is (was) a design philosophy - no feature.
> partially incompatible to the way other RISC cpus handle sosme thing...
Err - RISC CPUs don't have to be compatible at all (instruction set wise) - a SPARC CPU won't process software written vor ARM CPUs. And how things are handled internally doesn't matter for users and software developers.
The People's Republic of China and Taiwan.
> is it totally compatible with other RISC cpu's, i mean is it 100% to the standards,
Which standards?
No, it's based on Cyrix. VIA bought cyrix some time ago.
Yes, the blame goes to openssl, nobody denies that. But the worm is not an openssl-worm since it does not work (say) on NetBSD systems.
No, Apache is as much to blame here as Linux.
6 worm since it fails to infect any other combination (AFAIK).
This is an apache-modssl-openssl-0.9.6.d-or-earlier-linux-x8
> Processor speed /dev/random
> Old Unit: Megahertz
> New Unit: Megahertz *
IMHO it's more like:
Old Unit: MIPS, FLOPS, SPEC*, linpack etc.
New Unit: Megahertz of a maybe-equivalent Pentium 4 CPU
Well, that depends on the pressure and temperature ;-).
And what about 1800MHz? GSM (in europe and maybe elsewhere) uses both bands and most (all?) GSM cellphones available here nowadays are so-called 'dualband' i.e. can deal with 900 and 1800MHz frequencies.
> The thing you saw was Rudolph Gattenbrink about 1992?
The 'thing' certainly was Upuaut (the name of the robot) and here's the official website of Gantenbrink and his robot.
> Freedom can be bad. Suppose you make really cheap guns that work really well, and you decide to
> give them away completely free. Then some terrorist comes along and takes a few thousands of
> your guns, for free.
Yeah, you are right. I should sell those cheap weapons to those evil terrorists and make money that way. And I should do the same with the cheap bread I made to feed the hungry.
Sorry, I can't take someone serious who writes up such stupid unrelated nonesense like you. (I stopped reading after the second paragraph BTW).
Dude, if something is free you can't steal it. You can take it or not but you just can't steal it.
Yes, I know. Some of you think that freedom is a bad, bad thing...
> The first image transmitted over radio waves (from a commercial television station or
> demonstration) was Felix the Cat in 1946.
No, since they used wireless near-live TV during the Olympic Games 1936.
Paul Gottlieb Nipkow was German, not Russian.
[Going back to the start of the thread]
Since the 'newer, smaller, niftier' satellite replaces an old one this no problem.
Common myth. Let's look at the geostationary orbit (where most TV, telecom and weather satellites nowadays are) which is ~36000 km above the surface, i.e. it has an diameter of nearly 85000km and a length of over 265000km. So even if you require a minimum safety distance of 50km between satelites in geostationary orbit, there's place for over 5000 satellites.
Currently there are less than 300 AFAIK. (Here's a list of most of them). Please note that satellites which that are put put out of service usually will be parked in a "graveyard orbit" above the geostationary orbit - if there's still enough fuel and the motors still work of course.
The lower orbits (LEO, ~150-500km), where most military satellites, GPS, GLONASS, IRIDIUM and the like are placed is less problematic, since they are 'self cleaning' from old satellites: Objects there will deorbit sooner or later (the larger the sooner) since those orbits aren't very stable (due to earth's irregular shape) and the very thin atmosphere there reduces the orbital speed. That's why spacestations like Mir or ISS have to be boosted from time to time to higher orbits by a docked spacecraft.
The space debris problem is not caused by dead satellites, it's caused by all those tiny nuts and bolts left over from stage seperations, solar panel releases and so on which are affected much less by those deorbiting effects. Satellite and launch system designers nowadays take more care of this as they used in the 60-70s, e.g. the parts of the fairing which protects the payload of a launcher, are kept together connected by a wire or something after the fairing is ejected - the fairing just used to be blown up in seperate pieces by small pyros before.
> Nobody but she can testify that it was warm.
Actually this is the #1 reason I don't think she was hit by this meteorite - it's a common missconception that meteorites are hot when they hit the earth. There's an FAZ article about common myths about meteorites.
The #2 reason: Even a small piece of iron/rock like this, falling from more than 100m height surely would break a girl's foot if it hits it.
My guess: She bought the meteorite via internet and maybe it fell on her foot when she opened the package...
Ever heard of the OverWhelmingly Large Telescope (OWL)?
It's not going to be built by Americans...
No. There hasn't been a single installation so far with a more than a 1/30 km of collecting area.
> From the DirectFB web-site [directfb.org], they support Matrox [...]
But only on Linux. XFree should be an OS independent project and I really disklike the attemps from the linux camp to change that with the dependency of certain features on weird linux kernel modules and the like.
> Sure this is really cool, but does anyone actually need it?
Stupid question. Oviously the guy who did it...
AFAIK it's worse since it's not possible at all to get an IRIX license seperate from any hardware from any dealer (see here) and if you go to SGI directly and say "can I have IRIX 6.2 for my old Indy?" - well, good luck! (I bet they will tell you to ask your local dealer ;-)
They have done this 100 years ago with the Wuppertaler Schwebebahn.
The MD5 checksum mentioned in the weblog is *NOT* stored alongside the distribution file.
It comes from the package system (or 'ports' in FreeBSD jargon). The package system fetches the tarball from the distribution system and compares its own MD5 checksum against the one calculated from the fetched file.