Quote:
Originally Posted by djames4242 
Looks like, by simplifying (and eliminating redundancy in some of) the configuration panels, Apple is preparing for the Server edition to be adopted by a much wider audience.
As for the near-elimination of FTP and NFS server protocols, FTP is rarely used anymore (at least not without SSH/SFTP), and any pure Unix shops utilizing NFS are almost certainly using Solaris (or another flavor of Unix) for file serving. As long as OSX still supports these protocols as a client, this should mostly be a non-issue.

Looks like, by simplifying (and eliminating redundancy in some of) the configuration panels, Apple is preparing for the Server edition to be adopted by a much wider audience.
As for the near-elimination of FTP and NFS server protocols, FTP is rarely used anymore (at least not without SSH/SFTP), and any pure Unix shops utilizing NFS are almost certainly using Solaris (or another flavor of Unix) for file serving. As long as OSX still supports these protocols as a client, this should mostly be a non-issue.
BUT, the decision may keep some people (e.g., in small businesses) from simplifying a complex unix network by (kicking out e.g., Sun, and) providing the server functionality from MacOSX (referring to NFS here).
On the other hand, I vigorously applaud Apple's decision to provide MacOSX Server functionality for anyone, because there are many households with several Macs, and it would certainly make the greater public aware of and knowledgeable about MacOSX as a server.
Previously, the step to a dedicated MacOSX Server in the home was too big, for 2 reasons (both of which are being dealt with, so it seems):-
(i) more expensive (It wouldn't hurt though having to pay for MacOSX Server licenses >x clients, gradually increasing e.g., for x^2 clients, for x^3 clients, etc..., with x=5 or 10);
(ii) more difficult to manage (Well-done, Apple, for simplifying OSX Server administration)





-- "We Don't Support 3rd Party Products, contact your IT Department