From: Santhapur Naveen <naveens@amiindia.co.in>
To: "Wu, Jiaxin" <jiaxin.wu@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Verifying HTTP Boot in Home environment
Date: Mon, 20 Mar 2017 10:16:11 +0000 [thread overview]
Message-ID: <625A2455CC232F40B0F38F05ACED6D97B69AF274@VENUS1.in.megatrends.com> (raw)
In-Reply-To: <895558F6EA4E3B41AC93A00D163B7274162A480B@SHSMSX103.ccr.corp.intel.com>
Hi Jiaxin,
I think my earlier result was in a corporate environment. I might have missed something while verifying the same. :(
Please let me know if my understanding about this is correct or not.
The normal DHCP configuration in a corporate environment looks like this.
default-lease-time 600;
max-lease-time 7200;
allow booting;
option domain-name "cloudboot.com";
option domain-name-servers 192.168.184.1;
option vendor-class-identifier "HTTPClient";
option bootfile-name "http://www.cloudboot.com/EFI/Shell.efi";
subnet 192.168.xx.0 netmask 255.255.255.0 {
range 192.168.xx.ad 192.168.xx.cd;
}
and for home environment, it is almost the same except "option bootfile-name "http://www.cloudboot.com/EFI/Shell.efi";" will not be present.
If my understanding is not correct, please let me know.
Thanks,
Naveen
________________________________________
From: Wu, Jiaxin [jiaxin.wu@intel.com]
Sent: Monday, March 20, 2017 1:47 PM
To: Santhapur Naveen; edk2-devel@lists.01.org
Subject: RE: Verifying HTTP Boot in Home environment
Great:).
> -----Original Message-----
> From: Santhapur Naveen [mailto:naveens@amiindia.co.in]
> Sent: Monday, March 20, 2017 4:14 PM
> To: Wu, Jiaxin <jiaxin.wu@intel.com>; edk2-devel@lists.01.org
> Subject: RE: Verifying HTTP Boot in Home environment
>
> Hi Jiaxin,
>
> Thanks for your prompt reply.
> I've verified like the same and got the expected output.
>
> Many Thanks,
> Naveen
> ________________________________________
> From: Wu, Jiaxin [jiaxin.wu@intel.com]
> Sent: Monday, March 20, 2017 1:25 PM
> To: Santhapur Naveen; edk2-devel@lists.01.org
> Subject: RE: Verifying HTTP Boot in Home environment
>
> Hello Naveen,
>
> You can refer to the below wiki page for the detailed HTTP home
> environment usage:
> https://github.com/tianocore/tianocore.github.io/wiki/HTTP-Boot
>
> Thanks,
> Jiaxin
>
> > -----Original Message-----
> > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> > Santhapur Naveen
> > Sent: Monday, March 20, 2017 3:07 PM
> > To: edk2-devel@lists.01.org
> > Subject: [edk2] Verifying HTTP Boot in Home environment
> >
> > Hello all,
> >
> > The commit, fa848a4048943251fc057fe8d6c5a82e01d2ffb6 adds the
> > support for HTTP Boot usage in home environment. Would anyone out
> here
> > please help me the procedure to verify this?
> >
> > Best Regards,
> > Naveen
> > _______________________________________________
> > edk2-devel mailing list
> > edk2-devel@lists.01.org
> > https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2017-03-20 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 7:06 Verifying HTTP Boot in Home environment Santhapur Naveen
2017-03-20 7:55 ` Wu, Jiaxin
2017-03-20 8:14 ` Santhapur Naveen
2017-03-20 8:17 ` Wu, Jiaxin
2017-03-20 10:16 ` Santhapur Naveen [this message]
2017-03-21 1:25 ` Wu, Jiaxin
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-list 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=625A2455CC232F40B0F38F05ACED6D97B69AF274@VENUS1.in.megatrends.com \
--to=devel@edk2.groups.io \
/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