From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=DMARC_QUAR,MAILING_LIST_MULTI autolearn=no autolearn_force=no version=4.0.0 Received: from oberon.geminidataloggers.com (oberon.geminidataloggers.com [194.200.199.163]) by chiba.3jane.net (Postfix) with ESMTP id 93D26ABB4F for ; Wed, 18 Sep 2002 11:15:27 -0500 (CDT) Received: from limburger.internal.geminidataloggers.com (limburger.internal.geminidataloggers.com [192.168.0.41]) by oberon.geminidataloggers.com (8.9.3/8.9.3) with ESMTP id RAA26657; Wed, 18 Sep 2002 17:15:26 +0100 Received: from limburger (localhost.localdomain [127.0.0.1]) by limburger.internal.geminidataloggers.com (8.11.6/8.11.6) with ESMTP id g8IGFQ312287; Wed, 18 Sep 2002 17:15:26 +0100 Content-Type: text/plain; charset="iso-8859-1" From: Toby Dickenson To: Burton Samograd , gentoo-dev@gentoo.org Subject: Re: [gentoo-dev] new gentoo-sources kernels (r5+) Date: Wed, 18 Sep 2002 17:15:26 +0100 X-Mailer: KMail [version 1.4] References: <20020918032411.GK4904@kruhft.dyndns.org> <3D87F8C9.5070003@charter.net> <20020918155206.GL4904@kruhft.dyndns.org> In-Reply-To: <20020918155206.GL4904@kruhft.dyndns.org> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200209181715.26460.tdickenson@geminidataloggers.com> Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: b9e8e53c-d212-40cf-bbac-06ffeed0eb6c X-Archives-Hash: 77676d795def2806455ae0bbc6f3dc15 On Wednesday 18 Sep 2002 4:52 pm, Burton Samograd wrote: > On Tue, Sep 17, 2002 at 11:53:45PM -0400, tprado wrote: > > It sounds like you're probably making a simple mistake somewhere in y= our > > kernel upgrade somewhere. > > Acutally, it turns out it was that fancy new GrSecurity setting (I had > it set to med thinking that would be ok). =20 Ive seen that before. I also had alot of GrSecurity log messages mixed in= with=20 those error message, which gave a good clue about the cause of the proble= m.=20 Did you not have that? > Maybe someone could update > the install docs saying to keep it at low or off, since gentoo doesn't > seem to be able to work with it any higher. I think my problems were caused by the extra chroot checks fouling on an=20 initrd boot environment. Everything worked fine once I turned on GrSecuri= ty's=20 'use a sysctl' option, so all its extra checks are turned off at boot.