From: Rob Landley <rob@landley.net>
To: P J P <ppandit@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Export initial ramdisk compression config
Date: Wed, 25 Sep 2013 11:56:39 -0500 [thread overview]
Message-ID: <1380128199.1974.89@driftwood> (raw)
In-Reply-To: <alpine.LFD.2.03.1309250035480.5312@erqung.pbz> (from ppandit@redhat.com on Tue Sep 24 14:41:54 2013)
On 09/24/2013 02:41:54 PM, P J P wrote:
> Hello Andrew,
>
> Thank you so much for reviewing these patches.
>
> +-- On Mon, 23 Sep 2013, Andrew Morton wrote --+
> | It's a bit confusing whether all this appiles to initrd, to
> initramfs
> | or to both. Can you please clarify all this and be sure that it's
> all
> | consistent?
>
> IIUC, we no longer use initrd block device images. Instead we use
> initramfs
> which is a cpio(1) archive image. Both mkinitrd(8) & dracut(8) are
> invoked
> from /sbin/new-kernel-pkg tool. And mkinitrd(8) is nothing but a
> wrapper
> around dracut(8) these days.
$ find . -name "Makefile*" | xargs grep new-kernel-pkg
$ grep -r new-kernel-pkg scripts
$
Ah, so it's an out of tree bespoke Red Hat tool. No wonder I couldn't
find it.
> Looking at the dracut(8) tool, it seems it can easily support any
> number of
> compression tools, for it already has options --gzip, --bzip2, --xz &
> --lzma.
> Adding --lzo, --lz4 etc won't be much difficult.
You're reimplemented the posix "pax" command?
> | - Can we avoid having to update dracut each time a new compression
> | scheme is added? I assume your dracut changes will just exec
> | "$INITRD_COMPRESS -d", so as long as any new decompression
> | application uses the expected -d argument in the expected way, it
> | should work seamlessly?
>
> Yes, dracut(8) has | --compress=$INITRD_COMPRESS | option which
> could be
> used to pass compression program to dracut(8).
$ grep -r INITRD_COMPRESS linux
$
Is this what you're currently doing, or the change you're requesting in
the kernel?
> Not sure if dracut(8) expects
> an absolute path or just the program name. But to use this option,
> we'll need
> to patch /sbin/new-kernel-pkg tool.
>
> Alternatively, dracut(8) could be patched to recognise and read
> $INITRD_COMPRESS variable and internally it can define precedence
> order
> between environment variable, command-line options and default
> fall-back
> option.
How does your code get called?
Rob
next prev parent reply other threads:[~2013-09-25 16:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-15 9:19 [PATCH 2/2] Export initial ramdisk compression config P J P
2013-09-23 19:52 ` Andrew Morton
2013-09-24 19:41 ` P J P
2013-09-25 16:56 ` Rob Landley [this message]
2013-09-26 7:30 ` P J P
2013-10-09 21:48 ` Andrew Morton
2013-10-10 7:05 ` P J P
2013-10-10 14:43 ` P J P
2013-10-10 15:14 ` P J P
2013-09-30 21:41 ` P J P
2013-10-05 20:43 ` P J P
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=1380128199.1974.89@driftwood \
--to=rob@landley.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ppandit@redhat.com \
/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