> If you do go with ifolder, please document how you do it. Because a year or > two ago, I tried it... I was met with utter failure (it's so darn complex) > ... it wants to build only on suse... The only way I got it up was to build > a complete directory service on OES and do it the way Novell was intending > it to be done... I liked it, but man oh man, it was a big deal.
Yes. it's a bear. It requires the mono framework. Your best bet is to use stock Opensuse. (I can't remember if it likes Opensuse 11.3 or 11.4 best.) But those either come with mono, or have a repo you can add for mono. I got it running outside of OES, but i was not using ldap auth in that build. That said, i do have the OES version up and running and it's been pretty solid, although, we only have about 4 users on the system. The problem with ifolder from Novell was that it was really a competing product and mind change from their traditional client/mapped drive modus operandi. iFolder in no way integrated with the existing infrastructure that Novell customers had. So to use ifolder requires one to completely switch how they operate. On it's own, i think it's a great concept and a great utility, but it is a tough uphill battle to change any organizations operations that have been in place for decades. also, when it originally came out, the data stored on disk was encrypted, which was great, but meant that if I needed to restore a file, i had to restore the whole folder and let the user find the file. It wasn't nice. that said, i don't have any info on how ifolder actually operates in a full scale implementation. Use at home and a few folks at work is all i've seen and it works ok for me. bb _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
