1 |
Well I've been playing with initrd all day, and I came to the conclusion |
2 |
that its not worth the effort try to create an in-house mkinitrd (at |
3 |
least for me to do it). So I'll put it in as sys-apps/mkinitrd, and add |
4 |
an optional selinux patch to it. I pulled it myself from the rawhide |
5 |
src rpm I got from rpmfind.net. What is the preferred/correct way of |
6 |
handling this? Should I have the ebuild pull the src.rpm and do the |
7 |
rpm2targz magic in src_unpack, or should I just extract the tarball from |
8 |
it myself, and put it on distfiles? |
9 |
|
10 |
On Tue, 2003-08-05 at 12:12, Robin H.Johnson wrote: |
11 |
> I started on some of this before, when I almost needed an initrd for |
12 |
> some boxes (due to crappy hardware, i ended up buying some 3ware raid |
13 |
> controllers instead). |
14 |
> |
15 |
> Based on how redhat packages it, I'd suggest a mkinitrd package that |
16 |
> pulls in their srpm (from their RawHide sources as the latest contains a |
17 |
> number of fixed wrt lvm and other things), and builds /sbin/mkinitrd, |
18 |
> /sbin/nash, /sbin/grubby. |
19 |
> |
20 |
> As you note that you are not willing to maintain the mkinitrd ebuild, if |
21 |
> you do put it in, I'm willing to maintain it. |
22 |
-- |
23 |
Chris PeBenito |
24 |
<pebenito@g.o> |
25 |
Developer, SELinux |
26 |
Hardened Gentoo Linux |
27 |
|
28 |
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE6AF9243 |
29 |
Key fingerprint = B0E6 877A 883F A57A 8E6A CB00 BC8E E42D E6AF 9243 |