You can't. Ethernet cabling also evolved during its lifetime. In the early stage it was using different cables with different connectors. Even your PS/2 keyboard can be connected to your USB port using reduction. But I don't know about any reduction from BNC to 8P8C. In this Wikipedia article http://en.wikipedia.org/wiki/Ethernet you can find photo of ethernet card with both connectors.

Your thinking is exactly what brought these guys into troubles. Just because some big company wrote some paper doesn't mean they are right and in line with your interest. Yes, most of the terms of such agreements are not negotiable, but some are. The great difference in having someone else to see the agreement or at least have a quiet time to study it yourself is that you know the risks and can evaluate them. Even if it might mean that you loose the deal. Sometimes it is better than bad deal. Your attorney is crap. He just failed on small threat from bank employee. He should list the pros and cons of the agreement and let the client to decide whether to sign or not. Or, eventually negotiate what changes are possible.

It is not necessary to have all users switched to IPv6. What we need is to have websites available over IPv6 so users who don't have access to IPv4 can access them. Then we can slowly start migrating end-users to IPv6 without worrying about loosing functionality. And this is where today's experiment is aimed. It is test if transition can be done without hacks like naming website ipv6.example.com instead of www.example.com as we are used to with IPv4.

What you tell to your users to be interested in IPv6?
Do you tell them here it is and if you want, you can run it? Or you tell them that when using IPv6, they will get public IP and their skype connection will be better as it will not need to use public relays?
Yes it also depends on the fact whether you actualy give your users public IP address or not. Those who are already behind NAT know what I am talking about.

No the problem is different. They are not going to switch to IPv6. They will support both IPv4 and IPv6. But there are some clients that prefer IPv6 for DNS queries while they don't have any connectivity over IPv6 to outer world. The quick and simple solution will be to disable IPv6 on those clients.

Getting it in your plumbing analogy. Water company says we can double pressure if you want. And you ask them to double pressure while your current plumbing is not able to handle it. But you still could ask them not to and they will be OK with it.

It might be interesting to see the study carried other way round. How many people with mental problems can turn into game addict. As it is said in the article "While these kids were more likely to have behavioral problems to begin with" there were already mental problems. But yes uncontrolled gaming made it worse or maybe just helped the problem to stand out. Same is true with anything you can imagine. Alcohol, cigarettes, food, ... Should we ban these? No, we put some restrictions on availability of some of them depending on how much damage it can cause. Some of them are completely uncontrolled.

Parents should watch their kids if they don't have any problems. Not just checking if they have cold. Sometimes starting to play too much might be just indication that there is something wrong with kid's surrounding. Either in school or anywhere else. What you think will happen when kid is bullied? It will start avoiding people and eventually finds that playing games is much more satisfactory than playing with "friends".

And sometimes it is just big misunderstanding. As it was in movie Role Models.

As a coincidence I just read post on lifehacker on same topic. It contains more insight into problem. They say that different parts of brain are involved when reading harder to read text and thus resulting in better understanding or remembering of written. http://lifehacker.com/5733692/harder-to-read-fonts-may-improve-learning

Why are people so persistent with attempts to bring NAT to IPv6?
If you want DHCP functionality in your home network, then you have autoconfiguration in IPv6 and all your devices will get IPv6 address in the same way as DHCP assigned IPv4 addresses. If you have any device that supports IPv4 only, then you need to run your network dualstack to ensure that it can connect to its target.
And to your complaint about length of IPv6 address. You don't have to stick with autoconfiguration. You can assign pretty any IP address you like based on prefix you get from your provider. So you can still have [your prefix]::1 address. On the other hand with ULA adresses (FC00::/7) you should use random generated interface identifier part of the address that makes it more random than static public IP addresses, where you will quickly get familiar with your prefix. And as you noted you will never reach public internet with that IP address.
But in all cases it is much easier to use computer names and forget about IP addresses.

Yes, they will continue to run it in dual-stack. But instead of current practice where you need to enter ipv6.google.com you will just simply type www.google.com and will reach them via IPv6. It is similar for other sites. You, who are like me stuck in IPv4 space mark June 8 in your calendars. As it might be day when you might not reach some resources on internet. It is due to fact how DNS will be resolved. Your computer will ask for IP addres and will get AAAA record but you don't have IPv6 connectivity so you will not connect. In better case it will fall back to IPv4.

So why e.g. MS SQL Server does it exactly as GP wrote?
Also you can use much better algorithm for data aging than OS. You know your data and you know what is better to keep and what to let go to secondary storage.
But yes for applications where massive swapping is expected the strategy described might be useful.
I was always wondering if there couldn't be something similar done for code by compilers. So if you have application, that is swapped out and looping in wait loop, then this loop will ideally fit into very small memory footprint and leave RAM for better use of active processes.

Well and what about singing my own song in a public? Yes, these extortionists are collecting money even from performance of your own stuff. Just in case you eventually join them.

100.000 ports is only for edge level leafs. You have to add additional ports for up-link, aggregation switches and of course core switches. Then you imagine how big Christmas tree it is.

That PMAC idea is really cool. But beyond that. Nothing special. Try to build something more large and you will find that your core layer switches have not enough ports as number of aggregation level switches will increase. And I am not mentioning problems with throughput when distant nodes will start communicating to each other.
For me it looks like they are trying to make routers redundant. But building 100 000 node network with this topology will require really powerful core layer nodes.
For large datacenters I would see some combination of tree/grid topology.

Even single disk from RAID array can provide lot of information.
RAID 5 for example as also other variants uses block level striping. So as long as data someone is after does fit into such block, then it might be useful to have only one disk from raid array.
And also if you have all disks from an array you have more recovery data (parity blocks) than if you use only one disk. So the guessing is much easier.
But again are your data so critical for you to have such disk mechanically destroyed and not only data overwritten. Maybe few writes of random data.
And if your data are so important not to fall into wrong hands (competitors, news reporters, ...) why they are not encrypted in the first place? Not whole disk but the really sensitive data. Your disks might be stolen and then none of secure wiping will help you.
Of course there are occasional events where disk dies and it is not possible to wipe data as someone wrote. In such case mechanical destruction can be handy.
Once I put together computer pieces without any case and connected it to old 5 1/4 disk drive. I wrote a batch file for reading text of the diskette, which was ripped open so anyone was able to see it spinning, and put it into display. The next morning I came to work the program didn't work. When I looked closely I saw white line on the disk. It was because only small part of the disk was accessed and because it was open then dust settling on the disk helped to destroy it. As those days my intention was not to destroy it put together small program that read everything in memory and then moved heads randomly so not only a small part of the disk was brushed off.
But the point is that modern hard drives are more sensitive to dust than was old diskette. So why not to open the drive and run secure wipe on it and watch how it gets overwritten while it is being simultaneously brushed and have a fun.
How long you will leave it running is up to you.