[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Writing to ISO file again with different Paras creates old version
From: |
sean loony |
Subject: |
Writing to ISO file again with different Paras creates old version |
Date: |
Fri, 28 Feb 2020 08:46:20 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 |
Hello,
I don't know if this is a bug but its quite strange:
I create a ISO-file with xorriso. After deleting the iso-file
and changing some path paras the content of the new iso should be
different but the file looks like it was created with the old
options.
E.g.:
xorriso \
-abort_on FATAL \
-for_backup -disk_dev_ino on \
-dev /tmp/my.iso \
-disk_pattern on \
-update_l /foo/bar test1 /foo/bar/boo
-- -commit
This creates a ISO with
a dir test1 and the files from /foo/bar/boo
1. After creation I delete the iso file.
2. Now I change test1 to test2:
xorriso
..same as above... \
-dev /somewhere/my.iso -update_l /foo/bar test2 /foo/bar/boo
..same as above
This should give me a ISO with a dir
test2 and the files from /foo/bar/boo
But I get an ISO with
test1 and the files from /foo/bar/boo
!!??
I figured out if I waited a few minutes with step 2 it works.
If I change the file name of the iso everytime it works immediatelly:
use
-dev /somewhere/my_${RANDOM}.iso
for automatic different file name. $RANDOM is a bash variable and
creates a random number.
Does xorriso use some old tempfiles here or whats wrong?
My Version of xorriso is:
xorriso -version
xorriso 1.4.8
xorriso version : 1.4.8
Version timestamp : 2017.09.12.143001
Build timestamp : -none-given-
libisofs in use : 1.4.8 (min. 1.4.8)
libjte in use : 1.0.0 (min. 1.0.0)
libburn in use : 1.4.8 (min. 1.4.8)
libburn OS adapter: internal GNU/Linux SG_IO adapter sg-linux
libisoburn in use : 1.4.8 (min. 1.4.8)
Tested on ubuntu 18.0.4.4 64-Bit.
- Writing to ISO file again with different Paras creates old version,
sean loony <=