Negotiation and compromise assume that all parties are rational actors and that neither party must give up something they consider to be of vital importance. The process breaks down if that assumption is incorrect in any particular case.
Remember, humans are also emotional beings and we don't always apply logic and reason to decisions. Thus, bar brawls, civil wars, world wars, and terrorism will always be with us.
I'd expect the physical force would travel along the pole at it's local speed of sound in the material that the pole is made of. The pole's molecules have some space between them and are attracted to one another such that you have a solid. Therefore, pushing on one part of the pole will slightly compress the pole's material until the newly repositioned molecules bump into their neighbors and cause the motion to be propagated.
If you try to accelerate the pole too quickly (faster than its local speed of sound) a shock wave will develop instead.
Assuming your pole is iron and 300,000,000 meters long, the time would be 300,000,000 / 5130 seconds (speed of sound in iron is 5130 m/s), or 58479.532 seconds (16.244 hours).
Actually, a pole that long would act more like a wire and flex all over the place - your push would probably act like a wave instead (just like if you whipped a rope).
A 500 foot pole would be about the same, just faster due to shorter length. 500 feet is 152.4 meters, so the time would be 152.4 / 5130 seconds, or 297.08 ms. You would not notice the far end move for about 1/3 second.
Simple physics at work here!
1. Yep - if you follow the GPL rules.
2. Nope. The resultant binary is a "derivitave work" of the libs and is a copyright violation.
3. Yep - do as you wish with your own code.
4. Maybe - if sued for infringement you may have to settle by publishing or face major legal costs, injunctions, and all kinds of other nasties. GPLViolations.org guys are pretty vigilant about their enforcement efforts. I know if I found any GPL code I wrote in your binary I would seriously consider a suit. If I license code under GPL, it's for a reason and I absolutely demand that the GPL rules be followed.
5. Yep - You can pretty much do anything you want with BSD code. GPL is specifically designed to prevent taking any of it propritary in any way, shape, or form. BSD doesn't care.
I'd say you really, really, really should use BSD to meet your goals.
It's within the realm of possibility to build one from scratch. Just couple a microcontroller with an LCD display, put a big Li-Ion battery in to power it, and bolt on a USB port. Of course, it would be a real PITA to actually make it work.
There are places to order 6" 640 X 480 LCDs from, and a PIC microcontroller should have enough power to display simple JPGs and such. Writing the code would be a pretty hideous undertaking though.
Maybe start an open source project for it?
Let's not forget about neutrons too. Free neutrons tend to do interesting things when they combine with other atomic nuclei. However, free neutrons are not stable and have a half-life of about 15 minutes, at which time they disintegrate to a proton and an electron (plus some energy) and leave you with, yep, hydrogen.
A "data storm" can be caused by lots of things, even an unstable driver causing a NIC to spew garbage packets. Or an application that hits a bug and begins spewing to the network. Or a failure of Spanning Tree causing network loops to arise (which can really mess up an Ethernet).
The wierdest I ever saw was a situation at a school where the entire network (built around high-end Cisco switches) crashed hard. It took 3 hours of troubleshooting and disconnecting various segments to finally pin down the cause. It was a little mini-switch that some teacher attached to the LAN that somehow had a meltdown and began spewing "valid" Ethernet packets with all kinds of random garbage source and destination MAC addresses, random payload, and valid checksums. No hosts were attached to the mini switch, so it had to be something in its microcontroller going haywire. This cause every switch to go nuts trying to maintain its forwarding tables ("show cpu" was 100% utilization) and resulted in no traffic going anywhere. It even crossed VLAN boundaries since all the switches had "trunk" ports using tagged VLANS, so the garbage packets still made it through the entire LAN.
These things happen sometimes. Network gear is generally pretty robust, but can still fail in wierd ways.
Slashdot Mirror
Negotiation and compromise assume that all parties are rational actors and that neither party must give up something they consider to be of vital importance. The process breaks down if that assumption is incorrect in any particular case. Remember, humans are also emotional beings and we don't always apply logic and reason to decisions. Thus, bar brawls, civil wars, world wars, and terrorism will always be with us.
Bad stuff depending on how much hits. Full blast = no planet.
The pole would compress and flex. Even solid steel can be compressed like air with enough force.
The 500 foot pole would actually take 29.7 mS, not 297 --- decimal error. So expect about 1/30 second delay between push and movement at far end.
I'd expect the physical force would travel along the pole at it's local speed of sound in the material that the pole is made of. The pole's molecules have some space between them and are attracted to one another such that you have a solid. Therefore, pushing on one part of the pole will slightly compress the pole's material until the newly repositioned molecules bump into their neighbors and cause the motion to be propagated. If you try to accelerate the pole too quickly (faster than its local speed of sound) a shock wave will develop instead. Assuming your pole is iron and 300,000,000 meters long, the time would be 300,000,000 / 5130 seconds (speed of sound in iron is 5130 m/s), or 58479.532 seconds (16.244 hours). Actually, a pole that long would act more like a wire and flex all over the place - your push would probably act like a wave instead (just like if you whipped a rope). A 500 foot pole would be about the same, just faster due to shorter length. 500 feet is 152.4 meters, so the time would be 152.4 / 5130 seconds, or 297.08 ms. You would not notice the far end move for about 1/3 second. Simple physics at work here!
1. Yep - if you follow the GPL rules. 2. Nope. The resultant binary is a "derivitave work" of the libs and is a copyright violation. 3. Yep - do as you wish with your own code. 4. Maybe - if sued for infringement you may have to settle by publishing or face major legal costs, injunctions, and all kinds of other nasties. GPLViolations.org guys are pretty vigilant about their enforcement efforts. I know if I found any GPL code I wrote in your binary I would seriously consider a suit. If I license code under GPL, it's for a reason and I absolutely demand that the GPL rules be followed. 5. Yep - You can pretty much do anything you want with BSD code. GPL is specifically designed to prevent taking any of it propritary in any way, shape, or form. BSD doesn't care. I'd say you really, really, really should use BSD to meet your goals.
It's within the realm of possibility to build one from scratch. Just couple a microcontroller with an LCD display, put a big Li-Ion battery in to power it, and bolt on a USB port. Of course, it would be a real PITA to actually make it work. There are places to order 6" 640 X 480 LCDs from, and a PIC microcontroller should have enough power to display simple JPGs and such. Writing the code would be a pretty hideous undertaking though. Maybe start an open source project for it?
Let's not forget about neutrons too. Free neutrons tend to do interesting things when they combine with other atomic nuclei. However, free neutrons are not stable and have a half-life of about 15 minutes, at which time they disintegrate to a proton and an electron (plus some energy) and leave you with, yep, hydrogen.
And god-awful expensive it was - especially if you set it up with the old IBM shielded twisted pair cabling.
A "data storm" can be caused by lots of things, even an unstable driver causing a NIC to spew garbage packets. Or an application that hits a bug and begins spewing to the network. Or a failure of Spanning Tree causing network loops to arise (which can really mess up an Ethernet).
The wierdest I ever saw was a situation at a school where the entire network (built around high-end Cisco switches) crashed hard. It took 3 hours of troubleshooting and disconnecting various segments to finally pin down the cause. It was a little mini-switch that some teacher attached to the LAN that somehow had a meltdown and began spewing "valid" Ethernet packets with all kinds of random garbage source and destination MAC addresses, random payload, and valid checksums. No hosts were attached to the mini switch, so it had to be something in its microcontroller going haywire. This cause every switch to go nuts trying to maintain its forwarding tables ("show cpu" was 100% utilization) and resulted in no traffic going anywhere. It even crossed VLAN boundaries since all the switches had "trunk" ports using tagged VLANS, so the garbage packets still made it through the entire LAN.
These things happen sometimes. Network gear is generally pretty robust, but can still fail in wierd ways.