public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Toby Dickenson <tdickenson@geminidataloggers.com>
To: Burton Samograd <kruhft@kruhft.dyndns.org>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] new gentoo-sources kernels (r5+)
Date: Wed, 18 Sep 2002 17:15:26 +0100	[thread overview]
Message-ID: <200209181715.26460.tdickenson@geminidataloggers.com> (raw)
In-Reply-To: <20020918155206.GL4904@kruhft.dyndns.org>

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 your
> > 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).  

Ive seen that before. I also had alot of GrSecurity log messages mixed in with 
those error message, which gave a good clue about the cause of the problem. 
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 
initrd boot environment. Everything worked fine once I turned on GrSecurity's 
'use a sysctl' option, so all its extra checks are turned off at boot.


  reply	other threads:[~2002-09-18 16:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-18  3:24 [gentoo-dev] new gentoo-sources kernels (r5+) Burton Samograd
2002-09-18  3:53 ` tprado
2002-09-18 15:52   ` Burton Samograd
2002-09-18 16:15     ` Toby Dickenson [this message]
2002-09-18 23:48       ` Burton Samograd
2002-09-19  1:17         ` Christopher J. PeBenito
2002-09-19  7:11         ` Evan Read
2002-09-19  9:06           ` Christian Axelsson
2002-09-18 16:15     ` Mike Lundy

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=200209181715.26460.tdickenson@geminidataloggers.com \
    --to=tdickenson@geminidataloggers.com \
    --cc=gentoo-dev@gentoo.org \
    --cc=kruhft@kruhft.dyndns.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