From: Stephen Samuel <samuel@bcgreen.com>
To: "Anna G. Zapata" <azapata@du.edu>, linux-newbie@vger.kernel.org
Subject: Re: RPMs
Date: Mon, 16 Jun 2003 10:05:37 -0700 [thread overview]
Message-ID: <3EEDF8E1.1060502@bcgreen.com> (raw)
In-Reply-To: <HBEJLOFMLEPBMAAEFNFDKEBGCAAA.azapata@du.edu>
It's not clear from your email whether or not you know this, but -- once
you install an RPM, you do NOT need to keep the .rpm file arond any more.
other than .newrpm and .oldrpm configfile backups, RPM updates should not
occupy that much space on your system.
Also: you only need to install updates for RPMs that you already have
installed. If you don't have xyz-1.0.rpm, then there's no reason to
install the xyz-1.2.rpm security update for it.
I have some scripts to help automate that process for you if you'd like.
Anna G. Zapata wrote:
> I need more information on RPMs. I know there are many security updates
> every week. However, I am running out of disk space on my linux box and
> can't get all those RPM updates on there. Do I need all of them? How do I
> know what I need and what I don't?
>
> Thanks!
>
> Anna G. Zapata - GSEC, MCIS
> University of Denver
> University Technology Services - Network Security
> (303) 871-2009 (phone)
> (303) 871-4135 (fax)
> azapata@du.edu (email)
--
Stephen Samuel +1(604)876-0426 samuel@bcgreen.com
http://www.bcgreen.com/~samuel/
Powerful committed communication. Transformation touching
the jewel within each person and bring it to life.
-
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
prev parent reply other threads:[~2003-06-16 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 15:10 RPMs Anna G. Zapata
2003-06-16 15:53 ` RPMs Ray Olszewski
2003-06-16 17:05 ` Stephen Samuel [this message]
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=3EEDF8E1.1060502@bcgreen.com \
--to=samuel@bcgreen.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