Actually on the current 6rd deployment of comcast they are giving out more ip addresses for free. Mostly because they have to or you can't use the privacy extensions of ipv6.
Not quite, i was referring to this. i couldn't look that up earlier because i was on a really bad connection that was dropping packets left right and center.
OK, either you're a troll and I'm wasting my time (most likely) or you're misunderstanding something. What Hawking admitted wasn't that the radiation didnt' exist but that the radiation did not in fact violate the principle of conservation of information. Previously Hawking had believed that it must violate said principle because there was no understood way for there to be a connection between the information about the matter that had fallen in and gone past the event horizon and the radiation that would be emitted. This was challenged by another physicist, whose name escapes me since I can't look it up at the moment, who reasoned (along with a more definite proof of course) that the information gets left at the event horizon also. This is because of the fact that from the perspective of anyone outside the event horizon any matter or energy falling in will never actually reach the event horizon it'll just appear to be slowing down further and further until it for all intents and purposes stops. This allows the virtual particles making up hawking radiation to be influenced by the information left at the event horizon without there being a need to have communication between the singularity at the center and the event horizon.
There is something to be said though about going to a 64bit operating system. The fact that there are a little more than twice as many general purpose registers in the CPU available means that code can be compiled to not need to do memory fetches anywhere near as often which means that the code will run faster. the extra addressing space has always been a red herring argument (e.g. i only need it if i have more than 4gb of ram).
courier supports maildir backed imap, i use it myself and its great for being able to get at things over ssh (mutt), imap with kmail, or even web mail hooked up to the imap. as someone else said earlier, IMAP is THE way to go for storage. as far as searching, i'm not sure, i haven't found anything that's perfect at it yet.
At that point you do need to start designing things more like a network than as a bus that's attached to the processor since you'd have latencies of several clock cycles involved. and the only thing to do is really to increase cache sizes and move them ever closer to the processor so that the latencies can be avoided as much as possible. But as far as things like a graphics card goes, when you've got tens of billions of clock cycles per second and a latency of say 100 cycles, the user is never going to notice
While it wouldn't be as cheap as making your own, newegg has a set of clip ons for the circularly polarized films. big long ass url here. I don't know if that set would fit on yours but i'd imagine there are some out there. This might end up more comfortable and last longer than the ones you make yourself.
While this does mean that it could possibly make some Deep Field images. There is still another problem that makes this possibly intractable. The atmospheric absorption of some wavelengths means that it might still not be able to see certain areas in the spectrum effectively; this could prevent it from being able to produce nice deep field images like the hubble. However this ability to resolve objects that much better means that it could most certainly be effective at searching for planets.
You can't always count on seeing the loop in every area. By me they put them in the ground before they lay the asphalt so that they can save on costs. But the problem with that method is that not all of the loops are exactly where they should be.
I'm absolutely sure once a planet like that is found that SETI will point the telescopes at it for an extremely close look. Until then they may as well search around randomly while they've got the time and funding anyway.
echo -n "USCYBERCOM plans, coordinates, integrates, synchronizes and conducts activities to: direct the operations and defense of specified Department of Defense information networks and; prepare to, and when directed, conduct full spectrum military cyberspace operations in order to enable actions in all domains, ensure US/Allied freedom of action in cyberspace and deny the same to our adversaries." | md5sum 9ec4c12949a4f31474f299058ce2b22a -
This is what core dumps are for, you can then open them up in the debugger and examine the program at the state of execution when it crashed. You can also do debugging live still too.
If we can crack 128 bit encryption then AES 256 should be easily breakable, http://www.schneier.com/blog/archives/2009/07/new_attack_on_a.html there's several attacks on the flawed key schedule in that reduce the search space to something like 2^110.5 instead of the 256bits that AES 256 implies. (this means that AES 128 is actually more secure in this regard, at least as currently understood).
That and the good IR allows llvm to do the translation to the local architecture at "run" time (execution time anyway) so that you can have a single linked binary that is able to be run on multiple architectures with little fuss. What i'm not sure about is if ELF can handle so called "fat" binaries that would have the llvm IR and a few common architectures too.
Well what you need to do is forget the idea of a "singularity" (a division by zero, etc.) that's just an artifact from the math, and we've shown (i believe) that the math breaks down after you hit the event horizon (and possibly at the event horizon, i don't recall correctly). What this means is that we have no way of knowing or understanding what happens to the matter there.
No he's saying the ratio of the transmission doesn't affect the horsepower. If you trade speed for torque (or vice versa) then you end up with the same horsepower regardless of what the transmission is doing. (ignore friction in the transmission anyway)
Well that's just it there really isn't a diameter to the universe as far as most thinking goes for the shape of the universe. At least not in any dimension we can measure or perceive or what have you. The age (and shape too) of the universe is mostly (from my limited understanding of it all) based on measurements from the CMB (Cosmic Microwave Background) and from observations such as this (measuring the redshift in them, typically of the hydrogen alpha line [and others like it that we expect to find everywhere]). Both of these according to current theories predict that the farthest we should be able to see into the universe is about 14 billion years (give or take a billion, there's a lot of margin for error here...). Now what you might be alluding to (its hard to tell from such a simple/brief comment) is that those objects we see have moved far beyond the 14 billion light years away that we see them at currently and that is entirely correct. By some estimates i think its supposed that the position of the things we can see today are nearly 70 billion light years away due to their own velocity and the added energy from the expansion of the universe itself (this last bit is what can allow them to appear to move much faster than the speed of light, because the universe itself is enlarging equally in all directions in all points at all times).
for more information i'd suggest consulting astronomy cast episodes,
Actually on the current 6rd deployment of comcast they are giving out more ip addresses for free. Mostly because they have to or you can't use the privacy extensions of ipv6.
Not quite, i was referring to this. i couldn't look that up earlier because i was on a really bad connection that was dropping packets left right and center.
OK, either you're a troll and I'm wasting my time (most likely) or you're misunderstanding something. What Hawking admitted wasn't that the radiation didnt' exist but that the radiation did not in fact violate the principle of conservation of information. Previously Hawking had believed that it must violate said principle because there was no understood way for there to be a connection between the information about the matter that had fallen in and gone past the event horizon and the radiation that would be emitted. This was challenged by another physicist, whose name escapes me since I can't look it up at the moment, who reasoned (along with a more definite proof of course) that the information gets left at the event horizon also. This is because of the fact that from the perspective of anyone outside the event horizon any matter or energy falling in will never actually reach the event horizon it'll just appear to be slowing down further and further until it for all intents and purposes stops. This allows the virtual particles making up hawking radiation to be influenced by the information left at the event horizon without there being a need to have communication between the singularity at the center and the event horizon.
There is something to be said though about going to a 64bit operating system. The fact that there are a little more than twice as many general purpose registers in the CPU available means that code can be compiled to not need to do memory fetches anywhere near as often which means that the code will run faster. the extra addressing space has always been a red herring argument (e.g. i only need it if i have more than 4gb of ram).
Actually in the case of a bottle of lighter fluid there can be oxygen in there that was just sucked into the bottle from repeated squirtings.
courier supports maildir backed imap, i use it myself and its great for being able to get at things over ssh (mutt), imap with kmail, or even web mail hooked up to the imap. as someone else said earlier, IMAP is THE way to go for storage. as far as searching, i'm not sure, i haven't found anything that's perfect at it yet.
At that point you do need to start designing things more like a network than as a bus that's attached to the processor since you'd have latencies of several clock cycles involved. and the only thing to do is really to increase cache sizes and move them ever closer to the processor so that the latencies can be avoided as much as possible. But as far as things like a graphics card goes, when you've got tens of billions of clock cycles per second and a latency of say 100 cycles, the user is never going to notice
While it wouldn't be as cheap as making your own, newegg has a set of clip ons for the circularly polarized films. big long ass url here. I don't know if that set would fit on yours but i'd imagine there are some out there. This might end up more comfortable and last longer than the ones you make yourself.
While this does mean that it could possibly make some Deep Field images. There is still another problem that makes this possibly intractable. The atmospheric absorption of some wavelengths means that it might still not be able to see certain areas in the spectrum effectively; this could prevent it from being able to produce nice deep field images like the hubble. However this ability to resolve objects that much better means that it could most certainly be effective at searching for planets.
don't forget about the other three!
you/yew/ewe!
You can't always count on seeing the loop in every area. By me they put them in the ground before they lay the asphalt so that they can save on costs. But the problem with that method is that not all of the loops are exactly where they should be.
I'm absolutely sure once a planet like that is found that SETI will point the telescopes at it for an extremely close look. Until then they may as well search around randomly while they've got the time and funding anyway.
whoever you are, you deserve a cookie.
This is what core dumps are for, you can then open them up in the debugger and examine the program at the state of execution when it crashed. You can also do debugging live still too.
If we can crack 128 bit encryption then AES 256 should be easily breakable, http://www.schneier.com/blog/archives/2009/07/new_attack_on_a.html there's several attacks on the flawed key schedule in that reduce the search space to something like 2^110.5 instead of the 256bits that AES 256 implies. (this means that AES 128 is actually more secure in this regard, at least as currently understood).
While it won't catch everything, clamav i believe can be setup on the usb drive to be used that way.
damn idiots, its O2 + 2H2 => 2H2O
That and the good IR allows llvm to do the translation to the local architecture at "run" time (execution time anyway) so that you can have a single linked binary that is able to be run on multiple architectures with little fuss. What i'm not sure about is if ELF can handle so called "fat" binaries that would have the llvm IR and a few common architectures too.
Well what you need to do is forget the idea of a "singularity" (a division by zero, etc.) that's just an artifact from the math, and we've shown (i believe) that the math breaks down after you hit the event horizon (and possibly at the event horizon, i don't recall correctly). What this means is that we have no way of knowing or understanding what happens to the matter there.
I'm curious if you're banning microsoft shares AND nfs what do you use for networked file storage?
replying to undo moderation, where the fuck did the button go to let me do it without this shit
No he's saying the ratio of the transmission doesn't affect the horsepower. If you trade speed for torque (or vice versa) then you end up with the same horsepower regardless of what the transmission is doing. (ignore friction in the transmission anyway)
Well that's just it there really isn't a diameter to the universe as far as most thinking goes for the shape of the universe. At least not in any dimension we can measure or perceive or what have you. The age (and shape too) of the universe is mostly (from my limited understanding of it all) based on measurements from the CMB (Cosmic Microwave Background) and from observations such as this (measuring the redshift in them, typically of the hydrogen alpha line [and others like it that we expect to find everywhere]). Both of these according to current theories predict that the farthest we should be able to see into the universe is about 14 billion years (give or take a billion, there's a lot of margin for error here...). Now what you might be alluding to (its hard to tell from such a simple/brief comment) is that those objects we see have moved far beyond the 14 billion light years away that we see them at currently and that is entirely correct. By some estimates i think its supposed that the position of the things we can see today are nearly 70 billion light years away due to their own velocity and the added energy from the expansion of the universe itself (this last bit is what can allow them to appear to move much faster than the speed of light, because the universe itself is enlarging equally in all directions in all points at all times).
for more information i'd suggest consulting astronomy cast episodes,
http://www.astronomycast.com/listeners/questions-shows/questions-show-multiple-big-bangs-satellite-collisions-and-the-size-of-the-universe/
http://www.astronomycast.com/astronomy/ep-81-questions-on-the-shape-size-and-centre-of-the-universe/
False dichotomy, they'd do both. (though they'll check and triple check everything as they go along)
And because you just demonstrated some humility there by admitting it, you've caused california to have another set of rolling blackouts.