

neko wrote: ↑12 Mar 2019, 13:18[ operation of replacing vmlinuz & 000-kernel.xzm ]Code: Select all
% su # ls 64bit-kernel5.0.1-RTSX_USB.tar Porteus-CINNAMON-v4.0-x86_64-19.01.12.iso # mkdir mnt # mount -t iso9660 -o loop Porteus-CINNAMON-v4.0-x86_64-19.01.12.iso mnt # mkdir NEW # cp -a mnt/* NEW/. # cp -a /mnt/.[0-9A-Za-z]* NEW/. 2>/dev/null # umount -f mnt # rm -fr mnt # # mkdir w # cd w # tar -xf ../64bit-kernel5.0.1-RTSX_USB.tar # cd ../ # mv w/vmlinuz NEW/boot/syslinux/ # mv w/000-kernel.xzm NEW/porteus/base/ # # mkisofs -o NEW.iso -v -l -J -joliet-long -R -D -A Porteus -V Porteus \ -no-emul-boot -boot-info-table -boot-load-size 4 \ -b boot/syslinux/isolinux.bin -c boot/syslinux/isolinux.boot NEW # rm -fr NEW w # ls 64bit-kernel5.0.1-RTSX_USB.tar NEW.iso Porteus-CINNAMON-v4.0-x86_64-19.01.12.iso
Code: Select all
+ tar -xf ../64bit-ALL-kernel5.4.18.tar
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors

I assume the problem is due to this.
So what is the tar command's replacement code?

-update-
The tar -z option doesn't resolve it.
Code: Select all
root@porteus:/tmp# tar -xfz /tmp/*.tar
tar: z: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
root@porteus:/tmp# ls /tmp
64bit-ALL-kernel5.4.18.tar
Code: Select all
guest@porteus:~$ tar -I zstd -xf /tmp/*.tar
zstd: /*stdin*\: unsupported format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
guest@porteus:~$

Nor this.
Code: Select all
guest@porteus:~$ tar -axf /tmp/*.tar
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors
guest@porteus:~$