I had the same challenge, but today's computer has 48GB. There aren't enough 0s in the poll. :)

Are you in one of the markets they have IPv6 available? I didn't think they'd rolled it out everywhere yet.

Further: are you on a D2 or D3 cable connection? If you're still on a D2 modem, I'd recommend taking the plunge and bumping up to D3. IPv6 becomes much easier, and you'll have a bigger speed potential.

Perhaps you were speculating. The tone of your post was one of (an attempt at?) knowledge. And it's a bit misguided.

I don't want to speak for Morgaine, but I suspect this last sentence in your post is probably one of the things he took issue with. You're making it sound like administrators and network engineers need to

to migrate to v6 and that's not the case. It's more like flipping a switch and adding IPv6 to the game.

There's a distinct and important difference.

Where you're partially right is the challenge with old network gear that can easily handle IPv4 in hardware. A lot of those devices aren't capable of handling v6 in hardware, and possibly not even in software depending on how old they are. Enterprises with established network hardware are often loathe to swap them out for newer devices. If a switch needs to be flipped, it's that: replacement of old, legacy (and quite frankly, crappy) hardware.

What he said. Every device in my house is dual-stacked and happily running with both v4 and v6. It took all of 10 minutes to create a new account with the likes of Hurricane Electric and then set up my tunnel. I've got an entire /48 allocated to my home, which is more than I need for ever atom in the building. :)

Well... maybe.

The tunnel broker solution is a very easy one for those of us not connected to an ISP that provides a native IPv6 solution (yet?) And once you enable it, most of your browsers and whatnot will automatically try the v6 address they get back from an FQDN look-up.

As an aside, I recently tried to create an IPv6-only Linux VM on my VMWare rig. I wanted to see if enough of the infrastructure services were available via v6 to work. It worked fine; NTP, yum upgrades (CentOS), etc all work on it. The only interesting challenge is my NAS at home doesn't yet support NFS via v6.

I was going to post this exact thing. Hey... slashdot...

$ dig www.slashdot.org aaaa | grep "ANSWER SECTION"
$

Whassupwiddat?

For folks that want to let Adobe know about their displeasure regarding the new licensing model, make a Feature Request here: http://www.adobe.com/go/wish

The more, the merrier.

jas

My game of choice at the moment is Battlefield 3. The availability of that game isn't the only thing preventing me from converting to Linux for gaming. What about the next game I want to play, and the one after that? Are they also going to be released for Linux at the same time they're released for Windows?

Further, there's better support for the hardware I'm using when I play:
- Thrustmaster HOTAS joystick and throttle for flying in the game (including drivers to remap the buttons, toggles, etc)
- nVidia GTX680 with 3 LCD panels attached, running nVidia's surround video
- Sound Blaster from Creative, which includes utilities for controlling which output the card sends sound through, etc.

When I'm gaming, I just want the rig to work. I don't foresee that happening with Linux any time soon.

Your hands should be kept at shoulder width and shoulder height. For some that's 10/2, for others 9/3 (though that's pretty rare). Generally it's between those two for most people. If the bag deploys, it'll inflate within the bends in your elbows, and potentially push your hands outwards towards the side. You might end up with bruised knuckles, but that'll be the extent of it.

jas (15+ years on the race track, and have done the accident thing)

I have this:

http://pics.lateapex.net/smile1.jpg

tacked up on the wall next to my cubicle. It's never generated anything more than laughter as well as a few comments of disbelief. Of course if anyone were to run to their manager or HR about it, I'd take it down. Thankfully, that hasn't happened.

Have a nice day.

jas

For those of us that make IP networking our livelihood, yes, we're serious about Juniper being the best. While they're not flawless by any stretch, Juni has tried to do very few things and do them phenomenally well. That vs. Cisco which tries to do everything, and does them fairly poorly.

If I had to dig at Juni, it would be their hardware production isn't as tight as Cisco's. I've certainly seen more cases of "infant mortality" and "DOA" hardware from Juniper than I have from Cisco in my years of doing this stuff. Their strength is their nearly bullet-proof network operating system (which runs atop BSD.. that doesn't suck). With JUNOS, I've been able to do things with a router that shouldn't be possible or legal, but it works and just keeps on chugging along, routing packets.

Cisco's IOS is a turd, has always been a turd, and always will be a turd. They can polish it up all they want, but in the end, it's still a stinky turd. Unfortunately, they have a market share second to none. So we make do.

What this guy (or gal) said. Juniper. The end.

All of these things are quite doable with v6 as well. Stateless autoconfig will get your server an IP address that is, for all intents and purposes: fixed. In fact, as long as you know the /64 of the LAN and the MAC address of your Ethernet card, you'll know exactly what the v6 IP will end up being. This assumes the server follows the appropriate stateless autoconfig RFC; All UNI* OSs do by default (including OS X), Windows doesn't by default but a quick one-time command fixes that.

DNS is also a no-brainer, really. Instead of A records you enter AAAA records. Or, if you're like me, you enter them both for the same FQDN.
gimli IN A [v4 IP here]
          IN AAAA [v6 IP here]

Easy stuff.

To paraphrase one of the best video game characters Valve has ever created (IMHO), "I hate articles about Valve!"

For what little it may be worth, I've been using HTTPS w/Facebook for *months*. It's been available for general use for quite some time, it's just that no one bothered trying it. And as you pointed out, the only thing that didn't work (and still doesn't) is chat.

This isn't really news at all. It's just "news" because of what happened to Zuckerberg.

I've long been a fan of the old IBM M's, but I found that they were making my wrists and hands hurt. A lot. I still have a stack of them all boxed up in one of my closets at home... About 5 or 6 years ago, I bit the bullet and switched to a softer-touch MS Natural Ergo 4000 keyboard. It took me a few weeks to become accustomed to the split, humped keyboard layout. But now, I think it's perfect and perfectly comfortable. I have one here at work on my Mac, one at home on my Mac there, and another on my gaming rig.

There is *no* tactile feedback. In fact, the keys barely make any noise whatsoever, and the feedback is somewhat like pressing your fingers into Jell-o. It's a *HUGE* departure from the old Ms, but I can't say enough good things about these keyboards.

One complaint: I wish MS would make this *exact* keyboard in a Bluetooth model. But they won't, for some reason. They do have a wireless USB version, but it's absolute trash and often has problems with interference. So I stick with the cabled/tethered version.

Good luck in your hunt.