All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Olszewski <ray@comarre.com>
To: Revobild / Heimo Claasen <revobild@revobild.net>,
	linux-newbie@vger.kernel.org
Subject: Re: how to assess occupied space
Date: Sat, 14 Sep 2002 22:13:28 -0700	[thread overview]
Message-ID: <5.1.0.14.1.20020914220401.0227f0a0@celine> (raw)
In-Reply-To: <200209150354.g8F3sYPR007105@pyxis.wanadoo.be>

The command you want for checking directory sizes is "du". Its man page 
will teach you the details, but as a simple example, the command

         du -sh /home/*

will give you the amount of space being used by each home directory on the 
system.

In this context, your use of "package" is unclear.  A package is usually a 
portmanteau file that contains a set of related files, most often (putting 
aside source packages for the moment) an executable and associated stuff -- 
that is, a package is an .rpm, or .deb, or .tgz file. If that is what you 
mean, the more developed packaging systems have commands that tell you a 
lot about the package, including how much space it takes up when installed. 
For help with that, ask about whichever packaging system you use (or 
consult ithe man page for the package manager, if it has one).

But since a package typically installs stuff in several separate places 
(for example, an executable in /usr/bin, a man page somewhere else, 
possibly other documentation in /usr/share/doc, configuration stuff in 
/etc, and maybe boot/init stuff in /etc/init.d), there is no good way, at 
least not that I know of, to figure out how much space a package takes up 
by examining directories in the filesystem.

At , Revobild / Heimo Claasen wrote:
>Is there a practical way to get a sum-up of HD space occupied by one
>dir (including subdirs) and then, especially of a package ?
>
>I'd like to weed out never used stuff and recover scarce disk place.
>Is there a good, or any, "strategy" for this ?


--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  ray@comarre.com
-------------------------------------------------------------------------------

-
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

  parent reply	other threads:[~2002-09-15  5:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-15  0:00 how to assess occupied space Revobild / Heimo Claasen
2002-09-15  4:40 ` Mike Dresser
2002-09-15 12:12   ` Haines Brown
2002-09-15  5:13 ` Ray Olszewski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-15  0:00 Heimo Claasen
2002-09-15 18:51 ` Mike Dresser
2002-09-15 19:05 ` Ray Olszewski
     [not found] ` <Pine.LNX.4.33.0209151447040.23713-100000@router.windsormac hine.com>
2002-09-15 19:07   ` Ray Olszewski
2002-09-15 19:16     ` Mike Dresser
     [not found]     ` <Pine.LNX.4.33.0209151515110.2321-100000@router.windsormach ine.com>
2002-09-15 19:21       ` Ray Olszewski

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=5.1.0.14.1.20020914220401.0227f0a0@celine \
    --to=ray@comarre.com \
    --cc=linux-newbie@vger.kernel.org \
    --cc=revobild@revobild.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.