obmtool kolab_bootstrap -b errors

[ComCept Net GmbH Soliva]

> Anyway I don't understand why but I was mentioned
> to change to precompiled binarys from zfos and using obmtool.

>> Using source from zfos is another idea.
>> Usually that beats the precompiled binaries.

>> You could also try the development packages.

>>> If I would install on Linux and the developer would use Bourneshell
>>> I would do this but in this way......!

> I did this
> but also there I have after giving the command kolab_bootstrap -b errors
> which I could not identify.

> MISSPKG: none
> MISSING: none
> SURPLUS: none
> SUMMARY: NODE=proteus; CMD=kolab; DATE=2004-08-04/20:50:08; HASX11=; DONE

>> Seems that the install went fine.

>>> Yes it seems so!


> ---------- /tmp/obmtool.log ----------
>
> chmod o+rx /kolab/etc/kolab

>> (Why is that necessary?) 

>>> It seems that there is a bug with the rights it means is written in the
>>>  Mailing list but anyway for me a detail to troubleshoot if all is
running.

> /kolab/etc/kolab/kolab_bootstrap -b
>
> ---------- /kolab/etc/kolab/kolab_bootstrap -b ----------
>
> KOLAB BOOTSTRAP
>
> Please enter Hostname [proteus]: proteus
> proceeding with Hostname proteus
> Please enter your Maildomain [proteus]: comcept.ch
> proceeding with Maildomain comcept.ch
> Generating default configuration:
>  base_dn : dc=proteus
>  bind_dn : cn=manager,dc=proteus
> Please choose a manager password [ypf4AMvBhbYZ.]: xxxxxxx
>  bind_pw : xxxxxxx
> done modifying /kolab/etc/kolab/kolab.conf
>
> IMPORTANT NOTE:
> use login=manager and passwd=pxxxxxxx when you log into the webinterface!

>>(You did not want to give us that password, did you?)

>>> Yes it is so!

> postmap: fatal: unsupported map type: dbm

>> This is the first error, it seems that dbm is not available 
>> on for postfix on your system. Maybe that is an openpkg bug?

>>> The dbm error is not the problem it means I could solve this but
>>> it seems also that this has something to do with the shell!?

> diff: illegal option -- q
> usage: diff [-bitw] [-c | -e | -f | -h | -n] file1 file2
>        diff [-bitw] [-C number] file1 file2
>        diff [-bitw] [-D string] file1 file2
>        diff [-bitw] [-c | -e | -f | -h | -n] [-l] [-r] [-s] [-S name]
> directory1 directory2

>> That seems to be the second problem.
>> You might want to grep for uses of "diff" in the scripts
>> and see if that is a kolab or a openpkg problem.

>>> Now this is a BIG Problem it means this is the case, the reason why 
>>> the overall installation is not running it means somebody made here
>>> a package with commands which will NOT run under solaris and put the
>>> script under a solaris package! Now I have a problem with the script
>>> because if this script will NOT run properly it is VERY dificult to
>>> troubleshoot it means what was done and what was NOT done?
>>> Actually if I started the server I saw that openldap and freebusy is
>>> not running properly. ProFTP is not finding the freebusy and can not
>>> connect to openldap and so on and so on.....You see what where my
>>> problem is. The people who has written this script should trouble-
>>> shoot it and rewrite it in BOURNESHELL and not some other shell like
>>> BASH. Yes of course on Linux BASH is commen but NOT on solaris.
>>> I have no chance to get running Kolab because if the beginning was
>>> not done properly through the script it is too complex to look what
>>> was now done through the script and what was not done...! Zfos.org
>>> could perhaps help me....perhaps the script needs prerequisits or
>>> what else.....I tried also to install from sunfreeware BASH but I
>>> had the same symptome.....What Now....!!!!!!

> Any Help will be really appriciated....and many thanks in advanced!

Andrea