From: Sam Ravnborg <sam@ravnborg.org>
To: "Sally, Gene" <Gene.Sally@timesys.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.28-rc2] gen_init_cpio expands shell variables in file names
Date: Sat, 22 Nov 2008 12:35:34 +0100 [thread overview]
Message-ID: <20081122113534.GA24848@uranus.ravnborg.org> (raw)
In-Reply-To: <CFEB29247FA6A94796A15592E348E7B90D2706EE30@exchange07.timesys.com>
On Wed, Oct 29, 2008 at 09:54:17AM -0400, Sally, Gene wrote:
> Hi,
>
> This patch modifies gen_init_cpio so that lines that specify files can contain what looks like a shell variable that's expanded during processing.
>
> For example:
>
> file /sbin/kinit ${RFS_BASE}/usr/src/klibc/kinit/kinit 0755 0 0
>
> given RFS_BASE is "/some/directory" in the environment
>
> would be expanded to
>
> file /sbin/kinit /some/directory/usr/src/klibc/kinit/kinit 0755 0 0
>
> If several environment variables appear in a line, they are all expanded with processing happening from left to right. Undefined variables expand to a null string. Syntax errors stop processing, letting the existing error handling show the user offending line.
>
> This patch helps embedded folks who frequently create several RFS directories and then switch between them as they're tuning an initramfs. Having just been such an embedded folk, this seems the most efficient solution.
>
> I didn't see a maintainer for this area (forgive me if I overlooked) so I don't know who I should CC for this patch.
>
> Regards,
> gene
Hi gene.
Applied.
I fixed up the changelog (adding newlines and moving
your Signed-off-by:).
And I had to apply the patch manually as it was somehow broken.
Please see if you can improve this nect time you submit a patch.
Sam
prev parent reply other threads:[~2008-11-22 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 13:54 Sally, Gene
2008-11-22 11:35 ` Sam Ravnborg [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=20081122113534.GA24848@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=Gene.Sally@timesys.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®