[Info-vax] Looking into C-include files on VMS

[Joerg Schilling]

In article <n4CGm.107883$5n1.14437 at attbi_s21>,
John E. Malmberg <wb8tyw at qsl.network> wrote:

>> -	The ISO 9660 standard definitely does require directory entries
>> 	for "." and "..". ISO 9660 defines the name to be used internally
>> 	for "." to be the NULL character with the file name length set to 1.
>> 	ISO 9660 defines the name to be used internally for ".." to be
>> 	the character '\001' (CONTROL-A) with the file name length set to 1.
>
>When I looked at the ISO 9660 standard, I did not see that.  I was 
>paying more attention to what was needed for making a dual format ISO 
>9660 / ODS-2 volume.

Then you should reread the standard. ISO-9660 even requires these these
entries to be the first and second in a directory. 

>> Cleanly written software usually skips the entries for "." and ".." in case 
>> they apear as a return from readdir(). Mkisofs was not clean in former times 
>> but has been fixed for this problem a long time ago (IIRC in August 2006).
>
>It was about 2005 that I needed a more current port of mkiosf for 
>Alpha/VMS for an internal project.

Problems cannot be fixed before they are known. Mkisofs did apparently work 
correctly as long as there was no filesystem that returned the content in 
random order. This behavior was introduced with Reiserfs on Linux.

-- 
EMail:joerg at schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
      js at cs.tu-berlin.de		(uni)  
      joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily