Openldap and solaris 10

I'm trying to setup openldap 2.3.4 on Solaris 10. I've read the plethora of internet posting for Solaris 8 & 9 that claim to have a working ldap server, but little on Solaris 10. I've tried "everything" to get it work but to no avail. Can anyone point me to the minimum amount of documnets to get openldap working on Solaris 10.

Don't forget to:
1) add an nisDomainObject at the root DN
dn: dc=example,dc=com
objectclass: top
objectclass: organization
objectClass: nisDomainObject
nisDomain: example.com
objectclass: dcObject
o: Example Companies
dc: example
2) Add ACL in slapd.conf to allow reading of rootDSE.
access to dn.base="" by * read
A typical example for ACLs is shown below (note: add spaces before all the "by" lines, as indication of line continuations.
===
access to attrs=userPassword
by self write
by * auth
access to dn.base=""
by * read
access to dn.base="cn=Subschema" by * read
access to dn.subtree="ou=People,dc=example,dc=com"
by self write
by dn="cn=proxyagent,ou=profile,dc=example,dc=com" read
by users read
by anonymous auth
access to * by self write
by * read
===
Also I would like to make a qualification:
The "result.c" patch at
http://web.singnet.com.sg/~garyttt/result_c_patch.txt
IS MEANT for OpenLDAP version 2.2.XX, not 2.3.X, I haven't tried it on 2.3.X
But if it works, by all mean.
This patch existed since few years ago, but was never incorporated by OpenLDAP debvelopers, I am not sure if OpenLDAP developers will listen "in the name of InterOperability betwwen SUN and OpenLDAP products", and come out with an official patch in OpenLDAP 2.3.6 or later for rootDSE reading issue.
Assuming you use OpenLDAP 2.2.26 the latest stable release for 2.2.XX, and apply the "result.c" patch, after that you should be able to verify that it works using the following commands, prior to running "ldapclient -v init ...".
# cat chk_rootdse_openldap.sh
LDAP_ROOT=/usr/local
LD_LIBRARY_PATH=$LDAP_ROOT/lib:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH
echo "Testing LDAP Master..."
$LDAP_ROOT/bin/ldapsearch -h XXX.XXX.XXX.XXX -b "" -s base "(objectclass=*)" "+"
or
# cat chk_rootdse_solaris.sh
LDAP_ROOT=/usr/iplanet/ds5
LD_LIBRARY_PATH=$LDAP_ROOT/lib:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH
echo "Testing LDAP Master..."
$LDAP_ROOT/shared/bin/ldapsearch -h XXX.XXX.XXX.XXX -b "" -s base "(objectclass=*)" "+"
HTH.
Gary

Similar Messages

OpenLDAP and Solaris 10, I'm out of ideas

Hi All,
I have configured OpenLDAP sucessfully and set following results indicating that the user is loaded on the LDAP database
test5:/ $ cat /etc/passwd | grep admin777
test5:/ $ getent passwd admin777
admin777:x:5011:1000::/:/bin/bash
test5:/ $ id admin777
uid=5011(admin777) gid=1000(users) groups=1000(users)
test5:/ $ ldaplist -l passwd admin777
dn: uid=admin777,ou=People,dc=example,dc=com
shadowMin: 10
sn: sn
userPassword: {SSHA}Uy4yMkk71zNJ6XoAAhoKgjYPzXNnU4r5
loginShell: /bin/bash
uidNumber: 5011
gidNumber: 1000
shadowMax: 30
objectClass: inetOrgPerson
objectClass: posixAccount
objectClass: shadowAccount
uid: admin777
shadowLastChange: 15166
cn: cn
homeDirectory: /
shadowWarning: 7
test5:/ $
I've also added an overall security policy in the LDAP database
# Policies, example.com
dn: ou=Policies,dc=example,dc=com
pwdFailureCountInterval: 0
pwdMaxFailure: 3
pwdMustChange: TRUE
pwdAttribute: userPassword
pwdMinLength: 3
ou: Policies
pwdSafeModify: FALSE
pwdInHistory: 6
pwdGraceAuthNLimit: 0
pwdCheckQuality: 1
objectClass: top
objectClass: device
objectClass: pwdPolicy
pwdLockoutDuration: 1920
cn: default
pwdAllowUserChange: TRUE
pwdExpireWarning: 432000
pwdLockout: TRUE
pwdMaxAge: 7516800
But it seems that this policy is not activated, for example the pwdMinLength: is set to 3, but when the user changes his/her password, it seems that the Solaris policy takes over from the /etc/default/passwd file
test5:/ $ ssh [email protected]
* * * * * * * * * * * * W A R N I N G * * * * * * * * * * * * * *
THIS SYSTEM IS RESTRICTED TO AUTHORIZED USERS FOR AUTHORIZED USE
ONLY. UNAUTHORIZED ACCESS IS STRICTLY PROHIBITED AND MAY BE
PUNISHABLE UNDER THE COMPUTER FRAUD AND ABUSE ACT OR OTHER
APPLICABLE LAWS. IF NOT AUTHORIZED TO ACCESS THIS SYSTEM,
DISCONNECT NOW. BY CONTINUING, YOU CONSENT TO YOUR KEYSTROKES
AND DATA CONTENT BEING MONITORED. ALL PERSONS ARE HEREBY
NOTIFIED THAT THE USE OF THIS SYSTEM CONSTITUTES CONSENT
TO MONITORING AND AUDITING.
* * * * * * * * * * * * W A R N I N G * * * * * * * * * * * * *
Password:
Last login: Tue Jul 12 11:14:22 2011 from test5.example.
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
Sourcing //.profile-EIS.....
test5:/ $ id
uid=5011(admin777) gid=1000(users) groups=1000(users)
test5:/ $ passwd
passwd: Changing password for admin777
Enter existing login password:
New Password:
passwd: Password too short - must be at least 8 characters.
Please try again
New Password:
test5:/ $ cat /etc/default/passwd
#ident @(#)passwd.dfl 1.7 04/04/22 SMI
# Copyright 2004 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
MAXWEEKS=13
MINWEEKS=
PASSLENGTH=8
# NAMECHECK enables/disables login name checking.
# The default is to do login name checking.
# Specifying a value of NO will disable login name checking.
NAMECHECK=YES
It seems that the Solaris password policy forces the user to use the Solaris policy and ignore the LDAP ppolicy, below is my slapd.conf file
test5:/ $ cat /usr/local/etc/openldap/slapd.conf
# See slapd.conf(5) for details on configuration options.
# This file should NOT be world readable.
include /usr/local/etc/openldap/schema/core.schema
include /usr/local/etc/openldap/schema/cosine.schema
include /usr/local/etc/openldap/schema/inetorgperson.schema
include /usr/local/etc/openldap/schema/nis.schema
include /usr/local/etc/openldap/schema/ppolicy.schema
include /usr/local/etc/openldap/schema/DUAConfigProfile.schema
include /usr/local/etc/openldap/schema/solaris.schema
include /usr/local/etc/openldap/schema/java.schema
# Define global ACLs to disable default read access.
# Do not enable referrals until AFTER you have a working directory
# service AND an understanding of referrals.
#referral ldap://root.openldap.org
loglevel 256
pidfile /usr/local/var/run/slapd.pid
argsfile /usr/local/var/run/slapd.args
# Load dynamic backend modules:
modulepath /usr/local/libexec/openldap
moduleload ppolicy.la
# modulepath /usr/local/libexec/openldap
# moduleload back_bdb.la
# moduleload back_ldap.la
# moduleload back_ldbm.la
# moduleload back_passwd.la
# moduleload back_shell.la
# BDB database definitions
database bdb
suffix "dc=example,dc=com"
checkpoint 32 30
cachesize 10000
rootdn "cn=Manager,dc=example,dc=com"
# Cleartext passwords, especially for the rootdn, should
# be avoid. See slappasswd(8) and slapd.conf(5) for details.
# Use of strong authentication encouraged.
rootpw "{SSHA}6FWujVb4YNHJDyniwoWaHTMfXBJBM8u7"
# The database directory MUST exist prior to running slapd AND
# should only be accessible by the slapd and slap tools.
# Mode 700 recommended.
directory /usr/local/var/openldap-data
# Indices to maintain
index objectClass eq
index uid,uidNumber,gidNumber,shadowExpire,shadowLastChange eq
overlay ppolicy
ppolicy_default "cn=default,ou=Policies,dc=example,dc=com"
ppolicy_use_lockout
Edited by: King Rat on 12-Jul-2011 02:20
Edited by: King Rat on 12-Jul-2011 02:21

Hi there are you still working on this?
I'm also working on this. My setup is a little differant and I'm a little behind. I installed OpenLDAP server is installed on RHEL 5.5 and it is working with all the Linux servers, but Solaris 10 is giving me trouble. I see your using the ppolicy.schema I have not see this before I have been told to use the solaris.schema and the DUAConfigProfile.schema. It looks like you are using it with a overlay is this needed?
This is what my user account looks like.
dn: uid=user00,ou=People,dc=test,dc=net
uid: user00
cn: user00
objectClass: account
objectClass: posixAccount
objectClass: top
objectClass: shadowAccount
userPassword: {MD5}X03MO1qnZdYdgyfeuILPmQ==
shadowLastChange: 13048
shadowMax: 99999
shadowWarning: 7
loginShell: /bin/bash
uidNumber: 600
gidNumber: 500
homeDirectory: /home/user00
gecos: user00
Can you post the command you used to setup the client.
Example:
ldapclient init -a profileName=profile -a domainName=test.net 10.0.0.2
I also have these items and ACLs in the slapd.conf file.
# Allow LDAPv2 client connections. This is NOT the default.
allow bind_v2
access to attrs=shadowLastChange,userPassword
by self write
by * auth
access to *
by * read
Anyway I hope this helps and if you could help me with the client setup that would be great.

Problem with OpenLDAP and JNDI

I'm having problem working with OpenLDAP and JNDI.
First I have changed LDAP's slapd.conf file:
suffix          "dc=antipodes,dc=com"
rootdn          cn=Manager,dc=antipodes,dc=com
directory     "C:/Program Files/OpenLDAP/data"
rootpw          secret
schemacheck offthan i used code below, to create root context:
package test;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.naming.NameAlreadyBoundException;
import javax.naming.directory.*;
import java.util.*;
public class MakeRoot {
     final static String ldapServerName = "localhost";
     final static String rootdn = "cn=Manager,dc=antipodes,dc=com";
     final static String rootpass = "secret";
     final static String rootContext = "dc=antipodes,dc=com";
     public static void main( String[] args ) {
               // set up environment to access the server
               Properties env = new Properties();
               env.put( Context.INITIAL_CONTEXT_FACTORY,
                          "com.sun.jndi.ldap.LdapCtxFactory" );
               env.put( Context.PROVIDER_URL, "ldap://" + ldapServerName + "/" );
               env.put( Context.SECURITY_PRINCIPAL, rootdn );
               env.put( Context.SECURITY_CREDENTIALS, rootpass );
               try {
                         // obtain initial directory context using the environment
                         DirContext ctx = new InitialDirContext( env );
                         // now, create the root context, which is just a subcontext
                         // of this initial directory context.
                         ctx.createSubcontext( rootContext );
               } catch ( NameAlreadyBoundException nabe ) {
                         System.err.println( rootContext + " has already been bound!" );
               } catch ( Exception e ) {
                         System.err.println( e );
}this worked fine, I could see that by using "LDAP Browser/Editor".
and then I tried to create group with code:
package test;
import java.util.Hashtable;
import javax.naming.*;
import javax.naming.ldap.*;
import javax.naming.directory.*;
public class MakeGroup
     public static void main (String[] args)
          Hashtable env = new Hashtable();
          String adminName = "cn=Manager,dc=antipodes,dc=com";
          String adminPassword = "secret";
          String ldapURL = "ldap://127.0.0.1:389";
          String groupName = "CN=Evolution,OU=Research,DC=antipodes,DC=com";
          env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory");
          //set security credentials, note using simple cleartext authentication
          env.put(Context.SECURITY_AUTHENTICATION,"simple");
          env.put(Context.SECURITY_PRINCIPAL,adminName);
          env.put(Context.SECURITY_CREDENTIALS,adminPassword);
          //connect to my domain controller
          env.put(Context.PROVIDER_URL,ldapURL);
          try {
               // Create the initial directory context
               LdapContext ctx = new InitialLdapContext(env,null);
               // Create attributes to be associated with the new group
                    Attributes attrs = new BasicAttributes(true);
               attrs.put("objectClass","group");
               attrs.put("samAccountName","Evolution");
               attrs.put("cn","Evolution");
               attrs.put("description","Evolutionary Theorists");
               //group types from IAds.h
               int ADS_GROUP_TYPE_GLOBAL_GROUP = 0x0002;
               int ADS_GROUP_TYPE_DOMAIN_LOCAL_GROUP = 0x0004;
               int ADS_GROUP_TYPE_LOCAL_GROUP = 0x0004;
               int ADS_GROUP_TYPE_UNIVERSAL_GROUP = 0x0008;
               int ADS_GROUP_TYPE_SECURITY_ENABLED = 0x80000000;
               attrs.put("groupType",Integer.toString(ADS_GROUP_TYPE_UNIVERSAL_GROUP + ADS_GROUP_TYPE_SECURITY_ENABLED));
               // Create the context
               Context result = ctx.createSubcontext(groupName, attrs);
               System.out.println("Created group: " + groupName);
               ctx.close();
          catch (NamingException e) {
               System.err.println("Problem creating group: " + e);
}got the error code: Problem creating group: javax.naming.directory.InvalidAttributeIdentifierException: [LDAP: error code 17 - groupType: attribute type undefined]; remaining name 'CN=Evolution,OU=Research,DC=antipodes,DC=com'
I tried by creating organizational unit "ou=Research" from "LDAP Browser/Editor", and then running the same code -> same error.
also I have tried code for adding users:
package test;
import java.util.Hashtable;
import javax.naming.ldap.*;
import javax.naming.directory.*;
import javax.naming.*;
import javax.net.ssl.*;
import java.io.*;
public class MakeUser
     public static void main (String[] args)
          Hashtable env = new Hashtable();
          String adminName = "cn=Manager,dc=antipodes,dc=com";
          String adminPassword = "secret";
          String userName = "cn=Albert Einstein,ou=Research,dc=antipodes,dc=com";
          String groupName = "cn=All Research,ou=Research,dc=antipodes,dc=com";
          env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory");
          //set security credentials, note using simple cleartext authentication
          env.put(Context.SECURITY_AUTHENTICATION,"simple");
          env.put(Context.SECURITY_PRINCIPAL,adminName);
          env.put(Context.SECURITY_CREDENTIALS,adminPassword);
          //connect to my domain controller
          env.put(Context.PROVIDER_URL, "ldap://127.0.0.1:389");
          try {
               // Create the initial directory context
               LdapContext ctx = new InitialLdapContext(env,null);
               // Create attributes to be associated with the new user
                    Attributes attrs = new BasicAttributes(true);
               //These are the mandatory attributes for a user object
               //Note that Win2K3 will automagically create a random
               //samAccountName if it is not present. (Win2K does not)
               attrs.put("objectClass","user");
                    attrs.put("samAccountName","AlbertE");
               attrs.put("cn","Albert Einstein");
               //These are some optional (but useful) attributes
               attrs.put("giveName","Albert");
               attrs.put("sn","Einstein");
               attrs.put("displayName","Albert Einstein");
               attrs.put("description","Research Scientist");
                    attrs.put("userPrincipalName","[email protected]");
                    attrs.put("mail","[email protected]");
               attrs.put("telephoneNumber","999 123 4567");
               //some useful constants from lmaccess.h
               int UF_ACCOUNTDISABLE = 0x0002;
               int UF_PASSWD_NOTREQD = 0x0020;
               int UF_PASSWD_CANT_CHANGE = 0x0040;
               int UF_NORMAL_ACCOUNT = 0x0200;
               int UF_DONT_EXPIRE_PASSWD = 0x10000;
               int UF_PASSWORD_EXPIRED = 0x800000;
               //Note that you need to create the user object before you can
               //set the password. Therefore as the user is created with no
               //password, user AccountControl must be set to the following
               //otherwise the Win2K3 password filter will return error 53
               //unwilling to perform.
                    attrs.put("userAccountControl",Integer.toString(UF_NORMAL_ACCOUNT + UF_PASSWD_NOTREQD + UF_PASSWORD_EXPIRED+ UF_ACCOUNTDISABLE));
               // Create the context
               Context result = ctx.createSubcontext(userName, attrs);
               System.out.println("Created disabled account for: " + userName);
               //now that we've created the user object, we can set the
               //password and change the userAccountControl
               //and because password can only be set using SSL/TLS
               //lets use StartTLS
               StartTlsResponse tls = (StartTlsResponse)ctx.extendedOperation(new StartTlsRequest());
               tls.negotiate();
               //set password is a ldap modfy operation
               //and we'll update the userAccountControl
               //enabling the acount and force the user to update ther password
               //the first time they login
               ModificationItem[] mods = new ModificationItem[2];
               //Replace the "unicdodePwd" attribute with a new value
               //Password must be both Unicode and a quoted string
               String newQuotedPassword = "\"Password2000\"";
               byte[] newUnicodePassword = newQuotedPassword.getBytes("UTF-16LE");
               mods[0] = new ModificationItem(DirContext.REPLACE_ATTRIBUTE, new BasicAttribute("unicodePwd", newUnicodePassword));
               mods[1] = new ModificationItem(DirContext.REPLACE_ATTRIBUTE, new BasicAttribute("userAccountControl",Integer.toString(UF_NORMAL_ACCOUNT + UF_PASSWORD_EXPIRED)));
               // Perform the update
               ctx.modifyAttributes(userName, mods);
               System.out.println("Set password & updated userccountControl");
               //now add the user to a group.
                    try     {
                         ModificationItem member[] = new ModificationItem[1];
                         member[0]= new ModificationItem(DirContext.ADD_ATTRIBUTE, new BasicAttribute("member", userName));
                         ctx.modifyAttributes(groupName,member);
                         System.out.println("Added user to group: " + groupName);
                    catch (NamingException e) {
                          System.err.println("Problem adding user to group: " + e);
               //Could have put tls.close() prior to the group modification
               //but it seems to screw up the connection or context ?
               tls.close();
               ctx.close();
               System.out.println("Successfully created User: " + userName);
          catch (NamingException e) {
               System.err.println("Problem creating object: " + e);
          catch (IOException e) {
               System.err.println("Problem creating object: " + e);               }
}same error.
I haven't done any chages to any schema manually.
I know I'm missing something crucial but have no idea what. I have tried many other code from tutorials from net, but they are all very similar and throwing the same error I showed above.
thanks in advance for help.

I've solved this.
The problem was that all codes were using classes from Microsoft Active Directory, and they are not supported in OpenLDAP (microsoft.schema in OpenLDAP is just for info). Due to this some fields are not the same in equivalent classes ("user" and "person").
so partial code for creating user in root would be:
import java.util.Hashtable;
import javax.naming.ldap.*;
import javax.naming.directory.*;
import javax.naming.*;
import javax.net.ssl.*;
import java.io.*;
public class MakeUser
     public static void main (String[] args)
          Hashtable env = new Hashtable();
          String adminName = "cn=Manager,dc=antipodes,dc=com";
          String adminPassword = "secret";
          String userName = "cn=Albert Einstein,ou=newgroup,dc=antipodes,dc=com";
          env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory");
          //set security credentials, note using simple cleartext authentication
          env.put(Context.SECURITY_AUTHENTICATION,"simple");
          env.put(Context.SECURITY_PRINCIPAL,adminName);
          env.put(Context.SECURITY_CREDENTIALS,adminPassword);
          //connect to my domain controller
          env.put(Context.PROVIDER_URL, "ldap://127.0.0.1:389");
          try {
               // Create the initial directory context
               LdapContext ctx = new InitialLdapContext(env,null);
               // Create attributes to be associated with the new user
                    Attributes attrs = new BasicAttributes(true);
                              attrs.put("objectClass","user");
               attrs.put("cn","Albert Einstein");
               attrs.put("userPassword","Nale");
               attrs.put("sn","Einstein");
               attrs.put("description","Research Scientist");
               attrs.put("telephoneNumber","999 123 4567");
               // Create the context
               Context result = ctx.createSubcontext(userName, attrs);
               System.out.println("Successfully created User: " + userName);
          catch (NamingException e) {
               System.err.println("Problem creating object: " + e);
}hope this will help anyone.

Vista and Solaris 10, are they compatible?

I have attempted to follow dual boot guides found everywhere, but none tailor specifically to (or eve mention) Vista. This is a problem, because Vista does not use the same method of boot as previous versions of NT.
So far, in my many failed attempts at creating a Vista dual boot, I have experienced this:
When I install Solaris 10 on any partition (Solaris installs correctly and works great), and then attempt to install Windows Vista, Vista says all of my partitions do not meet its requirements for installation (that the drive is NTFS and at least 12 GB is all it tells me). Even after formatting, deleting, recreating, and reformatting a drive, the drive is still unusable. Only after deleting ALL drives, including Solaris 10, and recreating and brand new first partition does Vista allow me to install. If I create a partition that Vista allows me to use, and also a partition to use with Solaris, and THEN install Solaris, the partition that Vista liked can no longer be used!
When I install Windows Vista first (and it works fine) (which is what I tried first and reasoned is what I should be doing), and then install Solaris 10 on a partition (it installs correctlt and works great), I load up my computer and go into the GRUB bootloader. I can select Windows. However, when attempting to load windows, I get an error (in the Vista font by the way) that says my operating system cannot be loaded. When I load my Vista install disc, it cannot find any installations of windows, and it cannot repair the master boot record, saying something like the filesystem is corrupt. However, just as an experiment, I loaded Vista onto the former Solaris drive, and looked at my first partition. Every file was there, intact.
I have attempted this with Windows Home Premium 32 bit, Windows Business 32 bit, and Vista Ultimate x64. I don't want to believe that it's impossible to load Vista and Solaris simultaneously, I've seen as much stating its impossibility as I've seen documents telling me how to do it (<- cold irony).
As long as I can get AN INSTALLATION of Solaris 10 on my machine at the same time I have Vista able to boot, I'm fine, but I seem to have lost on all fronts.
Edited by: ZetaZeta on Sep 19, 2007 12:30 AM

In Solaris Express, this is not an issue, according to this weblog:
http://blogs.sun.com/moinakg/entry/solaris_vista_dual_boot_conclusion
For versions of Solaris Express prior to buid 70, this method was described for creating a dual-boot with the oh-too-picky Windows Vista:
http://linux.wordpress.com/2007/02/17/vista-and-solaris-express-dual-boot/
I am going to assume that setting up a dual-boot with Solaris 10 is similar to, if not the same as, Solaris Express, since the only steps specific to Solaris are the files I copy from Solaris.
I hope this helps anyone else with a problem similar to mine.

Windows Vista and Solaris...10...install failed...help.

Hi everyone!!
i installed Solaris OS twice on my system
i have vista previously on this...
i made a partition for sol...
after installation solaris boots fine
but windows is totally corrupted and doestn boot normally
ill have to erase the whole computers HD and then reinstall it again
both the OSs are not working at the same time
with solaris already installed if i try to repair or re install windows vista its erasing solaris partition totally
please help!!! what should i do to get my system running with both OS s.
any replies.....much awaited
thank u so much in advance....
-sriya
Message was edited by:
Sriya
i have dell inspiron...just delivered yday...640m
Message was edited by:
Sriya

Install Windows first, then Solaris {not the other way round}. When Solaris installer detects Windows installation and prompts you whether to preserve Windows partition, make sure to select 'preserve' option. I believe Solaris installer creates appropriate GRUB entries for Windows and Solaris. Even if it doesn't, you can always edit the GRUB menu after the installation is complete.
Check the following web site if you need detailed instructions:
http://multiboot.solaris-x86.org/index.html

How do I install dual-boot Solaris 8 and Solaris 9 on one hard disk ?

I tried to install Solaris 8 and Solaris 9 on same disk using CDs, but
the second installation overwrote the first Solaris which was installed
previoudly on the half-disk size partition of same disk.
How do I install two Solarises on one hard disk ?
Thanks
Yakov

There are no tricks to get Solaris to dual boot on the same drive. Just allocate and pick the free slices not used by the first Solaris install when you put in the second install. Technically speaking there is nothing preventing you from running seven separately bootable Solaris instances on the same drive (one of 8 available slices is overlap -- slice 2) provided you use a swap file on a root partition instead of reserving a whole slice for swap.

Dual boot windows 7 and solaris 11

Hi Friends,
Could some one please explain the steps to install dual boot windows 7 and solaris 11?
Thanks
Raja

Install Windows leaving a partition for Solaris. Install Solaris into the empty partition. Reboot. Use a partition manager if you need to shrink your current Windows Partition. GParted works great and is free.
alan

Dual Boot Windows 7 and solaris 10

Can some body guide me how to dual boot windows 7 and solaris 10?
Thanks

First partition your harddisk with at least 2 primary partitions, one for windows and the other for solaris if you only have one harddisk. It would be a good idea to create an additional small boot partition as the first partition as well if you intend on using an independent boot loader but it really depends on what your machine is capable of. For example, if you have multiple harddisk and your BIOS supports it, then you could just install each OS onto its own harddisk and use the BIOS function to disable/boot off specific harddisk. Otherwise, if you only have one harddisk and created multiple partitions, install windows7 first followed by solaris10, obviously installing into different partitions. If you have created a boot partition, then you can install the boot loader into that dedicated partition.

Dual Booting Windows and Solaris

Hi
how do i dual boot windows and solaris
Do i install windows first and then solaris or do it the other way around..?
how do i make sure that Windows and Solaris appear in my boot options..?
Is their a guide on doing this...?
Thanks
Liam

Hey I did a quick google search for you. So I havent tried this method myself but it sounds reasonable.
The text below is from the following link:
http://www.hccfl.edu/pollock/AUnix1/DualBoot.htm
"Solaris boot loader
Partition the drive to leave at least 2GB of space available for Solaris;
more drive space is desirable.
As with Linux, install Windows first then Solaris.
Do not use the Installation CD but boot and install
from Software CD 1.
If you accept the default partitioning scheme which
the installer provides you will soon run out of space in
your / and /usr partitions since only enough space is
allocated to install the system.
All extra space is allocated to /export/home.
A typical installation on a 4.5GB partition might look
something like this:
Filesystem Size Used Avail Use% Mounted on
/dev/dsk/c0d0s0 900M 536M 310M 64% /
/dev/dsk/c0d0s1 334M 109M 192M 36% /var
swap 671M 8.0k 671M 1% /var/run
swap 671M 8.0k 671M 1% /tmp
/dev/dsk/c0d0s5 845M 222M 565M 29% /opt
# (FAT32 partition):
/dev/dsk/c0d0p0:1 5.0G 3.3G 1.6G 66% /c
/dev/dsk/c0d0s7 1.1G 92M 954M 9% /export/home
/dev/dsk/c0d0s4 752M 225M 474M 33% /usr/local
The Solaris boot selector enables you to choose either
Solaris or Windows with Solaris as the default.
(I prefer grub or lilo!)
To mount FAT under Solaris:
# mount -F pcfs /dev/dsk/c0d0p0:c /dos (or �:1�?)
And the vfstab file:
/dev/dsk/c0d0p0:c - /dos pcfs - yes -
To create a GRUB boot floppy, follow these steps:
$ mkfs -t ext2 /dev/fd0
$ mount /dev/fd0 /mnt/fd0
$ mkdir /mnt/fd0/boot /mnt/fd0/boot/grub
$ cp /boot/grub/stage[12] /boot/grub/grub.conf \
> /mnt/fd0/boot/grub
$ /sbin/grub --batch <
Hope this helps!
/Oscar

Compiler directives to differetiate between solaris 9 and solaris 10

i have an API which makes certain function calls which are different for solaris 9 and solaris 10. i cannot add my own defines, since that would mean that applications too would have to define them.
does the Sun Workshop compiler provide any default directives to differentiate between solaris 9 and solaris 10? something like #ifdef __SunOS_5.10 or something like that?
thanks.

As explained in the C Users Guide, the compiler predefines several macros, one of which is represents the Solaris version number.
The macro name is derived from the output of the commands
uname -s and uname -r, starting with __, connected by _, and with dots replaced by _.
Running on Solaris 9:
% uname -s
SunOS
% uname -r
5.9
The defined macro name is __SunOS_5_9
On Solaris 10 you get __SunOS_5_10
__SunOS_5_9

SSH Differences between Solaris 9 and Solaris 10

I use public key authentication when connecting via SSH but have noticed a difference between Solaris 9 and Solaris 10 and wondered if it's an environment setup issue. I keep my keys in $HOME/.ssh
When connecting from Solaris 9 I can provide an identity file without a path regardless of the directory that I'm in e.g.
ssh -i my_identity_file user@hostnameThe above works even if I'm not in the $HOME/.ssh directory. But when using the same from Solaris 10 I get the following error:
Warning: Identity file my_identity_file does not exist.If I run the command from $HOME/.ssh on Solaris 10 it connects fine, and if I pass in the path like so it works fine:
ssh -i $HOME/.ssh/my_identity_file user@hostnameIs there a setting specific to SSH somewhere as I can't see anything in my environment that's different between the two systems. There's certainly no entry in $PATH that points to $HOME/.ssh. How could I get SSH to work on Solaris 10 by just providing the identity file name and not the full path
Regards
Rich

It's not explicitly defined in /etc/ssh/ssh_config, so I'm assuming it would be using the default which is ~/.ssh/id_dsa.
But surely that's irrelevant if I'm using the -i switch to provide the identity file?
Remember the problem here is that I have to provide a full path to the identity file, whereas before just the filename would do.
Rich

Function-Based Indexes (FBI) on Linux and Solaris

I have a question about FBI on different systems (Linux and Solaris).
---- Oracle on Linux -----
SQL> CREATE TABLE T_DUMMY(NAME VARCHAR(20));
Table created.
SQL> CREATE INDEX T_DUMMY_IDX ON T_DUMMY(UPPER(NAME));
Index created.
However, when I do the same on the Oracle running on Solaris, I get the following error:
---- Oracle on Solaris -----
SQL> CREATE TABLE T_DUMMY(NAME VARCHAR(20));
Table created.
SQL> CREATE INDEX T_DUMMY_IDX ON T_DUMMY(UPPER(NAME));
CREATE INDEX T_DUMMY_IDX ON T_DUMMY(UPPER(NAME))
ERROR at line 1:
ORA-01031: insufficient privileges
I know that I have to add "QUERY REWRITE" in order to create a FBI. However, why Oracle on Linux behave differently. Would it be any difference/problem if I do NOT add "QUERY REWRITE" for Oracle on Linux (For example, would the EXPLAIN PLAN different)?

general user settings are the same (privilege, role) Well, the specific settings must be different. I would check to see whether one of the roles has been granted the QUERY REWRITE system privilege on your Linux instance but not on Solaris.
Cheers, APC

Running Solaris 8 and Solaris 10 on a SPARC box at the same time

I know that this is not possible, but still... need to clear it out from the experts...
Have a upgrade request of Solaris 8 to Solaris 10. However, Solaris 8 environment should not be disturbed. How can this be done without going for another SPARC box?
Can I have both Solaris 8 and Solaris 10 running concurrently on the same SPARC box?
Thanks in advance.

Have a upgrade request of Solaris 8 to Solaris 10.
However, Solaris 8 environment should not be
disturbed. How can this be done without going for
another SPARC box?
Can I have both Solaris 8 and Solaris 10 running
concurrently on the same SPARC box?You can add a second boot disk and use Sun's Live Update to install the upgrade on the second boot disk. Boot from either, though you can't run both simultaneously.

Defferent work usleep in Solaris 10 and Solaris 9

I've compile program in Solaris 9 and Solaris 10(cc or gcc).
On Solaris 9 cpu load is lower then 1 %.
On Solaris 10 cpu load is more then 16%.
Why I have this big difference. 16% is very big for me.

I presume you compiled php on the Sun server, was this done using gcc or the Sun One C compiler.
If the latter then you can also use the flag: --enable-nonportable-atomics when you run configure

How to restart services in windows and solaris environment?

I need to start services running in windows and solaris platforms with java code. I have a fair idea how to do in C++ . So wondering if same can be done with java. .. Please help me out!
Thanx

you may also like to look at the wrapper project on source forge. It lets you set up services under any O/S with full control of the JVM that is running.
Btw my previous answer only helps you under MS, didn't notice that you wished to know how to do it under unix. If its a non-java service, you will need to determine what platform your on and then perform the appropriate action.

Openldap and solaris 10

Similar Messages

Maybe you are looking for