public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Christopher J. PeBenito" <pebenito@ieee.org>
To: Burton Samograd <kruhft@kruhft.dyndns.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] new gentoo-sources kernels (r5+)
Date: 18 Sep 2002 20:17:49 -0500	[thread overview]
Message-ID: <1032398269.5210.12.camel@chris> (raw)
In-Reply-To: <20020918234824.GC13256@kruhft.dyndns.org>

I've been running grsec for the better part of a year.  I've used just a
vanilla kernel+grsec patch, and the gentoo-sources kernel (r2 and r7). 
I've never had problems.  I _always_ use custom, so I know exactly what
is on (like a previous poster suggested).  I've never ran into any
problems.  I would suggest doublechecking your configuration.  Also, you
may want to do a 'make mrproper' to make sure everything is playing
nice... that kills the config tho.  Or you may want to turn off grsec to
make sure your kernel config is ok, and then try turning it back on.

In general, I vote that grsec stay in the gentoo-sources kernel (if it
actually came to a vote :) ).

Chris


On Wed, 2002-09-18 at 18:48, Burton Samograd wrote:
> On Wed, Sep 18, 2002 at 05:15:26PM +0100, Toby Dickenson wrote:
> > 
> > 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?
> 
> Nothing that pointed directly to GrSecurity no.  I was just getting
> errors about not being able to create symbolic links and not being
> able to mount devfs or /mnt/.init.d.  
> 
> I did manage to get a kernel to boot now using a lower GrSecurity
> level, but now it complains that I don't have devfs compiled into the
> kernel (which i know i do, as well as tmpfs and everything else that's
> required).  Maybe one should just leave GrSecurity off completely?
> 
> burton
-- 
Chris PeBenito
<pebenito@ieee.org>
AIM: PeBenito78
ICQ#: 10434387

"Engineering does not require science. Science helps
a lot, but people built perfectly good brick walls 
long before they knew why cement works."-Alan Cox


  reply	other threads:[~2002-09-19  1:17 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
2002-09-18 23:48       ` Burton Samograd
2002-09-19  1:17         ` Christopher J. PeBenito [this message]
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=1032398269.5210.12.camel@chris \
    --to=pebenito@ieee.org \
    --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