From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Amadeusz Żołnowski" <aidecoe-2qtfh70TtYba5EbDDlwbIw@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/3] dracut-functions: info which udev rules are skipped
Date: Fri, 09 Jul 2010 15:48:44 +0200 [thread overview]
Message-ID: <4C3728BC.6070107@redhat.com> (raw)
In-Reply-To: <20100705090847.4a2bcc7e@etiriah>
On 07/05/2010 09:08 AM, Amadeusz Żołnowski wrote:
> I found it useful. Maybe help others debugging.
> ---
> dracut-functions | 5 +++--
> 1 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/dracut-functions b/dracut-functions
> index 9c2999a..0caf0d6 100755
> --- a/dracut-functions
> +++ b/dracut-functions
> @@ -335,8 +335,9 @@ inst_rules() {
> inst_dir "/lib/udev/rules.d"
> inst_dir "$target"
> for rule in "$@"; do
> - rule=$(find_rule "$rule")&& \
> - inst_simple "$rule" "$target/${rule##*/}"
> + rule1=$(find_rule "$rule")&& \
> + inst_simple "$rule1" "$target/${rule1##*/}" \
> + || dinfo "Skipping udev rule: $rule"
> done
> }
>
pushed
next prev parent reply other threads:[~2010-07-09 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 7:06 [PATCH 1/3] dracut: info which module is sourced; updated dracut usage Amadeusz Żołnowski
2010-07-05 7:08 ` [PATCH 2/3] dracut-functions: info which udev rules are skipped Amadeusz Żołnowski
2010-07-05 7:12 ` [PATCH 3/3] dracut-functions: find_rule a bit smarter Amadeusz Żołnowski
2010-07-05 9:24 ` Amadeusz Żołnowski
2010-07-05 14:53 ` Victor Lowther
[not found] ` <1278341637.4056.17.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-07-07 9:19 ` Amadeusz Żołnowski
2010-07-07 10:27 ` [PATCH] dracut-functions: find_rule a bit smarter; thanks to V. Lowther Amadeusz Żołnowski
2010-07-09 13:48 ` Harald Hoyer [this message]
2010-07-09 13:47 ` [PATCH 1/3] dracut: info which module is sourced; updated dracut usage Harald Hoyer
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=4C3728BC.6070107@redhat.com \
--to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=aidecoe-2qtfh70TtYba5EbDDlwbIw@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