Dave Sherohman wrote: > While that is accurate as far as it goes... How likely is the average > user to ever need the cached debs?
[ snippage ]
> Realistically, if you're not going to install to additional machines and
> it's been more than a day or two since you installed a package (to
> provide time to notice any install/configuration problems), the odds of
> needing the deb again are pretty much nil. Using "clean" instead of
> "autoclean" will be fine in the large majority of cases.
Y'know, I had a long reply here basically arguing one against the other,
one being safer than the other. Then I decided to test the theory on my own
machines since I had not done autoclean/clean in a while...
[EMAIL PROTECTED]:~} du -sh /var/cache/apt/archives
732M /var/cache/apt/archives
[EMAIL PROTECTED]:~# aptitude autoclean
Freed 0B of disk space
[EMAIL PROTECTED]:~# du -sh /var/cache/apt/archives
740M /var/cache/apt/archives
[EMAIL PROTECTED]:~# aptitude autoclean
Freed 0B of disk space
[EMAIL PROTECTED]:~} du -sh /var/cache/apt/archives
[EMAIL PROTECTED]:~# aptitude autoclean
Freed 0B of disk space
[EMAIL PROTECTED]:~#
Apparently cron.daily/apt is firing off autoclean by default as it is
because I haven't done it in quite a few days. Which means offering autoclean
as a first step is kinda pointless and nets nothing. Go fig. Carry on.
--
Steve C. Lamb | But who decides what they dream?
PGP Key: 1FC01004 | And dream I do...
-------------------------------+---------------------------------------------
signature.asc
Description: OpenPGP digital signature
