If possible, would you consider buying OS X for a non Mac computer? Post: 302286734

Sponsored Content

The Lounge What is on Your Mind? If possible, would you consider buying OS X for a non Mac computer? Post 302286734 by tlarkin on Wednesday 11th of February 2009 11:03:10 PM

02-12-2009

Registered User

Quote:

Originally Posted by Neo

Yes, I agree. Just because OS X has a amazing GUI does not mean you cannot use the command line if you desire.

On the other hand, most users will be happy with the GUI as a desktop model.

More than likely I would not choose OS X as a remote server as I do agree most packages for OS X are designed for GUI installation.

PS: I recently installed LAMP for OS X, called MAMP, and it was the easiest LAMP/MAMP install I have ever seen.

Neo, I used to admin a bunch of Windows and Novell servers at my old job. 80 servers, 10,000 PC windows clients, maybe 300 Macs. I did all the Mac work with one other guy and then did some PC work.

Now at my new job I have 30+ Xserves running 10.5.5 Server, and 6,700 Mac clients all in a pure open directory environment. I use a third party suite called Casper from Jamf Software.

I can tell you from my experience that package deployment is not only easy, it is way customizable and there are so many things I can do with it. Very very robust products. I can push out an application to all my clients with in a day if I really wanted to from my office. I can send them jobs to netboot and automatically reimage, from my office across the WAN.

Apple is lacking a few things here and there but really to be honest it is some of the best things I have worked with, when it works. I don't mean to say they don't work but I have definitely had my isues. 10.5.3 was a giant heap of dung and so was Work Group Manager 10.5.3 I wanted to thunder kick all my Mac servers at that point in time.

If you are going to run Web servers I would say Linux all the way, but if you want a file server, home directories, open directory, DHCP, or any other service you can run on a sever OS X Server isn't that bad.

My main comment from before was suppose to be, you can do everything from the command line or the GUI, you have a choice, which no Linux or Unix distro really has accomplished yet. Maybe Ubuntu has come close, but I can't compare the end user experience to that of a Mac.

I intalled TomCat, PHP 5 and MySQL on one of my servers through an installer package and it took all of 3 minutes to do so. Then configured it through the GUI. I just now need to brush up on my mysql command line abilities and I will be set.

Just saying is all.

tlarkin

View Public Profile for tlarkin

Find all posts by tlarkin

2 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Urgent help with web design problems - mac, safari and unix computer

Hi (Help, Help, Help) I am on a computer course and have designed a web site as one of my assignments. just before Xmas my college tutor "very kindly" viewed my site with a mac, safari browser and unix operating system computer. This is what she Emailed back to me, and I am trying to sort...

2. Shell Programming and Scripting

My code worked on a Mac, now it does not work in another computer

I guess Mac has default bash. Then I copy my code to another comp and run it...And it gives me an error like "bad substitution".... How I can change my code??? Never had before this kind of situation. Help please. if then n=$(sort /Users/Natalie/lastserial | tail -1) ...

LEARN ABOUT OSX

cpmac

CPMAC(1)						    BSD General Commands Manual 						  CPMAC(1)

NAME

     /usr/bin/CpMac -- copy files preserving metadata and forks

SYNOPSIS

     /usr/bin/CpMac [-rp] [-mac] source target
     /usr/bin/CpMac [-rp] [-mac] source ... directory

DESCRIPTION

     In its first form, the /usr/bin/CpMac utility copies the contents of the file named by the source operand to the destination path named by
     the target operand.  This form is assumed when the last operand does not name an already existing directory.

     In its second form, /usr/bin/CpMac copies each file named by a source operand to a destination directory named by the directory operand.  The
     destination path for each operand is the pathname produced by the concatenation of the last operand, a slash, and the final pathname compo-
     nent of the named file.

     The following options are available:

     -r    If source designates a directory, /usr/bin/CpMac copies the directory and the entire subtree connected at that point.  This option also
	   causes symbolic links to be copied, rather than indirected through, and for /usr/bin/CpMac to create special files rather than copying
	   them as normal files.  Created directories have the same mode as the corresponding source directory, unmodified by the process' umask.

     -p    Causes /usr/bin/CpMac to preserve in the copy as many of the modification time, access time, file flags, file mode, user ID, and group
	   ID as allowed by permissions.

     -mac  Allows use of HFS-style paths for both source and target.  Path elements must be separated by colons, and the path must begin with a
	   volume name or a colon (to designate current directory).

NOTES

     The /usr/bin/CpMac command does not support the same options as the POSIX cp command, and is much less flexible in its operands.  It cannot
     be used as a direct substitute for cp in scripts.

     As of Mac OS X 10.4, the cp command preserves metadata and resource forks of files on Extended HFS volumes, so it can be used in place of
     CpMac.  The /usr/bin/CpMac command will be deprecated in future versions of Mac OS X.

SEE ALSO

     cp(1) MvMac(1)

Mac OS X							  April 12, 2004							  Mac OS X