>>> On 8/26/2011 at 01:46 PM, in message <[email protected]>, Mark Post <[email protected]> wrote: > The eDirectory product is only available on Netware (as you have now) and > Open Enterprise Server (OES) running on SLES on Intel/AMD systems. If you're > going to be running OES for eDirectory, you might as well use the other parts > of OES on that system, which include the various file server functions that > people are used to from Netware. I believe this does involve Samba, but I'm > not all that familiar with OES.
My knowledge is a bit rusty on this but let me clarify a few things. eDirectory is a standalone product althought it is included in many Novell products like OES. eDirectory can run on a number of OSes like Linux, Solaris, AIX and Windows and is an LDAP based directory. eDirectory only runs on Linux on x86/x86_64 based systems. One option is that you could keep the Netware around and connect Samba via LDAP. eDirectory on Netware 5 is old and that might cause problems. A better option would be to get eDirectory installed on Linux, join the directory tree on the Netware server so it can become a replica, and then promote the directory on the Linux box so the Netware server could be turned off. Not that I want to see a Netware box get turned off but maybe the organization is more comfortable with Linux. A couple of ideas for you to contemplate.... Mike ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
