[BusyBox] built-in commands problem
Thomas Eckert
tom at uni-freiburg.de
Wed Sep 22 21:00:18 UTC 2004
On Wed, 22 Sep 2004, [ISO-8859-15] Thomas Vögtle wrote:
>
>>> Sure. It's enabled in the default config, and I take the default config
>>> + CONFIG_FEATURE_SH_STANDALONE_SHELL=y
>>>
>>> The "not found" happen to all built in commands. dmesg was one example.
>>
>>
>> have you checked your PATH? does /bin/dmesg work? (both from within
>> bb-ash)
>
> What should my $PATH look like?
contain "/bin" ...
> But on the other hand, config help says:
> "... to use busybox applets in preference to executables in the PATH whenever
> possible."
>
> So I think $PATH could even be empty.
> I tried that with busybox 0.60.5, and yes, thats ok.
in 0.60.5 there was the special option: BB_FEATURE_SH_APPLETS_ALWAYS_WIN.
according to the help-text of *_STANDALONE_SHELL in 1.00-rc3 this should
behave the same way ...
> /bin/dmesg does work.
and that /bin/demsg is the _not_ the busybox-one? if so, what if you replace
it by a symlink to busybox (both calling "dmesg" with and without FQPN from
within bb-ash)?
>> (i assume that "./busybox dmesg" works fine, right?)
>
> Yes.
good.
More information about the busybox
mailing list