As far as I know, fios does not cap. Cable has terrible signal to noise problems on the upstream link, which is what forces them into needing to cap. I uploaded 12 gigs from home (fios) to dreamhost the other day with no issues. Just a steady 2 mbits/sec upstreaming for about 16 hours straight. not a problem at all.
Why not? False positives. It's capacitance based I believe, what happens if the wood is a little damp? Each stop is destructive, so now you are out on the order of $100 in parts, plus it wrecks the blade (good ones aren't cheap either), and it shuts down the equipment till the tech's can fix it. Now add a couple disgruntled shopworkers, who can at will shutdown the saws claiming a near miss and take the next couple hours off while the shop is fixing the saw.
after 2 physics courses you stop using "no actual work" and "friction" in the same statement. However your overall point that the requirements are pretty low is correct. I bet the maintenance will be fun if the bearings ever get old & dirty.
You appear to be unaware that 3.51 was considered the most reliable version of NT, and that in going to 4.0 there was a major and long lasting drop in reliability. Perhaps the biggest source of bsod was moving video drivers into kernel space.
Thank goodness Microsoft has none of those nasty high profile bugs and exploits you speak sooooo ill informedly about. If you are so worried about going out of business if you go down for a SECOND, why is it only now you are considering replacing a dusty old 1995 box, and don't even appear have a plan on how to proceed yet? PS, nine 9's reliability means that your pathetic old machine needs to be about 10000 time more reliable than the Verizon switching center down the street from me. Please tell us more how you accomplish this feat.. Multiple power feeds, hot swappable power supplies and drives?
On the outside chance that you are actually sincere (uh yeah, right) please take a look at http://www.securityfocus.com/microsoft
There isn't really any need to "a" community server for this, it should be as distributed ans DNS. It would be easiest for most if your ISP would host a SIP registrar server. Then your VoIP address can simply be "sip:myemail@mydomain". Without that, there are free SIP registrars one can already use, see http://www.cs.columbia.edu/~hgs/sip/servers.html for a few of them. Of course, the/. gang can always add an SVR record to their own DNS entries, point back to their selected sip registrar. Then once again you can use a sip uri of "sip:myemail@mydomain" while using a 3rd party registrar not hosted at mydomain.
This is not quite the angle you were looking for, but you might find it interesting or useful. Their service would let you do this and much more. However, not using your phone number... They give you a number, calls to it generate an http query, you implement the XML to drive their telephony server. See http://www.voxeo.com . I am not connected with voxeo in anyway.
Slashdot Mirror
As far as I know, fios does not cap. Cable has terrible signal to noise problems on the upstream link, which is what forces them into needing to cap. I uploaded 12 gigs from home (fios) to dreamhost the other day with no issues. Just a steady 2 mbits/sec upstreaming for about 16 hours straight. not a problem at all.
Why not? False positives. It's capacitance based I believe, what happens if the wood is a little damp? Each stop is destructive, so now you are out on the order of $100 in parts, plus it wrecks the blade (good ones aren't cheap either), and it shuts down the equipment till the tech's can fix it. Now add a couple disgruntled shopworkers, who can at will shutdown the saws claiming a near miss and take the next couple hours off while the shop is fixing the saw.
after 2 physics courses you stop using "no actual work" and "friction" in the same statement. However your overall point that the requirements are pretty low is correct. I bet the maintenance will be fun if the bearings ever get old & dirty.
Ah, another ASP.NET site /.'d to death.
You appear to be unaware that 3.51 was considered the most reliable version of NT, and that in going to 4.0 there was a major and long lasting drop in reliability. Perhaps the biggest source of bsod was moving video drivers into kernel space.
Thank goodness Microsoft has none of those nasty high profile bugs and exploits you speak sooooo ill informedly about. If you are so worried about going out of business if you go down for a SECOND, why is it only now you are considering replacing a dusty old 1995 box, and don't even appear have a plan on how to proceed yet? PS, nine 9's reliability means that your pathetic old machine needs to be about 10000 time more reliable than the Verizon switching center down the street from me. Please tell us more how you accomplish this feat.. Multiple power feeds, hot swappable power supplies and drives?
On the outside chance that you are actually sincere (uh yeah, right) please take a look at http://www.securityfocus.com/microsoft
Exactly. The ones who need a "heads up" is the clowns driving cages. Particularly those that make left turns in front of you.
There isn't really any need to "a" community server for this, it should be as distributed ans DNS. It would be easiest for most if your ISP would host a SIP registrar server. Then your VoIP address can simply be "sip:myemail@mydomain". Without that, there are free SIP registrars one can already use, see http://www.cs.columbia.edu/~hgs/sip/servers.html for a few of them. Of course, the /. gang can always add an SVR record to their own DNS entries, point back to their selected sip registrar. Then once again you can use a sip uri of "sip:myemail@mydomain" while using a 3rd party registrar not hosted at mydomain.
This is not quite the angle you were looking for, but you might find it interesting or useful. Their service would let you do this and much more. However, not using your phone number... They give you a number, calls to it generate an http query, you implement the XML to drive their telephony server. See http://www.voxeo.com . I am not connected with voxeo in anyway.