https://bugs.kde.org/show_bug.cgi?id=379268
--- Comment #30 from Thomas Schmitt <scdbac...@gmx.net> --- Hi, Łukasz wrote: > I don't see files from first session at all when mount with -t udf. Aha. That's like with my kernel if i mount with -t udf, or no -t at all. > I see them crippled when KDE automounts this disc. I wonder what mount options it uses at this occasion. (Is the filesystem then reachable by other programs or does only K3B show it ? Maybe it is not mounted but K3B rather has an own UDF reader.) > I see them properly with -t iso9660, despite the filesystem is UDF. That's because UDF specifies that an ISO 9660 superblock and directory tree shall be present for backwards compatibility. The tree is allowed to be empty, which would constitue a "pure" UDF filesystem. But genisoimage is an ISO 9660 producer with just enough UDF to please the DVD video players. So it produces ISO 9660 with UDF add-on just like Joliet as add-on for Windows of HFS as add-on for old Macs. ISO 9660 and its Rock Ridge enhancements are the main palyers. Leslie wrote: > 1) Problem with interface, about which I have been talking with Leslie. I understand from comments 3 and 4 that you did not discuss the same user interface part. You tested a saved but not yet burned project whereas Łukasz has problems with adding a new session to an already burned DVD+R. I can reproduce at leat the behavior which Łukasz experiences with mount -t udf. In my case by using genisoimage and xorrecord on unformatted DVD-RW. In the case of Łukasz and K3B' by genisoimage and growisofs on DVD+R. The decisive point is the output of genisoimage and its perception by Linux and/or K3B (if it reads UDF by own means). > 2) Problem with UDF multisession discs. If one cannot demonstrate a set of mkisofs options to make UDF and multi-session fully compatible, K3B should refuse to add any session to an UDF filesystem or an UDF session to any filesystem. If such options are found (against my expectation) then one should teach K3B to use them. Looking at our old construction site bug 367639 where we explored the multi-session stuff quite in vain, i'd say that d->multiSessionParameterJob->nextSessionStart() in libk3b/projects/datacd/k3bdatajob.cpp would be a good indicator for an add-on session. UDF would be ok only if nextSessionStart is 0. The plan to create the add-on session with UDF is recognizable by the return value "true" of createUdf() as of libk3b/projects/datacd/k3bisooptions.h I have no idea how to ask K3B whether the loaded session was UDF. K3B should not add an ISO 9660 session because Linux will prefer UDF over ISO 9660 when mounting without -t. Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
