Hi Jörg, ?? <feng.w...@aaadisc.com> wrote:
>> I know that some tools like mkisofs could make files to a udf image directly >> with efficient size. However the size created by mkisofs could be larger >> than the media size. What's more, the udf filesystem made by mkisofs is a >> UDF hybrid and not a UDF only filesystem. > Why do you have a problem with a hybrid? > This usually does not increase the size in a way that is relevant. I once used mkisofs but it did not support uid and gid. Now I update it to the latest version (3.02a09), this problem is resolved. But I find the Chinese characters (UTF-8 charset) are not supported very well. The commands I used are the following. root@Ubuntu:~# ls long-name/ 中.1 中中.2 中中中.3 中中中中.4 中中中中中.5 中中中中中中.6 ... ... root@Ubuntu:~# /opt/schily/bin/mkisofs -UDF -o a.udf ./long-name Setting input-charset to 'UTF-8' from locale. Total translation table size: 0 Total rockridge attributes bytes: 0 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 507 extents written (0 MB) root@Ubuntu:~# mount ./a.udf /mnt mount：块设备 /root/a.udf 写保护，将以只读方式挂载 root@Ubuntu:~# ls /mnt 中.1 中中.2 中中中#00A6._ 中中中中_#D14D 中中中中中_#7C02 中中中中中中_#8F1A ...... We can see that some filenames cannot be read correctly. >> So is there a rational method to get the rough size of a UDF image file to >> be created if we know the directory tree and sizes of files needed to be >> burned? I think 10% larger size overhead could be acceptable. > I recommend to use mkisofs, as this creates a proper readonly UDF. > mkisofs -UDF -print-size > gives you the size. Well that's what I want. It's really useful feature. Does it count the size of entries? I mean that one directory may have thousands small files. The directory's entry size cannot be negligible. ------------------ WF
