Topic: upgrading openssh

[Doug Nordwall]

can anyone see any problems with me simply upgrading the openssh rpms and not upgrading the openssh-e-smith rpm?

[zac]

yes, i can see large potential problems. for one, e-smith puts files in different places to standard redhat. the *-e-smith.rpm sets e-smith up to recognise that x program has been installed and tells e-smith how to deal with it (have i got that right?), so i'd wait for an 'official' update to be released. and is there any need to upgrade? i haven't had any problems with the current one....

zac

[Gordon Rowell]

zac wrote:
>
> yes, i can see large potential problems. for one, e-smith
> puts files in different places to standard redhat.

No we don't. We use templates to build the files in their
standard places - the _output_ of the template expansions are
in exactly the same places as you would expect on other RedHat
systems.

> the
> *-e-smith.rpm sets e-smith up to recognise that x program has
> been installed and tells e-smith how to deal with it (have i
> got that right?),

Roughly. The "management" RPMs (e-smith-*) provide templates and
action scripts - see www.e-smith.org for design documentation.

> so i'd wait for an 'official' update to be
> released. and is there any need to upgrade? i haven't had any
> problems with the current one....

Assuming that the later version puts all of the files in the
same place as the previous one and hasn't introduced new
mandatory keywords to the configuration file, you should be
able to upgrade the openssh* RPMs without changing anything
else. You should run "/sbin/e-smith/signal-event console-save"
to ensure that the configuration files are rebuilt from the
templates.

Gordon