1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Neil Bothwick wrote: |
5 |
> On Sun, 13 Aug 2006 20:39:07 -0700, gentuxx wrote: |
6 |
> |
7 |
>> Yeah, baselayout was one of the packages updated. |
8 |
> |
9 |
> From what to what? genlop will tell you. If it was a path level update, |
10 |
> it is unlikely anything has changed significantly in the configs. |
11 |
> |
12 |
- From v1.11.15-r3 to v1.12.4-r2. How do I know if it was a "path level |
13 |
update"? |
14 |
>> I prefer |
15 |
>> dispatch-conf, which I ran. I use a script that I wrote that runs |
16 |
>> emerge -DuatvN world, emerge --depclean, revdep-rebuild, dispatch-conf |
17 |
>> and updates AIDE, all in series. I ran it again, just to check, but |
18 |
>> it doesn't pick up anything. So, how do I find out which config file |
19 |
>> hosed me? |
20 |
> |
21 |
> If you didn't accept updates to the default config files, emerging |
22 |
> baselayout again should pull them back in. |
23 |
> |
24 |
> If you know which services were affected but didn't catch the exact |
25 |
> messages, try stopping and starting them manually so the output doesn't |
26 |
> get buried in all the other startup information. Setting RC_VERBOSE="yes" |
27 |
> in /etc/conf.d/rc may help. |
28 |
> |
29 |
> |
30 |
The config files were accepted. There didn't appear to be any |
31 |
significant changes which would have caused something like this. I'll |
32 |
try the RC_ setting and see if that provides any more clues. |
33 |
|
34 |
Thanks. |
35 |
|
36 |
- -- |
37 |
gentux |
38 |
echo "hfouvyyAhnbjm/dpn" | perl -pe 's/(.)/chr(ord($1)-1)/ge' |
39 |
|
40 |
gentux's gpg fingerprint ==> 5495 0388 67FF 0B89 1239 D840 4CF0 39E2 |
41 |
18D3 4A9E |
42 |
-----BEGIN PGP SIGNATURE----- |
43 |
Version: GnuPG v1.4.5 (GNU/Linux) |
44 |
|
45 |
iD8DBQFE4JSkTPA54hjTSp4RAhjrAJ9ua0Q5xXvgiJ1/lx1ZsiGMnfj4tgCgrFSN |
46 |
WiDCIZyo5qzgk7UC0lzg3QE= |
47 |
=3+Re |
48 |
-----END PGP SIGNATURE----- |
49 |
|
50 |
-- |
51 |
gentoo-user@g.o mailing list |