SliTaz SliTaz Forum

You are not logged in.

#1 2019-05-19 10:58:00

Darjeeling
Member
Registered: 2012-02-06
Posts: 210

"wc -m" bug

There are errors in last night's rolling boot.log:

[c]Switching / to tmpfs...
Done
Processing /etc/init.d/rcS...
wc: invalid option -- 'm'
BusyBox v1.12.0 (2010-03-12 18:25:03 CET) multi-call binary

Usage: wc [OPTION]... [FILE]...

Print line, word, and byte counts for each FILE, and a total line if
more than one FILE is specified. With no FILE, read standard input.

Options:
    -c    Print the byte counts
    -l    Print the newline counts
    -L    Print the length of the longest line
    -w    Print the word counts[/c]
The same thing occurs 11 times in boot.log. So, I looked around and found that ...

[c]/lib/libtaz.sh
/usr/libexec/tazpkg/search
/usr/libexec/tazpkg/upgrade[/c]
... contain the faulty "wc -m" statement.

Offline

#2 2019-05-20 07:50:57

bellard
Administrator
Registered: 2011-03-28
Posts: 657

Re: "wc -m" bug

You should update busybox:

tux@slitaz:~$ busybox | head -n1

BusyBox v1.30.1 (2019-05-04 15:00:17 CEST) multi-call binary.

Offline

#3 2019-05-20 17:36:34

Darjeeling
Member
Registered: 2012-02-06
Posts: 210

Re: "wc -m" bug

... oh no! I had completely forgotten about some old stuff I put in my test tree the previous day and then built a new iso with it. That was really stupid, especially because after much research I still couldn't see the obvious, that I had overwritten busybox with a much older version. But it won't happen again, promise!

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.017 seconds, 8 queries executed - Memory usage: 1.53 MiB (Peak: 1.77 MiB) ]