I wonder, how can someone who posts on slashdot not understand a 'Figure of Speech'
I'm sure he knows it's not theft, but all the sheeple reading the article wont know the difference between copyright infringement and theft, much less what copyright infringement is.
Riiight. So take a guy who say is an expert in search technology. He can still work at Burger King, but not what he's the most qualified to do. Totally evil.
No he can just live off his multi-million dollar severance packages, wait a few months, then go work for Google
His stories usualy only have 1 link to any sort of article with the other link pointing to his blog. WHy not just post the info in the story submission
Friday was virtualization day at the 2005 Ottawa Linux Symposium; the large room was devoted to that topic all day long. Your editor can only handle so much virtualization at once, and so failed to attend the full set of sessions. Two talks, however, gave a good overview of where a couple of the most important Linux virtualization projects are and what they see in the future.
Xen
A full house turned out to hear Xen hacker Ian Pratt discuss his project. Xen is riding high; the software is cool and getting cooler, the venture money is flowing in, and there is no lack of buzz. Ian's talk, while mostly technical in nature, showed the signs of an up-and-coming business: slick, animated slides, and a good marketing pitch ("virtualization in the enterprise") on why virtualization is a useful thing in the first place. This was worth seeing; it is easy to understand why something like Xen is cool technology, but it can be harder to get a handle on why investors are lining up to throw money at it.
Virtualization is not a particularly new idea. Your editor first experienced it on an IBM mainframe over twenty years ago; we shared files by sending them out our virtual card punch into a co-worker's virtual card reader. Given that the alternative, in that particular time and place, was a real card reader, this looked pretty good. Every now and then things would go weird, and we would have to reboot CMS on our virtual CPU. Not only have things changed little since then, but that was all old stuff even on those days.
In the Linux world, virtualization takes one of three forms. In the "single operating system image mode," as used by the Linux-vserver project (or a simple chroot() setup, for that matter), instances are run within resource containers. Getting strong isolation is hard with this approach. Full virtualization runs an unmodified operating system in a complete virtual machine; systems like VMWare and Qemu work this way. The problem with full virtualization is that it can be hard to do in a way which is both secure and efficient, especially on current x86 hardware. Finally, there is para-virtualization, where the guest operating system kernel is explicitly ported to a virtual machine architecture; both Xen and user-mode Linux are para-virtualized systems.
So why bother with all of this? One is server consolidation: move all of those servers onto fewer actual boxes, with the resulting savings in floor space, power, air conditioning, and hardware maintenance. If you can move virtual machines between physical hosts, you can shift them around to avoid down time; when the disk drive starts to squeal, the administrator can evacuate the virtual systems to working hardware and deal with the problem. Migration also allows workload balancing; it is easier to put more virtual systems on each physical host if they can be shifted around to keep the load on all of those hosts about the same.
One other use for virtualization is security: putting a process within a virtual machine encapsulates it nicely. Even if that process is compromised, there are limits to the damage it can do - as long as it remains trapped within its virtual host. It is also possible to monitor the behavior of the virtual hosts themselves; if one starts doing unusual things, there is a good chance it has been compromised. In this sense, virtualization achieves the same broad goal as SELinux: it puts walls between applications running on the same host. The virtualization approach has the advantage of relative simplicity for situations where all users of a host are to be completely isolated from each other.
Xen, currently, is at version 2.0.6. It provides secure isolation, resource control, quality of service guarantees, live migration of virtual machines, and an execution speed which is "close to native" on the x86 architecture. As a para-virtualization system, Xen requires that the guest kernel be ported to its virtual architecture; ports exist for NetBSD, FreeBSD, Pla
How is this a troll/flamebait? It's a logical comment, the number of us normal users who have or have access to the Developer Mac boxen is next to nil.
Slashdot Mirror
suit . . . lawsuit, not 'law suite'
might want to look up what suite means.
You can buy a 'subscription' to their 'members-only' forum for $.01 . . . dunno if they fixed that yet or not :)
All i saw were pictures of "Hey looks here's the stuff we used"
That's not really instructions on how to build one.
It's like shoving a completely dismantled BMW to a novice mechanic with a picture of a complete car and a person driving the car and say "here you go"
5 lbs is a bit much if you're just wanting to get rid of the car
I wonder, how can someone who posts on slashdot not understand a 'Figure of Speech'
I'm sure he knows it's not theft, but all the sheeple reading the article wont know the difference between copyright infringement and theft, much less what copyright infringement is.
ANybody have a better link? The BBC article is a bit light on the details. 8 People, Fifteen countries, and that's about it.
and you think anybody is going to care or notice? Nooooo this is SLASHDOT . . of course a Microsoft product is shitty
1-5) Everything is movable . . . see that little grey thing at the left side . . click it and move it . . it's been like that since IE5
Riiight. So take a guy who say is an expert in search technology. He can still work at Burger King, but not what he's the most qualified to do. Totally evil.
No he can just live off his multi-million dollar severance packages, wait a few months, then go work for Google
yea, people I know are sticking with UML until they get PAE added.
His stories usualy only have 1 link to any sort of article with the other link pointing to his blog. WHy not just post the info in the story submission
OLS: Xen and UML
[LWN subscriber-only content]
Friday was virtualization day at the 2005 Ottawa Linux Symposium; the large room was devoted to that topic all day long. Your editor can only handle so much virtualization at once, and so failed to attend the full set of sessions. Two talks, however, gave a good overview of where a couple of the most important Linux virtualization projects are and what they see in the future.
Xen
A full house turned out to hear Xen hacker Ian Pratt discuss his project. Xen is riding high; the software is cool and getting cooler, the venture money is flowing in, and there is no lack of buzz. Ian's talk, while mostly technical in nature, showed the signs of an up-and-coming business: slick, animated slides, and a good marketing pitch ("virtualization in the enterprise") on why virtualization is a useful thing in the first place. This was worth seeing; it is easy to understand why something like Xen is cool technology, but it can be harder to get a handle on why investors are lining up to throw money at it.
Virtualization is not a particularly new idea. Your editor first experienced it on an IBM mainframe over twenty years ago; we shared files by sending them out our virtual card punch into a co-worker's virtual card reader. Given that the alternative, in that particular time and place, was a real card reader, this looked pretty good. Every now and then things would go weird, and we would have to reboot CMS on our virtual CPU. Not only have things changed little since then, but that was all old stuff even on those days.
In the Linux world, virtualization takes one of three forms. In the "single operating system image mode," as used by the Linux-vserver project (or a simple chroot() setup, for that matter), instances are run within resource containers. Getting strong isolation is hard with this approach. Full virtualization runs an unmodified operating system in a complete virtual machine; systems like VMWare and Qemu work this way. The problem with full virtualization is that it can be hard to do in a way which is both secure and efficient, especially on current x86 hardware. Finally, there is para-virtualization, where the guest operating system kernel is explicitly ported to a virtual machine architecture; both Xen and user-mode Linux are para-virtualized systems.
So why bother with all of this? One is server consolidation: move all of those servers onto fewer actual boxes, with the resulting savings in floor space, power, air conditioning, and hardware maintenance. If you can move virtual machines between physical hosts, you can shift them around to avoid down time; when the disk drive starts to squeal, the administrator can evacuate the virtual systems to working hardware and deal with the problem. Migration also allows workload balancing; it is easier to put more virtual systems on each physical host if they can be shifted around to keep the load on all of those hosts about the same.
One other use for virtualization is security: putting a process within a virtual machine encapsulates it nicely. Even if that process is compromised, there are limits to the damage it can do - as long as it remains trapped within its virtual host. It is also possible to monitor the behavior of the virtual hosts themselves; if one starts doing unusual things, there is a good chance it has been compromised. In this sense, virtualization achieves the same broad goal as SELinux: it puts walls between applications running on the same host. The virtualization approach has the advantage of relative simplicity for situations where all users of a host are to be completely isolated from each other.
Xen, currently, is at version 2.0.6. It provides secure isolation, resource control, quality of service guarantees, live migration of virtual machines, and an execution speed which is "close to native" on the x86 architecture. As a para-virtualization system, Xen requires that the guest kernel be ported to its virtual architecture; ports exist for NetBSD, FreeBSD, Pla
Yea, like Joe Schmoe PC User is going to understand Linux :)
Yes, and going over 35 on that stretch of highway is wrong.
.
*Note to self* As long as I think it's okay, it's not illegal. .
Hey thanks for the advice fucktard.
How is this a troll/flamebait? It's a logical comment, the number of us normal users who have or have access to the Developer Mac boxen is next to nil.
And how many of us have these developer machines?
What that? Zero . . ah ok . . .
j1m+5n0w meet OET Bulletin 63: Clicky
If (when using the Cantenna) you violate the power laws then yes, they're quite illegal.
Of course not! Let's all jump to the conclusion that M$ deliberately deleted Apple's HQ becase M$ hates Apple and M$ is evil!
Jesus gimmie a break.
Well considering the article is from 2002 . .. no
and i'm 98.7% sure it's been posted here on /. somewhere before
nah i'm a J Random White Dude, not Gangbanger Paki Muslim so the Patriot act affects me about this much --->---
skip the first 5 and it'd be close
Lets see
Gangbanger
Turned Muslim
Trained In Pakistan
Flying back to US
Yup . . he's probably going to help old ladies across the street and help the homeless
why can't I shoot you in the face?
oh right, that's cuz it's illegal . . mkay
Because it was deemed that 35 was a 'Safe' speed to drive on that particular stretch of roadway.