Harald Wagener wrote:
one more addition: The rpm database seems to be corrupt after the
installation completes (observed on the updated machine as well as a
fresh install done earlier for another machine, thought it to be a freak
error at the first time). I do a db_recover in /var/lib/rpm, which
deletes all __db.nnn files, and after that a 'rpm --rebuilddb' - after
that, all works (reasonably) well.
I didn't check if this is a problem with a pure redhat install, but
people might get stuck on this.
I have not noticed this in the many installs I have done.
(Most of them are network/NFS installs with my own kickstart config)
BTW - Doing a full kickstart install in text mode works fine even
if the disk is brand new/empty. (Non-interactive kickstart mode)
I keep wanting to take the time to respin an installer with our
packages in it but it has been just as simple to add in a kickstart
post-install script to install those things that are not part of
the distribution. (And install a new kernel, etc)
--
Michael Sinz -- Director, Systems Engineering -- Worldgate Communications
A master's secrets are only as good as
the master's ability to explain them to others.
|