From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute via buildroot <buildroot@buildroot.org>
Cc: Fiona Klute <fiona.klute@gmx.de>
Subject: Re: [Buildroot] [PATCH 1/1] package/busybox: save shell history only on exit
Date: Mon, 21 Apr 2025 23:52:35 +0200 [thread overview]
Message-ID: <20250421235235.4a1c4bfb@windsurf> (raw)
In-Reply-To: <20250303121450.140083-1-fiona.klute@gmx.de>
On Mon, 3 Mar 2025 13:14:49 +0100
Fiona Klute via buildroot <buildroot@buildroot.org> wrote:
> From: "Fiona Klute (WIWA)" <fiona.klute@gmx.de>
>
> Both busybox.config and busybox-minimal.config set
> CONFIG_FEATURE_EDITING_SAVEHISTORY=y. This causes the Busybox shell to
> write the history file after every command, which can be a problem on
> storage with limited write cycles (e.g. eMMC).
>
> Set CONFIG_FEATURE_EDITING_SAVE_ON_EXIT=y to change behavior to write
> the history file only on exit, which reduces writes without losing the
> history feature.
>
> Signed-off-by: Fiona Klute (WIWA) <fiona.klute@gmx.de>
> ---
> Of course writes would be reduced even more by disabling history
> entirely, but "save on exit" seems like a reasonable tradeoff to
> me. It is also what Bash does, so it's unlikely to cause issues.
Makes sense, applied!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-04-21 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 12:14 [Buildroot] [PATCH 1/1] package/busybox: save shell history only on exit Fiona Klute via buildroot
2025-04-21 21:52 ` 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=20250421235235.4a1c4bfb@windsurf \
--to=buildroot@buildroot.org \
--cc=fiona.klute@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.