4 ms·
My solution is booting to Windows for the driver support, battery, etc. then VMware. No hardware issues ever, plus additional security.
by MichaelGG 12y ago
My solution is booting to Windows for the driver support, battery, etc. then VMware. No hardware issues ever, plus additional security.
- mattkrea 12y agoWhat do you mean by "additional security"? From Windows?
- c54 12y agoHe probably means the additional security of whatever is running in the VM, a compromised VM wouldn't be able to escape its restricted virtual world.
- mooreds 12y agoYes, I use vagrant and virtualbox and haven't had any issues running a centos or ubuntu. Best of both worlds, and heaven compared to cygwin (oh, the scripts I've written to deal with cygwin).
- barrkel 12y agoMost of my scripts run unmodified between Cygwin and Linux (OSX is a different story, if you don't have GNU tools on the path). The single biggest problem with Cygwin is performance: forking is very slow. When I need to rewrite a script for Cygwin, it's almost invariably to reduce the number of processes spawned. But almost all of the time, it just works, even building third-party stuff from source. On my home setup, I spend about half my terminal time with Cygwin, the other half in ssh sessions to Linux boxes, and there's no real mental context switch required.