On 2/23/19 7:54 PM, Dimitry Sibiryakov wrote:
23.02.2019 17:51, Paul Reeves wrote:
It is linked to the fact that rpm installs don't allow
interaction at install time, so the security database is not
initialised.
IIRC, rpm install 2.5 used to initialize security database using
random password for sysdba. Was it changed in 3.0?
Supporting of RPM in _our_ (i.e. SF) binaries became unreal. That's
first of all because no matter of the fact that all them have .rpm
extensions and even same internal format _content_ of RPMs for different
distro should be a bit different, and this difference does not get
smaller from year to year. We used to fix (but "hack" is more precise
word here) that using post-install script which in turn caused fatal
problems when trying to upgrade firebird using our .rpm.
That's why support of rpm's was dropped in FB3. Certainly various distro
provide binaries in rpm form but we (project) do not publish rpm's any
more. I.e. any question regarding ability to initialize security
database using random password should better be asked not here. On my
mind that should be possible. Moreover, it's done in a case of using
'-silent' switch in install.sh from .tar.gz binary package and when
doing 'make silent_install' when building from sources.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
