Re: Busybox identification
tito via busybox <[email protected]>
| Newsgroups | gmane.linux.busybox |
|---|---|
| Message-ID | <20260327081816.36cc0b1e@devuan> |
On Thu, 26 Mar 2026 22:14:44 -0500 Jeff Pohlmeyer via busybox <[email protected]> wrote: > On Thu, Mar 26, 2026 at 8:13 PM Laurent Bercot via busybox > <[email protected]> wrote: > > This thread is bananas. > > Run "busybox", without options or arguments. > > If your shell gives you an error, you have no busybox binary in your PATH. > > If your shell returns success, you have a busybox available in your PATH, > > That is not 100% reliable, it depends on the option CONFIG_BUSYBOX: > > The busybox applet provides general help message and allows the > included applets to be listed. It also provides optional --install > command to create applet links. If you unselect this option, running > busybox without any arguments will give just a cryptic error message > > $ busybox > busybox: applet not found > Symbol: BUSYBOX [=y] > Prompt: Include busybox applet > > -- Jeff > Hi, don't forget that the busybox binary itself could be renamed to a command: mv busybox ls ./ls busybox busybox so to be sure you must add a symbolic link to every binary on system: ln -s ls busybox ./busybox BusyBox v1.38.0.git (2026-03-27 07:46:44 CET) multi-call binary. BusyBox is copyrighted by many authors between 1998-2015. Licensed under GPLv2. See source distribution for detailed copyright notices. Also notice that if CONFIG_FEATURE_COMPRESS_USAGE=y is set i suspect that the string "BusyBox v1.38.0.git (2026-03-27 07:46:44 CET) multi-call binary." is not detected by strings command: strings busybox | grep "Busybox" as it is decompressed at runtime. Ciao, Tito _______________________________________________ busybox mailing list [email protected] https://lists.busybox.net/mailman/listinfo/busybox