Your weight is higher at the poles than on Everest because the earth is not a sphere, but an oblate spheroid. And the mountain would raise you away from the central mass of the earth even more.
The moon is 384,000 km up and even it has to maintain an orbital velocity considerably faster than a jumping person to avoid falling to Earth.
But if someone built a tower 384,000 km high, it would travel faster than the moon. And if you jumped off that tower, you'd also never reach the ground.
If you have a "login" without security, like SMTP, if you were to hook up 12 SMTP servers like this, the simple replay of logging into one and sending an email would work fine. EHLO, and all that, assuming no dropped packets, would send a perfect copy of the one email through all the others.
and the only thing they really have in common is that they are (usually) built on IP (the "IP" in TCP/IP and UDP/IP).
http://en.wikipedia.org/wiki/Internet_protocol_suite The Internet Protocol Suite is called TCP/IP. UDP is a subset of The Internet Protocol Suite. Thus, UDP is a subset of TCP/IP. There is no UDP/IP. That's a typo of TCP/IP or UDP.
You are just making it clear you don't know what TCP/IP means, or belligerent, for that matter. You are being deliberately contentious. You are ignoring cites that support my position, and can present none that support yours.
Traditionally, they also aren't running a full OS. Chromebook is a netbook. Windows 8 running on a small laptop isn't a netbook.
Perhaps you're confused with tablets.
Nope. My phone has more cores, more RAM, and more software options than the last "netbook" I saw (a recent HP chromebook). Setting a phone on my desk, connecting HDMI to it, and a bluetooth mouse and keyboard, and it'll out-perform the netbook. The reason they don't compare is that the netbook comes with the larger screen, and can't make calls.
http://en.wikipedia.org/wiki/I... repeatedly calls it TCP/IP, and it explicitly includes UDP. The confusion isn't there. The Internet Protocol Suite *is* TCP/IP They are the same.
Why are you being belligerent? "TCP/IP suite" wasn't made up by me. I gave a cite. There are millions more where that came from. It's not an obscure thing I made up. Go read any of the large number of good books on TCP, and they'll include UDP as a subset of TCP/IP. Something like TCP/IP Explained by Miller is a good book to start with.
UDP is a subset of TCP/IP.
That you don't know what TCP/IP is is a separate issue. Try learning something, rather than accusing everyone else of being wrong, when you don't know what you are talking about. You once heard TCP and UDP are different. I understand. But you don't know what TCP/IP is. Learn that before you make a fool of yourself. Oops, too late.
Nope. When you take classes from the same institution that teaches highway patrolmen how to determine fault, you pick some things up. But you don't keep every piece of information catelogued with the source, so you can quote it back to some jackass on the Internet. Why, is your unsubstantiated opinion more important than everyone else's?
I expect the proprietary software wouldn't run on a netbook. Go for an actual computer, rather than a huge phone that can't make calls. Cheap notebooks cost about the same as a netbook anyway.
You didn't see the second part of the question. Yes, there are a few protocols that use Ethernet without using TCP/IP. Do any on that smaller list us IP addresses?
I can think of quite a few that use Ethernet, but I can't think of anything that uses static IP addresses that doesn't use TCP/IP, on Ethernet or otherwise.
That there may be something someone has made work in a lab doesn't mean that we should assume the most obscure and inane definitions for the task at hand.
They used to be pumps, and often still are. I was told that if they are very loud, and the sound comes on and off when you activate it, then the dispensers are pumps.
IF there's no security, then just mirror port 1 on all the other ports (obviously, presuming you've plugged the 16 pumps on ports 1-16). The software "logs in" to pump 1, and pumps 2-16 think they are logged in by the same computer. That their handshake was discarded doesn't matter, if security was bad enough. Then, when you push the update to 1, 2-16 will think it's for them, and install it without issue.
Nope. Those "inner rings" wouldn't allow you to walk south for one mile, so they are invalid. And allowing that you start walking south, and continue "straight" regardless of whether it later becomes north, would (at a first glance) would send you too far north, so that you can't get back home. If you are exactly one mile north of the south pole, you could satisfy the conditions , if you allow spinning in place to count for "walking west" as you'll be spinning west.
They use 20 towers for the link. You are assuming that it's 1 on each end and 18 "repeaters" in the middle. I'd read some details in the system where they are doing dumb amplification most of the way, so they don't catch, decode, and repeat the signal. An amplifier isn't a repeater. That's why I didn't give any details. Because the details aren't clear because it's all proprietary, and they don't want it clear what they are doing and how, so others have more work to do to copy them. A dumb amp can do a pretty good job of amplifying signal with minimal distortion, and doesn't ad much delay.
Most people expect a 2-5 second delay after click to action. So it's not a "problem" for web pages, just not necessarily optimal. And DNS isn't the bottleneck for latency. My computer, and router cache DNS, and my DNS is my ISP's, so the link from me to them is short. Their connection to the server of authority is immaterial because it's recursed to about once a day.
They are solving a problem that doesn't exist. The next step is to try to convince people that the non-problem is a problem.
I worked for one of those. The problem for us was rain on the satellite feed, not the ground links. And it still applies to many places. You need a big dish (or dish farm) to pull from the satellites, or about 1 Gbps from a main distribution center.
Slashdot Mirror
Your weight is higher at the poles than on Everest because the earth is not a sphere, but an oblate spheroid. And the mountain would raise you away from the central mass of the earth even more.
An object on the Moon would weigh less than it would on Earth because of the lower gravity, but it would still have the same mass.
Because the mass beneath your feet would be lower.
Show your math please.
A mountain at 42,164bkm would have the peak in geosynchronous orbit. http://en.wikipedia.org/wiki/G...
The moon is 384,000 km up and even it has to maintain an orbital velocity considerably faster than a jumping person to avoid falling to Earth.
But if someone built a tower 384,000 km high, it would travel faster than the moon. And if you jumped off that tower, you'd also never reach the ground.
If you have a "login" without security, like SMTP, if you were to hook up 12 SMTP servers like this, the simple replay of logging into one and sending an email would work fine. EHLO, and all that, assuming no dropped packets, would send a perfect copy of the one email through all the others.
Belligerent? Are you sure you know what that word means?
http://dictionary.reference.co... "given to waging war." Synonyms: combative, quarrelsome (others trimmed)
UDP and TCP are completely different protocols,
Good so far
and the only thing they really have in common is that they are (usually) built on IP (the "IP" in TCP/IP and UDP/IP).
http://en.wikipedia.org/wiki/Internet_protocol_suite The Internet Protocol Suite is called TCP/IP. UDP is a subset of The Internet Protocol Suite. Thus, UDP is a subset of TCP/IP. There is no UDP/IP. That's a typo of TCP/IP or UDP.
You are just making it clear you don't know what TCP/IP means, or belligerent, for that matter. You are being deliberately contentious. You are ignoring cites that support my position, and can present none that support yours.
Traditionally, netbooks are x86 based.
Traditionally, they also aren't running a full OS. Chromebook is a netbook. Windows 8 running on a small laptop isn't a netbook.
Perhaps you're confused with tablets.
Nope. My phone has more cores, more RAM, and more software options than the last "netbook" I saw (a recent HP chromebook). Setting a phone on my desk, connecting HDMI to it, and a bluetooth mouse and keyboard, and it'll out-perform the netbook. The reason they don't compare is that the netbook comes with the larger screen, and can't make calls.
http://en.wikipedia.org/wiki/I... repeatedly calls it TCP/IP, and it explicitly includes UDP. The confusion isn't there. The Internet Protocol Suite *is* TCP/IP They are the same.
Why are you being belligerent? "TCP/IP suite" wasn't made up by me. I gave a cite. There are millions more where that came from. It's not an obscure thing I made up. Go read any of the large number of good books on TCP, and they'll include UDP as a subset of TCP/IP. Something like TCP/IP Explained by Miller is a good book to start with.
UDP is a subset of TCP/IP.
That you don't know what TCP/IP is is a separate issue. Try learning something, rather than accusing everyone else of being wrong, when you don't know what you are talking about. You once heard TCP and UDP are different. I understand. But you don't know what TCP/IP is. Learn that before you make a fool of yourself. Oops, too late.
We already practice that in the US, and it's nothing like what was described before.
Nope. When you take classes from the same institution that teaches highway patrolmen how to determine fault, you pick some things up. But you don't keep every piece of information catelogued with the source, so you can quote it back to some jackass on the Internet. Why, is your unsubstantiated opinion more important than everyone else's?
TCP/IP is a suite of protocols that includes UDP. http://www.protocols.com/pbook...
UDP isn't TCP, but UDP is one of the many protocols in the TCP/IP suite.
I expect the proprietary software wouldn't run on a netbook. Go for an actual computer, rather than a huge phone that can't make calls. Cheap notebooks cost about the same as a netbook anyway.
You didn't see the second part of the question. Yes, there are a few protocols that use Ethernet without using TCP/IP. Do any on that smaller list us IP addresses?
I can think of quite a few that use Ethernet, but I can't think of anything that uses static IP addresses that doesn't use TCP/IP, on Ethernet or otherwise.
That there may be something someone has made work in a lab doesn't mean that we should assume the most obscure and inane definitions for the task at hand.
TCP/IP is the name of the protocol suite that includes UDP. UDP is a subset of TCP/IP. TCP is a subset of TCP/IP. UDP/IP doesn't exist.
They used to be pumps, and often still are. I was told that if they are very loud, and the sound comes on and off when you activate it, then the dispensers are pumps.
IF there's no security, then just mirror port 1 on all the other ports (obviously, presuming you've plugged the 16 pumps on ports 1-16). The software "logs in" to pump 1, and pumps 2-16 think they are logged in by the same computer. That their handshake was discarded doesn't matter, if security was bad enough. Then, when you push the update to 1, 2-16 will think it's for them, and install it without issue.
http://en.wikipedia.org/wiki/L...
Rockets on the bottom is the right way to land a rocket.
Since you are standing on a solid ground, and not on the Earth, the north pole is on the moon?
Nope. Those "inner rings" wouldn't allow you to walk south for one mile, so they are invalid. And allowing that you start walking south, and continue "straight" regardless of whether it later becomes north, would (at a first glance) would send you too far north, so that you can't get back home. If you are exactly one mile north of the south pole, you could satisfy the conditions , if you allow spinning in place to count for "walking west" as you'll be spinning west.
So anti-competitive collusion from an oligopoly isn't a "price control"? Most people would put price fixing into "price control".
They use 20 towers for the link. You are assuming that it's 1 on each end and 18 "repeaters" in the middle. I'd read some details in the system where they are doing dumb amplification most of the way, so they don't catch, decode, and repeat the signal. An amplifier isn't a repeater. That's why I didn't give any details. Because the details aren't clear because it's all proprietary, and they don't want it clear what they are doing and how, so others have more work to do to copy them. A dumb amp can do a pretty good job of amplifying signal with minimal distortion, and doesn't ad much delay.
Latency is a big issue for the web.
Most people expect a 2-5 second delay after click to action. So it's not a "problem" for web pages, just not necessarily optimal. And DNS isn't the bottleneck for latency. My computer, and router cache DNS, and my DNS is my ISP's, so the link from me to them is short. Their connection to the server of authority is immaterial because it's recursed to about once a day.
They are solving a problem that doesn't exist. The next step is to try to convince people that the non-problem is a problem.
you are not "self employed" if you are being told what to do by a third party.
By your definition, you are a telephone company employee if you take phone orders.
The real world proves you wrong, unless you assert they can do NYC to Chicago in a single hop.
I worked for one of those. The problem for us was rain on the satellite feed, not the ground links. And it still applies to many places. You need a big dish (or dish farm) to pull from the satellites, or about 1 Gbps from a main distribution center.