All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Dave Young <dave-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] use linkup in dhclient-script.sh
Date: Tue, 22 Jan 2013 15:35:36 +0100	[thread overview]
Message-ID: <50FEA3B8.2040701@redhat.com> (raw)
In-Reply-To: <20130106061754.A96B664097-4/PLUo9XfK+sDdueE5tM26fLeoKvNuZc@public.gmane.org>

Am 06.01.2013 07:17, schrieb Dave Young:
> 
> linkup is a wrapper function for waiting interface ready and up.
> change to use linkup as what we do in ifup script.
> 
> Signed-off-by: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> ---
>  modules.d/40network/dhclient-script.sh |    6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)
> 
> --- dracut.orig/modules.d/40network/dhclient-script.sh
> +++ dracut/modules.d/40network/dhclient-script.sh
> @@ -25,8 +25,7 @@ setup_interface() {
>          if ! ip link set $netif mtu $mtu ; then
>              ip link set $netif down
>              ip link set $netif mtu $mtu
> -            ip link set $netif up
> -            wait_for_if_up $netif
> +            linkup $netif
>          fi
>      fi
>  
> @@ -62,8 +61,7 @@ netif=$interface
>  case $reason in
>      PREINIT)
>          echo "dhcp: PREINIT $netif up"
> -        ip link set $netif up
> -        wait_for_if_up $netif
> +        linkup $netif
>          ;;
>      BOUND)
>          echo "dhcp: BOND setting $netif"

merged

      parent reply	other threads:[~2013-01-22 14:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-06  6:17 [PATCH] use linkup in dhclient-script.sh Dave Young
     [not found] ` <20130106061754.A96B664097-4/PLUo9XfK+sDdueE5tM26fLeoKvNuZc@public.gmane.org>
2013-01-22 14:35   ` 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=50FEA3B8.2040701@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=dave-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 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.