Re: How to go on with ISO 9660 large file support ?

2014-05-27 Thread Wolfgang Solfrank
Hi Thomas, unfortunately, I'm a bit scarce on round tuits right now, so here only some random comments: - cd9660_readdir() serving as VOP_READDIR(9) The case of mount -o norrip,nogens already used a delivery function with delayed file candidates: cd9660_vnops.c : iso_shipdir().

Re: How to go on with ISO 9660 large file support ?

2014-05-27 Thread Thomas Schmitt
Hi, Wolfgang Solfrank: I'm a bit scarce on round tuits right now, The global tuits shortage crisis is of course a big obstacle. Especially since ISO 9660 is essential when booting installation CDs or DVDs. I plan to repack NetBSD-6.1.3-i386.iso with my development kernel and to perform an

Re: How to go on with ISO 9660 large file support ?

2014-05-27 Thread Thomas Schmitt
Hi, New code should use kmem(9) for variable-sized or one-time allocations, Currently it is running on kmem(9). There is old malloc(9) usage in cd9660 which i tried to mimic until i came to the deprecation statement in the man page. Shall i change the old malloc(9) usage, too ? Or in a later

Re: How to go on with ISO 9660 large file support ?

2014-05-27 Thread Christos Zoulas
In article 20140527142117.6807560...@jupiter.mumble.net, Taylor R Campbell campbell+netbsd-tech-k...@mumble.net wrote: For the most part, struct iso_node is private to the kernel implementation of cd9660. Since fstat(1) and pmap(1) use it, you should avoid changing the offsets within the

Re: How to go on with ISO 9660 large file support ?

2014-05-27 Thread Thomas Schmitt
Hi, Christos Zoulas: I'd say it is not critical that those work if we have to run through hoops to achieve compatibility. I.e. clean code would be my priority. The fully API compatible code is slightly cleaner than the only ABI compatible code, which saves sizeof(void *) with every