right now. new address-of-packed-member and format-overflow
warnings have new GCC_NO_ADDR_OF_PACKED_MEMBER amd
GCC_NO_FORMAT_OVERFLOW variables to remove these warnings.
apply to a bunch of the tree. mostly, these are real bugs that
should be fixed, but in many cases, only by removing the 'packed'
attribute from some structure that doesn't really need it. (i
looked at many different ones, and while perhaps 60-80% were
already properly aligned, it wasn't clear to me that the uses
were always coming from sane data vs network alignment, so it
doesn't seem safe to remove packed without careful research for
each affect struct.) clang already warned (and was not erroring)
for many of these cases, but gcc picked up dozens more.
sector sizes with -S.
For this i had to recycle the -S parameter but its preserved as an extension
to the -P parameter. These parameters are hardly ever use though since using
either or both the origional -S and the -P parameter without specific values
would break the standard. Also the -F now has a double meaning.
* Add some XXXs noting where we might want to check for 16bit overflow.
* Use uintNN_t instead of int if the values is read from or written to
using udf_rwNN().
files matching *.o (!) in the list). Thanks to cube@ for spotting
what I could not see. Should fix issue with UPDATE builds across
the recent time_t merge and associated shared lib major bumps.
Use this routine both in mount_fs and rump_fs to provide equivalent
command line parameters and therefore usage interchangeability.
While doing this, combine some common mountgoop to mountprog.h
percentage to the volume space to be pre-allocated for metadata on format.
Implementations that can't extent the metadata partitions can thus use the
discs too.
Note that the kernel UDF code can't write to UDF 2.50 metadata partitions
yet; this is a work-in-progress.
Also note that the default formatting version choice is still version 2.01
i.e. without the metadata partition.
