mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Cedric Blancher <cedric.blancher@gmail.com>, barebox@lists.infradead.org
Cc: Dan Shelton <dan.f.shelton@gmail.com>
Subject: Re: Booting from NFSv4 file system?
Date: Wed, 14 Feb 2024 14:54:53 +0100	[thread overview]
Message-ID: <a5a7596a-e9ed-42cf-9f5b-16a68235509a@pengutronix.de> (raw)
In-Reply-To: <CALXu0UeQAXPGuuEqT-buX5o_H7YbSdUYqkpyP7i1d5yc55xcfQ@mail.gmail.com>

Hello Ced,

On 13.02.24 08:51, Cedric Blancher wrote:
> Good morning!
> 
> Does Barebox support booting from a NFSv4 file system? Explicitly
> neither NFSv2 or NFSv3 will work in our case, as both protocol
> versions are no longer allowed by our IT department.

It's a funny coincidence that the same question was asked just a few
days earlier:

 https://lore.barebox.org/barebox/CAAvCNcByUskEuqLMPmO6mbCOZHhYNx_OXZKYO+HKyz_=Cs2RCQ@mail.gmail.com/T/#t

Do you and Dan both perhaps use the same Enterprise Linux that now ships without
UDP support in the kernel NFS server?

To sum up the other thread: We don't have a TCP stack in barebox, but that's a
hard requirement to do NFSv4. There's AFAIK no one currently working on this.

The immediate options are either using TFTP to download the kernel and then
use NFS for mounting the rootfs within the kernel or to use a userspace NFS
server. I am using NFS Ganesha at home for this.

Cheers,
Ahmad

> 
> Ced

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |




  reply	other threads:[~2024-02-14 13:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13  7:51 Cedric Blancher
2024-02-14 13:54 ` Ahmad Fatoum [this message]
2024-02-17  8:01   ` Cedric Blancher
2024-02-17  9:12     ` Ahmad Fatoum

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=a5a7596a-e9ed-42cf-9f5b-16a68235509a@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=cedric.blancher@gmail.com \
    --cc=dan.f.shelton@gmail.com \
    /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