There's an
IETF working group addressing the very real problem of IDN. It's not as simple as you would have the/. readers believe.
The DNS protocol itself is 8-bit clean, so even BIND can handle UTF-8 characters. That isn't the problem. Go read some of the drafts for a much better treatment than I could give.
But let's not start doling out domains before the solution is complete. And it's not.
Actually, there are many, many, many Whois databases. Check out section 2.1 of this Internet draft for an overview of them. (I'm listed as co-author, but Andrew Newton did 95% of the work.)
I work in the database group at the RIPE NCC, and there are actually more privacy problems with the IP database than I'm comfortable with. We do our best to protect user information, but of course we also have an obligation to make the information available to those who genuinely need it. It's a tough balance to maintain, since we are a public resource, and do not require registration of any kind to access the database.
The Regional Internet Registry (RIR) community has guidelines defining the largest network that can be listed without providing end-user contact information. Currently, any network bigger than a/29 (more than 8 IP addresses) needs to have contact information of a person on-site.
One of the great things about the RIPE NCC and the other RIR's is that if you don't like the policy, you can change it.:)
...is that ICANN is there to serve the Internet, not control it.
But "the Internet" (whatever that is) never asked for ICANN. ICANN was created by the good and pure desire of the US government to get completely out of the business of running the Internet it created. Unfortunately it just got a little out of hand.
ICANN did have a no-win situation regarding meeting locations.
If they did the logical thing, and scheduled meetings in the places that actually had Internet access they would get slammed for contributing to the "digital divide". Yes, it's a crock, but I'm pretty sure this was the logic.
So they decided to be "global", and whiz about the globe having meetings in Antartica, the Bikini Atoll, and on the ISS. No wonder they need a $40 million budget.
Virtually every point you have in your little paper is nonsense, at least when it comes to commericial grade NFS implementations.
I'd be very interested to know which points are nonsense, and also what you consider a "commercial grade" NFS implementation. Remember that a lot of these issues are client-side related, and I'm especially not sure what a "commercial grade" NFS client is.
My experience with NFS is limited to Network Appliance, Solaris, Linux, BSDi, SCO, and Digital Unix (as well as some early Windows NFS applications).
Personally I recommend never using NFS. Heck, I wrote a paper about it. It's a bit old, and doesn't cover NFSv4. But of course, NFSv4 doesn't address the basic issue of using the wrong model for the problem, so that's not a big deal.:)
Why does everyone think Linux on Sparc would be better?
As a software developer, the reason I would prefer Linux on Sparc is the same reason I prefer open source in general: I can see what's really going on and fix it if necessary.
We added Sun's Recommended Patches to our servers in December 2001, and one of our applications started leaking memory. I spent a few days and finally tracked it down to the gethostbyname_r() call in POSIX threaded applications in the patched Solaris. We sent Sun support a 20-line program to demonstrate the problem.
Well, it's now almost March 2002, and Sun hasn't fixed it. If it was a Linux box, I probably would have just fixed it myself.
If you're forced to use expensive, slow Sun hardware and deal with their incompetent support staff, at least you can fix the problems and serve your customers with Linux!
Someone on the ibm-main list today mentioned that the processors are themselves duplicated on chip, with comparison logic to ensure that both sides are computing the same thing. Does Intel even parity-check their processors?
I'm not sure how one would parity-check a processor per se, but the Itaniums do indeed parity check their on-chip cache memory.
And remember, we're bashing Sun today, not Intel. Sun makes their own CPU's. Yes, they might be expensive, but they sure are slow!
Sun was caught with its pants down. Instead of Sun offering a comparable product, their cupboard is bare.
I've been working in the IT industry for almost 9 years now, and I can assure you that Sun has been arrogant, overpriced, and mediocre in quality the entire time I've dealt with them. I eagerly await the company's demise, and am glad that Linux will help that along.
By agreeing that the global environment is a chaos system and saying global warming is a fact you contradict yourself.
I think you overstate the unpredictability of chaotic systems. After all, any 3-body system is provably unpredictable (as in: earth, moon, sun). This doesn't mean that the behavior is totally unbounded and that anything can happen.
Additionally, the previous poster seemed to be noting that we are currently experiencing global warming. There's no prediction involved, hence even by your interpretation of chaos, no contradiction is involved.
your clear lack of understanding of the English language (or a reasonable thought, for that matter) apparently makes you a genius.
You shouldn't be too hard on him. Based on the office locations of his company he's either German, in which case it's understandable, or from London, in which case he's never had a chance to learn English.
Couldn't hurt to have a couple of those admin folks in London do a spell check on the web page though. Even a British dictionary could catch most of the problems.
We received mail from an open relay running on IP address 10.0.0.1. You are listed in whois.apnic.net as the technical contact for this address. Please close this relay, or we will be forced to blackhole your address space.
English to Chinese. Chinese to English.
We accept the mail transport the temporary residence IP address from one opening relay 10.0.0.1. You are listed take in whois.apnic.net the technical contact for this address. Please closes this relay, or we are will forced to blackhole your address space.
Not to shabby, I suppose. But do you really think a semi-clueful administrator is going to be able to figure out what this means? I work at RIPE NCC, and if I got the second version I'd be scratching my head trying to figure it out (and I spend a lot of time deciphering e-mail from people who don't speak English natively, who all seem to think that the RIPE NCC is continually launching cyberattacks against their site).
it's late. i'm tired. DIV 0 ERROR! - why not just make divide by zero return zero, or NaN, or whatever, anyway?
This is easy to achieve with floating point math, at least on a Unix box: #include <stdio.h> #include <signal.h>
int main() {
signal(SIGFPE, SIG_IGN);
printf("Positive number divided by 0 yields: %f\n", 11.0/0);
printf("Negative number divided by 0 yields: %f\n", -11.0/0);
return 0; }
On my system, I get: Positive number divided by 0 yields: inf Negative number divided by 0 yields: -inf
In the integer world, there really is no value for infinity, so you can't so casually ignore division by zero. In any language with exceptions you can trap the error and carry on as well. Or you could just be a man and test your code before shipping it to the user.:)
While what you say is more or less true, let's not forget that in the hands of bad people, the US system is not as happy and carefree as you suggest. The classic example of this is President Nixon.
Now I know Nixon is a big conservative hero, but the reality is that he used his power, both political and military, to opress political opposition to further his own ends.
The best example of this is probably not the whole Whitewater scandal, but rather the Pentagon Papers. For those not in the know, this was a book written by the Pentagon designed to be a report of the US involvement in Vietnam. When a newspaper (NY Times) got a hold on it and started printing it, Nixon arranged to have the first order against a newspaper printing a story in the history of the US issued.
Now mind you, this wasn't a list of current battle strategies or logistics, but a history of the war that had been going on for 7 or 8 years at this point. The newspaper was vindicated in the end, but not before suffering attacks and threats.
It's also why setting up a bootable CDROM is in many cases the way to go.
This isn't the point. The problem is that whatever exploit the script-kiddie used to root your box is going to still be there, no matter how many times you hit the big red button and reboot.
You need to know what happened, so you can patch the hole.
Slashdot Mirror
The DNS protocol itself is 8-bit clean, so even BIND can handle UTF-8 characters. That isn't the problem. Go read some of the drafts for a much better treatment than I could give.
But let's not start doling out domains before the solution is complete. And it's not.
FOUR acronyms in the story title. Compared to three non-acronyms. That's some kind of record, IIRC.
Actually, it's worse than that.
RIPE NCC -> RIPE Network Cordination Centre
RIPE -> Reseaux IP Europeens
IP -> Internet Protocol
Actually, there are many, many, many Whois databases. Check out section 2.1 of this Internet draft for an overview of them. (I'm listed as co-author, but Andrew Newton did 95% of the work.)
/29 (more than 8 IP addresses) needs to have contact information of a person on-site.
:)
I work in the database group at the RIPE NCC, and there are actually more privacy problems with the IP database than I'm comfortable with. We do our best to protect user information, but of course we also have an obligation to make the information available to those who genuinely need it. It's a tough balance to maintain, since we are a public resource, and do not require registration of any kind to access the database.
The Regional Internet Registry (RIR) community has guidelines defining the largest network that can be listed without providing end-user contact information. Currently, any network bigger than a
One of the great things about the RIPE NCC and the other RIR's is that if you don't like the policy, you can change it.
...is that ICANN is there to serve the Internet, not control it.
But "the Internet" (whatever that is) never asked for ICANN. ICANN was created by the good and pure desire of the US government to get completely out of the business of running the Internet it created. Unfortunately it just got a little out of hand.
ICANN did have a no-win situation regarding meeting locations.
If they did the logical thing, and scheduled meetings in the places that actually had Internet access they would get slammed for contributing to the "digital divide". Yes, it's a crock, but I'm pretty sure this was the logic.
So they decided to be "global", and whiz about the globe having meetings in Antartica, the Bikini Atoll, and on the ISS. No wonder they need a $40 million budget.
Virtually every point you have in your little paper is nonsense, at least when it comes to commericial grade NFS implementations.
I'd be very interested to know which points are nonsense, and also what you consider a "commercial grade" NFS implementation. Remember that a lot of these issues are client-side related, and I'm especially not sure what a "commercial grade" NFS client is.
My experience with NFS is limited to Network Appliance, Solaris, Linux, BSDi, SCO, and Digital Unix (as well as some early Windows NFS applications).
Personally I recommend never using NFS. Heck, I wrote a paper about it. It's a bit old, and doesn't cover NFSv4. But of course, NFSv4 doesn't address the basic issue of using the wrong model for the problem, so that's not a big deal. :)
what the fuck, the project I'm working on is just a prototype, for god sake...
The only way this will be "just a prototype" and not get foisted on some unsuspecting customer is if you make the code self destruct in some way.
My advice: do the full product lifecycle here, i.e. requirements, design, document, implement, test.
Do you think your sales reps are going to understand that this is "just a prototype"?
Why does everyone think Linux on Sparc would be better?
As a software developer, the reason I would prefer Linux on Sparc is the same reason I prefer open source in general: I can see what's really going on and fix it if necessary.
We added Sun's Recommended Patches to our servers in December 2001, and one of our applications started leaking memory. I spent a few days and finally tracked it down to the gethostbyname_r() call in POSIX threaded applications in the patched Solaris. We sent Sun support a 20-line program to demonstrate the problem.
Well, it's now almost March 2002, and Sun hasn't fixed it. If it was a Linux box, I probably would have just fixed it myself.
If you're forced to use expensive, slow Sun hardware and deal with their incompetent support staff, at least you can fix the problems and serve your customers with Linux!
Someone on the ibm-main list today mentioned that the processors are themselves duplicated on chip, with comparison logic to ensure that both sides are computing the same thing. Does Intel even parity-check their processors?
I'm not sure how one would parity-check a processor per se, but the Itaniums do indeed parity check their on-chip cache memory.
And remember, we're bashing Sun today, not Intel. Sun makes their own CPU's. Yes, they might be expensive, but they sure are slow!
Sun was caught with its pants down. Instead of Sun offering a comparable product, their cupboard is bare.
I've been working in the IT industry for almost 9 years now, and I can assure you that Sun has been arrogant, overpriced, and mediocre in quality the entire time I've dealt with them. I eagerly await the company's demise, and am glad that Linux will help that along.
By agreeing that the global environment is a chaos system and saying global warming is a fact you contradict yourself.
I think you overstate the unpredictability of chaotic systems. After all, any 3-body system is provably unpredictable (as in: earth, moon, sun). This doesn't mean that the behavior is totally unbounded and that anything can happen.
Additionally, the previous poster seemed to be noting that we are currently experiencing global warming. There's no prediction involved, hence even by your interpretation of chaos, no contradiction is involved.
your clear lack of understanding of the English language (or a reasonable thought, for that matter) apparently makes you a genius.
You shouldn't be too hard on him. Based on the office locations of his company he's either German, in which case it's understandable, or from London, in which case he's never had a chance to learn English.
Couldn't hurt to have a couple of those admin folks in London do a spell check on the web page though. Even a British dictionary could catch most of the problems.
English to Chinese. Chinese to English.
Not to shabby, I suppose. But do you really think a semi-clueful administrator is going to be able to figure out what this means? I work at RIPE NCC, and if I got the second version I'd be scratching my head trying to figure it out (and I spend a lot of time deciphering e-mail from people who don't speak English natively, who all seem to think that the RIPE NCC is continually launching cyberattacks against their site).
Pillows are used for sleeping, sitting, napping, shooting people, again lots of things.
Where the hell are you buying your pillows from son?!?!?! Using the Q Division's Eternal Rest line of sleeping aids?
Wasn't Nixon dead by the time Whitewater broke? I think you mean Watergate?
Um... yeah. Mea culpa.
Incredibly off-topic, but your sig interested me:
:)
it's late. i'm tired. DIV 0 ERROR! - why not just make divide by zero return zero, or NaN, or whatever, anyway?
This is easy to achieve with floating point math, at least on a Unix box:
#include <stdio.h>
#include <signal.h>
int main()
{
signal(SIGFPE, SIG_IGN);
printf("Positive number divided by 0 yields: %f\n", 11.0/0);
printf("Negative number divided by 0 yields: %f\n", -11.0/0);
return 0;
}
On my system, I get:
Positive number divided by 0 yields: inf
Negative number divided by 0 yields: -inf
In the integer world, there really is no value for infinity, so you can't so casually ignore division by zero. In any language with exceptions you can trap the error and carry on as well. Or you could just be a man and test your code before shipping it to the user.
While what you say is more or less true, let's not forget that in the hands of bad people, the US system is not as happy and carefree as you suggest. The classic example of this is President Nixon.
Now I know Nixon is a big conservative hero, but the reality is that he used his power, both political and military, to opress political opposition to further his own ends.
The best example of this is probably not the whole Whitewater scandal, but rather the Pentagon Papers. For those not in the know, this was a book written by the Pentagon designed to be a report of the US involvement in Vietnam. When a newspaper (NY Times) got a hold on it and started printing it, Nixon arranged to have the first order against a newspaper printing a story in the history of the US issued.
Now mind you, this wasn't a list of current battle strategies or logistics, but a history of the war that had been going on for 7 or 8 years at this point. The newspaper was vindicated in the end, but not before suffering attacks and threats.
This isn't liberal innuendo, it's the facts.
That's the problem with that Anonymous Coward guy.
I figure that the x86 has maybe 3 years to go 64-bit across the board, or we'll be facing another 640K like situation.
Looking at the cost of RAM these days, I'd say a lot less than 3 years.
Maybe what we need is.... the War on Security. :)
Well, you can't say GNU's got GNOBOLs.
According to this article no private entity can deliver a package or envalope for less than $3 or twice the cost of a first class letter.
Yeah, like all of those not-understanding people who actually designed and built the Internet. The class of people that make up the IETF.
RFC2775 pretty much covers this.
It's also why setting up a bootable CDROM is in many cases the way to go.
This isn't the point. The problem is that whatever exploit the script-kiddie used to root your box is going to still be there, no matter how many times you hit the big red button and reboot.
You need to know what happened, so you can patch the hole.