Sponsored Content
The Lounge What is on Your Mind? Which OS is better for software development ? Post 302548194 by Scott on Wednesday 17th of August 2011 05:12:58 PM
Old 08-17-2011
I think the answer is in the question!

Windows is the best OS for Windows development, as Solaris is for Solaris development, etc. If you're working cross-platform, then the OS is somewhat irrelevant to the question.

Sorry to say that I can't see any outcome to this thread that might not result in it being closed at some point (rule #8), so I will save anyone the trouble, and close it now.
 

2 More Discussions You Might Find Interesting

1. What is on Your Mind?

Thinking of career change to software development

I'm currently administering applications and unix OS. Have no IT degree, learned on the job over last 6-7 years. Have good shell scripting skills, basic perl, know some apache, mysql, sql etc. I enjoy scripting, setting up scripts to use in conjunction with databases and apache etc. I think... (3 Replies)
Discussion started by: frustrated1
3 Replies

2. What is on Your Mind?

Back to Cyber Situational Awareness Software Development

After mulling over self-publishing a cyberspace situational awareness mini-series starting with a short book on human cyber consciousness, I think it is best I delay writing a book and focus on software development. The general idea of human cyber consciousness is indirectly discussed in this... (0 Replies)
Discussion started by: Neo
0 Replies
ad(5)							Standards, Environments, and Macros						     ad(5)

NAME
ad - Active Directory as a naming repository DESCRIPTION
Solaris clients can obtain naming information from Active Directory (AD) servers. The Solaris system must first join an AD domain and then add the ad keyword to the appropriate entries in the nsswitch.conf(4) file. The Solaris system joins the AD domain by using the kclient(1M) utility. The AD name service only supports the naming databases for passwd and group. Windows users are not able to log in. The user_attr(4) database has no entries for Windows users, and the passwd(1) command does not sup- port the synchronization of user passwords with AD. The Solaris AD client uses auto-discovery techniques to find AD directory servers, such as domain controllers and global catalog servers. The client also uses the LDAP v3 protocol to access naming information from AD servers. The AD server schema requires no modification because the AD client works with native AD schema. The Solaris AD client uses the idmap(1M) service to map between Windows security identi- fiers (SIDs) and Solaris user identifiers (UIDs) and group identifiers (GIDs). User names and group names are taken from the sAMAccountName attribute of the AD user and group objects and then tagged with the domain where the objects reside. The domain name is separated from the user name or group name by the @ character. The client uses the SASL/GSSAPI/KRB5 security model. The kclient utility is used to join the client to AD. During the join operation, kclient configures Kerberos v5 on the client. See kclient(1M). FILES
/etc/nsswitch.conf Configuration file for the name-service switch. /etc/nsswitch.ad Sample configuration file for the name-service switch configured with ad, dns and files. /usr/lib/nss_ad.so.1 Name service switch module for AD. SEE ALSO
passwd(1), svcs(1), idmap(1M), idmapd(1M), kclient(1M), svcadm(1M), svccfg(1M), svccfg(1M), nsswitch.conf(4), user_attr(4), smf(5) SunOS 5.11 22 Oct 2008 ad(5)
All times are GMT -4. The time now is 06:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy