Slashdot Mirror
Install Slash on Mac OS X
bcapps2012 writes "I just saw this on Slashcode.com and thought it would be of interest to many apple.slashdot.org readers. Pudge has gotten Slashcode installed on Mac OS X. As jwachter notes: 'For those of you who haven't been following the issue of how to get slash running on OS X, various Slashcode posters have been asking how to get it done for roughly 2 or 3 years now (essentially since the first preview of OS X was released).' Finally Mac OS X has joined the family."
I thought Mac OS X was BSD-derived and largely compatible with Linux stuff, especially with something like Apache which is pretty vanilla, looking over Slash I doubt it's too horrible about its demands on a Unix-like platform. What caused the problems?
OS X is indeed BSD derived and actually includes a copy of Apahce right out of the box. All of the Unix tools one would need (MySQL, PHP) are avaialble for OS X. Not sure what could've caused the problem though.
What's interesting about the copy of Apache that ships with OS X is that it has a nice GUI interface, so those too timid to configure httpd.conf should still be able to cope.
Quod scripsi, scripsi.
Bit of a rant, I'm sorry, please bare with me.
Development and Production (public) environments, in my experience, are best when kept on the same platform.
Same as you, I found all these wonderful little widgets to play with on Win2K, and decided to set up a Linux (RedHat 6.3 at the time) server to go live with a site. Found out that I lacked the practical experience installing some critical modules and libraries, and the entire project ended up flopping over like a dead cow. It sucked. Really really bad. If you want to know if this project is a really good idea, if it turns out ok, develop it on Linux first, or stick with Win2K if/when you decide to go live with it.
Short of buying or building a dedicated Linux box, I'd strongly suggest just setting up a partition on your drive, or another drive, to futz around with Linux and this new project on. That's all. Nothing too too fancy. Just a dual-boot setup, as standard. It would give you a real sense of the problems you face with this project.
/RANT (Again, my apologies.)
Informatus Technologicus
Nothing caused the problems. MacSlash has been running on it for years--since 10.0, if not the first beta. Color me unimpressed. Pudge should've known this too.
--
$tar -xvf
Bullshit. The only moved to Apple hardware recently with the acquisition of the Xserve. Otherwise Netcraft has them running FreeBSD as late as last December (link above), and they note that they only switched to the Xserve sometime since July 1.
Even though they updated it, they're still running an older version of Slashcode, so maybe it's not as relevant to this story since it's not the latest and greatest. I don't know the details of the porting issues to know if this is a factor at all... But unlike you, I checked my facts and admit when I don't know the truth!
Better yet, get one of the virtual machines (blochs, vmware,...) so you can run both at the same time. No rebooting needed!
Just to clarify, you only get the nice GUI's for a variety of servers, system monitoring apps, etc. with Mac OS X Server. The majority of actualy functionality is either there or readily available for Mac OS X client/standard, but you need to play under the hood or use third-party GUI's to configure them. Apache can be turned on simply by clicking the Web-Sharing button in System Prefs, but any custom configuration needs knowledge of Apache and the underpinnings of OS X.
Works just find on 10.2.6 - mostly the difference between Server and Plain vanilla install is the level of technical support, and the fun GUI tools to use everything. Everything's the same for the most part on the back end, Server just introduces GUI features to otherwise console-only functions. That, and Apple gives better technical support to OSX Server customers. I'd repeat myself again but I'm tired.
Although, Server uses a slightly different kernel build, although only slightly, and they're updated slightly behind that of the consumer edition, presumably for stability and testing reasons.
moox. for a new generation.
Just something not mentioned in the guide: when you install Bundle::libnet (or Bundle::LWP, one of the two) it installs its own version of /usr/bin/head. You want to backup /usr/bin/head to /usr/bin/head.bak or whatever BEFORE installing those two, then when they're installed, copy your backup back to its original spot. Normally this isn't a problem but osx doesn't treat HEAD and head as different programs like normal.