| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
On Dec 31, 2005, at 12:48 , John C. Welch wrote:
On 12/31/05 12:17, "webmaster" <email@hidden> wrote:
On Dec 31, 2005, at 11:44 , John C. Welch wrote:
On 12/31/05 11:16, "webmaster" <email@hidden> wrote:
On Dec 31, 2005, at 10:03 , John C. Welch wrote:
On 12/31/05 07:25, "Robert Dell" <email@hidden> wrote:
if somebody wants to run a dns server only, do it on a client. if somebody wants to run a web server only, do it on a client.
If you want kerberos, this is incorrect.
That's a load if you're now trying to convince me that kerberos isn't
available on client.
Only the client pieces. The KDC bits, and the integration with the other pieces are only a part of server. You CAN roll your own KDC, but by the time you're done, you'll have spent more in time than you would have with server.
What KDC bits are missing ???
kdcsetup, sso_util are the fast answers. You can work around them, but how
long does it take for your time to add up to $500 bucks?
if somebody wants to run a mail server only, do it on a client.
If you want an easy to maintain user database, this is incorrect.
Server software doesn't give you an easier to maintain database, it provides you with the same database.
Oh really? So you can show me the full Open Directory implementation for creating an OD domain and master that ships standard on client? I await your information eagerly.
What you're getting at is it doesn't give you the GUI tools to work with OD while management via CLI is awkward and cumbersome at best, but it's still the same database or are you claiming that OSX is the only OS to provide OD support and the thought that redhat or linux can use OD is just a passing fancy?
No, the client is actually missing pieces, among them slapconfig, NeST, (not
as important as it used to be, but still needed in many implementations),
serveradmin, . Open Directory is more than just OpenLDAP and some kerb
tools. I've also not found CL management of Open Directory to be any more
tedious than the GUI.
By the time you beat on OS X client to be able to duplicate Server sans the
server administrator tools, you're going to spend as much, if not more in
time than the cost of server just getting it ready to go.
Maybe your time is of little to no value to you, but I don't have time to
waste on proving that something can be done when there's no technical reason
to justify it. That's just ego and sysadmindick-waving, and I don't get paid
for that.
-- John C. Welch Writer/Analyst
-- Dale
_______________________________________________ Do not post admin requests to the list. They will be ignored. Macos-x-server mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/macos-x-server/email@hidden
| References: | |
| >Re: Yet Another Alternative (Re: OSX Server Pieces on Multiple Machines) (From: "John C. Welch" <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.