From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 71AA91381FB for ; Sat, 8 Dec 2012 00:59:49 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id ABD99E0732; Sat, 8 Dec 2012 00:59:35 +0000 (UTC) Received: from mail-ee0-f53.google.com (mail-ee0-f53.google.com [74.125.83.53]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C5221E06C8 for ; Sat, 8 Dec 2012 00:57:33 +0000 (UTC) Received: by mail-ee0-f53.google.com with SMTP id c50so617447eek.40 for ; Fri, 07 Dec 2012 16:57:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=FPqdDan2IGwW+QLyvc2a/j7PEEzgB5GUOEw1tDbha9g=; b=n58hNMRAjPOcbkfOr9rVblxBFfFml5r5mfzj37Aotujk3OZbKcZj/SWx66zQ7xIZKy p9FfuMLhSqDN6b46t5YV+gHnkJRMMDup2p+Zi6xS8xhk/y/Hs7UElGjmi0PIsFmrZ/Kg wd8xk7Mo5dluxoCWsV6nfdvro2LZB2I0KqnaUMJO77HwAIAxrVs+kl2/x1mhhmm4IdKt pYSAugneD2Dhu2XDj4LvQ80yxXC/evbI+6+h8rN2M/krwDTZsb844/AuCrCPAzKrVBQ8 glfRV1qLmlLw3den1Kkw4cPquHvRLjXIlpu1DXh9bODYg0xv7jPXYzGUO9pY48pGY8qi Bi/A== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.14.194.195 with SMTP id m43mr22735303een.44.1354928252492; Fri, 07 Dec 2012 16:57:32 -0800 (PST) Received: by 10.223.158.68 with HTTP; Fri, 7 Dec 2012 16:57:32 -0800 (PST) In-Reply-To: <50BF2066.9020300@gmail.com> References: <5c00f8dd-b7d0-40c7-90cd-cbff12abfd85@email.android.com> <50BECEC7.6040103@gmail.com> <50BF2066.9020300@gmail.com> Date: Fri, 7 Dec 2012 16:57:32 -0800 Message-ID: Subject: Re: [gentoo-user] System maintenance procedure? From: Grant To: Gentoo mailing list Content-Type: multipart/alternative; boundary=047d7b342c4c2f9a0304d04cd168 X-Archives-Salt: 699cd094-2f6d-488a-881f-4e4b8590b58b X-Archives-Hash: 329ef7030311aefeb0f24056339d7731 --047d7b342c4c2f9a0304d04cd168 Content-Type: text/plain; charset=ISO-8859-1 > 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 --047d7b342c4c2f9a0304d04cd168 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable > I run depclean about once a month after a large update, usually KDE, q= t
> or something like that. =A0I sync and update about twice a week. = =A0I try to
> time mine to hit those important updates to things like= KDE or
> something. =A0I'm actually waiting on KDE 4.9.4 to hit the tree no= w. =A0It
> 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. =A0If a> package can work for a few weeks, survive reboots and a couple updat= es,
> then odds are it is safe to remove the binaries you built for i= t. =A0The
> sources, I usually only keep what I have installed. =A0Most of the tim= e
> that is enough. =A0If you have the hard drive space, you can keep= them
> like you do the binary package. =A0If you pick a monthly upda= te time
> frame, then adjust your time frame for old packages. =A0You may can ke= ep
> 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. =A0It leaves what is installed plus a=
> older version or two. =A0It's been a while since i really looked i= nto this
> but it seems to have a fairly safe setting when you just r= un the plain
> command with no options. =A0When you use the -d option= , it leaves only
> what you have installed and gets rid of everything else. =A0The -d opt= ion
> is about the most aggressive option for eclean.
>
>= This is just to give you ideas. =A0This is one of those 'it depends= 9;
> questions. =A0The technically correct way is to run depclean after eac= h
> full update. =A0Thing is, I doubt it will hurt anything if you le= ave them
> on there except for taking up drive space.
>
>= Just don't forget to update the configs after each update. =A0Sometime= s
> missing those can lead to a system that won't boot. =A0It's no= t 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. =A0When I reboot, which is not to often, = I
> make a new backup of /etc. =A0Right now, my uptime is almost 75 d= ays. =A0I
> keep that backup just in case something will only break w= hen rebooting.
> Some config files are only read when booting so until you reboot, you<= br>> don't know you have a problem. =A0Having a copy of the world fi= le is good
> in case you lose the drive with the OS on it. =A0You can= at least know
> what you need to emerge to get back to where you were.
>
>= Hope that helps.
>
> Dale

Thanks Dale.
<= br>
- Grant
--047d7b342c4c2f9a0304d04cd168--