Maybe in another 50 years that strip of flag will fetch (equivalent of the time) a couple of million dollars (or whatever currency is in use at the time).
Oh it will. Oh yes, it will. When sold as scrap nylon.
Congratulations! You consider a crippled system acceptable because you are afraid of running it natively.
2. What superior functionality am I missing out on when I bridge my VM networking? Do you run a "bond0" on your laptops two Ethernet ports? A couple of examples of this "superior functionality" that don't work in a VM would be nice.
Lack of context switch to Windows, and running Windows network stack every time I try to transmit or receive a packet, to start...
3. You may have a point with file systems, but ZFS snapshots still work inside my VM, and I can also do snapshot of the VM if I want.
ZFS is crippled under Linux to begin with -- you can't cripple it more. The best way of handling filesystem snapshots under linux is placing filesystem over LVM2, not filesystem-level snapshots.
4. I find Virtualbox in full screen mode is identical, as long as you don't push right-control+F. And using Putty to access a VM is identical to a physical box - you do code like a real man, using just as your editor "vi".don't you?
Terminal application for Linux is not called "Putty". And I happen to actually use Linux desktop as a desktop.
5. This is completely false. The user may not learn everything (like what a pain Linux wireless and power management can be), but they can learn almost everything. They will not learn nothing.
You are an example of user that "learned Linux" by running VMWare on Windows. You don't even understand how crippled your system is, and you are not aware of the fact that everything you "need" Windows for, can be easier accomplished with Linux. You therefore are a great example why this kind of "learning Linux" should never be done.
I filed a bug against an ATI driver and provided all the relevant info. Go look up driver bugs if you want to see what's out there.
Don't use fglrx. If you have hardware that requires it, get hardware that doesn't. I have actually read the specifications and bought Lenovo Thinkpad X220 that works perfectly with Linux. How come, I didn't get a laptop on sale in Best Buy advertised to WORK WITH WINDOWS 7, then shoehorned Linux into it and went bawwing all over the Internet about Linux not being Windows 7?
If you think power management is just for suspend functionality, then you have no business commenting on this issue. The topic has been fully covered on slashdot for crying out loud.
No, I think that any other form of power management would be useless with VMWare. Also "fully covered on slashdot for crying out loud" issue was fixed already. The above mentioned Thinkpad doesn't have any problems with it.
And it's STILL a wrong solution. Even if you needed live process migration, it was successfully achieved more than a decade ago -- but then no one cared. Virtualization is a hopelessly obsolete technology (it was used as "OS" for mainframes) that was resurrected because it allows to compensate for Windows' deficiencies by hiding hardware from mis-engineered OS and implementing management functionality (such as package management, multitasking/compartmentalization, storage management, backups) that was made terribly wrong and absolutely inflexible in Windows.
This is also completely irrelevant because the discussion is not about VMWare ESX, it's about desktops running Windows and VMWare Player under it. There would be no excuse for it even if you were right.
Why not? Things have come a long way since VMware was released - things like VT/Pacifica extensions have made the whole setup a lot more stable, and relatively current CPUs have more than enough cycles to burn.
And all I/O, all storage access, and networking will still go through Windows, thus defeating the purpose of OS. And VMWare will "integrate" UI with Windows, thus turning everything into incomprehensible mess.
Which drivers "had significant issues"? And how "power management" would be improved, other than by stealing CPU time from Linux? Or do you mean, you run Linux under Windows JUST FOR SUSPEND FUNCTIONALITY?
If by any chance you are not talking out of your ass, FOR $DEITY SAKE, GET RID OF VM AND DISCOVER THAT EVERYTHING IS SUPPORTED ALREADY!
Yes, but there were models with graphics adapters supported by fglrx and nothing else, ACPI tables written by Sauron and edited by Cthulhu, and similar other horrors that still work under Windows but fall apart with everything else. Things got better since then.
1. Because Linux under VM is subject to all flaws of Windows, including atrocious resource management exacerbated by VM restricting resources by itself. 2. Because Linux under VM is completely dependent on Windows networking, what robs it from most of its superior functionality. 3. s/networking/filesystem/ 4. VM, even best ones, introduce annoying UI quirks that user would attribute to Linux. 5. User will never learn anything about Linux if he will have Windows environment to do everything he does, even if setting up a superior configuration under Linux is a matter of minutes.
Yes, it is. VMWare creates another layer that passes all I/O through Windows, thus creating an even worse abomination than Windows itself. This is why Microsoft supporters are still yapping about poor Linux performance, or UI, or networking -- they all "use" Linux in VMWare.
If you want to recommend a non-current version of Ubuntu, at least do it right -- it would be the latest LTS release (10.04). Not that there is a good reason to run it on a personal desktop, as 11.04 is fine as it is, except for the choice of default desktop environment.
1. It's even easier to do nothing at all. 2. Actually modern laptops are fine -- it's the previous generation that was all messed up. At worst you can happen to have Optimus where only one of two graphics adapters is supported. I am posting this from Lenovo X220. 3. Who asked about laptops in the first place?!
Slashdot Mirror
Maybe in another 50 years that strip of flag will fetch (equivalent of the time) a couple of million dollars (or whatever currency is in use at the time).
Oh it will. Oh yes, it will. When sold as scrap nylon.
(just look at inflation).
More ASSumptions from Mr. Belits. Again, all wrong.
I am sure, it is not all wrong, as I am posting this from my perfectly working Thinkpad X220 right now.
what do I know I'm from marketing.
Quoted for truth.
Congratulations! You consider a crippled system acceptable because you are afraid of running it natively.
2. What superior functionality am I missing out on when I bridge my VM networking? Do you run a "bond0" on your laptops two Ethernet ports? A couple of examples of this "superior functionality" that don't work in a VM would be nice.
Lack of context switch to Windows, and running Windows network stack every time I try to transmit or receive a packet, to start...
3. You may have a point with file systems, but ZFS snapshots still work inside my VM, and I can also do snapshot of the VM if I want.
ZFS is crippled under Linux to begin with -- you can't cripple it more. The best way of handling filesystem snapshots under linux is placing filesystem over LVM2, not filesystem-level snapshots.
4. I find Virtualbox in full screen mode is identical, as long as you don't push right-control+F. And using Putty to access a VM is identical to a physical box - you do code like a real man, using just as your editor "vi" .don't you?
Terminal application for Linux is not called "Putty". And I happen to actually use Linux desktop as a desktop.
5. This is completely false. The user may not learn everything (like what a pain Linux wireless and power management can be), but they can learn almost everything. They will not learn nothing.
You are an example of user that "learned Linux" by running VMWare on Windows. You don't even understand how crippled your system is, and you are not aware of the fact that everything you "need" Windows for, can be easier accomplished with Linux. You therefore are a great example why this kind of "learning Linux" should never be done.
I filed a bug against an ATI driver and provided all the relevant info. Go look up driver bugs if you want to see what's out there.
Don't use fglrx. If you have hardware that requires it, get hardware that doesn't. I have actually read the specifications and bought Lenovo Thinkpad X220 that works perfectly with Linux. How come, I didn't get a laptop on sale in Best Buy advertised to WORK WITH WINDOWS 7, then shoehorned Linux into it and went bawwing all over the Internet about Linux not being Windows 7?
If you think power management is just for suspend functionality, then you have no business commenting on this issue. The topic has been fully covered on slashdot for crying out loud.
No, I think that any other form of power management would be useless with VMWare. Also "fully covered on slashdot for crying out loud" issue was fixed already. The above mentioned Thinkpad doesn't have any problems with it.
Then don't. Ubuntu boots faster than Windows restores from hibernation.
And it's STILL a wrong solution. Even if you needed live process migration, it was successfully achieved more than a decade ago -- but then no one cared. Virtualization is a hopelessly obsolete technology (it was used as "OS" for mainframes) that was resurrected because it allows to compensate for Windows' deficiencies by hiding hardware from mis-engineered OS and implementing management functionality (such as package management, multitasking/compartmentalization, storage management, backups) that was made terribly wrong and absolutely inflexible in Windows.
This is also completely irrelevant because the discussion is not about VMWare ESX, it's about desktops running Windows and VMWare Player under it. There would be no excuse for it even if you were right.
Why not? Things have come a long way since VMware was released - things like VT/Pacifica extensions have made the whole setup a lot more stable, and relatively current CPUs have more than enough cycles to burn.
And all I/O, all storage access, and networking will still go through Windows, thus defeating the purpose of OS. And VMWare will "integrate" UI with Windows, thus turning everything into incomprehensible mess.
I checked. What you wrote isn't true.
Oh yes it is: http://slashdot.org/~cgeys
I think you should apologize to cgens.
Die in a fire.
All distributions have exactly the same hardware support.
You're completely missing (or ignoring) the scope of the question being asked: "The assignment is to use an OS different from what you normally use."
Running something that looks like crippled Linux under Windows, is not "using OS other than Windows".
Die in a fire.
Which drivers "had significant issues"? And how "power management" would be improved, other than by stealing CPU time from Linux? Or do you mean, you run Linux under Windows JUST FOR SUSPEND FUNCTIONALITY?
If by any chance you are not talking out of your ass, FOR $DEITY SAKE, GET RID OF VM AND DISCOVER THAT EVERYTHING IS SUPPORTED ALREADY!
Yes, but there were models with graphics adapters supported by fglrx and nothing else, ACPI tables written by Sauron and edited by Cthulhu, and similar other horrors that still work under Windows but fall apart with everything else. Things got better since then.
1. Because Linux under VM is subject to all flaws of Windows, including atrocious resource management exacerbated by VM restricting resources by itself.
2. Because Linux under VM is completely dependent on Windows networking, what robs it from most of its superior functionality.
3. s/networking/filesystem/
4. VM, even best ones, introduce annoying UI quirks that user would attribute to Linux.
5. User will never learn anything about Linux if he will have Windows environment to do everything he does, even if setting up a superior configuration under Linux is a matter of minutes.
Yes, it is. VMWare creates another layer that passes all I/O through Windows, thus creating an even worse abomination than Windows itself. This is why Microsoft supporters are still yapping about poor Linux performance, or UI, or networking -- they all "use" Linux in VMWare.
1. No.
2. No.
3. No.
especially network cards.
You mean, WIRELESS network adapters made by BROADCOM, that you have in your CRAPPY LAPTOP, right? Right!
screwing with things like Ndiswrapper
No sane person would use ndiswrapper on his own hardware now. If wireless card is unsupported, replace it or don't use it at all.
Oh, for fuck sake!
It's not even that Gentoo is hard to install, but maintenance can drive any newbie insane if he will want to use latest version of anything.
If you want to recommend a non-current version of Ubuntu, at least do it right -- it would be the latest LTS release (10.04). Not that there is a good reason to run it on a personal desktop, as 11.04 is fine as it is, except for the choice of default desktop environment.
1. It's even easier to do nothing at all.
2. Actually modern laptops are fine -- it's the previous generation that was all messed up. At worst you can happen to have Optimus where only one of two graphics adapters is supported. I am posting this from Lenovo X220.
3. Who asked about laptops in the first place?!
I repeat, don't run Linux under Windows. Ever.
why not?
Because.
The answer involves things far beyond newbie's understanding.
Ubuntu. Current version (11.04). Use "Classic" desktop instead of Unity.
Also see http://www.unixmen.com/linux-tutorials/linux-distributions/linux-distributions4-ubuntu/1540-top-things-to-do-after-installing-ubuntu-1104-natty-narwhal .
DON'T run Linux under Windows. Just don't.
No, I did.