First of all, compassion and condolences for Schilling’s family.<p>Second of all, I had a very recent positive interaction with him. I recently was in contact with Mr. Schilling to report a bug in CDR tools. Even though he was (looking back) dying, he was very prompt in replying to me and discussing the bug with me over email. However, even though I gave him a fix, he was unable to apply it, probably because of his poor health.<p>Thirdly, there is a really serious bug in CDR tools: It will start creating bad timestamps in 2028. That’s not a typo: 2028 (<i>not</i> 2038). Because of how ISO 9660 filesystems store timestamps (8-bit number, 0 is 1900), on 2038 (1900 + 128), unless the 8-bit number is explicitly made an unsigned number (assumed with other ISO 9660 implementations), there will be issues with timestamps. [1]<p>A full bug report, complete with a bugfix is here: <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990468" rel="nofollow">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990468</a><p>A fork of cdrtools with this bug fixed is on GitHub: <a href="https://github.com/samboy/iso9660" rel="nofollow">https://github.com/samboy/iso9660</a><p>Again, prayers for Schilling’s family, and he was very professional in his interactions with me, even in his final days.<p>[1] The issue is with how Schilling’s CDR tools calculates timezones; the time zone becomes an invalid number starting in 2028.