From: Chris PeBenito <pebenito@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] initrd
Date: 05 Aug 2003 10:55:36 -0500 [thread overview]
Message-ID: <1060098935.9166.16.camel@chris.pebenito.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]
For the new SELinux API in 2.6, it is required that the SELinux policy
is loaded by initrd. We don't have a mkinitrd in portage. I could add
a Gentoo-fixed RedHat mkinitrd, but I'd prefer not to, since all I have
to do in the initrd is 3 commands (and I don't want to maintain a
mkinitrd ebuild either). However, there is a static shell in the RedHat
mkinitrd package (nash) that is compiled with dietlibc which I do want,
because its tiny, and made to run in a initrd.
Would it be acceptable to create something like a "mkpolicyinitrd"
package that pulls in the RH src rpm, and compiles nash out of it, and
adds in my own mkinitrd script? I could also put the mkinitrd in our
selinux-base-policy ebuild, and just create a nash ebuild.
I would rather have a ebuild just for nash. Is there any preference, or
other suggestions?
--
Chris PeBenito
<pebenito@gentoo.org>
Developer, SELinux
Hardened Gentoo Linux
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE6AF9243
Key fingerprint = B0E6 877A 883F A57A 8E6A CB00 BC8E E42D E6AF 9243
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-08-05 15:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 15:55 Chris PeBenito [this message]
2003-08-05 17:12 ` [gentoo-dev] initrd Robin H.Johnson
2003-08-05 20:25 ` Martin Schlemmer
2003-08-05 20:50 ` Chris PeBenito
2003-08-05 21:23 ` Martin Schlemmer
2003-08-06 5:12 ` Chris PeBenito
2003-08-06 5:36 ` Robin H.Johnson
2003-08-06 18:29 ` Martin Schlemmer
2003-08-06 14:05 ` Aron Griffis
2003-08-06 14:30 ` Grant Goodyear
-- strict thread matches above, loose matches on Subject: below --
2002-10-23 20:49 [gentoo-dev] Initrd Paulo Goncalves
2002-10-21 8:31 ` Sylvain
2002-10-25 15:48 ` Christian Skarby
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=1060098935.9166.16.camel@chris.pebenito.net \
--to=pebenito@gentoo.org \
--cc=gentoo-dev@gentoo.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