From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: stephan@asklandd.dk
Cc: buildroot@buildroot.org,
Giulio Benetti <giulio.benetti@benettiengineering.com>
Subject: Re: [Buildroot] [PATCH 2/2] package/util-linux: fix mount helper lookup path
Date: Sat, 10 Oct 2026 22:34:34 +0200 [thread overview]
Message-ID: <asqhIhzhU4O5knwN@windsurf> (raw)
In-Reply-To: <20260314232106.2944800-1-stephan@asklandd.dk>
Hello Stephan,
On Sun, Mar 15, 2026 at 12:21:05AM +0100, stephan@asklandd.dk wrote:
> From: Stephan Henningsen <stephan@asklandd.dk>
>
> When using /bin/mount to mount filesystems that are not supported
> directly by the kernel, it delegates the mount operatin to helper
> programs, e.g. mount.fuse.sshfs. Normally /bin/mount searches
> these directories in order for a helper: /sbin, /sbin/fs.d, /sbin/fs.
>
> In reality, Buildroot installs e.g. mount.fuse.sshfs into /usr/sbin,
> and as a result /bin/mount fails to mount sshfs entries defined in
> /etc/fstab.
>
> The patch changes the default search path at configuration.
>
> Signed-off-by: Stephan Henningsen <stephan@asklandd.dk>
Sorry for the delay, I've now applied your patch. I hesitated a bit
between your patch and --enable-fs-paths-extra=/usr/sbin (perhaps only
when MERGED_USR is disabled), but oh well your patch is simple and
straightforward, so I went for it.
Thanks a lot!
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-10 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 23:21 [Buildroot] [PATCH 2/2] package/util-linux: fix mount helper lookup path stephan
2026-10-10 20:34 ` Thomas Petazzoni via buildroot [this message]
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=asqhIhzhU4O5knwN@windsurf \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=stephan@asklandd.dk \
--cc=thomas.petazzoni@bootlin.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