From: bzs@theworld.com
To: Brian.Inglis@SystematicSw.ab.ca
Cc: cygwin@cygwin.com
Subject: Re: cleanup disk space (was: /lib/debug/usr/bin/cygwin1.dbg)
Date: Tue, 10 Jul 2018 04:11:00 -0000 [thread overview]
Message-ID: <23364.12720.381316.199665@gargle.gargle.HOWL> (raw)
In-Reply-To: <a34c0083-c5a6-62cd-e1db-b2349ab8f973@SystematicSw.ab.ca>
I hesitate to jump in here but what about the common compression
programs cygwin provides like bzip2 and xz?
Maybe everyone knows about them and clearly you can't do this on files
you actually need to use (e.g., executables, tho looking at /usr/bin
some are 20MB each and if you know you don't actually run them
ever...) And even an error can generally be undone with a simple
uncompress command within reason. Don't compress the respective
uncompress command!
And zip and tar can be used to package up entire directories or
wildcard matched files in one command.
And if you find you really don't miss what you packed up they can be
moved off disk entirely to a thumb drive or CD/DVD or whatever for
more savings tho that's also true of the uncompressed versions but zip
or tar archives are particularly handy for this.
Maybe it's too obvious, apologies.
--
-Barry Shein
Software Tool & Die | bzs@TheWorld.com | http://www.TheWorld.com
Purveyors to the Trade | Voice: +1 617-STD-WRLD | 800-THE-WRLD
The World: Since 1989 | A Public Information Utility | *oo*
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-07-10 4:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-08 17:45 /lib/debug/usr/bin/cygwin1.dbg ? Ulli Horlacher
2018-07-08 18:06 ` David Stacey
2018-07-08 20:41 ` cleanup disk space (was: /lib/debug/usr/bin/cygwin1.dbg) Brian Inglis
2018-07-10 4:11 ` bzs [this message]
2018-07-10 4:45 ` cleanup disk space Heavenly Avenger
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=23364.12720.381316.199665@gargle.gargle.HOWL \
--to=bzs@theworld.com \
--cc=Brian.Inglis@SystematicSw.ab.ca \
--cc=cygwin@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).