Re: [gentoo-user] Confusing boot up messages

2006-08-14 Thread Neil Bothwick
On Mon, 14 Aug 2006 08:20:04 -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

Re: [gentoo-user] Confusing boot up messages

2006-08-14 Thread gentuxx
-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 significa

Re: [gentoo-user] Confusing boot up messages

2006-08-14 Thread Neil Bothwick
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 scrip

Re: [gentoo-user] Confusing boot up messages

2006-08-13 Thread gentuxx
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nick Rout wrote: > has baselayout recently been updated? If so etc-update (or one of its > clones) should fix things. > Yeah, baselayout was one of the packages updated. I prefer dispatch-conf, which I ran. I use a script that I wrote that runs emer

Re: [gentoo-user] Confusing boot up messages

2006-08-13 Thread Nick Rout
has baselayout recently been updated? If so etc-update (or one of its clones) should fix things. On Sun, 13 Aug 2006 19:42:21 -0700 gentuxx wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I just ran an update today, and after rebooting, I get a bunch of odd > errors when all of the

[gentoo-user] Confusing boot up messages

2006-08-13 Thread gentuxx
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I just ran an update today, and after rebooting, I get a bunch of odd errors when all of the services are starting. I wasn't able to capture the exact warnings, and I couldn't find a log that contained them. But it was something to the effect of "WAR