They are not kidding. dot.tv is the registrar for the.tv top level domain. They have a *very* strange TOS agreement. Try registering a domain, instead of just getting it "first come first serve", when you try to register, they immediately put the domain out for more bidders, and you'll have to compete for it.
If ABC decided they wanted to get abc.tv for their great new internet TV station, they would put in their notice, and dot.tv would put it up for auction, so, say CBS could bid on it too. ABC would have to be the highest bidder in order to get the domain which they deserve. With all that, ethics go right out the window. Greed is the winner on this playing field.
All this crap really makes me appreciate Linux, Apache, MySQL, and people who really understand good business.
Re:You've got to be careful with this...
on
Taking On A Spammer
·
· Score: 1
My brother and I are both in Clarksville, TN reading this! How odd....
Um.. the reason you would store the number that way is easy. And.. it's not "storing a number backwards" it's little endian byte order, and it does make perfect sense.
The reason they are stored that way is because the current processors are based on the original 8-bit processors plus the 16-bit addons. Now you get a 32-bit processor that needs to be backwards compatible.
They are stored in memory in reverse byte order, and processed in the same order. Say you have a 32 bit unsigned int variable at memory location 0x100 (for simplicity) that means it's taking 4 bytes, 0x100->0x103. So, if you store a number like 45 (0x0000002D) in it, it would go into memory as 2D 00 00 00. If you want to copy that to a byte, you copy memory location 0x100, and you've got it. In big endian byte order, it'd be stored as 00 00 00 2D (natural form) but if you want to store it in a byte, you have to grab memory location 0x100 + sizeof(unsigned long int) - sizeof(byte) so you'd get location 0x103, which is where that single byte is stored.
Does all that make sense? You may think something like "oh, storing a number backwards is evil and makes no sense", but if you are programming in assembler, it does make ALOT of sense, and you're very glad that the processor does it for you.
Slashdot Mirror
They are not kidding. dot.tv is the registrar for the .tv top level domain. They have a *very* strange TOS agreement. Try registering a domain, instead of just getting it "first come first serve", when you try to register, they immediately put the domain out for more bidders, and you'll have to compete for it.
If ABC decided they wanted to get abc.tv for their great new internet TV station, they would put in their notice, and dot.tv would put it up for auction, so, say CBS could bid on it too. ABC would have to be the highest bidder in order to get the domain which they deserve. With all that, ethics go right out the window. Greed is the winner on this playing field.
All this crap really makes me appreciate Linux, Apache, MySQL, and people who really understand good business.
My brother and I are both in Clarksville, TN reading this! How odd....
What do you call /dev/eth0?
No such file or directory
I do love Linux, but people keep misusing things like "/dev/eth0" which don't exist. Please stop making the Linux community look stupid.
Um.. the reason you would store the number that way is easy. And.. it's not "storing a number backwards" it's little endian byte order, and it does make perfect sense.
The reason they are stored that way is because the current processors are based on the original 8-bit processors plus the 16-bit addons. Now you get a 32-bit processor that needs to be backwards compatible.
They are stored in memory in reverse byte order, and processed in the same order.
Say you have a 32 bit unsigned int variable at memory location 0x100 (for simplicity) that means it's taking 4 bytes, 0x100->0x103. So, if you store a number like 45 (0x0000002D) in it, it would go into memory as 2D 00 00 00. If you want to copy that to a byte, you copy memory location 0x100, and you've got it. In big endian byte order, it'd be stored as 00 00 00 2D (natural form) but if you want to store it in a byte, you have to grab memory location 0x100 + sizeof(unsigned long int) - sizeof(byte) so you'd get location 0x103, which is where that single byte is stored.
Does all that make sense? You may think something like "oh, storing a number backwards is evil and makes no sense", but if you are programming in assembler, it does make ALOT of sense, and you're very glad that the processor does it for you.
Just my 2 cents.
Jeremy