Was wondering what does your dev environment look like. I am more of a Web Developer and have a Mac as personal computer and a dev box which runs Debian. So, I basically use SSH into the Debian box from my Mac.<p>I wanted to get into systems programming for linux and wanted to know how to approach that in this environment. By systems programming I mean things like writing device drivers, play with linux kernel etc.<p>Thanks.
For my personal development at home I use an old asus eeepc 900 as my tiny server. I've taken it apart to remove the screen and used ubuntu mini.iso to install CLI mode + apache2, MySQL and php5. I use apache with mod_vhost_alias to map a directory structure to hostnames automatically so developing/testing a project is very easy. My apache webroot folder is actually a folder in my dropbox, so my code is automatically backed up too.<p>I have a macbook (a 13" unibody) with the dropbox account and MAMP to develop on (type the code). I usually mount the folder of the project I'm working on, on the macbook and turn off dropbox to go easy on the syncing.<p>Lately I tend to go more to my linux roots (I was a linux only user for quite some years before I bought the macbook) so I bought an asus 1005P and put ubuntu on it, again with mod_vhost_alias and dropbox. I must admit it's a great little machine and it has almost 8hrs of battery time, wich is a real plus.<p>For me developing is something I should be able to do anywhere, at all time. Hence the rather unconventional development environment...
Aquamacs. Interchangeable MacBook/MacBook Pro. Usually, no external monitor. I'm at pains to get things working on my laptop, even though we deploy on Debian; I almost never code "remote".<p>For the times when I have to edit remotely or in a terminal: pico. Shut up.<p>I've played with Coda and TextMate, but a couple times a year I have to write serious amounts of Win32, and I need to form a relationship with my text editor.
I have a similar setup as you – work on a mac with a Debian testing box. I've always run a local server with PHP and MySQL to run things natively, but have been moving more and more to working on the testing box. My favorite software for this is Coda (www.panic.com/coda).<p>I use the built in SVN support of Coda to setup a repository on the dev box. I also set up a dev domain (dev.domain.com or beta.domain.com). I use the local server on my Mac to run rapid quick testing changes and then use the GUI on coda to see which files need to get pushed to SVN or the dev domain.<p>Oh and for MySQL, can't live without Sequel Pro.
Development Server:<p>- In-house racked 64-bit dual processor Dell with Raid-1 SCSI & 16 GB memory running:<p>- RHEL 5.4 with XEN virtualization<p>- Apache<p>- Zend Server Community Edition PHP stack<p>- MySql<p>- JRE & JDK<p>- Subversion<p>- JIRA bug tracker (nice features and surprisingly affordable)<p>Workstations:<p>- Windows XP SP2<p>- Zend Studio<p>- Various browsers for checking site display<p>- ZoneAlarm set fairly restrictive<p>- Windows Live Messenger for easy free SMS contact when needed
Well I use HyperVM which runs on Xen to boot up virtual environments for testing and deployment. At the moment I only have CentOS images setup, but when I find some time I'll add a few more linux variants.<p>Though, I have to say, I'm trying to move to something else. HyperVM is so botched at the moment, it's just useless to add features to. The guy that ran the project apparently is no longer with us, so the source has been released to the public, and currently nobody is maintaing the project.
OS X, 2 monitors. 8 Terminal windows, 2 fullscreen MacVim windows (with vim running the NERDTree and Buffer Explorer plugins).<p>I do all my Java/Flex/Ruby/Python development like that, and I think it works great. I've written code generators to give me Java or Flex classes as needed, without having to write much boilerplate.<p>Just do what feels most comfortable, and make small changes as needed to make it better.
For a long time I've just been running Linux and use emacs and the zsh shell as the main environment I operate in within it.<p>I recently got a laptop though and for reasons I won't get into, have a visceral and probably irrational dislike for Apple and I really didn't want to deal with Linux wireless not working well, or sleep not working well, or whatever else may or may not work well on the laptop. Anyway, for the laptop I got a machine with Windows 7 and I installed Linux on top of it in a virtual machine.<p>I have to say, I love it! If I want to look at something in IE or use MS Office (I prefer it over OpenOffice, sorry), or whatever else I might want to do in Windows, I don't have to reboot. I can snapshot and tinker, without worrying about breaking it, and Win 7 works really well. When I want to do dev work I boot up the Linux VM and put it up full screen and haven't had any problems yet. Next time I put together my main machine, I'm considering doing the same there, though I have gotten quite used to all the Linux apps.
I like to use Windows for my dev environment, but I code for Linux systems. When I used 32-bit Windows, I used pubuntu to run an ubuntu server inside Windows without using a VM. It was nice and fast and worked well aside from a few networking quirks that I eventually worked out. pubuntu isn't compatible with 64bit Windows yet, and I was really itching to use all of my RAM so now I run CentOS on an old laptop of mine with 256MB of ram and a busted display (not good for anything but a testing server anyway), which I have stuffed in the server closet.<p>I have my workspace folder on my dev machine shared, and on the laptop I am using cifs to mount it as a local folder (/workspace on my laptop is actually c:\workspace on my windows machine), so as I make changes to files, they are instantly reflected on the laptop. This makes for extremely convenient testing.
It really depends on what I'm doing. For python/java, I use Eclipse. For ruby, Netbeans. Shell: emacs. Any new languages that doesn't have any good ide support (such as go and objective-j): emacs. For smalltalk, well, squeak (but you use whatever version the smalltalk is, as they all come with an ide, which is part of the system, and is very hard to separate ide and production/dev environment).<p>Os-wise: I always try to stick with linux, as there are very good dev tools that are a pain to use elsewhere (for c programming, you can access the documentation by typing man and the name of the function on the terminal, which is very convenient, albeit a bit ugly).
At work: Windows 7, at home: Ubuntu 10.04<p>At both places: 2 monitors, Emacs (js2-mode, python-mode, php-mode, charp-mode, yasnippet, a custom theme, and more), a terminal shell (sometimes inside of emacs) and a browser open.<p>When I did systems programming (just for curiosity), I used just a shell and emacs on CentOS, Slackware and FreeBSD; along with some good books on messing around with that stuff. The OSes were run inside of virtual box just in case I really messed something up :-)
Try to install everything needed on the server side using macports (lamp stack, memcache, etc). MacVim and svn/git from command line to write code/manage.<p>I started running all the server software on my laptop about 5 years ago and haven't looked back since. I don't need a network connection, ssh, or anything to work. I've done quite a bit of development in the air as a result. It's also wicked fast (never any network latency) --- which adds up over time.
I code Bine in Automatic Chamber on an old Linebarger Oculon cryptangled with redundant deep-remote diamondwisp StraightRazers. Pretty standard, really.
Acer Aspire One netbook dual booting Ubuntu 10.04 and Windows 7. I do mostly web development using Python and Django on my Ubuntu partition, gedit, terminal, firefox and chrome are pretty much all I need. I come from an ASP.NET/C# background, so I have Visual Studio on my Win7 partition, but honestly the only time I boot into windows is to watch netflix.
I do front-end stuff mostly. html, css, javascript, and some php, Django or RoR (depending on the team I work with).<p>I work on my Acer Aspire one (no, really), with an external monitor. I run Ubuntu (virtualbox for testing in ie). I do all of my coding in gedit or vim, and use Git for bigger projects.
I'm a web developer too, and have a similar set up, with a debian dev machine (it's actually a small Linode VPS), and I connect from my PC via ssh. I also use SlickEdit to work on the remote files via sftp, which I find to be super useful.
Ubuntu 9.10 on Acer Aspire One netbook and 10.04 on desktop
Emacs23 nox mode with starter kit from technonancy's fork.
Ruby 1.8.7 and 1.9.1 on RVM
Rails/HAML/LESS
Prgmr 512mb vps for remote dev environment and testing
Chrome+Firefox
Web Dev work: Aptana Studio, Sequel Pro, Terminal (2x or 3x usually) HTTP Client (excellent little app for working with API's), all on Mac OSX and 2 screens, always.
OS X, dual monitors. Textmate, Sequel Pro, Transmission. I do all of my web development with these three applications and in my opinion, they're the best.
I flip between Windows 7 and Ubuntu 10.04. Dual monitors everywhere, and usually a VM on either setup to allow me to run the other OS without a reboot.<p>I don't use IDE's, just text editors. GEdit on Ubuntu, intype on Windows. I have LAMP setup on Ubuntu, and WAMP for windows.<p>All my ruby programming goes on Linux for the most part.