mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Cedric Blancher <cedric.blancher@gmail.com>
To: barebox@lists.infradead.org
Subject: Re: Booting from NFSv4 file system?
Date: Sat, 17 Feb 2024 09:01:00 +0100	[thread overview]
Message-ID: <CALXu0Uc=pG-P7_6kaqkYLEJEWHu4zCLM9XztmH3XndDGnDS2Qg@mail.gmail.com> (raw)
In-Reply-To: <a5a7596a-e9ed-42cf-9f5b-16a68235509a@pengutronix.de>

On Wed, 14 Feb 2024 at 14:54, Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:
>
> 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?

No, it's a reaction to a EOL/EOS warning that in 18 months we will not
have NFS-over-UDP support, as UDP support in NFS is depreciated since
YEARS, and NFSv2 and NFSv3 are being phased out in favor of NFSv4.

That aside many enterprises now started banning UDP based applications
wherever they can, and NFS-over-UDP with its depreciation is high on
that list. I have several customers who cannot do that anymore, and
even in Institute Pasteur it will no longer be happening in 2025.

So we need a replacement, and we need it fast.

>
> 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.

So basically in 18 months the NFS support in barebox will become useless, right?

>
> The immediate options are either using TFTP to download the kernel

But tftp requires UDP, right? There is no tftp-over-TCP, right?

> and then
> use NFS for mounting the rootfs within the kernel or to use a userspace NFS
> server.

But will it still be UDP?

> I am using NFS Ganesha at home for this.

I would prefer the JAVA NFS server from DESY, but even they no longer
support NFSv3 via UDP, only TCP.

Ced
--
Cedric Blancher <cedric.blancher@gmail.com>
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur



  reply	other threads:[~2024-02-17  8:03 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
2024-02-17  8:01   ` Cedric Blancher [this message]
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='CALXu0Uc=pG-P7_6kaqkYLEJEWHu4zCLM9XztmH3XndDGnDS2Qg@mail.gmail.com' \
    --to=cedric.blancher@gmail.com \
    --cc=barebox@lists.infradead.org \
    /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