Hold on, if they send it to a HIGHER orbit, how does it ever get to re-entry?
It doesn't. At least not very often. (It depends on how the last of the fuel is burned off.) It is usually moved far away enough to not affect any other satellites. The real clean-up process is left for future generations with more advanced space technology.
Shouldn't be difficult to integrate with a subway system.
Assuming that there is already an existing transit system. Even then, subway stations are still underground (in many cases), so that doesn't help an above ground rail system.
if there is enough room, run PRT alongside the subway lines at some point (i.e. replace one subway track of several with a PRT track).
It doesn't make sense for a city to spend millions (billions?) ripping up an existing transit system (regardless of how inefficient it is). It makes better sense to increase capacity by just adding to an existing one.
run PRT rail to the subway 'railhead', and make people swich forms of transit. Since PRT runs constantly, there won't be much wait for a PRT 'pod'; tho there will be one for the subway.
Adding transfers slows down overall transit times (and probably decreases efficiency).
I suspect the user satisfaction of the PRT system will be substantially higher than that of traditional mass-transit. People will likely even pay a premium to use it.
If you expect people to pay a premium to use the new sky cars, then you must also leave the existing infrastructure in place to justify the premium cost of transit. Otherwise people will just revert back to driving their own vehicles.
Step 1: Look at the size of the stations shown in the article or the animation.
And just how far apart do these stations have to be in order to be safe? As long as you can find a quarter mile long strip of free land in the middle of a heavily congested downtown area, it will be okay (but only for that particular stop). The next nearest stop will be a mile away (counting space for merging/diverging traffic). That could be 10 blocks or more away, each with large buildings full of commuters competing to ride a skycar. I don't know of many downtown areas that have room for an entire transit station (including stairs, elevators, fare collection, room for the sky cars, etc.). Most of the most dense population centers (where these things are needed the most) are surrounded by tall buildings on all sides and have very few clear tracts of land wider than a sidewalk. You can't just rip up a skyscraper just so that you can have enough room to build a small transit station that will not be able to support anything other than the 2-3 buildings surrounding it.
Not really. If you gradually raise gas prices and stop building large numbers of new roads, the problem takes care of itself without causing any big problems: people will gradually and slowly switch to other technologies and pick more sensible places to live (closer to work, etc.).
I work downtown and have to commute about 25 minutes each way. (Compared to most people it is a fairly light commute.) For me, riding a bicycle 20 miles is not feasable. There are no subways or light rail within at least 4 hours of my city. Buses don't run at midnight when I go to work. I would love to live closer to my job so that I can avoid dealing with traffic and never-ending road construction. Unfortunately, I can't do so because I can't afford it. The only decent residences that are closer to my job are $1500 - $4000 apartments that they pass off as luxury condominiums. I really hadn't planned on spending over half of my paycheck on rent. Even with the longer commute it would actually be cheaper to move further away from my job...
No, you just have to be a normal (i.e., non-slashdot) user. People store anything and everything in their free email accounts, from email/web site logins and passwords to their only copy of their email/phone contact lists.
Ah, but if they vouch for the validity of Domains they own (could be one in use only temporarily, but oh well) we can quickly have a registry and say, 'This domain has sent spam messages' and know that either it's an open relay, or compromised or even worse overtly friendly to spam. If they spoof the validity of the sender of email coming from domains they don't own, that would a failure of the system.
So, who will maintain this registry? And how will we prevent abuse of it? And what will happen in this scenario:
user@isp.com send out spam through their (valid) email account. user2@isp.com does the same thing, along with user3, user5, user452, etc. isp.com gets listed in this registry for sending spam. user@isp.com gets their account terminated (along with the other spammers), but doesn't get their entry removed from the registry in a timely manner (maybe it is not easy to get "de-listed"). What happens to the thousands (tens of thousands, millions) of other users at isp.com? Are they going to have to suffer because of a few errant spammers (that subsequently had their accounts terminated)? I don't want emails from myfamily@isp.com to be blocked because of an overzealous spam registry...
That's where you pull the plug on the other machines and then kill your infection before you plug the others in.
Uh, no. Assuming that you even know immediately which machines are owned, you can't just go pulling 50 (100? 250? 1,000???) other machines off the network. You have to worry about servers (with uptime requirements) and workstations, probably in different offices/server rooms, probably on different floors, in different buildings, maybe even in different cities. Not to mention the fact that all of those hacked machines will constantly try to reinfect each other and will completely kill off all of your internal network bandwidth (don't even think about your uplinks to the internet). You need an automated tool to deal with this, and it needs to be running on *all* of your machines. It may not stop the initial infection, but it will allow your office to keep working without everything going offline at once.
Secondly, why don't more people move back to city and thus not need cars as much? Before electric trolley cars used to be in place of buses. People could walk to work because of how close things used to be. American society has become too suburbanized and this is one of the biggest problems with regards to the fuel problem. Don't complain about fuel problems when you live 25 miles from your job and can't take the train!
Because I can't afford to. If we actually had some decent apartments near my job that weren't $1500/mo. I might actually live closer to work. Unfortunately developers only want to build high-rise condos/townhouses that aren't meant for average people. Even with $2/gal. gas it costs less for me to commute 20 miles each way in my SUV. And let's not talk about the complete and utter lack of decent public transit here. Buses stop too early for me (I don't work the standard 8am-5pm shift), and we don't have subways or light rail.
What about the price for the drives themselves? Doesn't it balance out when 160GB IDE/SATA drives are $100 (or less) and 140GB SCSI drives are at least 3 times as much? You only need one controller, but you need several drives. In smaller setups (small office, home network, etc.) IDE RAID should suffice just fine.
if you're running Slackware 9 on a Pentium III 2600MHz with 512MB of RAM
Where did you find a PIII 2.6GHz? I didn't think that any cooling system (short of dropping the entire system into liquid nitrogen) could handle a 1300+ MHz overclock on a PIII...
...and if you do have a crash on your $10k shoot, send the disk to a data recovery service.
Sure. Just tell your customer to push back their magazine release because the pictures from their $10k photo shoot will be delayed for a couple of weeks (or more) while your camera gets fixed...
Why would a coporation be worried about it being dropped? If anything, Open Source projects seem to be a haven for ancient code where it can linger on forever and ever, continually being tweeked and improved over the ages.
Just because it is an open source project doesn't mean that there will always be someone around to update it when there is a major (i.e., root) exploit found for it. That may be fine for smaller setups where you can just firewall something off really quickly, or maybe do a quick code change here and there to temporarily "break" the functionality that causes the issue. Many corporate setups don't have the luxury of quickly hacking in a fix for every little issue as soon as it comes out, especially when downtime is not an option. They have to worry about things like debugging, testing, reintegration, and redeployment. If there is a support contract a corporation has someone to call to complain to and demand a fix from. Corporations also don't have the option to just up and change their entire setup if a particular software product suddenly becomes no longer available. It's not always easy to just rip out a DNS server and install a new one in it's place. There are usually several other scripts and programs that have been integrated into it and depend on that software's specific setup in order to function properly.
It would probably make sense, but the fear wouldn't spread as easily. Since oxygen is already associated with being good for you, nobody would be afraid of it. People are already afraid of carbon monoxide, so as soon as they hear monoxide in any chemical's name (especially with dihydrogen, something most people have never heard of anyway), they automatically assume that it is an evil chemical.
My new MSI motherboard is even simpler.. it has a live update Windows program that works just fine in Windows XP to flash the BIOS. No need to reboot to DOS first.
That's all well and good, assuming that you actually run Windows, instead of Linux like the post you were replying to...
That doesn't work for large organizations that use different servers for outbound and inbound (MX) traffic. Not everyone sends outbound mail from their MX record. Sites like AOL, Hotmail, etc. use different sets of servers.
Besides, when you have dozens of servers (or more), which one is considered the "main server"?
Okay... So what's the difference between Miss Earth, Miss World, and Miss Universe? Since we are not (at least not knowingly...) inviting contestants from around the universe to participate, all of them pretty much have the same people competing with each other...
I would like to be able to send and receive email from my server to my family members that use AOL. The fact that you think it is a shame that they still use AOL makes no difference to me. You can't just say "make them change over to a real ISP" because it is not up to me to decide who they use for their ISP. If they are happy with AOL then it is not my position to judge them for it, just as it is not your position to judge me for letting them use AOL.
Slashdot Mirror
Hold on, if they send it to a HIGHER orbit, how does it ever get to re-entry?
It doesn't. At least not very often. (It depends on how the last of the fuel is burned off.) It is usually moved far away enough to not affect any other satellites. The real clean-up process is left for future generations with more advanced space technology.
Shouldn't be difficult to integrate with a subway system.
Assuming that there is already an existing transit system. Even then, subway stations are still underground (in many cases), so that doesn't help an above ground rail system.
if there is enough room, run PRT alongside the subway lines at some point (i.e. replace one subway track of several with a PRT track).
It doesn't make sense for a city to spend millions (billions?) ripping up an existing transit system (regardless of how inefficient it is). It makes better sense to increase capacity by just adding to an existing one.
run PRT rail to the subway 'railhead', and make people swich forms of transit. Since PRT runs constantly, there won't be much wait for a PRT 'pod'; tho there will be one for the subway.
Adding transfers slows down overall transit times (and probably decreases efficiency).
I suspect the user satisfaction of the PRT system will be substantially higher than that of traditional mass-transit. People will likely even pay a premium to use it.
If you expect people to pay a premium to use the new sky cars, then you must also leave the existing infrastructure in place to justify the premium cost of transit. Otherwise people will just revert back to driving their own vehicles.
Step 1: Look at the size of the stations shown in the article or the animation.
And just how far apart do these stations have to be in order to be safe? As long as you can find a quarter mile long strip of free land in the middle of a heavily congested downtown area, it will be okay (but only for that particular stop). The next nearest stop will be a mile away (counting space for merging/diverging traffic). That could be 10 blocks or more away, each with large buildings full of commuters competing to ride a skycar. I don't know of many downtown areas that have room for an entire transit station (including stairs, elevators, fare collection, room for the sky cars, etc.). Most of the most dense population centers (where these things are needed the most) are surrounded by tall buildings on all sides and have very few clear tracts of land wider than a sidewalk. You can't just rip up a skyscraper just so that you can have enough room to build a small transit station that will not be able to support anything other than the 2-3 buildings surrounding it.
I work downtown and have to commute about 25 minutes each way. (Compared to most people it is a fairly light commute.) For me, riding a bicycle 20 miles is not feasable. There are no subways or light rail within at least 4 hours of my city. Buses don't run at midnight when I go to work. I would love to live closer to my job so that I can avoid dealing with traffic and never-ending road construction. Unfortunately, I can't do so because I can't afford it. The only decent residences that are closer to my job are $1500 - $4000 apartments that they pass off as luxury condominiums. I really hadn't planned on spending over half of my paycheck on rent. Even with the longer commute it would actually be cheaper to move further away from my job...
No, you just have to be a normal (i.e., non-slashdot) user. People store anything and everything in their free email accounts, from email/web site logins and passwords to their only copy of their email/phone contact lists.
Ah, but if they vouch for the validity of Domains they own (could be one in use only temporarily, but oh well) we can quickly have a registry and say, 'This domain has sent spam messages' and know that either it's an open relay, or compromised or even worse overtly friendly to spam. If they spoof the validity of the sender of email coming from domains they don't own, that would a failure of the system.
So, who will maintain this registry? And how will we prevent abuse of it? And what will happen in this scenario:
user@isp.com send out spam through their (valid) email account. user2@isp.com does the same thing, along with user3, user5, user452, etc. isp.com gets listed in this registry for sending spam. user@isp.com gets their account terminated (along with the other spammers), but doesn't get their entry removed from the registry in a timely manner (maybe it is not easy to get "de-listed"). What happens to the thousands (tens of thousands, millions) of other users at isp.com? Are they going to have to suffer because of a few errant spammers (that subsequently had their accounts terminated)? I don't want emails from myfamily@isp.com to be blocked because of an overzealous spam registry...
That's where you pull the plug on the other machines and then kill your infection before you plug the others in.
Uh, no. Assuming that you even know immediately which machines are owned, you can't just go pulling 50 (100? 250? 1,000???) other machines off the network. You have to worry about servers (with uptime requirements) and workstations, probably in different offices/server rooms, probably on different floors, in different buildings, maybe even in different cities. Not to mention the fact that all of those hacked machines will constantly try to reinfect each other and will completely kill off all of your internal network bandwidth (don't even think about your uplinks to the internet). You need an automated tool to deal with this, and it needs to be running on *all* of your machines. It may not stop the initial infection, but it will allow your office to keep working without everything going offline at once.
Waitaminit... you want us to read the original submission, read the linked articles, *and* research it on Google too? I thought this was Slashdot...
Secondly, why don't more people move back to city and thus not need cars as much? Before electric trolley cars used to be in place of buses. People could walk to work because of how close things used to be. American society has become too suburbanized and this is one of the biggest problems with regards to the fuel problem. Don't complain about fuel problems when you live 25 miles from your job and can't take the train!
Because I can't afford to. If we actually had some decent apartments near my job that weren't $1500/mo. I might actually live closer to work. Unfortunately developers only want to build high-rise condos/townhouses that aren't meant for average people. Even with $2/gal. gas it costs less for me to commute 20 miles each way in my SUV. And let's not talk about the complete and utter lack of decent public transit here. Buses stop too early for me (I don't work the standard 8am-5pm shift), and we don't have subways or light rail.
What about the price for the drives themselves? Doesn't it balance out when 160GB IDE/SATA drives are $100 (or less) and 140GB SCSI drives are at least 3 times as much? You only need one controller, but you need several drives. In smaller setups (small office, home network, etc.) IDE RAID should suffice just fine.
if you're running Slackware 9 on a Pentium III 2600MHz with 512MB of RAM
Where did you find a PIII 2.6GHz? I didn't think that any cooling system (short of dropping the entire system into liquid nitrogen) could handle a 1300+ MHz overclock on a PIII...
Better question... How did it get moderated "30% Informative"?
Actually, you left one out (Insurrection). I think that it should go like this:
9. The Search for the Fountain of Youth
10. The Search for Little Picard
...and if you do have a crash on your $10k shoot, send the disk to a data recovery service.
Sure. Just tell your customer to push back their magazine release because the pictures from their $10k photo shoot will be delayed for a couple of weeks (or more) while your camera gets fixed...
In may cases they are also getting paid as well. Many of them make in a few years more than I will see in a lifetime...
Why would a coporation be worried about it being dropped? If anything, Open Source projects seem to be a haven for ancient code where it can linger on forever and ever, continually being tweeked and improved over the ages.
Just because it is an open source project doesn't mean that there will always be someone around to update it when there is a major (i.e., root) exploit found for it. That may be fine for smaller setups where you can just firewall something off really quickly, or maybe do a quick code change here and there to temporarily "break" the functionality that causes the issue. Many corporate setups don't have the luxury of quickly hacking in a fix for every little issue as soon as it comes out, especially when downtime is not an option. They have to worry about things like debugging, testing, reintegration, and redeployment. If there is a support contract a corporation has someone to call to complain to and demand a fix from. Corporations also don't have the option to just up and change their entire setup if a particular software product suddenly becomes no longer available. It's not always easy to just rip out a DNS server and install a new one in it's place. There are usually several other scripts and programs that have been integrated into it and depend on that software's specific setup in order to function properly.
It would probably make sense, but the fear wouldn't spread as easily. Since oxygen is already associated with being good for you, nobody would be afraid of it. People are already afraid of carbon monoxide, so as soon as they hear monoxide in any chemical's name (especially with dihydrogen, something most people have never heard of anyway), they automatically assume that it is an evil chemical.
My new MSI motherboard is even simpler.. it has a live update Windows program that works just fine in Windows XP to flash the BIOS. No need to reboot to DOS first.
That's all well and good, assuming that you actually run Windows, instead of Linux like the post you were replying to...
That's like Miami residents that say Miami isn't at the bottom of Florida, Key West is. In either case, it is a long way away from where I am...
That doesn't work for large organizations that use different servers for outbound and inbound (MX) traffic. Not everyone sends outbound mail from their MX record. Sites like AOL, Hotmail, etc. use different sets of servers.
Besides, when you have dozens of servers (or more), which one is considered the "main server"?
Okay... So what's the difference between Miss Earth, Miss World, and Miss Universe? Since we are not (at least not knowingly...) inviting contestants from around the universe to participate, all of them pretty much have the same people competing with each other...
There already is a site that works pretty well. It's called ORDB
Maybe, but to upgrade your kernel you don't have to purchase an entire operating system to go along with it...
I would like to be able to send and receive email from my server to my family members that use AOL. The fact that you think it is a shame that they still use AOL makes no difference to me. You can't just say "make them change over to a real ISP" because it is not up to me to decide who they use for their ISP. If they are happy with AOL then it is not my position to judge them for it, just as it is not your position to judge me for letting them use AOL.
Lucky you... At midnight I was stepping off an elevator just in time to begin my overnight shift at work...