public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] how do you keep up with system administration?
Date: Wed, 30 May 2007 08:21:09 +0100	[thread overview]
Message-ID: <20070530082109.68382cf9@zaphod.digimed.co.uk> (raw)
In-Reply-To: <d9a0a6da0705292005x7825c4e0t999f6188ed5b558e@mail.gmail.com>

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

On Tue, 29 May 2007 23:05:56 -0400, Denis wrote:

> > I use 'gunzip -c /proc/config.gz > .config && make oldconfig'
> > consistently, never had a problem.  I always keep a working kernel
> > in  
> 
> Oh neat-o!  I didn't know there was a copy of the running config
> in /proc...

It's an option you need to enable in the kernel, or you can copy .config
from your current kernel source directory.

> Does this basically just insert the current kernel configuration
> inside the menuconfig interface of the new kernel as the starting
> point?  How does this play with the new kernel options that have since
> appeared or those that have been eliminated?  I suppose you still have
> to check over every menu in the new kernel to make sure you're not
> missing anything...

That's what make oldconfig does, and prompts you for any new items.
There's no need to run menuconfig unless you want to change something.

Waiting for kernel version releases is not a good idea and the -r updates
generally include security fixes. Read the Changelog and decide whether
you need that particular update, some fixes only apply to certain
architectures. Like many others, I have a cron task that syncs then mails
the results of emerge -upvDN world to me, but I have added --changelog to
that command so the mail also contains the details of each update.

This runs in the early hours, so I can read it whenever it suits me during
the day and apply the changes as I want. I run testing, so frequent
updating is a good thing; with a stable system, weekly would be fine, but
the longer you leave it the more work is involved.


-- 
Neil Bothwick

"Time is the best teacher....., unfortunately it kills all the students"

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-05-30  7:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 14:01 [gentoo-user] how do you keep up with system administration? Denis
2007-05-29 14:29 ` Mark Shields
2007-05-29 14:32 ` Kevin O'Gorman
2007-05-29 14:40 ` Ryan Sims
2007-05-29 14:48 ` Albert Hopkins
2007-05-29 14:50 ` Daniel Iliev
2007-05-29 16:49   ` Roy Wright
2007-05-29 17:07 ` Ralf Stephan
2007-05-29 17:39 ` Florian Philipp
2007-05-29 19:07   ` Denis
2007-05-29 18:45 ` kashani
2007-05-30  0:16 ` Tim Allinghan
2007-05-30  1:19   ` Denis
2007-05-30  2:20     ` Ryan Sims
2007-05-30  2:53       ` Michael Sullivan
2007-05-30  3:05       ` Denis
2007-05-30  7:21         ` Neil Bothwick [this message]
2007-05-30  9:06           ` Eray Aslan
2007-05-30  3:20     ` Kevin O'Gorman
2007-05-30 10:03       ` Benno Schulenberg
2007-05-30 17:20         ` Denis
2007-05-30 20:57           ` Neil Bothwick
2007-05-30  3:49 ` Boyd Stephen Smith Jr.
2007-05-30  4:37   ` Denis
2007-05-30  7:22     ` Neil Bothwick
2007-05-30  7:25     ` John covici

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=20070530082109.68382cf9@zaphod.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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