public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris PeBenito <pebenito@gentoo.org>
To: "Robin H.Johnson" <robbat2@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] initrd
Date: 06 Aug 2003 00:12:11 -0500	[thread overview]
Message-ID: <1060146731.1532.13.camel@chris.pebenito.net> (raw)
In-Reply-To: <20030805171215.GB23572@cherenkov.orbis-terrarum.net>

[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]

Well I've been playing with initrd all day, and I came to the conclusion
that its not worth the effort try to create an in-house mkinitrd (at
least for me to do it).  So I'll put it in as sys-apps/mkinitrd, and add
an optional selinux patch to it.  I pulled it myself from the rawhide
src rpm I got from rpmfind.net.  What is the preferred/correct way of
handling this?  Should I have the ebuild pull the src.rpm and do the
rpm2targz magic in src_unpack, or should I just extract the tarball from
it myself, and put it on distfiles?

On Tue, 2003-08-05 at 12:12, Robin H.Johnson wrote:
> I started on some of this before, when I almost needed an initrd for
> some boxes (due to crappy hardware, i ended up buying some 3ware raid
> controllers instead).
> 
> Based on how redhat packages it, I'd suggest a mkinitrd package that
> pulls in their srpm (from their RawHide sources as the latest contains a
> number of fixed wrt lvm and other things), and builds /sbin/mkinitrd,
> /sbin/nash, /sbin/grubby.
> 
> As you note that you are not willing to maintain the mkinitrd ebuild, if
> you do put it in, I'm willing to maintain it.
-- 
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 --]

  parent reply	other threads:[~2003-08-06  5:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-05 15:55 [gentoo-dev] initrd Chris PeBenito
2003-08-05 17:12 ` 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 [this message]
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=1060146731.1532.13.camel@chris.pebenito.net \
    --to=pebenito@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=robbat2@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