-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
James Zuelow wrote:
> On Monday 26 June 2006 22:04, Fielder George Dowding wrote:
>
>> Ummm... Well, dist-upgrade and update (within the currently installed
>> distribution) are two different things. I myself update regularly
>> although not daily. I use dselect so I take a look at the new stuff and
>> sometimes the updated stuff before I do the install. I do a dist-upgrade
>> when I am moving from, say stable (eg.: woody) to testing (eg.: sarge)
>> because I know testing is slated to become stable within six months or so.
>>
>
>> Maybe "dist-upgrade" was a slip of the finger although Greg did explain
>> the differences.
>>
>
> Umm, no. I guess I take it for granted that one would update before upgrading, or else you'll just use the same package list over and over again which would defeat the purpose of the upgrade.
>
> To be precise the exact command I have running is:
>
> apt-get update && apt-get -d dist-upgrade
>
> That runs via cron, so I get new packages downloaded at night. Then I can do a quick apt-get dist-upgrade to install the new packages.
>
> If I'm happy, apt-get autoclean deletes the obsolete versions while keeping the current ones. If I'm not happy (and I notice problems in time) I can use dpkg to force a downgrade of troublesome packages. Most of the time I am happy, or can live with problems for a little bit while I wait for related packages that might fix a problem to filter down from unstable.
>
> dist-upgrade will install additional dependencies, where upgrade will not. Therefore on stable systems I tend to use upgrade since they are mainly pulling down security and bug fixes that do not introduce new dependencies. On testing systems (like the one I broke) I tend to use dist-upgrade since the package list changes so rapidly.
>
> Sorry for the confusion.
> ---------
Ha! Thanks for the cron command. I will have to study the implications,
but it may lead to a solution of the machine I have at Mable T. It is a
server which is on all the time (unless there is a power outage). I have
been wanting to set it up to automatically (via cron) update and
install, but I have been reluctant to do so because I didn't want it to
break. I don't visit Mable T.'s more than twice a week on average, and
some weeks (such as my week of baiting mosquitoes and piping) I don't
visit at all.
My goal is to keep the box _updated_ with the latest bug and security
fixes. Now that testing also has security updates, I have upgraded the
box to etch. I would add packages by hand rarely. So perhaps this is the
solution for which I have been looking.
- --
Fielder George Dowding, Chief Iceworm .^. Debian/GNU Linux
dba Iceworm Enterprises, Anchorage, Alaska /v\ "etch" Testing
Since 1976 - Over 30 Years of Service. /( )\ User Number 269482
^^-^^ "irad" 301256
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEoXTF2kl99FX0AIkRAhaMAKCNdhZ+nOo2JhT1FM/xSnr1HsHkUQCfe0em
Cr/omrayZXYhYlL3VujvutU=
=bmOY
-----END PGP SIGNATURE-----
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
Received on Tue Jun 27 10:09:39 2006
This archive was generated by hypermail 2.1.8 : Tue Jun 27 2006 - 10:09:39 AKDT