SLES10 vs OES2 - a planning question....
I hate to post something in a forum where it does not belong so please forgive me if I shouldn't have posted this here.
I am a long time Netware fan, but have moved all but one server over to OES1 Linux flavor and am getting ready to make another change...I think.
I currently use my lone OES1 Netware Server to hold my master partition for edir and for our main NSS File System. I would like to move totally to OES2 Linux or maybe just SLES 10. To my understanding, OES2 Linux flavor is just SLES10 with edir, nss, iprint, imanager, etc - the novell versions of things.
The questions:
1) If I move to SLES10, do I even need edir and NSS? (it's primary use is going to be a LAMP web server in a cluster environment) Right now I'm running one with OES1 linux and I use the NSS and eDir w/ LUM which I'm not sure if I really need. What are the advantages/disadvantages to this? Do I need eDir to manage this server, what do would I lose if I just went straight SLES10? How do I mass manage a cluster of SLES10 servers - ZFS? Will I need eDir then?
2) With respect to the filesystem, I'm finally comfortable with the Linux versions, but still feel tethered to NSS. I like NSS because it allows me to still manage my drives with eDir and still allows for the same old school drive mapping upon client login that I'm used to. Is there a better/newer way to use Linux for a main company filesystem (several terabytes connected to a fiber SAN with 10 or so drive mappings for every user)? Should I go with SLES10 with NSS and eDir bolted on top or just stay with OES2 Linux? Has NSS gotten better with OES2 than with OES1? Do I have to have NSS to map drives via the client login script to Linux servers?
Thanks for any advice from some seasoned SLES users.
-Steve
|
Threaded Mode
