> I don't think that humanity was saved at the end of 12 Monkeys.
I think it does. Or what's the reason behind the last scene in the plane you have mentioned?
I think she will (try to) prevent him from releasing the virus or at least take samples of the original virus "back to future" so they can find a cure for the mutated virus in their presence.
(I agree as well it should be on the list. They could have taken RoboCop or Star Wars from the list instead).
Someone cheated you by selling you something he doesn't own. Don't expect the paper you might have gotten has any validity when man starts colonizing the moon.
Back people and US navy
on
Review: U-571
·
· Score: 1
So you were wondering what happened to the token black guy? The Americans are loading the German POWs onto the S-33. Mr. Politically Correct asks one of the German submariners "what, you never seen a black man before." You know, it's nice that Mr. Mastow had the guts to take on an important subject like the Nazi persecution of non-Aryans in such a deft and subtle way.
What's somewhat ironic is the fact that the US navy was pretty racistic at that time as well - only white people were allowed to serve on US navy submarines like the S-33 until the fifties or sixties.
> I'd guess a cracked solder joint in the power supply causing a voltage fluctuation when the > toilet flushed, and that's probably why the power supply died as well, when the crack turned > into a break. That was certainly not the case - other vibrations or shocks (e.g. shutting the door, moving the chair to the desk, hitting run/stop-restore on the keyboard, footsteps) would have caused it as well - but that didn't happen.
The problem with the power supply was that it simply didn't provided the correct voltage. It was closer to 4V than to 5V.
> I'd guess but don't know that the brick was plugged into the wall on the side next to the toilet, right?
No, it wasn't. And further more: it was a brick wall, the power supply was on the floor, more closer to the opposite wall. Sadly, ASCII art is considered "lame" by slashdot's filtering system, so I can't provide a sketch from the room.
Disclaimer: This is all from memory since it was 13-15 years from now.
No. The 9 (not 11) VAC was only used (IIRC) to deliver a 50Hz (60Hz in other countries) time base for the RTCs built into the 6526 CIAs, to power the 'datasette' and to create an additional 5V voltage and 12V. Now I remember how I probably killed it: I fed the 12V to the wrong place... (I didn't need the datasette and the RTCs were rarely used anyway).
But it depends on the models, later models didn't need the 9VAC at all and could operate on 5V only.
Is it IP traffic? If yes: Can you find out the destination of the traffic? If it all points to a single or a handfull IP#s DDOS is very likely. (a tool like ntop is handy to find that out).
Is it TCP or UDP? Are the sender adresses OK or spoofed? What service are the packets targeted at (port numbers)?
As kid I used to have a C64. After some years its power supply was slowly dying and it became more and more instable: electric equippement like a vacuum switched on nearby caused it to crash or made it reset. But the/really/ funny thing is that flushing the toilet next to my room caused a reset---and that nearly 100% repeatable.
It was one of those old style toilets whith a big water tank high above the seat and if you pulled the trigger a huge amount of water caused a "whoosh" that would have made Al Bundy happy...
I think I worked around the problem by stabilizing the reset line with a condensor or so. Then the power supply finally died, so I played with 6V batteries to power my C64 and one day accidently killed it somehow:-(. IIRC the toilet has gone by now as well.
I have no clear idea that the physics behind that was: Was it the same effect that made rising/falling raindrops cause thunders? Or did the quick movement of a large mass of (soemwhat) electric conductive material disturbed the electric field?
BTW: Switching on the light+fan in the toilet had no effect on the C64.
The RWE is (amongst other things) an electric and gas company. They mainly burn coal, natural gas and oil to produce electricity. Mr. Volz talking about global warming is like Mr. Burns talking about radioactive waste.
It's for performance reasons I guess - NetBSD does the same for quite a few of its ports (e.g. the m68k and powerpc ones). The kernel does nearly no floating point calculations and if you do the few ones the kernel does with soft-float to avoid using the floating point instructions you manage to keep the contents of the FP registers unchanged. So there's no need to save and restore them when the CPU switches between user and kernel mode (syscalls etc.). Storing/loading n floating point registers in memory for every syscall is quite expensive, you know.
This of course is not necessary if the CPU has two (at least partly) different sets of FP registers for kernel (supervisor, privileged,...) and user (unprivileged) mode or an instruction to quickly exchange (parts of) the FP register sets. (SPARCs do have this to some degree with its concept of register windows).
Erm, no. The JVM works on byte code. You can compile any language to Java's byte code if you have the right compiler - and there are quite a few. Currently there are solutions for about 160 programming languages (number is from that page, I haven't counted them) --- including Prolog.
If that's true than the more advanced HiperLAN/2 will probably fail---HiperLAN doesn't sound as cool as 802.11[a,b,g,h, whatever], not even remotely...
> It was unlikely any of the workers could have survived the fall [...] > Russia would not allow Kazakh rescuers to approach the building [...] > There was no information about the condition of the eight workers, he said [...] > A special Russian rescue team left Moscow for Baikonur [...] > The plane was to arrive three hours later, or 13 hours after the accident took place.
They don't know what happend to the construction crew. If someone was lucky enough to survive the accident and is lying badly injured in the rubble now he has to wait for 13 hours because of Russian politics.
The big question is, what is cheaper: Maintain and repair the engines after every launch or make new through-away engines which only have to last a few seconds of thrust.
Well, this does work somewhat. I know it since we are in the same situation: We have a uplink that is shared between ~150 users and try to make it usable for everyone everytimes but manage that only partly because we control only our end of the line.
One reason that it does only partly work with tcp because when one or more packet is just dropped the tcp stack won't notice it immediatly, instead it waits for the ACK from the other side. This is good, because if the sender's window is "empty", i.e. it has send all packets the window size allows it to send, the tcp stack will keep quite for a while. But after the wait timeouts it will send all those packets starting after the last ack'd packet again - which makes it worse. Clever TCP stacks could theoretically now dynamically adjust their window size so that it's exactly as long as the "longest allowed burst".
And of course there's the ICMP source quench message the router could send to tell a host to throttle the packet flow, but sadly this is not a MUST in RFC terms which means it's not often implemented and the message is just ignored.
And if someone ping-floods you or does some other kind of DOS you have of course no chance to prevent him from flooding the link from your side.
To make it short: You can't really achieve QoS through a link if you control only one side of it.
The guy is in contact with the builders of the Buran which is to be auctioned:
One of Whyte's principal investors is closely associated with Alexander Bashilov, Director General of NPO Molniya JSC in Moscow, who Whyte said has been given authority by the Russian government to sell one of the Russian shuttles.
I guess the NPO Molniya does know better
what they have built
where it is now and
what of it is on sale.
than NASA does.
And BTW
The page from NASA you seem to bet your life on is dated 1997
The page doesn not say that Ptichka has not been completed by now
Do you really think that that site only contains 100% correct informations?!?!?
That thread is over for me now. If you can't admit that you're wrong that's OK for me. But please don't say Willie Whyte is a liar because of that five year old little yellow web page hosted at some NASA site.
The guy says it has never flown in space. I think he knows what he's talking about better than you - if it has flown in space he can expect a higher bid, so why should he lie?
The one on auction has never flown in space.Please RTFA:
Admitting he wouldn't know one space shuttle from another, Whyte said all he knows is that the Buran to be auctioned has never flown in space. But he does have a lot confidence in his source for the hardware.
According to the article this "cloud" (outer ionosphere) is 300 to 1000 kilometers above earth - the region called "low earth orbit" by astronaticans (BTW with the exception of the apollo program all manned space activities took place there). The density of the atmosphere in this height is so low that this reagion is usually declared as space by the media.
Because of the low density a cubic kilometer of "air" (or space) of that cloud doesn't contain much thermal energy - even if it's billions of K hot.
Well, PostgreSQL would handle overload situations more gracefully, that's for sure.
If you ever waited 15s for a webpage just to have a blank page or error message presented to you, you can be sure the backend of that site is MySQL.
On PHPBuilder there's an Article about the performance of the two with a real world application (actually, it's sourceforge). It's a little bit old now, but I guess it would look even better for PostreSQL now.
As I wrote, they *can* limit the upstream by dropping packets on their side of the cable. But this is no QoS as this doesn't stop extranous packets sent from "uncapped" cable modems entering the cable and flooding it - it wouldn't help the cable modem users on the same cable segment which are nice netizens and stay in their limit.
Nice idea, they would be lucky if they could. But they' can't effictivly limit the upstream of a single customers over a shared media like cable. They could of course simply drop packets on their side but the cable would still be clogged up.
That's why uncapping cable modems is immoral: If you unlimit your rate you are stealing bandwidth from other users on your cable segment and lower the quality of their cable service.
Great idea - if you accidently drop a coin on your pc case it will most likely shatter the case, maybe it gets stuck in the aerogel or simply falls through.
Slashdot Mirror
> I don't think that humanity was saved at the end of 12 Monkeys.
I think it does. Or what's the reason behind the last scene in the plane you have mentioned?
I think she will (try to) prevent him from releasing the virus or at least take samples of the original virus "back to future" so they can find a cure for the mutated virus in their presence.
(I agree as well it should be on the list. They could have taken RoboCop or Star Wars from the list instead).
Someone cheated you by selling you something he doesn't own. Don't expect the paper you might have gotten has any validity when man starts colonizing the moon.
> I'd guess a cracked solder joint in the power supply causing a voltage fluctuation when the
> toilet flushed, and that's probably why the power supply died as well, when the crack turned
> into a break.
That was certainly not the case - other vibrations or shocks (e.g. shutting the door, moving the chair to the desk, hitting run/stop-restore on the keyboard, footsteps) would have caused it as well - but that didn't happen.
The problem with the power supply was that it simply didn't provided the correct voltage. It was closer to 4V than to 5V.
> I'd guess but don't know that the brick was plugged into the wall on the side next to the toilet, right?
No, it wasn't. And further more: it was a brick wall, the power supply was on the floor, more closer to the opposite wall. Sadly, ASCII art is considered "lame" by slashdot's filtering system, so I can't provide a sketch from the room.
Disclaimer: This is all from memory since it was 13-15 years from now.
No. The 9 (not 11) VAC was only used (IIRC) to deliver a 50Hz (60Hz in other countries) time base for the RTCs built into the 6526 CIAs, to power the 'datasette' and to create an additional 5V voltage and 12V. Now I remember how I probably killed it: I fed the 12V to the wrong place...
(I didn't need the datasette and the RTCs were rarely used anyway).
But it depends on the models, later models didn't need the 9VAC at all and could operate on 5V only.
No, there was no pump or any other electric system combined with the toilet.
Is it IP traffic?
If yes: Can you find out the destination of the traffic? If it all points to a single or a handfull IP#s DDOS is very likely. (a tool like ntop is handy to find that out).
Is it TCP or UDP? Are the sender adresses OK or spoofed? What service are the packets targeted at (port numbers)?
As kid I used to have a C64. After some years its power supply was slowly dying and it became more and more instable: electric equippement like a vacuum switched on nearby caused it to crash or made it reset. But the /really/ funny thing is that flushing the toilet next to my room caused a reset---and that nearly 100% repeatable.
:-(. IIRC the toilet has gone by now as well.
It was one of those old style toilets whith a big water tank high above the seat and if you pulled the trigger a huge amount of water caused a "whoosh" that would have made Al Bundy happy...
I think I worked around the problem by stabilizing the reset line with a condensor or so. Then the power supply finally died, so I played with 6V batteries to power my C64 and one day accidently killed it somehow
I have no clear idea that the physics behind that was: Was it the same effect that made rising/falling raindrops cause thunders? Or did the quick movement of a large mass of (soemwhat) electric conductive material disturbed the electric field?
BTW: Switching on the light+fan in the toilet had no effect on the C64.
The RWE is (amongst other things) an electric and gas company. They mainly burn coal, natural gas and oil to produce electricity. Mr. Volz talking about global warming is like Mr. Burns talking about radioactive waste.
It's for performance reasons I guess - NetBSD does the same for quite a few of its ports (e.g. the m68k and powerpc ones). The kernel does nearly no floating point calculations and if you do the few ones the kernel does with soft-float to avoid using the floating point instructions you manage to keep the contents of the FP registers unchanged. So there's no need to save and restore them when the CPU switches between user and kernel mode (syscalls etc.). Storing/loading n floating point registers in memory for every syscall is quite expensive, you know.
...) and user (unprivileged) mode or an instruction to quickly exchange (parts of) the FP register sets. (SPARCs do have this to some degree with its concept of register windows).
This of course is not necessary if the CPU has two (at least partly) different sets of FP registers for kernel (supervisor, privileged,
Erm, no. The JVM works on byte code. You can compile any language to Java's byte code if you have the right compiler - and there are quite a few. Currently there are solutions for about 160 programming languages (number is from that page, I haven't counted them) --- including Prolog.
If that's true than the more advanced HiperLAN/2 will probably fail---HiperLAN doesn't sound as cool as 802.11[a,b,g,h, whatever], not even remotely...
> It was unlikely any of the workers could have survived the fall
[...]
> Russia would not allow Kazakh rescuers to approach the building
[...]
> There was no information about the condition of the eight workers, he said
[...]
> A special Russian rescue team left Moscow for Baikonur [...]
> The plane was to arrive three hours later, or 13 hours after the accident took place.
They don't know what happend to the construction crew. If someone was lucky enough to survive the accident and is lying badly injured in the rubble now he has to wait for 13 hours because of Russian politics.
Reminds me of the Kursk disaster..
The big question is, what is cheaper:
Maintain and repair the engines after every launch or make new through-away engines which only have to last a few seconds of thrust.
Well, this does work somewhat. I know it since we are in the same situation: We have a uplink that is shared between ~150 users and try to make it usable for everyone everytimes but manage that only partly because we control only our end of the line.
One reason that it does only partly work with tcp because when one or more packet is just dropped the tcp stack won't notice it immediatly, instead it waits for the ACK from the other side. This is good, because if the sender's window is "empty", i.e. it has send all packets the window size allows it to send, the tcp stack will keep quite for a while. But after the wait timeouts it will send all those packets starting after the last ack'd packet again - which makes it worse. Clever TCP stacks could theoretically now dynamically adjust their window size so that it's exactly as long as the "longest allowed burst".
And of course there's the ICMP source quench message the router could send to tell a host to throttle the packet flow, but sadly this is not a MUST in RFC terms which means it's not often implemented and the message is just ignored.
And if someone ping-floods you or does some other kind of DOS you have of course no chance to prevent him from flooding the link from your side.
To make it short: You can't really achieve QoS
through a link if you control only one side of it.
- what they have built
- where it is now and
- what of it is on sale.
than NASA does. And BTW- The page from NASA you seem to bet your life on is dated 1997
- The page doesn not say that Ptichka has not been completed by now
- Do you really think that that site only contains 100% correct informations?!?!?
That thread is over for me now. If you can't admit that you're wrong that's OK for me. But please don't say Willie Whyte is a liar because of that five year old little yellow web page hosted at some NASA site.The guy says it has never flown in space. I think he knows what he's talking about better than you - if it has flown in space he can expect a higher bid, so why should he lie?
Maybe you should check your "facts" first.
Yes, it's the Antonov 225 "Mriya". You find dozons of pages about it on the web.
According to the article this "cloud" (outer ionosphere) is 300 to 1000 kilometers above earth - the region called "low earth orbit" by astronaticans (BTW with the exception of the apollo program all manned space activities took place there). The density of the atmosphere in this height is so low that this reagion is usually declared as space by the media.
Because of the low density a cubic kilometer of "air" (or space) of that cloud doesn't contain much thermal energy - even if it's billions of K hot.
If you ever waited 15s for a webpage just to have a blank page or error message presented to you, you can be sure the backend of that site is MySQL.
On PHPBuilder there's an Article about the performance of the two with a real world application (actually, it's sourceforge). It's a little bit old now, but I guess it would look even better for PostreSQL now.
As I wrote, they *can* limit the upstream by dropping packets on their side of the cable. But this is no QoS as this doesn't stop extranous packets sent from "uncapped" cable modems entering the cable and flooding it - it wouldn't help the cable modem users on the same cable segment which are nice netizens and stay in their limit.
Nice idea, they would be lucky if they could. But they' can't effictivly limit the upstream of a single customers over a shared media like cable. They could of course simply drop packets on their side but the cable would still be clogged up.
That's why uncapping cable modems is immoral: If you unlimit your rate you are stealing bandwidth from other users on your cable segment and lower the quality of their cable service.
And before you attemp making your case of aerogel, please read How Do You Work With Silica Aerogel Without Breaking It?.
Probably the best scene is in Star Trek IV ("The Voyage Home") when he takes a 20th century's computer mouse and thought it was a microphone.