From: Grant <emailgrant@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] System maintenance procedure?
Date: Tue, 4 Dec 2012 19:55:22 -0800 [thread overview]
Message-ID: <CAN0CFw2jDh=qbFSh6sn0mwTcwCfhA--BcQ+c95P-o=NVKeVf4A@mail.gmail.com> (raw)
In-Reply-To: <50BEA1A8.3090500@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
> > My unattended daily system maintenance procedure is like this:
> >
> > layman -S
> > emerge --sync
> > emerge -pvDuN world
> > emerge -pv --depclean
> > eclean -p distfiles
> > eclean -p packages
> >
> > And then attended like this:
> >
> > emerge -DuN world
> > revdep-rebuild
> > etc-update
> > elogv
> > emerge --depclean
> > eclean distfiles
> > eclean packages
> >
> > Am I missing any good stuff?
> >
> > - Grant
>
>
> I would use the -a option unless the output of the first part is being
> emailed to you or something.
Exactly, it's being emailed to me and I should have said so.
> Other than using -a instead of -p, I don't see anything missing. Just
> check the USE flags before letting it update. They get changed
> sometimes and it could cause issues. Sometimes the change is for the
> good so always look into it first.
>
> You *may* want to look into dispatch-conf too. It does the same as
> etc-update but it keeps records in case a updated config file borks your
> system. Just a thought.
I will do that. dispatch-conf sounds like a good thing.
- Grant
[-- Attachment #2: Type: text/html, Size: 1419 bytes --]
next prev parent reply other threads:[~2012-12-05 3:57 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 [this message]
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
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='CAN0CFw2jDh=qbFSh6sn0mwTcwCfhA--BcQ+c95P-o=NVKeVf4A@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