From owner-freebsd-current@freebsd.org Tue Jun 16 15:53:26 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 688E233FD17 for ; Tue, 16 Jun 2020 15:53:26 +0000 (UTC) (envelope-from miguelmclara@gmail.com) Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49mXmP4Z0Tz4D4J for ; Tue, 16 Jun 2020 15:53:25 +0000 (UTC) (envelope-from miguelmclara@gmail.com) Received: by mail-pl1-x62c.google.com with SMTP id m7so8576903plt.5 for ; Tue, 16 Jun 2020 08:53:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+t9OB7YpYITCmo40A/7FMy31A5gun81q9D3BlUnY1l8=; b=RPKMRxzxizmmdBrqhBJvqYEGCofyCuvoSZekrQjIE5WjCHl1zdNLka7VMfkvH0QfAW NdypQQKWxvgSlt46keI5kmwD84OepY5q5fqS/OHhTFpEqniWtfdqElDSqNCD1CXzBxth rT5YH29ggjvXpT5J29PnYH1YFtubdEku/ENNBXWfnY40S7D+7osMJsIEoZHVrsv6ud1T iEtPGVsTykNAwOKQPvQ8+hwsEoZuAlpkbySBz/XiPd40VuwaWSLEbRQH4IkuCraHDJ44 eAlVgwhEO//jk6EFRqz91unBM0v/eon2vLdUtVbRULhJrJf59u4SsRhPdCpKIb173Q+s qXuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+t9OB7YpYITCmo40A/7FMy31A5gun81q9D3BlUnY1l8=; b=PV6L5aPkJrJ7qi54VZ7P42VTbk3BN1o/pQO5LAXvQHYgd1xj80zQcYxR0q/gqEJWZs CbnGpfmnLVzg3BzNOglBa0EVhlIhsPYRSjFOAnciHj2w6hxHhcYGxkejxR6ouM89nmls wNfAEKXd+cRVkyjSUF9EnnR97khSqGZUgRTMh0I9LSTfsGiryXaEQ54cP/kB9hSxNaL0 1zsV6FhRZcJBl4/i3vVZTDKARMt+J+Y3PnSWwTtTJNddKQw/hdLCqvFwGSU62dHXmc3l rSa9O9IF/XAf1nVoz/j8mZcpvg8F/JM95/X2lMCmpd7coen4fPIrEd8F76CaKK+V0oRU XRsw== X-Gm-Message-State: AOAM5321EFVASXkhDT4Rey04J3DBlmeJq+t61wLVWmetXdutL9KRDAfX u/0GOkP2s4mFQNXt+GFoYaxffKT9911h/mwFt+ikSR6Zpl4= X-Google-Smtp-Source: ABdhPJxXbyPLBKoYFsd6xUM0Yc0y6RAAKFuDrCHFYLvdcnYRoU95va9Cq6wNBOx1yX6V0XLVF4kOnlciFqw9SNYI3jk= X-Received: by 2002:a17:90a:4d09:: with SMTP id c9mr3520411pjg.137.1592322803894; Tue, 16 Jun 2020 08:53:23 -0700 (PDT) MIME-Version: 1.0 References: <202006161535.05GFZJFn081325@gndrsh.dnsmgr.net> In-Reply-To: <202006161535.05GFZJFn081325@gndrsh.dnsmgr.net> From: Miguel C Date: Tue, 16 Jun 2020 16:52:47 +0100 Message-ID: Subject: Re: CTF: UEFI HTTP boot support To: "Rodney W. Grimes" Cc: freebsd-current X-Rspamd-Queue-Id: 49mXmP4Z0Tz4D4J X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=RPKMRxzx; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of miguelmclara@gmail.com designates 2607:f8b0:4864:20::62c as permitted sender) smtp.mailfrom=miguelmclara@gmail.com X-Spamd-Result: default: False [-2.37 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.89)[-0.891]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_HAM_LONG(-1.01)[-1.007]; URI_COUNT_ODD(1.00)[1]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::62c:from]; NEURAL_HAM_SHORT(-0.48)[-0.476]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jun 2020 15:53:26 -0000 On Tue, Jun 16, 2020 at 4:35 PM Rodney W. Grimes < freebsd-rwg@gndrsh.dnsmgr.net> wrote: > > I've been trying out FreeBSD with raspberry Pi4 (4GB) and wanted to see > > what the state of HTTP BOOT is in FreeBSD, so I bumped into this! > > > > I'm curious if it should be possible to point to a img/iso directly (I > > tried to use the img.xz unpacked it and make it available on a local web > > server and that didn't seem to work for me) but maybe thats cause those > > images miss something, so arm64 aside does that work for amd64? I.E. > using > > the bootonly.iso? > > One problem you run into in attemtping this is even if you get an > image downloaded and started that image is being provided by some > memory device driver that emulates some type of iso device. > FreeBSD does not have a driver for that device so once the kernel > gets to the point of mounting its root file system it falls on > its face with a mountroot failure. > > > > > And on the other hand is there any doc on how to set up dhcp/http > specific > > to FreeBSD similar to https://en.opensuse.org/UEFI_HTTPBoot_Server_Setup > ? > > Since Linux uses this idea of a kernel payload and an initrd payload > to boot with it is much easier to get these 2 things over the network > and then have a workable system. FreeBSD does not have the initrd > payload and that complicates things, you need a functionaly filesystem > avaliable at the end of kernel initilization. > > > > I looked into https://www.freebsd.org/doc/handbook/network-diskless.html > > but that doesn't seem to be up to date (or at least it focuses only on > PXE > > and TFTP). > > Yes, old but workable. I have a more advanced system that supports NFS > booting using NFS support in PXE. The only thing done via tftp is to > upgrade the PXE running on the client to one that speaks NFS, then the > kernel is loaded via NFS and the root file system is later provided > via NFS. The use of NFS provides very fast boots, and I do not need > a web server to do it :-). > > > For clarification my ultimate goal is to use a few pi4's as "thin > clients", > > so eventually I will have to setup an image of the system with the needed > > software (freerdp) but for starters I just wanted to check if pointing > > directly to a img/iso would work and that does not seem to be the case. > > I would strongly suggest use of NFS instead of trying to provide an > ISO image, as you no longer need to store the ISO in memory on the > client box, and with a pi4 your already memory contrained. > Thanks for the tips, but I was really looking for HTTP BOOT info no NFS, that's why I replied to this thread. I might look into that at some point if HTTP BOOT is not an option of course, but this thread is about a Call for Testers for UEFI HTTP BOOT, not NFS and I would like to help test, the pi4 project just conveniently touches on the same use case (an it also does have support for http boot using https://rpi4-uefi.dev/) so I'm curious if I can test that way. Other than the iso I can ofc attempt the dhcp+dns+webserver setup but for that I would need a bit more guidance as the linked URL here is linux centric, hence why some docs would help.