Trace via installation
Pablo Iranzo Gómez
Pablo.Iranzo at redhat.com
Sat May 3 23:04:25 UTC 2008
On Sun, 4 May 2008, Yishai Hadas wrote:
> Hi All,
> I'm using RedHat enterprise 3.
> During installation from ISO one of the rpms that appears in comps.xml
> is not installed.
Is the group where it's listed into being specified on ks?
> When it's installed later manually from a command line all is OK (Except
> of signature warning)
The signature warning will always appear until you import the GPG
signing key, you can do so by running rpm --import
/usr/share/doc/rpm-*/RPM-GPG-KEY
> My questions:
>
> * Any idea how may it happen ?
>
> * Can I force post installation step in Ks.cfg to install this
> rpm ?
%post
rpm -Uvh --nodeps /mnt/source/RedHat/RPMS/package.rpm
>
> o It resides under the RedHat/RPMS/ library of the ISO
>
> * Can I force anaconda to ignore signatures warning ?
If the problem is anaconda complaining about the signature of
package during install (for your description before, I don't think that
its your case), you should retest package and ISO integrity.
> o I'm not sure that this is my problem
>
> * How can I turn on verbose trace to see warnings/errors via
> installation ?
You've the information on VT3 and VT4, as well as anaconda.log on
the installed system. If you're using %pre and %post scripts you can also
setup logging then copy the logs to target system in %post.
>
> * How can I know how to build the dependencylist of a given rpm
> ?
man rpm
rpm -q --requires package.rpm
> If there is a PDF or any other on line documentation about the
> installation process with anaconda I would be happy to get a URL to.
Check official documentation at:
http://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/
Regards
Pablo
More information about the Kickstart-list
mailing list