It's also very useful for testing, development, prototyping. What better way to have a vast variety of platforms for these tasks?
For prototyping your metal-based services, you can purchase a roomful of servers or you can install vmware. Which is gonna get you to production within your budget?
Unless you write all of your own software, you are going to have old legacy applications in your system, whether you like it or not. If these applications are not CPU intensive but they are still necessary, virtualization is an ideal solution.
IPv6 is for when you want to talk to someone who isn't part of your home network.
With IPv6 autoconf, you can just plug your computers into your network and you don't have to configure them at all. Isn't that how a home network is supposed to work?
Can you HONESTLY say that if someone showed you a pile of IP V6 addresses and said "One of these has a problem in either the address or the subnet" you could just pick it out on the fly?
Don't we have, like, computers, that do that kind of thing?
For internal to my own network, I'm not sure what IPV6 offers *me*
Probably nothing. Most small internal networks won't benefit.
IPv6 has private addresses, just like IPv4 except the chance of collision is vanishingly small. With IPv6 you can properly route packets to your buddy's lan without requiring one of you to change their private IP addresses.
I've never had much luck in getting two Windows machines to handle file sharing without opening up perms fully since there's no mutual authentication that I can work out
What's amusing is that you started out complaining about DNS, and when we get to the bottom of your complaint, it turns out that it's all based on your ignorance of Windows authentication.
Slashdot Mirror
It's also very useful for testing, development, prototyping. What better way to have a vast variety of platforms for these tasks?
For prototyping your metal-based services, you can purchase a roomful of servers or you can install vmware. Which is gonna get you to production within your budget?
Unless you write all of your own software, you are going to have old legacy applications in your system, whether you like it or not. If these applications are not CPU intensive but they are still necessary, virtualization is an ideal solution.
On the contrary, these instructions are run directly by the host processor at full speed.
VMware emulates the rest of the computer, but it's just time-slicing the CPU to the emulator, so pure CPU runs more or less at full speed.
Please note in your virtual machines that the CPU is not virtualized, it is the same make and model as your actual hardware.
It's I/O that suffers with virtualization, because the I/O devices have to be emulated.
It's not the database, it's the application
a database with strange performance variations can draw out race conditions in poorly written applications
If the virtualized database takes too long to respond and an internal error happens, that can create quite a mess.
Much better to have a database server with guaranteed response time.
I would not virtualize the servers that are running the virtual machines.
Why not write in Qt for Windows? It's certainly pleasant to work with, and you get Linux and OSX ports basically for free.
Qt for Windows builds with mingw, so YES it is possible to build Windows desktop apps for free.
"Rotational media is only going to stick around because it's CHEAP."
Is there any other reason for technology to stick around when it competes with other technology?
"They value ENERGY EFFICIENCY over everything."
Is that why most laptops have fans to conduct away the heat energy that they are wasting?
The Internet is burning down market models all over the world
You can't pass judgement on the new models, until the smoke and ash from the old ones is gone.
You can download the samba source package in a few seconds for free, it's jam-packed with all the info you could ever need.
If you want better than that, you'd better have a checkbook and some money in your account.
within your address range handed out by the ISP
And you don't think this can be tracked?
IPv6 is for when you want to talk to someone who isn't part of your home network.
With IPv6 autoconf, you can just plug your computers into your network and you don't have to configure them at all. Isn't that how a home network is supposed to work?
What in the US Constitution gives the US federal government authority to regulate the protocols supported by routers?
If those routers are crossing state lines then it's well established that the federal government can require that they are all painted green.
Can you HONESTLY say that if someone showed you a pile of IP V6 addresses and said "One of these has a problem in either the address or the subnet" you could just pick it out on the fly?
Don't we have, like, computers, that do that kind of thing?
You dont see them howling for more.
Why not google for:
www.nokiasiemensnetworks.com
"Nokia Siemens Networks Moving to Ipv6: An urgent priority"
one of these days someone is going to separate you from some of your teeth.
"did you have anything useful or constructive to add?"
anger managment maybe?
DHCPv6 is not the only way to do it, so mandating it is kind of silly
With zeroconf and IPv6 autoconfig, you don't actually need to run a DHCP server at all.
Who is switching IP addresses? With IPv6, your ISP has no shortage, so they will just give you a permanent one.
For internal to my own network, I'm not sure what IPV6 offers *me*
Probably nothing. Most small internal networks won't benefit.
IPv6 has private addresses, just like IPv4 except the chance of collision is vanishingly small. With IPv6 you can properly route packets to your buddy's lan without requiring one of you to change their private IP addresses.
So, did you have anything useful or constructive to add?
You should crack a book about Windows Authentication. Try running a samba server and look at the debug output
Maybe you can realize that begging for tech support doesn't exactly confirm your credentials for passing judgement about network protocols.
You don't even need cookies at all if you just track their IP address
I've never had much luck in getting two Windows machines to handle file sharing without opening up perms fully since there's no mutual authentication that I can work out
What's amusing is that you started out complaining about DNS, and when we get to the bottom of your complaint, it turns out that it's all based on your ignorance of Windows authentication.
is there a free dynamic dns solution?
"On my home network, I've got my own machines"
You can run YOUR VERY OWN server for free!
Come on, no one is rolling out a data center with a million new boxes. And all of them internet facing? Really? No multi-tier architectures?
Apple sells 13 millon iPhones in a quarter. They're ALL internet facing, no multi-tier architectures, and they ALL need IP addresses!
if it's you and your own little network, you don't even need DNS. That's what /etc/hosts is for.
"For internal to my own network, I'm not sure what IPV6 offers *me*"
If *YOU* happen to live in a world where everyone's telephone is on the Internet, then IPv6 means you actually get to have an IP address.