busybox tar command

[bigpcman]

I'm still a bit confused about the tc tar command. If I load the bash shell extension is tar replaced with a different tar command?

[^thehatsrule^]

No, it is not.  Just run `tar` to see.

[roberts]

I have had no issue with busybox tar command. I do notice that it seems to be more sensitive to the order of the options, mainly -f should be the last option when used.

[curaga]

GNU tar is a part of advcomp.tce.

[tobiaus]

GNU tar is a part of advcomp.tce.

oh, thank you!

[florian]

After i load advcomp.tcz which contains gnu tar (among other compression utilities), /tmp/tcloop/advcomp/bin/tar really is gnu tar, however /bin/tar still points to /bin/busybox.

I thought that /bin/tar would have been replaced with a link to /tmp/tcloop/advcomp/bin/tar
Is this a bug in tce-load? or is it a feature?

[Jason W]

I see that /bin/tar is part of advcomp.tce and the rest is in /usr/local/bin.  /usr/local/bin and /usr/local/sbin are at the front of $PATH and will be the programs used even if the same one exists in /bin, /sbin, /usr/bin, /usr/sbin.  GNU tar can be placed in /usr/local/bin and it will be the tar used instead of the busybox one; no need to overwrite busybox links, just place the gnu or other apps in /usr/local/(s)bin.  This makes it easy to either use or revert to busybox commands when "real" ones are installed in /usr/local, just delete the one in /usr/local/bin or use the command "busybox tar".  The need to overwrite system commands is greatly reduced by /usr/local/bin being at the front of the PATH.

TCZ's don't overwrite existing files or symlinks and thus busybox tar is not overwritten by the tcz.