On Sunday 03 April 2011 23:51, Tomasz Czapiewski wrote: > > So, what is your shell? > > In TV it's BusyBox 1.18.4 ash > On PC it's bash 4.1.5 > > > > > > >>> Can you run this: > >>> > >>> ls -Qlan /tmp | grep '^[^cbt]' | ( while read p x u g s m d y n; do echo > >>> "P$p $u.$g > >>> S$s > >>> d$m $d $y > >>> :$n > >>> "; done ) >LOG > >>> > >>> and post resulting LOG file? > >> > >> Looks ok to me: > >> http://pastebin.com/hGhZUgrV > > > > Can you send it as an attachment? Trailing spaces can be mangled by > > pastebin.com > > > > -- > > vda > > > > > > Ok, output from commands on both machines in attachements.
They both look strange: TONS of whitespace on each line. I can't reproduce it. I suspect you added whitespace by cut-n-pasting the script. IOW: instead of S$s line, you have S$s<122 space chars> line, and similarly for other lines in the script. (Otherwise, I must conclude that _both_ bash and ash are buggy, and for some reason they are buggy only on your machine, they work fine for me - not very likely theory!) > I can get logs from BusyBox hush in TV or dash in PC if you want them, > too. > > But, as I've said the problem was on PC exactly the same when perl was not > available and MC used 'ls -Qlan' output from coreutils, command executed > on bash. > Midnight Commander team already fixed the issue there in later versions. -- vda _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
