[arch-releng] [RFC] [PATCH] [archiso] Switch from cdrkit to libisoburn

[Gerardo Exequiel Pozzi]

On 08/28/2011 09:41 PM, Sven-Hendrik Haase wrote:
> On 29.08.2011 01:27, Gerardo Exequiel Pozzi wrote:
>> On 08/28/2011 06:03 PM, Sven-Hendrik Haase wrote:
>>> On 28.08.2011 22:27, Gerardo Exequiel Pozzi wrote:
>>>> On 08/28/2011 02:26 PM, Sven-Hendrik Haase wrote:
>>>>> On 28.08.2011 19:07, Gerardo Exequiel Pozzi wrote:
>>>>>> On 08/12/2011 03:08 PM, Gerardo Exequiel Pozzi wrote:
>>>>>>> * Preparing terrain for UEFI support.
>>>>>>> * Also make isohybrid hack in one step.
>>>>>>> * Removed UDF layer, since xorriso does not support it.
>>>>>>> * Removed unsupported options by xorriso
>>>>>>> (-uid/-gid/-allow-limited-size)
>>>>>>> * Removed option already default in xorriso (-input-charset utf-8)
>>>>>>>
>>>>>>> Signed-off-by: Gerardo Exequiel Pozzi<vmlinuz386 at yahoo.com.ar>
>>>>>>> ---
>>>>>>>      README                    |    9 ++++-----
>>>>>>>      archiso/mkarchiso         |    9 ++++-----
>>>>>>>      configs/baseline/build.sh |    1 +
>>>>>>>      configs/releng/build.sh   |    1 +
>>>>>>>      4 files changed, 10 insertions(+), 10 deletions(-)
>>>>>>>
>>>>>> Is there any objections about this? xorriso is currently used by
>>>>>> archboot and works fine. Images generated looks good.
>>>>>>
>>>>> Will this still work with filesystem images that are over 4GiB?
>>>>>
>>>> The issue about you talk is with file size inside the filesystem (ISO
>>>> 9660), (2^32 - 1 bytes = 4GiB minus one hair)
>>>> But we are using "level 3", so this limitation is not an issue, since
>>>> files bigger than 4GiB will use multi-extent feature, the new limit is
>>>> 8TiB per file :)
>>>>
>>>> Just for test, this is a proof of concept:
>>>>
>>>> # mkdir /tmp/big-test
>>>> # cd /tmp/big-test
>>>> # for x in {1..5}; do dd if=/dev/urandom of=data${x}GiB bs=1M
>>>> count=$((x*2**10)) ; done
>>>> # md5sum data*>   checksum.md5
>>>> # xorriso -as mkisofs -v -r -l -iso-level 3  -o ../trance.iso .
>>>> # mount ../trance.iso /mnt
>>>> # cd /mnt
>>>> # md5sum -c checksum.md5
>>>> data1GiB: OK
>>>> data2GiB: OK
>>>> data3GiB: OK
>>>> data4GiB: OK
>>>> data5GiB: OK
>>>> #
>>>>
>>>> Ready to burn on blu-ray :P
>>>>
>>> Sounds good, this is actually relevant to me as I have an Arch-based
>>> distribution that mounts an image with a size>   4GiB.
>>>
>> Cool. I know about lglive (you made a nice good work).
>>
>> I ask to you, because some time ago you added UDF support. If it was
>> added only for this, as you can see, can be dropped.
>>
>> Thanks for the feedback.
>>
> Indeed, it can be dropped then. Come to think of it, are there any plans
> to use some kind of union fs like UnionMount (the linux kernel mainline
> union fs) or aufs3 (linux 3 aufs) again in Archiso?
>
OK.

I some of these goes to mainline, maybe.
You know the history, every year appears a new kind of union 
mount/filesystem, but is rejected for mainline. There is a new "promise" 
for linux-3.2, but who knows...

-- 
Gerardo Exequiel Pozzi
\cos^2\alpha + \sin^2\alpha = 1