Re: Busybox identification

El mié, 25 mar 2026 a las 14:48, Nigel Hopper via busybox (<
[email protected]>) escribió:

> Hi
>
> I work for a team that audits software. This includes Docker Images, many
> that contain Busybox. I believe all the other Linux Operating Systems use
> the os-release file to identify which version of the OS is installed.
>

> My understanding is that Busybox does not do this as it sees itself as a
> collection of utilities that ‘acts’ like an OS,
>

Busybox does not "act like an OS" at all. It is just a collection of
userspace utilities. It is not a kernel, for example.


> just in a very stripped-down way.
>
> Using the os-release file allows us to correctly identify which OS we are
> processing and how to ID all the packages in it.
>
> Is there any way Busybox can be identified as being the 'installed OS’
> other than if it was listed in an os-release file?
>

Busybox is just a collection of utilities -- it is not an "installed OS" in
any meaningful way.

Also note that "Busybox is installed on this system" alone is probably not
very helpful: you can configure Busybox in many different ways, it can
provide just some utilities but not others, etc.

For each individual utility that Busybox may provide (e.g. "ls"), the
actual ls in the system may be the one provided by Busybox, or it may be
provided by other packages (in the case of ls, this would probably be
coreutils). So the fact that "Busybox is installed" does not really tell
you which utilities are actually provided by Busybox.

And even for utilities that _are_ actually provided by Busybox, these may
have been configured in many ways as well (see config options for each
applet).


>
> It would significantly make our processing much simpler.
>

I am afraid it will not be possible to make your processing simpler in the
way you expect.

Guillermo

-- 
Guillermo Rodriguez Garcia
[email protected]

_______________________________________________
busybox mailing list
[email protected]
https://lists.busybox.net/mailman/listinfo/busybox