News for hackers. Stuff that matters.
Re:Replacing a Development VPS with Linux on OSX by typicalrunt on Wednesday September 07, 2011 @11:27AM (#2969893)
There are some useful tips in that article.

Using qemu in a no-gui mode is pretty cool. I've used VirtualBox, VMWare Fusion, and Parallels on OSX before, but I hate having to deal with the GUI window (and having the system reserve resources for it).

Since OSX is based on Unix under the hood, it shouldn't be too difficult to for a developer to use either OSX or Linux as their development machine. It's not like the knowledge gap between Windows and OSX/*nix machines. So other than messing around with Linux, the article fails to mention why he doesn't use OSX (other than some unfounded 'flaky' and 'impossible' critiques).

Re:Replacing a Development VPS with Linux on OSX by jmlacroix on Wednesday September 07, 2011 @11:52AM (#2970010)
Hello, I'm the author.

I mostly use OSX for everything. The only times I switch to the VM is when I'm having a hard time installing something (for an example, see my earlier comment - http://news.ycombinator.com/item?id=2969509) or want to try a tool that's not available under OSX.

I admit the post would have been better with examples and without then unfounded critiques, taking notes for the next ones.

Re:Replacing a Development VPS with Linux on OSX by martijn_himself on Thursday September 08, 2011 @04:13AM (#2973073)
Just wondering if you could think of anything obvious I'm doing wrong (I'm pretty much a newbie when it comes to this)...

I'm following the instructions in your post on my Macbook Pro (2010); however I get 'Booting from DVD/CD... 180MB medium detected. Boot failed: Could not read from CDROM (code 0005) No bootable device.' I am using the netinstall Arch Linux ISO.

Many thanks!

Re:Replacing a Development VPS with Linux on OSX by halostatue on Wednesday September 07, 2011 @11:57AM (#2970034)
VirtualBox also can run without GUI windows:

    VBoxManage start vmname -type=headless
If you need to see the GUI, you need the VNC extensions installed (which are, IIRC, not FOSS).
Re:Replacing a Development VPS with Linux on OSX by Bockit on Wednesday September 07, 2011 @11:45AM (#2969985)
I may be missing something but I think you can do what is proposed with VirtualBox. I use it for my virtual dev machines and run them in headless mode. For example the command:

vboxmanage startvm "Name of VM" --type=headless

to boot an image up, takes about 10 seconds to be ready to ssh into (You can ssh immediately it just waits till it has booted to connect).

vboxmanage controlvm "Name of VM" poweroff

If you want to turn it off from the outside.

Re:Replacing a Development VPS with Linux on OSX by ch0wn on Wednesday September 07, 2011 @11:37AM (#2969944)
I used to work on Django project on a Mac. Dependencies like python-mysqldb can be quite tricky to install on OSX, whereas Ubuntu only requires you to type 'apt-get install python-mysqldb' and you're done.

More importantly, though, I do not like the idea of having all those services constantly running on my desktop system. I'm using Ubuntu for both development and deployment now and I still use a separate VM.

Re:Replacing a Development VPS with Linux on OSX by zokier on Wednesday September 07, 2011 @04:26PM (#2971268)
I think one of the main reasons why I like VMs so much is that they allow my base OS to stay relatively clean. Especially as I like to try out all kind of new stuff constantly, VMs make that easy without having to care how they affect the rest of my system. Even if you aren't trying out new stuff, keeping separate projects mostly isolated makes me feel happier. imho also configuring stuff becomes easier when your machines become basically single-purpose systems.
Re:Replacing a Development VPS with Linux on OSX by chrischen on Wednesday September 07, 2011 @02:07PM (#2970653)
It's often a good idea to simulate your production server as closely as possible.
Re:Replacing a Development VPS with Linux on OSX by mentat on Wednesday September 07, 2011 @05:07PM (#2971452)
If you want no-gui VirtualBox that "just works" try vagrant.