Updated change log and web page

master
Thomas Schmitt 7 years ago
parent 8b3a1a51cc
commit febce317a6
  1. 2
      ChangeLog
  2. 76
      xorriso/changelog.txt
  3. 10
      xorriso/xorriso_eng.html

@ -2,6 +2,8 @@
SVN trunk (to become libisoburn-1.4.4 or higher)
===============================================================================
* Bug fix: -as mkisofs did not unescape "\=" in the source part of pathspecs
* Bug fix: -boot_image "any" "system_area=/dev/zero" did not zeroize loaded
data
* Bug fix: -pathspecs "on" did not properly handle "\\="
* New -pathspecs mode "as_mkisofs"

@ -17124,33 +17124,75 @@ xorriso/misc_funct.c
Bug fix: -pathspecs "on" did not properly handle "\\="
[]
09 Dec 2015 [5633]
ChangeLog
xorriso/xorriso_eng.html
xorriso/changelog.txt
Updated change log and web page
------------------------------------ cycle - xorriso-1.4.3 -
------------------------------------ cycle - xorriso-1.4.3 - 2015.12.09.162402
* Bug fix: -as mkisofs did not unescape "\=" in the source part of pathspecs
* Bug fix: -pathspecs "on" did not properly handle "\\="
* New -pathspecs mode "as_mkisofs"
Dec 2015 []
10 Dec 2015 [5635]
configure.ac
xorriso/configure_ac.txt
acinclude.m4
Checking for availability of LIBBURN_ARCH_LIBS
>>> xorriso must warn like libburn does , >>> *-to-come
2015.12.11.120319 [5636]
xorriso/xorrisoburn.h
Forgot to commit declaration of Xorriso_graftable_pathspec() in rev 5631
[]
15 Dec 2015 [5637]
configure.ac
xorriso/configure_ac.txt
acinclude.m4
Following build system changes in libisofs about ACL and xattr
2015.12.22.133736 [5638]
xorriso/xorriso_timestamp.h
Setting timestamp of experimental xorriso-1.4.3 tarball
------------------------------------ cycle - xorriso-1.4.3 - 2015.12.22.133736
2015.12.23.112013 [5639]
xorriso/xorriso_private.h
xorriso/base_obj.c
xorriso/opts_a_c.c
xorriso/drive_mgt.c
xorriso/iso_img.c
xorriso/write_run.c
Bug fix: -boot_image "any" "system_area=/dev/zero" did not zeroize loaded data
2015.12.24.080343 [5640]
xorriso/iso_img.c
El Torito load size 0 what not shown with -report_el_torito as_mkisofs or cmd
2015.12.26.090812 [5641]
xorriso/iso_img.c
Silencing a false warning of gcc on Sid about uninitialized "image" variable
26 Dec 2015 [5642]
xorriso/make_xorriso_standalone.sh
Updated the production script for GNU xorriso to work with plain repo checkouts
26 Dec 2015 [5643]
xorriso/make_xorriso_standalone.sh
Letting production of GNU xorriso ignore failure of command "man -H"
27 Dec 2015 []
ChangeLog
xorriso/xorriso_eng.html
xorriso/changelog.txt
Updated change log and web page
------------------------------------ cycle - xorriso-1.4.3 -
------------------------------------ cycle - xorriso-1.4.3 - 2015.12.27.150821
* Bug fix: -boot_image "any" "system_area=/dev/zero" did not zeroize loaded data
[]
ChangeLog
@ -17179,7 +17221,27 @@ the list in file doc/grub-mkrescue_reserved_commands.txt
Current pending changes:
(none)
>>> check whether the flat assumption of GPT block size 512 can do harm
>>> Issue warning if -hfsplus is "off" and -report_system_area as_mkisofs
does not find any blessings.
>>> Report HFS+ blessings with -report_system_area "plain" ?
>>> SuSE does EFI -boot-load-size 1.
Shall xorriso do so with oversized EFI partition ?
>>> HFS+ problems on coverty VM
# mount /dev/sdb3 /mnt/hfs
# ls /mnt/hfs
ls: reading directory /mnt/hfs: Input/output error
System boot empty-file.txt mach_kernel
[ 359.020970] hfsplus: walked past end of dir
# mount -o loop /dev/sdb /mnt/iso
# ls /mnt/iso
System boot boot.catalog efi.img empty-file.txt mach_kernel
---------

@ -659,6 +659,16 @@ cdrecord and mkisofs.</DT>
<UL>
<LI>-as mkisofs did not unescape "\=" in the source part of pathspecs</LI>
<LI>-pathspecs "on" did not properly handle "\\="</LI>
<LI>-boot_image "any" "system_area=/dev/zero" did not zeroize loaded data</LI>
<LI>HFS+ production could cause MBR partition of type 0xEE without GPT</LI>
<LI>HFS+ directories could announce more children than they actually have</LI>
<LI>The HFS+ filesystem was not marked by in GPT of GRUB2 hybrid layout</LI>
<LI>When reading an ISO filesystem, the presence of --protective-msdos-label
was not recognized if a partition is appended</LI>
<LI>
xorrisofs option --protective-msdos-label did not work if no system partition
data were given by option -G or alike.
</LI>
<!--
<LI>- none yet -</LI>
-->

Loading…
Cancel
Save