From: Evan Read <eread@freeshell.org>
To: Burton Samograd <kruhft@kruhft.dyndns.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] new gentoo-sources kernels (r5+)
Date: Thu, 19 Sep 2002 07:11:55 +0000 [thread overview]
Message-ID: <20020919071155.GA13203@SDF.LONESTAR.ORG> (raw)
In-Reply-To: <20020918234824.GC13256@kruhft.dyndns.org>
On Wed, Sep 18, 2002 at 04:48:24PM -0700, 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
Under 1.2 I have enabled all specified in the Gentoo Security Guide.
Works great.
--
Evan Read
http://eread.freeshell.org
"The future comes 60 minutes an hour no matter who you are or what you
do."
The Screwtape Letters - C.S. Lewis
next prev parent reply other threads:[~2002-09-19 7:12 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
2002-09-19 7:11 ` Evan Read [this message]
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=20020919071155.GA13203@SDF.LONESTAR.ORG \
--to=eread@freeshell.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