On Saturday 05 August 2006 11:02, Joachim Schrod wrote:
Joachim Schrod wrote:
That said, the apt-for-SUSE documentation could really be better, both for client and server usage. Especially repository selection leaves too many decisions to the user without giving information for guidance. And that the RPM options in apt.conf don't seem to be documented at all, is getting on my nerve, too.
While I'm at it, other examples where the documentation is awfully inadequate: -- RPM key management (i.e., what to do when apt decides not to do an upgrade because public keys are missing)
apt --no-checksig upgrade apt --no-ch upgrade works too ;) (This is in the man page)
-- How to share the apt downloads between several systems and not download them for each system anew.
you could share the apt cache directory I suppose... try with exporting and importing /var/cache/apt, or /var/cache/apt/archives See YaST -> Network Services -> NFS Server and YaST -> Network Services -> NFS Client
-- How to hold dangerous upgrades (kernel, glibc), while still using apt upgrade for the rest.
?
-- How to do daily auto-updates, or daily auto-checks for updates.
man cron, man crontab Hmm, I suppose you did not have a look in /usr/share/doc/packages/apt? There are cron / init script examples there (apt-cron/)... ;P And gpg-check/ might also be interesting. But it's better do do updates /manually/. Pay attention to what is about to be installed, and refuse if you're not happy. Cheers, Leen