From owner-freebsd-current@freebsd.org Tue Jun 16 16:24:07 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 9742934177B for ; Tue, 16 Jun 2020 16:24:07 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) (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 49mYRp61FBz4HXr for ; Tue, 16 Jun 2020 16:24:06 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: by mail-lj1-x230.google.com with SMTP id c17so24282575lji.11 for ; Tue, 16 Jun 2020 09:24:06 -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=GXarinitELuZHopucU0QZprgRSmkxRZcpI7hXA4N1dU=; b=I2u9QvoeQRt9E7gg4yEcLa7nGnnwqew3LSMGJ8Bqhst5t3qDNO+2kFCjoYIvGls6t3 LURjN6NVlr/6kmGhG+fAv3maUEcG4be6RmEbpeULRZCXRxOIFMmtOK4cLrBXbS6K+Z3v IxXwZG3NNMSlleYtjRClLERXEdIr1nmNRItmtSlg8gGv/CzKumw2eIfqshvZQ+k8AQ6x 8gBpdDpVwbTu+oTr5FDKLFFOX/jde8nHesmfzXuiVwutxqdmzchoLb6YcECoLBwCfFEq y5fGbf6mDjWKKUj5MRB7F4S2+ikXog36XoodCxv2b3ZXH1uJLxXMLUGYCkscWD95xbB7 0gQQ== 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=GXarinitELuZHopucU0QZprgRSmkxRZcpI7hXA4N1dU=; b=TU9Qjc5qRweGM/EoUzbmqJuoY/dTPqnwJ06UShylfnRDFHms2Dsh6OJvPhtgLpFdyI 3Gww2PeWFfMlgaFKNQaTOKzJX515AsHYEo4nlLMelhJm+iU844vDHldTzq6RmfX41wPx ozhn0KaQYSnCr+3cPc8TTUTnECKeCEHxnsO04Dd3qbIlJTjvTy7wVAaIHLvhWhNAmB2F TImywsEKImpppWmI4Fj4yBg6HWjoT0ri/WXi/uPE7TZTb72zISbxHdUeM658F5GzFEJ9 Ei/Cy3qXpbKp7qW2KHwHLcBBALV2xI36wjtNaOVQVaU3XpOBk0Iv2xHa+52RZR6lYGq6 isAw== X-Gm-Message-State: AOAM530cQjMqf6YgH41vrf40MbzlZ1v7plZYZthccLA4dwFUL3L9Eeq3 2U7KrTIFMi4NkNecbshlSop5BwrOtidpI4Uo/S4p9OZx X-Google-Smtp-Source: ABdhPJyCsYcoLyVJW3GOhBnsgJ6BgvqEkMbSGXPJFLxYVgDvwqjLAQKp8bsxGRvyxw8EJtPUkER0IVpvG+H7p6KXC7Q= X-Received: by 2002:a2e:9dcd:: with SMTP id x13mr2013859ljj.465.1592324643948; Tue, 16 Jun 2020 09:24:03 -0700 (PDT) MIME-Version: 1.0 References: <202006161535.05GFZJFn081325@gndrsh.dnsmgr.net> In-Reply-To: From: Andreas Nilsson Date: Tue, 16 Jun 2020 18:23:51 +0200 Message-ID: Subject: Re: CTF: UEFI HTTP boot support To: Miguel C Cc: "Rodney W. Grimes" , freebsd-current X-Rspamd-Queue-Id: 49mYRp61FBz4HXr X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=I2u9Qvoe; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of andrnils@gmail.com designates 2a00:1450:4864:20::230 as permitted sender) smtp.mailfrom=andrnils@gmail.com X-Spamd-Result: default: False [-3.77 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.86)[-0.860]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_HAM_LONG(-1.01)[-1.008]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::230:from]; NEURAL_HAM_SHORT(-0.91)[-0.907]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; 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 16:24:07 -0000 On Tue, Jun 16, 2020, 17:53 Miguel C wrote: > 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. > > > Am I just misremembering or can't you get freebsd to load an mfsroot-image, which can act as rw fs ? I seem to remember pc-bsd DVDs using this say 7 years ago. You would of course have to modify/build your own iso image with the mfsroot-image on it. Best regards Andreas