From: Dale Amon <amon@vnl.com>
To: Stephen <mridion@hotmail.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Problems loading policy
Date: Fri, 5 Dec 2003 18:36:01 +0000 [thread overview]
Message-ID: <20031205183601.GB32487@vnl.com> (raw)
In-Reply-To: <BAY1-DAV25idcOHuICu0000353b@hotmail.com>
On Sat, Dec 06, 2003 at 01:57:47AM +1100, Stephen wrote:
> I have compiled my kernel with ROMFS, capabilities and SELinux. Here is my
> kernel dmesg
You haven't actually given the info showing whether
the initrd loaded or not.
One item to be wary of though. Make sure cramfs is
deselected in the kernel build if you are using romfs.
For some reason initrd will try cramfs first and not
even look at romfs in that case.
--
------------------------------------------------------
Dale Amon amon@islandone.org +44-7802-188325
International linux systems consultancy
Hardware & software system design, security
and networking, systems programming and Admin
"Have Laptop, Will Travel"
------------------------------------------------------
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2003-12-05 18:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 14:57 Problems loading policy Stephen
2003-12-05 18:36 ` Dale Amon [this message]
2003-12-05 20:32 ` Information flow models John D. Ramsdell
2003-12-08 17:57 ` Karl MacMillan
2003-12-10 13:18 ` John D. Ramsdell
2003-12-10 15:11 ` Karl MacMillan
2003-12-10 15:29 ` John D. Ramsdell
2003-12-10 15:37 ` Karl MacMillan
2003-12-10 19:06 ` Joshua D. Guttman
2003-12-10 20:18 ` Karl MacMillan
2003-12-11 13:10 ` John D. Ramsdell
2003-12-11 16:04 ` Karl MacMillan
2003-12-11 17:43 ` Joshua D. Guttman
2003-12-11 20:23 ` Stephen Smalley
2003-12-11 20:45 ` Stephen Smalley
2003-12-11 20:46 ` Karl MacMillan
2003-12-11 21:00 ` Stephen Smalley
2003-12-23 19:12 ` Trent Jaeger
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=20031205183601.GB32487@vnl.com \
--to=amon@vnl.com \
--cc=mridion@hotmail.com \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.