public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] System maintenance procedure?
Date: Fri, 7 Dec 2012 16:57:32 -0800	[thread overview]
Message-ID: <CAN0CFw3Qfn-1twFi8fG3bG-Q3jHdwHEDf1BHERxOjVQjvgduow@mail.gmail.com> (raw)
In-Reply-To: <50BF2066.9020300@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2540 bytes --]

> I run depclean about once a month after a large update, usually KDE, qt
> or something like that.  I sync and update about twice a week.  I try to
> time mine to hit those important updates to things like KDE or
> something.  I'm actually waiting on KDE 4.9.4 to hit the tree now.  It
> should be there pretty soon, if there is no major problems.
>
> I would set a rough update time schedule. If say you set yours to update
> every week, then keep two maybe three weeks of old packages.  If a
> package can work for a few weeks, survive reboots and a couple updates,
> then odds are it is safe to remove the binaries you built for it.  The
> sources, I usually only keep what I have installed.  Most of the time
> that is enough.  If you have the hard drive space, you can keep them
> like you do the binary package.  If you pick a monthly update time
> frame, then adjust your time frame for old packages.  You may can keep
> less of them depending on how you run your rig.
>
> When you use eclean and friends with no options, it seems to leave a
> pretty good set of binaries behind.  It leaves what is installed plus a
> older version or two.  It's been a while since i really looked into this
> but it seems to have a fairly safe setting when you just run the plain
> command with no options.  When you use the -d option, it leaves only
> what you have installed and gets rid of everything else.  The -d option
> is about the most aggressive option for eclean.
>
> This is just to give you ideas.  This is one of those 'it depends'
> questions.  The technically correct way is to run depclean after each
> full update.  Thing is, I doubt it will hurt anything if you leave them
> on there except for taking up drive space.
>
> Just don't forget to update the configs after each update.  Sometimes
> missing those can lead to a system that won't boot.  It's not very
> likely but they do happen from time to time.
>
> Another thing about my system that may help you, I keep a copy of /etc
> and my world file backed up.  When I reboot, which is not to often, I
> make a new backup of /etc.  Right now, my uptime is almost 75 days.  I
> keep that backup just in case something will only break when rebooting.
> Some config files are only read when booting so until you reboot, you
> don't know you have a problem.  Having a copy of the world file is good
> in case you lose the drive with the OS on it.  You can at least know
> what you need to emerge to get back to where you were.
>
> Hope that helps.
>
> Dale

Thanks Dale.

- Grant

[-- Attachment #2: Type: text/html, Size: 2903 bytes --]

  reply	other threads:[~2012-12-08  0:59 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05  0:30 [gentoo-user] System maintenance procedure? Grant
2012-12-05  1:00 ` nybblenybblebyte
2012-12-05  1:21 ` Dale
2012-12-05  3:55   ` Grant
2012-12-05  1:36 ` Neil Bothwick
2012-12-05  4:04   ` Grant
2012-12-05  4:34     ` Dale
2012-12-05  5:15       ` Grant
2012-12-05 10:22         ` Dale
2012-12-08  0:57           ` Grant [this message]
2012-12-08 22:04       ` Grant
2012-12-08 23:25         ` Dale
2012-12-15  3:38         ` Grant
2012-12-05 12:50     ` Neil Bothwick
2012-12-08  0:55       ` Grant
2012-12-05  3:15 ` Pandu Poluan
2012-12-05  3:29   ` Allan Gottlieb
2012-12-05  3:34   ` Dale
2012-12-05 10:05 ` Alan McKinnon
2012-12-08  0:56   ` Grant
2012-12-08 11:58     ` Neil Bothwick
2012-12-08 20:06     ` Alan McKinnon
2012-12-08 21:07       ` Grant
2012-12-08 21:25         ` Alan McKinnon
2012-12-08 21:54           ` Grant
2012-12-08 22:08             ` Alan McKinnon
2012-12-09  0:41               ` Grant
2012-12-08 22:49             ` Neil Bothwick
2012-12-08 23:20               ` Dale
2012-12-09  4:22                 ` Dale
2012-12-09 13:18                 ` Bruce Hill
2012-12-09 16:48                   ` Neil Bothwick
2012-12-09 17:01                     ` Bruce Hill
2012-12-09 19:06                       ` Neil Bothwick
2012-12-11 13:36                     ` Bruce Hill
2012-12-11 14:04                       ` Neil Bothwick
2012-12-11 17:20                       ` Michael Orlitzky
2012-12-12  6:05                       ` Alan McKinnon
2012-12-12  9:29                         ` Neil Bothwick
2012-12-12 15:10                         ` Bruce Hill
2012-12-12  9:49                       ` Neil Bothwick
2012-12-12 12:16                         ` design [depois das dez]
2012-12-09  0:33               ` Peter Humphrey
2012-12-10  7:50 ` Daniel Wagener
2012-12-10  8:41 ` [gentoo-user] " Steven J. Long

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=CAN0CFw3Qfn-1twFi8fG3bG-Q3jHdwHEDf1BHERxOjVQjvgduow@mail.gmail.com \
    --to=emailgrant@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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