Follow Slashdot blog updates by subscribing to our blog RSS feed

 


Forgot your password?
Close
typodupeerror
×
OS X Businesses Operating Systems Programming Apple IT Technology

Install Slash on Mac OS X 60

Posted by pudge from the that-is-fantastic-news dept.
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."
This discussion has been archived. No new comments can be posted.

Install Slash on Mac OS X More

Install Slash on Mac OS X

Comments Filter:

  • One question... (Score:5, Interesting)

    by Sheetrock ( 152993 ) on Tuesday August 19, 2003 @01:59PM (#6735946) Homepage Journal
    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?

    • Re:One question... (Score:4, Informative)

      by bluethundr ( 562578 ) * on Tuesday August 19, 2003 @02:20PM (#6736147) Homepage Journal
      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. [macdevcenter.com] 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.

      • Re:One question... (Score:4, Informative)

        by h0tblack ( 575548 ) on Tuesday August 19, 2003 @08:06PM (#6739826)
        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.

    • Re:One question... (Score:5, Informative)

      by notNeilCasey ( 521896 ) <NotNeilCasey.yahoo@com> on Tuesday August 19, 2003 @02:28PM (#6736241) Homepage
      jwachter posts in the comments on the page in question:
      For the past year, a conflict between Apache::Cookie and Apache::Request on OS X has been the last obstacle to getting this done.
      So that was part of the problem ... I guess. -Neil

    • Nothing caused the problems. MacSlash [macslash.org] has been running on it for years--since 10.0, if not the first beta. Color me unimpressed. Pudge should've known this too.

      • Re:One question... (Score:5, Informative)

        by Anonymous Coward on Tuesday August 19, 2003 @03:27PM (#6736952)
        Bullshit [netcraft.com]. 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 [macslash.org].

        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!
      • We migrated to OS X Server a few months back, actually. We bought our Xserve two summers ago, only to be stymied by problems in the Dynamic Libraries. We hired a consultant, who we've in turn hired as our chief engineer, to help us surmount these problems and get it working. We went from Slash .9 to a very recent build in one big leap. Exciting, no? Tom Bridge, Business Mgr, MacSlash

    • Re:One question... (Score:1, Interesting)

      by Anonymous Coward
      No, OS X is not compatible with Linux stuff. OS X IS compatible with most GNU and other open source applications based on unix like frameworks.
      • I talked with an apple rep after a Panther demo a couple of weeks ago, and Panther is going to include a set of Linux APIs.

        He didn't have much information about which ones, what it meant for running PPC Linux binaries, etc., but it'll be interesting to see what they're planning for it.

    • Re:One question... (Score:5, Insightful)

      by 47Ronin ( 39566 ) <(moc.ninor74) (ta) (nnelg)> on Tuesday August 19, 2003 @05:25PM (#6738614) Homepage
      It's not the architecture... The problem is that the directions for SlashCode are so complex that it turns off most people. It's 10 times easier to install GeekLog or MovableType on OSX because the instructions for the install are super-straightforward.

      • Re:One question... (Score:2, Interesting)

        by bcapps2012 ( 668378 )
        I'll tell you why it's important to me (and why I contributed Pudge's story in the first place). I am working to set up a Slashdot-site for use by the San Francisco Bay Area watershed [sfbayjv.org] and open space [openspacecouncil.org] community. This will be the discussion side of an on-line GIS system to track environmental restoration and creek protection projects.

        In addition, I will be setting up an archive to capture printed/digital publications, volunteer monitoring data, and project photographs. (Kinda like a SunSite, but not quite.) [berkeley.edu]

  • How about Win32? (Score:4, Interesting)

    by jpop32 ( 596022 ) on Tuesday August 19, 2003 @02:20PM (#6736143)
    Anyone managed that?

    I have an idea for a web site and I'd like to toy with it on my home machine (W2k), and if it turns out ok I'd go public (on Linux, naturally).

    • Re:How about Win32? (Score:5, Informative)

      by HaloZero ( 610207 ) <protodeka@gma3.1415926il.com minus pi> on Tuesday August 19, 2003 @02:28PM (#6736250) Homepage
      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.)
      • That's funny, I had the exact problem. I had all sorts of problems with serving on a Win2K machine but when I put the stuff on a linux server that I set up myself (first linux install, BTW) everything just worked.

      • Re:How about Win32? (Score:1, Informative)

        by Anonymous Coward
        Better yet, get one of the virtual machines (blochs, vmware,...) so you can run both at the same time. No rebooting needed!
      • Development and Production (public) environments, in my experience, are best when kept on the same platform.

        Not always. Developing on a different platform may mean:

        • Increased efficiency due to productivity tools not available on the target platform. This is particularly evident if your target platform is less powerful, and you can afford a much better development computer.
        • More bugs exposed due to subtle differences between platforms. Many of these are portability issues, but some will turn out to be
        • ncreased efficiency due to productivity tools not available on the target platform. This is particularly evident if your target platform is less powerful, and you can afford a much better development computer.

          Huh? [sourceforge.net].

          Oh, you said "May"... never mind...

      • develop it on Linux first, or stick with Win2K if/when you decide to go live with it.

        When (if) it goes live, I won't be the person administering the machine or taking care of it short of installing and configuring slashcode, and for that I also plan to enlist the help of some Linux wizards. Learning to do everything myself seems like too much overhead just for getting slashcode to run.

        I wouldn't even think of hosting the thing on Windows. To each his own (to Windows desktop, to Linux server). :-)

      • Re:How about Win32? (Score:3, Insightful)

        by laird ( 2705 )
        While it's a good idea to run the same hardware/OS in staging and production to minimize risks, there are many situations where mixed platforms make sense. For example, when deploying J2EE applications, most of the best IDE's are typically available for NT (let's not start a religious war, please), but you'd never want to run a production environment on NT. One of the nice things about J2EE is that in practice Java server applications really are quite portable between operating systems.

        And for non-Java app
      • Bit of a rant, I'm sorry, please bare with me.

        Certainly not. How dear you!
      • This is what I love about using Mac OS X -- I have the same environment on my laptop as on my server. Plus no freaking worms/viruses/hacker 3l33t
    • If you would be developing a site with the intention of going live on Linux, why not just install Linux in a separate partition and only have to go through installation headaches once?
      • If you would be developing a site with the intention of going live on Linux, why not just install Linux in a separate partition and only have to go through installation headaches once?

        Because I have 0 experience installing and administering Linuxes. And spending a month or so getting to know it just to find out that in the end the whole idea won't fly isn't appealing.

        But, I guess I'll have to get my feet wet, sooner of later...

  • Why didn't someone just ask MacSlash? (Score:5, Interesting)

    by mike_lynn ( 463952 ) on Tuesday August 19, 2003 @03:00PM (#6736600)
    They've been running Slashcode on an XServe for quite some time now, they even mention it here [macslash.org].
    Somehow I doubt it's taken this long to get Slashcode running on OS X. OS X tends to be semi-trivial to port to for non-hardware or assembly code dependant software.

    • Re:Why didn't someone just ask MacSlash? (Score:4, Insightful)

      by HebrewToYou ( 644998 ) on Tuesday August 19, 2003 @03:41PM (#6737164)
      Sometimes it's just rewarding to get things done by yourself. I remember when I was being taught some basic data structures in JAVA -- the professor told us that we can't use the util class because Sun had included these data structures. I didn't understand why we were being told to write code that already works perfectly well until I actually had to do it and fix all the annoying little bugs. I guess I'm trying to say that there are lessons in the process that are worth learning on your own.
    • Also, if you read this comment [slashdot.org] it looks like MacSlash wasn't too excited to help someone else get slash code going on Xserve :\

  • Great... (Score:5, Funny)

    by Anonymous Coward on Tuesday August 19, 2003 @03:50PM (#6737287)
    Now even Macs can suffer the most god-awful uncompliant HTML markup since people stopped using Microsoft Publisher to export web pages.

  • Not as trivial as you would think (Score:4, Interesting)

    by hexghost ( 444585 ) on Tuesday August 19, 2003 @04:49PM (#6738139) Homepage
    First, a little background: My company currently hosts cyberlodge.org, basically the first "open source" union. It currently runs on FreeBSD 4.8, and slashcode. We wanted to move it over to an xserve, for political and geek reasons. Suffice to say, its not a simple job getting Slashcode to run on OSX. Many of the perl modules don't build correctly. After about 3 weeks of reading everything on the web, emailing macslash (getting nothing back), chatting with pudge on irc, etc, we finally gave up. Guess i'll have to check it out again.
    • Yeah, let me know how it goes. :)

    • INSTALL NOTE: (Score:4, Informative)

      by hexghost ( 444585 ) on Wednesday August 20, 2003 @12:52PM (#6746280) Homepage
      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.

  • OS X Server only? (Score:4, Interesting)

    by piecewise ( 169377 ) on Tuesday August 19, 2003 @09:53PM (#6740557) Journal
    will this work only on OS X Server or can it work on OS X "Client"... 10.2.6?

    • Re:OS X Server only? (Score:4, Informative)

      by Hadlock ( 143607 ) on Wednesday August 20, 2003 @04:35AM (#6742140) Homepage Journal
      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.

  • I don't want to start a holy war here but (Score:4, Funny)

    by coolmacdude ( 640605 ) on Wednesday August 20, 2003 @12:03AM (#6741225) Homepage Journal
    what is the deal with you Slash fanatics? You sit at your machines and... Aw forget it, nevermind.

Slashdot Top Deals

Remember the good old days, when CPU was singular?

Close