From: Michael Sullivan <michael@espersunited.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] how do you keep up with system administration?
Date: Tue, 29 May 2007 21:53:45 -0500 [thread overview]
Message-ID: <1180493625.11392.17.camel@camille.espersunited.com> (raw)
In-Reply-To: <64e8d2f20705291920y7eeb1d4cg6444a8c6b90148bf@mail.gmail.com>
On Tue, 2007-05-29 at 22:20 -0400, Ryan Sims wrote:
> On 5/29/07, Denis <denis.che@gmail.com> wrote:
> > On 5/29/07, Tim Allinghan <deserted@westnet.com.au> wrote:
> >
> > > Last thing before I hop off each night, emerge --sync followed by a -pv
> > > -uDN world, if I'm happy I fire it up and head to bed :)
> >
> > I'm sure that makes for particularly sweet dreams ;-)
> >
> > One thing I've wondered about... When you update X or nvidia drivers,
> > do you need to kill X before running emerge?
>
> I've never done it *before* the emerge, but I usually restart after
> the merge, like any other service. Only time I've ever had a problem
> with a program running while emerging is with a glibc upgrade a while
> back screwing with a running Firefox, restarting Firefox solved
> things.
>
> > I usually dread kernel updates because then I have to go through
> > kernel menuconfig all over again, and for me, that takes some time. I
> > guess one can reuse the old .config file, but I understand it's not
> > always a safe thing to do. Is it reasonably ok to wait for every
> > "major" 2.6.x release to update, or is it necessary to update on every
> > minor 2.6.x.y release also?
>
> I use 'gunzip -c /proc/config.gz > .config && make oldconfig'
> consistently, never had a problem. I always keep a working kernel in
> grub.conf in case of screwups, and I read the options very carefully
> before selecting. One caveat: going from 2.4 to 2.6 I reconfigured
> by hand from scratch. Whenever we get to 2.8 (or whatever the next
> major release is), I'll do that again.
If you wanted to shorten your command, I believe zcat does the exact
same thing as gunzip -c
-Michael Sullivan-
>
> --
> Ryan W Sims
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-05-30 2:59 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 [this message]
2007-05-30 3:05 ` Denis
2007-05-30 7:21 ` Neil Bothwick
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=1180493625.11392.17.camel@camille.espersunited.com \
--to=michael@espersunited.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