Forum: Opóźnienie przy uruchamiamiu mc rozwiązanie.

/usr/sbin/cru: line 28: [: not found
/usr/sbin/cru: line 33: [: not found
/usr/sbin/cru: line 36: cat: not found
/usr/sbin/cru: line 28: [: not found
/usr/sbin/cru: line 33: [: not found
/usr/sbin/cru: line 36: cat: not found
/usr/sbin/cru: line 28: [: not found
/usr/sbin/cru: line 33: [: not found
/usr/sbin/cru: line 36: cat: not found
/usr/sbin/cru: line 28: [: not found
/usr/sbin/cru: line 33: [: not found
/usr/sbin/cru: line 36: cat: not found
/usr/sbin/cru: line 28: [: not found
/usr/sbin/cru: line 33: [: not found
/usr/sbin/cru: line 36: cat: not found
/usr/sbin/cru: line 28: [: not found
/usr/sbin/cru: line 33: [: not found
/usr/sbin/cru: line 36: cat: not found

config CONFIG_ASH
bool "ash"
default y
help
   Tha 'ash' shell adds about 60k in the default configuration and is
   the most complete and most pedantically correct shell included with
   busybox. This shell is actually a derivative of the Debian 'dash'
   shell (by Herbert Xu), which was created by porting the 'ash' shell
   (written by Kenneth Almquist) from NetBSD.

config CONFIG_ASH_EXPAND_PRMT
bool " Support expand PS#"
default y
depends on CONFIG_ASH
help
   "PS#" may be have commands. It option enable expand string
   from prompt before each show.

root@Asus:/tmp/home/root# opkg list_installed
bash - 4.3.42-1a
entware-opt - 222108-2
file - 5.25-1
findutils - 4.6.0-1
glib2 - 2.46.2-1
htop - 2.0.1-1
ldconfig - 2.23-5
libattr - 20160302-1
libblkid - 2.28-1
libc - 2.23-5
libcurl - 7.49.0-1
libevent2 - 2.0.22-1
libffi - 3.2.1-2
libgcc - 5.4.0-5
libiconv-full - 1.11.1-3
libintl-full - 0.19.6-2
libmagic - 5.25-1
libmount - 2.28-1
libncurses - 6.0-1b
libncursesw - 6.0-1b
libopenssl - 1.0.2h-1
libpthread - 2.23-5
librt - 2.23-5
libslang2 - 2.3.0-1
libssh2 - 1.7.0-1
libssp - 5.4.0-5
libstdcpp - 5.4.0-5
libuuid - 2.28-1
locales - 2.23-5
mc - 4.8.17-3
nano - 2.6.0-1
terminfo - 6.0-1b
transmission-daemon-openssl - 2.92-3
zlib - 1.2.8-1

Cytat

I finally realized what's actually going on when you try to use mc with TomatoUSB busybox ash (/bin/sh points to busybox binary, and it's actually busybox ash shell). I took a look at mc sources (more specifically, src/subshell/common.c), and now it's all clear. mc needs a way to know subshell current working dir in order to change its dir accordingly, so it creates a named pipe for this (subshell_pipe[WRITE]) -- to have subshell echo its CWD there after each prompt. In case of bash, it appends pwd>&subshell_pipe[WRITE];kill -STOP $$ to PROMPT_COMMAND, which gets executed before every prompt, but busybox ash doesn't use PROMPT_COMMAND, so the only way to get it done is emulating similar behaviour with PS1, and it launches this command during subshell initialization for this: precmd() { if [ ! "${PWD##$HOME}" ]; then MC_PWD=\"~\"; else [ "${PWD##$HOME/}" = "$PWD" ] && MC_PWD="$PWD" || MC_PWD="~/${PWD##$HOME/}"; fi; echo "$USER@$(hostname -s):$MC_PWD"; pwd>&subshell_pipe[WRITE]; kill -STOP $$; }; PRECMD=precmd; PS1='$($PRECMD)$ '. This can only work if PS1 is being expanded, so it needs CONFIG_ASH_EXPAND_PRMT=y busybox config, otherwise you get plain $($PRECMD)$ string as a result, and nothing executed/piped (like in case of TomatoUSB shell). What happens in the latter case, is that mc waits 10 seconds after subshell initialization for CWD to get forwarded, and when these 10 seconds expire, it silently disables the subshell.

Cytat

@PiotrC1
OK, I tried, and it works as expected. I think there's something wrong with your colleagues build. A simple way to test if CONFIG_ASH_EXPAND_PRMT=y is really set is to run this command PS1='$(echo "# ")'. If the prompt looks like this after the command:

$(echo "# ")

Then it's off. It should look like this:

#

In the config I used I only disabled deprecated 2.4 modutils stuff and emptied CONFIG_CROSS_COMPILER_PREFIX, everything else was unchanged.