-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Neil Bothwick wrote: > 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. > - From v1.11.15-r3 to v1.12.4-r2. How do I know if it was a "path level update"? >> 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. > > The config files were accepted. There didn't appear to be any significant changes which would have caused something like this. I'll try the RC_ setting and see if that provides any more clues.
Thanks. - -- gentux echo "hfouvyyAhnbjm/dpn" | perl -pe 's/(.)/chr(ord($1)-1)/ge' gentux's gpg fingerprint ==> 5495 0388 67FF 0B89 1239 D840 4CF0 39E2 18D3 4A9E -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE4JSkTPA54hjTSp4RAhjrAJ9ua0Q5xXvgiJ1/lx1ZsiGMnfj4tgCgrFSN WiDCIZyo5qzgk7UC0lzg3QE= =3+Re -----END PGP SIGNATURE----- -- gentoo-user@gentoo.org mailing list
