mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Brian C. Lane" <bcl-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] new_dhcp_next_server is really new_next_server
Date: Fri, 07 Feb 2014 18:45:31 +0100	[thread overview]
Message-ID: <52F51BBB.6020005@redhat.com> (raw)
In-Reply-To: <1391631039-29864-1-git-send-email-bcl-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On 02/05/2014 09:10 PM, Brian C. Lane wrote:
> The variable that dhclient sets doesn't have dhcp in the name. This
> could cause problems with setups where the server is not the same as the
> dhcp server.
> ---
>  modules.d/95nfs/nfs-lib.sh | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/modules.d/95nfs/nfs-lib.sh b/modules.d/95nfs/nfs-lib.sh
> index f5fc56d..9ced2e6 100755
> --- a/modules.d/95nfs/nfs-lib.sh
> +++ b/modules.d/95nfs/nfs-lib.sh
> @@ -97,7 +97,7 @@ nfsroot_from_dhcp() {
>      [ -z "$path" ] && [ "$(getarg root=)" == "/dev/nfs" ] && path=/tftpboot/%s
>      [ -z "$server" ] && server=$srv
>      [ -z "$server" ] && server=$new_dhcp_server_identifier
> -    [ -z "$server" ] && server=$new_dhcp_next_server
> +    [ -z "$server" ] && server=$new_next_server
>      [ -z "$server" ] && server=${new_root_path%%:*}
>  }
>  
> 

Thanks! Pushed.

  parent reply	other threads:[~2014-02-07 17:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05 20:10 [PATCH] new_dhcp_next_server is really new_next_server Brian C. Lane
     [not found] ` <1391631039-29864-1-git-send-email-bcl-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-02-07 17:45   ` Harald Hoyer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-02-06 13:52 Brian C. Lane
2014-02-04 17:11 Brian C. Lane

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=52F51BBB.6020005@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=bcl-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox