3
I've received a Tar/GZipped file that was created on an embedded Linux device.
The file can be extracted perfectly fine on a Linux desktop if I run something like tar zxf myFile.tgz
. The file extracts to something like
dir1/
file1
file2
dir2/
file1
file2
subdir1/
file1
...but I suspect the specific file content and layout are irrelevant.
When I try to extract this same file in Windows (using either 7-Zip or WinZip), I get:
myFile/
<extensionless file with temp-looking name e.g. "logs_xqUt09">
It's probably relevant that that top-level directory happens to be named "myFile
" when the .tgz
I received is itself named myFile.tgz
...but I don't know with certainty that it's anything more than coincidental.
I browsed SuperUser a bit, and found a few related issues, one of which suggested that 7-Zip handles .tgz
files better than WinZip, but apparently not in this situation.
Does anyone know what gives? Why would a .tgz
be fully extractable under Linux but not Windows? What workarounds might there be?
If I rename that extensionless file to a .tar
file, then that .tar
file is extractable with 7-Zip and/or WinZip.
I'd still like to understand what's going on, and if there's a workaround that doesn't involve that manual file renaming, because ideally the original .tgz
file delivered by the embedded device should be extractable under Linux and Windows.
There is WSL and
Starting with version 1803, Windows 10 is adding native support for tar
– LotPings – 2019-04-03T00:20:00.910