From: Armen Kaleshian <akaleshian@kriation.com>
To: "Anna G. Zapata" <azapata@du.edu>
Cc: linux-newbie@vger.kernel.org
Subject: Re: upgrading open ssh
Date: Mon, 23 Feb 2004 17:52:59 -0500 [thread overview]
Message-ID: <20040223225259.GA11316@sevoog.kriation.com> (raw)
In-Reply-To: <HBEJLOFMLEPBMAAEFNFDMECJCFAA.azapata@du.edu>
Piece of cake. ;-)
rpm -e <the name of the package>
You might run into some dependency issues, and if you get stuck into a loop,
just use the --nodeps switch to remove a package that's causing the loop.
As long as you're just removing the openssh-* packages, you'll be all set to use
the one compiled from source.
Let me know if you need anything else.
--Armen
On Mon, Feb 23, 2004 at 03:03:36PM -0700, Anna G. Zapata wrote:
: Armen,
:
: How do I go about removing the rpm version?
:
: Thanks for all your help.
:
: Anna
:
: -----Original Message-----
: From: Armen Kaleshian [mailto:akaleshian@kriation.com]
: Sent: Monday, February 23, 2004 2:31 PM
: To: Anna G. Zapata
: Cc: linux-newbie@vger.kernel.org
: Subject: Re: upgrading open ssh
:
:
: Anna..
:
: Since you were using an rpm version of SSH before, and now you've converted to a
: source package, it might be a little more difficult to stay consistant.
:
: On my system, I removed the rpm version and replace it with the source version,
: by compiling and installing it the way you did.
:
: I suggest removing the rpm package of SSH that you have, and then simply just
: run make install on the SSH source directory you have, and that way, you're
: guaranteed to run the version you're expecting.
:
: Good Luck!
:
: --Armen
:
:
: On Mon, Feb 23, 2004 at 02:12:15PM -0700, Anna G. Zapata wrote:
: : Hi all,
: :
: : I downloaded and installed the latest version of open ssh. I was running openssh-3.6.1p2-19 on a Fedora box.
: However,
: : how do I know that the new install took and that the old open ssh has been done away with? I did the ./configure,
: make,
: : and make install, but I think I'm missing some steps.
: :
: : Thank you as always.
: :
: : Anna Zapata
: : UTS - Network Security
: : 303.871.2009
: :
: :
: : -
: : To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
: : the body of a message to majordomo@vger.kernel.org
: : More majordomo info at http://vger.kernel.org/majordomo-info.html
: : Please read the FAQ at http://www.linux-learn.org/faqs
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2004-02-23 22:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 21:12 upgrading open ssh Anna G. Zapata
2004-02-23 21:30 ` Armen Kaleshian
2004-02-23 22:03 ` Anna G. Zapata
2004-02-23 22:52 ` Armen Kaleshian [this message]
2004-08-19 15:13 ` ssh setup: user 'locked out' daily Eve Atley
2004-08-19 16:12 ` John Kelly
2004-08-19 18:54 ` Eve Atley
2004-09-08 5:27 ` -p option for useradd ( was Re: ssh setup: user 'locked out' daily ) Stephen Samuel
2004-12-22 15:38 ` Interpreting disk space and changing backup path Eve Atley
2004-12-22 16:28 ` Ray Olszewski
2004-12-22 20:37 ` qwms-avib
2004-02-23 21:44 ` upgrading open ssh Ray Olszewski
2004-02-23 21:45 ` caszonyi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040223225259.GA11316@sevoog.kriation.com \
--to=akaleshian@kriation.com \
--cc=azapata@du.edu \
--cc=linux-newbie@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox