From: Philip Webb <purslow@ca.inter.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Knock on wood
Date: Wed, 12 Aug 2009 09:51:49 -0400 [thread overview]
Message-ID: <20090812135149.GB4887@ca.inter.net> (raw)
In-Reply-To: <4A82C5A8.5060107@gmail.com>
090812 Dale replied to bn :
>> I am becoming very reluctant in updating critical components -
>> eg my kernel, which is basically untouched since I installed late 2007.
> I keep at least two working kernels in /boot.
> I do mine manually and name them in my own way,
> something like bzImage-<kernel version>-<local version>.
> When I upgrade and get a known good kernel where everything works well,
> I then do some house cleaning with regard to the older kernels.
> As far as packages, just use 'buildpkg' in 'make.conf'
> and then you have a binary backup that can be restored in a few minutes
> Backups are also nice. Just in case.
Exactly what I was going to advise ! It's worth mentioning 'make oldconfig'
to help configure the new kernel ('?' gives you help on each new item).
Someone else already mentioned System Rescue CD (based on Gentoo).
The tools are all there in Gentoo: you just have to find & use them.
Perhaps someone should write a doc 'Gentoo for the Time-Challenged'.
--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatchassdotutorontodotca
next prev parent reply other threads:[~2009-08-12 13:51 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 5:13 [gentoo-user] Knock on wood Alan E. Davis
2009-08-12 8:38 ` Neil Bothwick
2009-08-12 12:58 ` Dale
2009-08-12 9:10 ` Philip Webb
2009-08-12 11:43 ` bn
2009-08-12 12:13 ` William Kenworthy
2009-08-12 12:28 ` Etaoin Shrdlu
2009-08-12 12:44 ` Ward Poelmans
2009-08-12 12:51 ` Volker Armin Hemmann
2009-08-12 18:34 ` Ward Poelmans
2009-08-12 18:41 ` Volker Armin Hemmann
2009-08-12 15:52 ` bn
2009-08-12 13:37 ` Dale
2009-08-12 13:41 ` Neil Bothwick
2009-08-12 14:20 ` Dale
2009-08-12 18:02 ` Neil Bothwick
2009-08-12 20:19 ` Stroller
2009-08-12 20:36 ` Neil Bothwick
2009-08-12 23:48 ` Dale
2009-08-12 20:58 ` Mike Edenfield
2009-08-12 21:08 ` Volker Armin Hemmann
2009-08-12 21:25 ` Mike Edenfield
2009-08-12 21:46 ` BRM
2009-08-12 21:59 ` Neil Bothwick
2009-08-13 3:46 ` Mike Kazantsev
2009-08-13 7:31 ` Neil Bothwick
2009-08-14 4:41 ` Mike Kazantsev
2009-08-14 8:15 ` Neil Bothwick
2009-08-12 22:07 ` Stroller
2009-08-12 23:43 ` Neil Bothwick
2009-08-12 13:51 ` Philip Webb [this message]
2009-08-12 14:22 ` Dale
2009-08-12 20:01 ` Dan Farrell
2009-08-12 23:54 ` Dale
2009-08-13 17:08 ` Dan Farrell
2009-08-13 19:34 ` Dale
2009-08-13 19:58 ` Paul Hartman
2009-08-12 20:17 ` Stroller
2009-08-12 23:06 ` bn
2009-08-12 23:59 ` Dale
2009-08-12 15:28 ` Paul Hartman
2009-08-19 7:08 ` Keith Dart
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=20090812135149.GB4887@ca.inter.net \
--to=purslow@ca.inter.net \
--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