I’ve found cygwin (cygwin.com). To me, it’s 100 times better than any sort of dual boot or mammoth virtual machine. It allows me to stay in windows, yet have a linux command window. It’s free. Cool!
It installs fairly easily, and runs on Windows. So now I have a linux machine that runs in a plain DOS-like window. But continuing a trend I’ve noticed, even the Windows-based setup applet (which you’ll run repeatedly, as you choose different packages or applications or options to install) is non-standard in strange little ways. There’s no cursor bar, so navigating the hundreds (thousands?) of packages is mousebound and a little tedious. But it gets the job done. It downloads whatever packages you choose, and installs them silently. No reboot needed, no close & rerun; just install and go. Nice. Decently simple and functional.
Installing GCC, however, was sort of crazy. The linux/unix crew, I’m beginning to remember, is a very different animal from the mainstream windows or mac crew. To install the gnu c compiler, which apparently is a grandfather and mainstream of compilers in the nix world, was a LOT more work than I’m used to. I was happy to find the instructions here. They work. But oh the hassle of it!
Since I gave up the command line (DOS and unix) in the mid-90’s, in favor of Windows, install has always been just a few button clicks. It’s gotten prettier, slower, and with more needless clicks added, but I never imagined how simple it is. The contrast with linux installs is incredibly immense. First you have to unpack the thing with certain command options, and you must know on your own where to put the whole mess. Then you run a “./configure” command, which says a whole lot of things on the screen, and if you take the time to read it all, you’re sunk. Apparently it runs a large script of pre-pre-install tasks, querying all manner of archaic abilities of your platform. Then you have to run “make check”, then “make install”, and “make clean”. The volume of text... (more)