From: Heavenly Avenger <avenger@avenger.ws>
To: cygwin@cygwin.com
Subject: Re: cleanup disk space
Date: Tue, 10 Jul 2018 04:45:00 -0000 [thread overview]
Message-ID: <17a2c4c5-8017-de94-4054-710d36f43304@avenger.ws> (raw)
In-Reply-To: <23364.12720.381316.199665@gargle.gargle.HOWL>
Hello! I maybe am getting the message underway and I don't see the
history on the message itself, and you seem to be replying somebody that
posted a question before I joined the list.
But I believe that if space is a concern there are two main points I can
think of:
- Selectively installing only packages you need. I do this myself, get
rid of any x, gtk, kde, gnome related stuff
- Using NTFS compression. You can do this by a per-folder level and
compress just given folders (or files) "in-place" without making it
unable to run/open the files. NTFS does this compression transparent to
the user -- at the cost of additional CPU cycles to decompress the file
when a read is attempted.
To enable NTFS compression, you can do it for the whole disk. Open
explorer, right-click disk, properties, and check the "compress this
drive to save disk space" in the dialog that is displayed.
You can do this for specific files/folders by right-clicking them,
clicking 'properties', then 'advanced' and then checking the
compression-specific checkbox that's displayed.
This should go smoothly with cygwin... but nowadays I believe the space
cygwin spends is negligible comparing to the size of the available disks...
Zipping the files with bzip2/gzip/whatever may work for some editors
that know to expand the files before opening, but that won't be the case
in the majority of the applications. The transparent and native
compression should be the best shot to shrink a big and cluttered cygwin
installation in no time. Again, for the (potential) cost of performance.
Hope this helps!
On 7/10/2018 1:10 AM, bzs@theworld.com wrote:
> 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.
>
--
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
prev parent reply other threads:[~2018-07-10 4:45 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
2018-07-10 4:45 ` Heavenly Avenger [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=17a2c4c5-8017-de94-4054-710d36f43304@avenger.ws \
--to=avenger@avenger.ws \
--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).