|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary
[1,407]
Women 4 times more likely than men to cough up personal info
[589]
Japan's 10 funniest tech-related commercials [Videos]
[407]
Throwing away a promo CD is "unauthorized distribution"?
[1,265]
Adults too quick to dismiss educational video games
[682]
Attack of the iPhone clones [Slideshow]
[578]
10 things IT needs to know about AJAX
[1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow]
[409]
|
|
You may be right
Virtualization per-se in a Linux environment has only marginal benefits. Many of those benefits can already be achieved in other ways, and it looks like from examining the road maps for Linux Kernel development that most, if not all, of those features will be available for Linux-on-Linux 'virtualization' in the near term.
I'd go so far as to say it is going to be pretty hard to even draw a line and say 'this setup is virtualized' and 'this setup isn't'. You COULD draw the line at a 'container' maintaining its own supervisor level address space, but frankly if the host and guest are the same OS what exactly is the advantage of that in the 1st place? It really isn't much different than running some microkernel based architecture. Worse really.