mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Warren Togami <wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: including python in the initramfs
Date: Tue, 16 Jun 2009 14:26:07 -0400	[thread overview]
Message-ID: <4A37E3BF.3050903@redhat.com> (raw)
In-Reply-To: <1245174031.2150.67.camel@polyethylene>

On 06/16/2009 01:40 PM, Daniel Drake wrote:
> One idea: we could create a separate module which installs all the files
> identified by "rpm -q --filesbypkg python". But that's obviously not
> distro-portable. It could work for us but I'd prefer that we're able to
> share the work we're doing with others. Any other ideas?

Aside from the other reasons this is a bad idea, you cannot safely do 
rpm queries for this if you intend on the initrd to ever be built from 
an rpm scriptlet like %post.  The rpmdb locking will cause problems.

Is it really not possible to run the security client after initrd?

What does the security client do?

Warren


--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2009-06-16 18:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 17:40 including python in the initramfs Daniel Drake
2009-06-16 18:22 ` Victor Lowther
     [not found]   ` <A4EC33E8-3A45-4A6B-AE97-5B48EA425F75-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-06-16 18:49     ` Daniel Drake
2009-06-16 18:55       ` Warren Togami
     [not found]         ` <4A37EA8E.7090508-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-17  7:06           ` Seewer Philippe
     [not found]             ` <4A38960B.20305-omB+W0Dpw2o@public.gmane.org>
2009-06-17  8:28               ` Daniel Drake
2009-06-16 18:26 ` Warren Togami [this message]

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=4A37E3BF.3050903@redhat.com \
    --to=wtogami-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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