• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

Trying to use Mac for proper work

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

    #11
    +1 for mamp

    Comment


      #12
      Originally posted by NickFitz View Post
      I think the locate database can be updated using the bash script at /usr/libexec/locate.updatedb (which appears to be part of the FreeBSD distribution judging by the copyright and comments). Of course it's always possible that some other way of doing it has also been added. There's a man page for it, available by typing man locate.updatedb in Terminal, or using your favourite GUI-based man page reader (I use ManOpen).
      Yes, locate.updatedb can be used, but starting with Leopard (or was it Tiger?), running it via sudo this spits out something like:
      "This WILL reveal all filenames on your machine to all login users, which is a security risk."

      and will probably leave the created file with no read access for non-admin users. If you really are the sole user of your system this may be what you want, but I don't currently do this myself.

      Instead of using periodic weekly, use

      sudo /etc/periodic/weekly/310.locate

      This will set the database ownership and protection correctly, but won't do the other weekly stuff like rotating logs.

      Here's a method for using Spotlight from the command line:
      1. put this into your .bash_profile

        function loc { mdfind "kMDItemDisplayName == '$@'wc"; }
        (should all be on one line)
      2. execute it via source .bash_profile
      3. see the results via loc my.cnf


      And as a GUI alternative to Spotlight, I use NotLight (scroll down or search that page to find it).
      Last edited by Sysman; 28 March 2010, 00:06.
      Behold the warranty -- the bold print giveth and the fine print taketh away.

      Comment


        #13
        I believe I fixed the issue with my.conf

        Durbs,

        You were able to get the my.conf files. You had about three of them, plus the one found on google.

        I used the default_my.conf file within the include directory, copied it to my desktop and renamed it to my.conf. I placed it in the proper folder /etc/
        and the I received the next error you received about the section on [mysqld] not being in the my.conf file.

        There is a section in the my.conf file called [mysqld.1], i renamed that section (renamed it when it was on my desktop) to [mysqld] and the setup of mysql workbench was complete.

        Comment


          #14
          Originally posted by stek View Post
          Best to download MAMP - there a free and paid for, both sort out MySQL without woes.

          MAMP: Mac, Apache, MySQL, PHP
          Nowadays there's also XAMPP. Free. Linux, OS X, Windows, Solaris versions available, which makes sense if you are running multiple platforms.

          I've only tried the Windows version myself, and it worked fine.
          Behold the warranty -- the bold print giveth and the fine print taketh away.

          Comment


            #15
            Originally posted by Sysman View Post
            Nowadays there's also XAMPP. Free. Linux, OS X, Windows, Solaris versions available, which makes sense if you are running multiple platforms.

            I've only tried the Windows version myself, and it worked fine.
            +1 for XAMPP, works fine on my macs.
            Also you can try the VM approach, but not the best approach on RAM starved laptop and 20 million row dataset.

            Comment

            Working...
            X