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] Confusing boot up messages
Date: Mon, 14 Aug 2006 09:04:03 +0100	[thread overview]
Message-ID: <20060814090403.5dea8aa1@hactar.digimed.co.uk> (raw)
In-Reply-To: <44DFF05B.4050105@gmail.com>

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

On Sun, 13 Aug 2006 20:39:07 -0700, gentuxx wrote:

> Yeah, baselayout was one of the packages updated.

From what to what? genlop will tell you. If it was a path level update,
it is unlikely anything has changed significantly in the configs.

> I prefer
> dispatch-conf, which I ran.  I use a script that I wrote that runs
> emerge -DuatvN world, emerge --depclean, revdep-rebuild, dispatch-conf
> and updates AIDE, all in series.  I ran it again, just to check, but
> it doesn't pick up anything.  So, how do I find out which config file
> hosed me?

If you didn't accept updates to the default config files, emerging
baselayout again should pull them back in.

If you know which services were affected but didn't catch the exact
messages, try stopping and starting them manually so the output doesn't
get buried in all the other startup information. Setting RC_VERBOSE="yes"
in /etc/conf.d/rc may help.


-- 
Neil Bothwick

"Do you reply to our surveys.?"
[X]Never [ ]Always [ ]Sometimes

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

  reply	other threads:[~2006-08-14  8:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14  2:42 [gentoo-user] Confusing boot up messages gentuxx
2006-08-14  2:51 ` Nick Rout
2006-08-14  3:39   ` gentuxx
2006-08-14  8:04     ` Neil Bothwick [this message]
2006-08-14 15:20       ` gentuxx
2006-08-14 15:47         ` Neil Bothwick
2006-08-14 15:31 ` Willie Wong

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=20060814090403.5dea8aa1@hactar.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