with its release, comes the obsolesence of the GNOME and KDE projects.
WTF??? Not even Microsoft would dare make such blatant and patently false claims. I'm all for marketing but this is unadulterated bullshit and I don't even want to look at something that starts with BS like this!
Delta Airlines, just prior to their recent bankruptcy filings, launched a new website that they are so proud of they are advertising the new website on television and radio. In their radio commercial they described the site as being "written in delicious Java".
Now it's one thing to be proud of a website and it's another thing to advertise that website. But, why would anyone need to know that it was written in Java? It's an airline reservation website for the general public! Why is the public supposed to know or care that the Delta Airlines website is "written in delicious Java"? What moron would put that in the advertisement?
This is a block level operation, whereas rsync is file level. With this system you can restore the disk image including partitions. Restoring from rsync would require you to create the partition, format the partition and the restore the files. Also, if you need the MBR...
As the article says, this is drive imaging whereas rsync is file copying.
IPv6 addresses are derived from the upstream router, always. So long as you have the physical location of key routers, the rest can be derived with a high level of probability. That's good enough.
Perhaps probability is good enough for you but, it isn't good enough for me when my life hangs in the balance. Fortunately, it isn't good enough for the FCC as they require far greater accuracy than "high probability", even for cell phones. When the router in question is serving a small town of 5,000 people that covers 100 sqare miles, how do they find you? The "highly probable" location may be 10 miles away from your physical location.
can you PLEASE tell me why anyone would even remotely want to use a technology that obstructs the use of inbound connections?
Because, it "obstructs the use of inbound connections". In other words, NAT is the beginning of a great firewall. Additionally, there will still be cases where it will be undesirable for a host to be directly addressable. NAT is unlikely to go away with IP6. Translation gateways may not be required but, they will not be eliminated.
Thirdly, the entire planet wouldn't need to switch to IPv6 - only ISPs that provide VoIP would actually need to use IPv6, and then only for systems that have IPv6 installed.
No, in order to have reliable 911 location capability by using IP6, it will be necessary for every possible client host connection point to be both, IP6 enabled and on an extremely accurate and up-to-date physical map so that the VoIP provider will know which 911 PSP to route the call to and so that the 911 service can respond to the correct location. Remember that the likes of Vonage do not provide internet connectivity. They only provide PSTN termination services. Also, the client host could be mobile as is the case of VoIP WiFi phones.
Fourthly, if you're going to be sarcastic with a Slashdot user with a UID in four digits, know the subject first.
Kahn. I am laughing at the superior UID! And after you said that, everyone else is too.
New York, California, New Jersey and Florida -- accounted for four of every four surveillance orders, according to the Administrative Office of the U.S. Courts.
Now those are some numbers that are hard to argue with.
So VoIP 911 service can work for those who subscribe to wire based internet service. Problem solved.
More accurately, requiring 911 location for present VoIP technology will make it such that, only local providers of wire based internet service can offer VoIP. In other words, if PacBell and Comcast are in your neighborhood, you can only buy VoIP service from them. You can't buy it from Vonage or any of the thousands of other providers because none of them has a wire to your house.
Now think about it for a second. How cheap do you think the service will be if there is only one or two providers for you to choose from? There are presently thousands of VoIP providers to choose from.
So you say, all we have to do is get the entire planet to switch to IP V6, promise not to ever use NAT again and, provide a real-time physical map of every router on the planet, or the US at the very least.
Hmmmm. Let me think. Hmmm. I don't foresee any problems with this. As you said, it can be done easily.
You have my permission, implement this plan immediately. </SARCASM>
Do you simply have no idea what VoIP is and how it works?
VoIP has two benefits or advantages. One advantage is taht it offers dirt cheap longdistance phone service by carrying the calls over the internet.
The other major advantage is that VoIP is completely portable. It is not tied to any specific location. If you can get internet access, you can use VoIP.
So, if you are driving down the highway, passing a truckstop with a wi-fi hotspot, and you decide to use your laptop or palm top computer to place a VoIP call, you can do just that. But, how can anyone, let alone your VoIP longdistance provider, know that you 100 feet east of the truck stop on highway 99 in Hicksville Arkansas and connect you to the local 911 service. How can they know that you are not in fact sipping a mai tai on an Indonesian beach? They can't! And that is why 911 location service cannot work reliably with any present day VoIP implementation.
Cable companies and DSL providers of VoIP services offer 911 location service. They can do this because they have a fixed cable going to a fixed installation. In other words, their wire runs from your house to their office so they know exactly where you are. But, with services like Vonage that don't actually own the cable or provide the last mile service, this is not an option. Vonage and the like have no way of reliably determining the VoIP caller's exact location.
I am quite sure that cable, DSL and regular phone companies will push very hard to require VoIP to support 911 location services because it will give them back the control over the consumer that is presently slipping away with VoIP.
And there we have it, VoIP vaporizes with a small puff of white smoke. The fact of the matter is that it is not possible to provide a reliable 911 service with the present VoIP implementations.
Wire line services can provide 911 location service because the phones are physically wired to a specific location. A number cannot move without the phone company knowing exactly where it has moved to. This is not possible with the present incarnation of VoIP. In fact, the only way that reliable 911 location service will ever be possible is if every VoIP device has a GPS receiver in it and transmits the location information when the VoIP terminal registers with the PBX. Any other way WILL fail.
This will require an all new VoIP implementation/protocol, as well as new VoIP equipment to make it work. Now, I just have to figure out how to make an ATA with GPS receiver embedded in it receive the GPS signal while under a desk indoors.
If VoIP is regulated, the baby Bells will won it. Do you feel pown3d?
might I suggest just buying Dual Layer discs and just doing a straight copy
The problem here is two fold. First, it is likely that he would have to get a new DVD writer as his probably does not support dual layer writing. Secondly, and perhaps most importantly, DVD-5 disks are a bit less than $1US each whereas DVD-9 discs run around $10US each.
I'm sure that a ten fold cost increase factors into the decision somewhere.
I'm running Open Office 2.0. Well, it's actually 1.9.79~ the 2.0 beta, on a 2.8Ghz P4 with 1GB RAM running the preload QuickStarter program. Writer takes 15 seconds to open a blank document for the first time. Closing Writer and subsequently re-opening a blank document takes 7 seconds.
Dual booting the same machine into Windows XP with Microsoft Office and running Word, I am able to type in the blank document in three seconds. Closing the document and subsequently re-opening the blank document, it opens instantly.
It may not sound like much but, there is an enormous gulf between opening instantly and waiting 7 seconds. Open Office feels like an obese pig in comparison to MS Word or even WordPerfect. It's still a great program but, like the original poster said, it feels FAT!
I forgot to metion that the same super server could service hundreds of concurrent users if you used Linux or Citrix with thin clients. Depending on your applications disk io is not the big bottleneck. Usually when it comes to terminal server bottlenecks it is memory, processors, and then disk io.
When you do it this way, the cost goes down in dramatic fashion. A $50,000 server setup is only $250 per user when you have 200 users running off it and A server as large as you suggest could easily run 500 or more users concurrently, which would further bring the cost down to $100 per user!
OK. Given that a two processor version of the DL 585 is $16,000US and does not include any storage, we can assume that a fully loaded box processors, memory and some storage, is going to run $28,000 plus and that doesn't include monitors. That's more than $1,000 per user just for hardware. Since the average business PC runs under $1,000 the server solution that you suggest just isn't cost effective.
Now add to that cost, the single point of failure issue. Even if the hardware never fails, all you need is for some malicious or clueless user to run:(){:&:;};: at a bash prompt and you're fired.
Re:John Stewart had one of these guys on....
on
Paul Graham on PR
·
· Score: 1
It was quite astounding how the guy managed to spin things around to make them sound easier to digest (justifying became "Educating and Explaining", relaxing pollution laws became the "Clear Skies" etc (reworded from memory)).
The reason for the lack of current reviews is simply because of a lack of "current" products. Fax technology has changed little if any at all in the past ten years so, what was a viable solution ten years ago, is still just as viable today. New features have been tried. Some, like routing, have been tried repeatedly without being truly successful. There just isn't a whole lot more that you can add to a fax server while maintaining interoperability with the world's fax machines.
As far as recommending a fax product, there are numerous commercial ones available, some are even "New and Improved" but, since you asked on Slashdot, I'll recommend the open source choice, Hylafax, despite your C# requirement. It's open so you can develop on or against it to your heart's content. Something I doubt any of the commercial offerings will permit.
This brings us to your final requirement where the api's language must be modern. I'm not certain, but, I think that Hylafax is written in C so it definitely doesn't fit your C# requirements, despite the fact that the two languages are not mutually exclusive unless you make them so in your own head. But, requiring that a decades old solution be "up-to-date" in terms of the programming language seems a bit unreasonable to me. Must a fax application be rewritten in the latest fad language solely for the the sake of the language?
What I suspect you will wind up doing is some VB script that uses DCOM to print-to-fax from a Windows 2003 server.
Indeed, of all the interfaces to CUPS that I have seen, two stand head and shoulders above the rest. Yast is hands down the best Linux interface. The other interface worthy of note is for an Apple variety.
It's still a great big steaming pile. I never thought it would happen, but from time-to-time I catch myself saying; "Maybe I should go back to lpd" <shudder>
One more rant, whoever it was that was unimaginative enough to come up with the foomatic name should be flogged.
surely you can see the immediate need and usefulness of transparent windows and wobbly windows. Not to mention that the present versions of X11 are only using from 50 to 100 megabytes of memory when modern systems have 512 to 1 gig available. I think once we get the bugs worked out of these new features, then we can look into more advanced stuff like "hot-plug monitors" and dynamic resolutions.
What units are you referring to when you quote 70up/30dn? Reading the Verizon site, they say kiloBytes per second(kBps). This indicates that multimegabit speeds are possible. But, your post appears to be saying kilobits per second(kbps) which, like a 56k modem isn't terribly exciting.
Also, your post states higher uplink speeds than downlink speeds. Is this correct? It seems contrary to most broadband connections.
I was in agreement with you, until you laid down the challenge and I remembered an FAA site. In searching for it, I found some other interesting stuff.
Slashdot Mirror
with its release, comes the obsolesence of the GNOME and KDE projects.
WTF??? Not even Microsoft would dare make such blatant and patently false claims. I'm all for marketing but this is unadulterated bullshit and I don't even want to look at something that starts with BS like this!
Delta Airlines, just prior to their recent bankruptcy filings, launched a new website that they are so proud of they are advertising the new website on television and radio. In their radio commercial they described the site as being "written in delicious Java".
Now it's one thing to be proud of a website and it's another thing to advertise that website. But, why would anyone need to know that it was written in Java? It's an airline reservation website for the general public! Why is the public supposed to know or care that the Delta Airlines website is "written in delicious Java"? What moron would put that in the advertisement?
This is a block level operation, whereas rsync is file level. With this system you can restore the disk image including partitions. Restoring from rsync would require you to create the partition, format the partition and the restore the files. Also, if you need the MBR...
As the article says, this is drive imaging whereas rsync is file copying.
PoE was using unused lines in the ethernet cable
;)
Yes.
and gbit new uses all 4 pairs
No. Gigabit ethernet uses the same pairs as 10/100 ethernet.
so is that the end of PoE?
No.
can plugging in a gbit network card into a PoE enabled line damage that card or the computer?
No. Unless you do it while you are in the bath tub
$129 for a lousy system upgrade?
IPv6 addresses are derived from the upstream router, always. So long as you have the physical location of key routers, the rest can be derived with a high level of probability. That's good enough.
Perhaps probability is good enough for you but, it isn't good enough for me when my life hangs in the balance. Fortunately, it isn't good enough for the FCC as they require far greater accuracy than "high probability", even for cell phones. When the router in question is serving a small town of 5,000 people that covers 100 sqare miles, how do they find you? The "highly probable" location may be 10 miles away from your physical location.
can you PLEASE tell me why anyone would even remotely want to use a technology that obstructs the use of inbound connections?
Because, it "obstructs the use of inbound connections". In other words, NAT is the beginning of a great firewall. Additionally, there will still be cases where it will be undesirable for a host to be directly addressable. NAT is unlikely to go away with IP6. Translation gateways may not be required but, they will not be eliminated.
Thirdly, the entire planet wouldn't need to switch to IPv6 - only ISPs that provide VoIP would actually need to use IPv6, and then only for systems that have IPv6 installed.
No, in order to have reliable 911 location capability by using IP6, it will be necessary for every possible client host connection point to be both, IP6 enabled and on an extremely accurate and up-to-date physical map so that the VoIP provider will know which 911 PSP to route the call to and so that the 911 service can respond to the correct location. Remember that the likes of Vonage do not provide internet connectivity. They only provide PSTN termination services. Also, the client host could be mobile as is the case of VoIP WiFi phones.
Fourthly, if you're going to be sarcastic with a Slashdot user with a UID in four digits, know the subject first.
Kahn. I am laughing at the superior UID! And after you said that, everyone else is too.
New York, California, New Jersey and Florida -- accounted for four of every four surveillance orders, according to the Administrative Office of the U.S. Courts.
Now those are some numbers that are hard to argue with.
So VoIP 911 service can work for those who subscribe to wire based internet service. Problem solved.
More accurately, requiring 911 location for present VoIP technology will make it such that, only local providers of wire based internet service can offer VoIP. In other words, if PacBell and Comcast are in your neighborhood, you can only buy VoIP service from them. You can't buy it from Vonage or any of the thousands of other providers because none of them has a wire to your house.
Now think about it for a second. How cheap do you think the service will be if there is only one or two providers for you to choose from? There are presently thousands of VoIP providers to choose from.
So you say, all we have to do is get the entire planet to switch to IP V6, promise not to ever use NAT again and, provide a real-time physical map of every router on the planet, or the US at the very least.
Hmmmm. Let me think. Hmmm. I don't foresee any problems with this. As you said, it can be done easily.
You have my permission, implement this plan immediately. </SARCASM>
Do you simply have no idea what VoIP is and how it works?
VoIP has two benefits or advantages. One advantage is taht it offers dirt cheap longdistance phone service by carrying the calls over the internet.
The other major advantage is that VoIP is completely portable. It is not tied to any specific location. If you can get internet access, you can use VoIP.
So, if you are driving down the highway, passing a truckstop with a wi-fi hotspot, and you decide to use your laptop or palm top computer to place a VoIP call, you can do just that. But, how can anyone, let alone your VoIP longdistance provider, know that you 100 feet east of the truck stop on highway 99 in Hicksville Arkansas and connect you to the local 911 service. How can they know that you are not in fact sipping a mai tai on an Indonesian beach? They can't! And that is why 911 location service cannot work reliably with any present day VoIP implementation.
Cable companies and DSL providers of VoIP services offer 911 location service. They can do this because they have a fixed cable going to a fixed installation. In other words, their wire runs from your house to their office so they know exactly where you are. But, with services like Vonage that don't actually own the cable or provide the last mile service, this is not an option. Vonage and the like have no way of reliably determining the VoIP caller's exact location.
I am quite sure that cable, DSL and regular phone companies will push very hard to require VoIP to support 911 location services because it will give them back the control over the consumer that is presently slipping away with VoIP.
And there we have it, VoIP vaporizes with a small puff of white smoke. The fact of the matter is that it is not possible to provide a reliable 911 service with the present VoIP implementations.
Wire line services can provide 911 location service because the phones are physically wired to a specific location. A number cannot move without the phone company knowing exactly where it has moved to. This is not possible with the present incarnation of VoIP. In fact, the only way that reliable 911 location service will ever be possible is if every VoIP device has a GPS receiver in it and transmits the location information when the VoIP terminal registers with the PBX. Any other way WILL fail.
This will require an all new VoIP implementation/protocol, as well as new VoIP equipment to make it work. Now, I just have to figure out how to make an ATA with GPS receiver embedded in it receive the GPS signal while under a desk indoors.
If VoIP is regulated, the baby Bells will won it. Do you feel pown3d?
might I suggest just buying Dual Layer discs and just doing a straight copy
The problem here is two fold. First, it is likely that he would have to get a new DVD writer as his probably does not support dual layer writing. Secondly, and perhaps most importantly, DVD-5 disks are a bit less than $1US each whereas DVD-9 discs run around $10US each.
I'm sure that a ten fold cost increase factors into the decision somewhere.
It doesn't render properly in Firefox or Konqueror. Must be one of those IE only sites.
I'm running Open Office 2.0. Well, it's actually 1.9.79~ the 2.0 beta, on a 2.8Ghz P4 with 1GB RAM running the preload QuickStarter program. Writer takes 15 seconds to open a blank document for the first time. Closing Writer and subsequently re-opening a blank document takes 7 seconds.
Dual booting the same machine into Windows XP with Microsoft Office and running Word, I am able to type in the blank document in three seconds. Closing the document and subsequently re-opening the blank document, it opens instantly.
It may not sound like much but, there is an enormous gulf between opening instantly and waiting 7 seconds. Open Office feels like an obese pig in comparison to MS Word or even WordPerfect. It's still a great program but, like the original poster said, it feels FAT!
I forgot to metion that the same super server could service hundreds of concurrent users if you used Linux or Citrix with thin clients. Depending on your applications disk io is not the big bottleneck. Usually when it comes to terminal server bottlenecks it is memory, processors, and then disk io.
When you do it this way, the cost goes down in dramatic fashion. A $50,000 server setup is only $250 per user when you have 200 users running off it and A server as large as you suggest could easily run 500 or more users concurrently, which would further bring the cost down to $100 per user!
OK. Given that a two processor version of the DL 585 is $16,000US and does not include any storage, we can assume that a fully loaded box processors, memory and some storage, is going to run $28,000 plus and that doesn't include monitors. That's more than $1,000 per user just for hardware. Since the average business PC runs under $1,000 the server solution that you suggest just isn't cost effective.
:(){ :&:;};: at a bash prompt and you're fired.
Now add to that cost, the single point of failure issue. Even if the hardware never fails, all you need is for some malicious or clueless user to run
It was quite astounding how the guy managed to spin things around to make them sound easier to digest (justifying became "Educating and Explaining", relaxing pollution laws became the "Clear Skies" etc (reworded from memory)).
Patriot Act. Nuff said.
The reason for the lack of current reviews is simply because of a lack of "current" products. Fax technology has changed little if any at all in the past ten years so, what was a viable solution ten years ago, is still just as viable today. New features have been tried. Some, like routing, have been tried repeatedly without being truly successful. There just isn't a whole lot more that you can add to a fax server while maintaining interoperability with the world's fax machines.
As far as recommending a fax product, there are numerous commercial ones available, some are even "New and Improved" but, since you asked on Slashdot, I'll recommend the open source choice, Hylafax, despite your C# requirement. It's open so you can develop on or against it to your heart's content. Something I doubt any of the commercial offerings will permit.
This brings us to your final requirement where the api's language must be modern. I'm not certain, but, I think that Hylafax is written in C so it definitely doesn't fit your C# requirements, despite the fact that the two languages are not mutually exclusive unless you make them so in your own head. But, requiring that a decades old solution be "up-to-date" in terms of the programming language seems a bit unreasonable to me. Must a fax application be rewritten in the latest fad language solely for the the sake of the language?
What I suspect you will wind up doing is some VB script that uses DCOM to print-to-fax from a Windows 2003 server.
Indeed, of all the interfaces to CUPS that I have seen, two stand head and shoulders above the rest. Yast is hands down the best Linux interface. The other interface worthy of note is for an Apple variety.
It's still a great big steaming pile. I never thought it would happen, but from time-to-time I catch myself saying; "Maybe I should go back to lpd" <shudder>
One more rant, whoever it was that was unimaginative enough to come up with the foomatic name should be flogged.
surely you can see the immediate need and usefulness of transparent windows and wobbly windows. Not to mention that the present versions of X11 are only using from 50 to 100 megabytes of memory when modern systems have 512 to 1 gig available. I think once we get the bugs worked out of these new features, then we can look into more advanced stuff like "hot-plug monitors" and dynamic resolutions.
From the screenshot, that's exactly what it is. My first thought was; this is the 911 emergency version of Clippy.
Imagine Clippy popping up when your mother's leg has been torn off in a car wreck. There are some places that Microsoft shouldn't go on any day.
What units are you referring to when you quote 70up/30dn? Reading the Verizon site, they say kiloBytes per second(kBps). This indicates that multimegabit speeds are possible. But, your post appears to be saying kilobits per second(kbps) which, like a 56k modem isn't terribly exciting.
Also, your post states higher uplink speeds than downlink speeds. Is this correct? It seems contrary to most broadband connections.
I was in agreement with you, until you laid down the challenge and I remembered an FAA site. In searching for it, I found some other interesting stuff.
Interference and model jets Ironic?
2002 CAA Omega interference PDF
Did Personal Electronic Devices(PEDs) cause TWA 800 to explode??
US House Commitee
2001 NASA Report PDF
2002 NASA Report PDF
I never could find the FAA listing of aircraft incidents. It showed several cases of problems with avionics that the cockpit crew attributed to PEDs