From owner-freebsd-net@freebsd.org Sun May 28 21:49:13 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 403ABD864E7 for ; Sun, 28 May 2017 21:49:13 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 6B7CA1A3D; Sun, 28 May 2017 21:49:10 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id AAA13247; Mon, 29 May 2017 00:49:08 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1dF63g-000Lke-EA; Mon, 29 May 2017 00:49:08 +0300 Subject: Re: svn commit: r314948 - in head: lib/libstand sys/boot/i386/libi386 To: "Rodney W. Grimes" Cc: Kamil Czekirda , Baptiste Daroussin , "George V. Neville-Neil" , Steven Hartland , Toomas Soome , freebsd-net@FreeBSD.org, Mariusz Zaborski References: <201705281538.v4SFcxJ7018338@pdx.rh.CN85.dnsmgr.net> From: Andriy Gapon Message-ID: Date: Mon, 29 May 2017 00:48:12 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <201705281538.v4SFcxJ7018338@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 May 2017 21:49:13 -0000 On 28/05/2017 18:38, Rodney W. Grimes wrote: >> On 28/05/2017 01:09, Kamil Czekirda wrote: >>> In initial revision I noticed, that I'm not sure it should be default behavior. >>> In a lot of installations pxeloader can base on the cache and doesn't require >>> second, full request with the same answer. In that situation we can switch off >>> bootp() and I think it would be nice to have this switch and give them to users. >>> Flag during compilation is sensible. >>> >>> In very simple and popular case we have chain with four requests for the same >>> information (!): >>> PXE (NIC) -> iPXE -> pxeloader -> dhclient >>> and it's possible to switch off request from iPXE and pxeloader without breaking >>> boot process. >> >> Well, the information given to PXE/NIC and iPXE is not exactly the same as >> bootfile must differ. Also, a nit: as far as I know, it's currently impossible >> to run dhclient on a network booted _diskless_ system. > > I dont think that is actually true. Infact dont we need to run > dhclient on a diskless client if we intend to keep our dhcp lease beyond the > initial issue time period, ie renewal ever X minutes? Well, just test it. >> So, yeah, in some setups we can shave off a request from pxeboot and it probably >> makes sense to have that option. -- Andriy Gapon