Fix for the /opt/bin/update-alternatives problem!!!

[Rejan]

Hi Sollie, tried ln -s /opt/bin/busybox head /opt/bin/head but got file exist, even after rm /opt/bin/head

Editing the the file /opt/bin/update-alternatives with qualified path to head was the thing that helped.

After editing I did the /opt/lib/ipkg/info/busybox-links.postinst, checked everything and did a ipkg upgrade and all linked well and works again.

Rejan.

[sollie]

Hi Sollie, tried ln -s /opt/bin/busybox head /opt/bin/head but got file exist, even after rm /opt/bin/head

Thats what it says all the time, but its making the file.

Sollie.

[Rejan]

Hi Sollie, even though the file is made, the postinst-file didn't work until I did a fully qualified path in update_alternatives.

The link still defaults to the old busybox, easy way to test is to write the command: head-? and check versioninfo on Busybox. That was how I found out that it defaulted wrong version of Busybox.

[sollie]

K, thanks.

Sollie.

[Faw]

Ok, I've tried everything time to ask.

I have the same problem, syntax error in update-alternatives.
I tried everything on this post, and still nothing.

Right now, if I type 'head -?' I get the 'error while loading shared libraries'
if I type '/opt/bin/head -?' I get 'Busybox v1.7.2 blah,blah,blah' so I guess that's ok.

I changed the /opt/bin/update-alternatives line from:
local olink=`head -n 1 $ad/$name`
to:
local olink=`/opt/bin/busybox head -n 1 $ad/$name` and
local olink=`/opt/bin/head -n 1 $ad/$name`

and neither worked. Help please?

BTW, 'ln -s /opt/bin/busybox head /opt/bin/head' gave me an error message, 'ln -s /opt/bin/busybox /opt/bin/head' worked ok.

[Rejan]

Did you use full path as I described it:
local olink=`$IPKG_OFFLINE_ROOT/opt/bin/busybox head -n 1 $ad/$name`

Also

'ln -s /opt/bin/busybox head /opt/bin/head' gave me an error message, 'ln -s /opt/bin/busybox /opt/bin/head' worked ok.

The last one I think links busybox to the command /opt/bin/head instead of command '/opt/bin/busybox head' to '/opt/bin/head' which seems like a bad idea. So the linkname for you will be wrong according to syntax, or?

Usage: ln [OPTION] TARGET... LINK_NAME|DIRECTORY

Rejan.

[Gizmo1007]

Just to confirm,

The problem is "Syntax error" comes up when installing / running some busybox commands particularly at configuration of ipkg installs correct?

when you complete the tasks as defined by Sollie and Rejan is the expected output as per below?

update-alternatives: Linking //opt/sbin/losetup to /opt/bin/busybox
update-alternatives: Linking //opt/sbin/lsmod to /opt/bin/busybox
update-alternatives: Linking //opt/sbin/mkswap to /opt/bin/busybox
update-alternatives: Linking //opt/sbin/modprobe to /opt/bin/busybox
update-alternatives: Linking //opt/sbin/pivot_root to /opt/bin/busybox
update-alternatives: Linking //opt/sbin/rdate to /opt/bin/busybox
update-alternatives: Linking //opt/sbin/rmmod to /opt/bin/busybox
update-alternatives: Linking //opt/sbin/route to /opt/bin/busybox
update-alternatives: Linking //opt/sbin/start-stop-daemon to /opt/bin/busybox
update-alternatives: Linking //opt/sbin/swapoff to /opt/bin/busybox
update-alternatives: Linking //opt/sbin/swapon to /opt/bin/busybox
update-alternatives: Linking //opt/sbin/sysctl to /opt/bin/busybox

One suggestion for those of you struggling to get this going is to do an install of uclibc-opt first, then reinstall busybox and then do the edits per sollie's info

[Faw]

Finally! Thanks everyone for the help.

The last one I think links busybox to the command /opt/bin/head instead of command '/opt/bin/busybox head' to '/opt/bin/head' which seems like a bad idea. So the linkname for you will be wrong according to syntax, or?

Usage: ln [OPTION] TARGET... LINK_NAME|DIRECTORY

Rejan.

I tested it and it works: ln -s /opt/bin/busybox /opt/bin/head
It seems busybox checks the arg[0] (program name, in this case head) to see the command. If I create that link I get the correct help:

Busybox 1.7.2 ....
Usage head [OPTION] ...