On 8/19/2013 12:15 PM, Felix Miata wrote:
On 2013-08-19 10:34 (GMT+0200) Joerg Schilling composed:
Rajko wrote:
Joerg Schilling wrote:
This is definitely no output from the original "tar" but a clone.
That is BusyBox, used by openSUSE during installation. http://www.busybox.net/about.html
The OP does not seem to understand that with beginning to write star in 1982, "tar" is not the name of a single program but that there are more such implementations.
I (OP) have seen no such discussion in any docs. When looking up tar, such as in a Linux reference manual (e.g. ISBN: 0-7821-2735-5 or 0-7821-2341-4), tar --help, or man tar, there's been no explicit or implicit mention that tar is anything but GNU tar, no direct or indirect mention of gtar or star posing as tar. The man page does mention a utar format, but doesn't say why it might be needed or desired. I've seen nothing prior to this thread to imply one should expect a tar file created by an x86 Linux system's installed by default tar command using the most common tar options shouldn't be expected to be extracted without special options by the installed by default tar command on another x86 Linux system, including one that substitutes busybox for a shell and individual binary tools like tar.
OK I know Joerg was being a little intentionally obtuse as if he never heard of a set top box or other situation where it's not practical to compile or even install anything, asking why don't you just install star etc, but so is this. If you really never encountered a tar incompatibility before then your experience differs from mine. I would never be surprised when when default tar with default options turns out to be incompatible between implementations. gtar is gnu tar, which is just one of many different tars out there, including busybox, including other unix-like os's, including mks tools on windows, etc etc. So your set top box runs "linux", but that doesn't mean anything beyond the kernel. It's a set top box, and as is absolutely typical for embedded and appliances, it's system is not the same as a regular full desktop system and it's "tar" is really just the minimal barely useful implementation in busybox. Just like it's sh is probably not bash but ash, and many common things that work on a desktop will not work exactly the same if tried on that appliance. Stephan said it right the first time. You just need to tell gtar* to specially create a file that an older or simpler tar implementation will understand. It's normal to try the defaults first of course, and it's annoying to encounter the incompatibility, but it's not even remotely a surprise when it turned out to require some special handling in a case like this. * (yes, you are running gtar whether it says so or not, yes a user as long experienced as you is expected to know that, just like sh is really bash on every normal linux system, and just as with tar, on your set top box sh is probably NOT bash but most likely ash) This is all true of practically all of the core unix utils. There are many awks, many finds, many seds, etc... The ones on linux desktops are ususally gnu, so awk is really gawk, installed as /usr/bin/awk, and it's pretty different from anyone elses's awk, and it's even pretty different from the awk on a "linux" system that happens to be specially constructed, ie an appliance, ie probably using busybox for everything although busybox is not the only place such special versions come from either. -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org