From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Marc Milgram <mmilgram-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [Patch] dracut: write-ifcfg.sh: load net-lib.sh
Date: Tue, 20 May 2014 11:36:03 +0200 [thread overview]
Message-ID: <537B2203.5010304@redhat.com> (raw)
In-Reply-To: <20140507141827.27588.20483.sendpatchset-cl2/UFW8KLzV1gMhexUvwR/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
On 07.05.2014 16:18, Marc Milgram wrote:
> When kdump boots the second kernel, it complains:
>
> dracut-pre-pivot[429]: //lib/dracut/hooks/pre-pivot/85-write-ifcfg.sh: line 168: is_persistent_ethernet_name: command not found
>
> is_persistent_ethernet_name is defined in net-lib.sh, but write-ifcfg.sh
> doesn't load that library. Solution is to load the library.
>
> Tested that this fix eliminates the error message.
>
> Signed-off-by: Marc Milgram <mmilgram-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> ---
> diff --git a/modules.d/45ifcfg/write-ifcfg.sh b/modules.d/45ifcfg/write-ifcfg.sh
> index 5de2e90..e30749b 100755
> --- a/modules.d/45ifcfg/write-ifcfg.sh
> +++ b/modules.d/45ifcfg/write-ifcfg.sh
> @@ -5,6 +5,8 @@
> # NFS root might have reached here before /tmp/net.ifaces was written
> udevadm settle --timeout=30
>
> +command -v is_persistent_ethernet_name || . /lib/net-lib.sh
> +
> if [ -e /tmp/bridge.info ]; then
> . /tmp/bridge.info
> fi
Thanks!
http://git.kernel.org/cgit/boot/dracut/dracut.git/commit/?id=8fa1afb65cef30d56ce2e141b0b594cf780120a1
prev parent reply other threads:[~2014-05-20 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 14:18 [Patch] dracut: write-ifcfg.sh: load net-lib.sh Marc Milgram
[not found] ` <20140507141827.27588.20483.sendpatchset-cl2/UFW8KLzV1gMhexUvwR/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2014-05-20 9:36 ` Harald Hoyer [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=537B2203.5010304@redhat.com \
--to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mmilgram-H+wXaHxf7aLQT0dZR+AlfA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.