And sad though his passing is, it marks something else for me - that a person committed to "improving the world a little" is recognised without having made billions in an IPO or become a media celebrity. Maybe we can all aim a little lower (or higher depending on how you see it) now.
Thank you Jorg.
Our condolences to your loved ones.
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.
Thirdly, there is a really serious bug in CDR tools: It will start creating bad timestamps in 2028. That’s not a typo: 2028 (not 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. 
A full bug report, complete with a bugfix is here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990468
A fork of cdrtools with this bug fixed is on GitHub: https://github.com/samboy/iso9660
Again, prayers for Schilling’s family, and he was very professional in his interactions with me, even in his final days.
 The issue is with how Schilling’s CDR tools calculates timezones; the time zone becomes an invalid number starting in 2028.
I wish we had a better word for what strenholme is doing besides "maintainer".
To have known the deceased and decide to continue their work is something special indeed.
If Eric Youngdale could come out of the woodwork and retroactively add a “CDR tools, as a special GPL exception, can integrate CDDL licensed code” clause, that might allow us to use Schilling’s more recent code, but, to be safe, I prefer to work with the older codebase to keep the license simple.
But that's what Debian did already with wodim/cdrkit much to Jörg's dismay. I don't think it received much development and afaik never got BluRay support.
If the copyright holder is dead, there is nothing to be afraid of in violating his license, surely...? At worst you could ask his heirs to add that exception.
> Copyright protection generally lasts for 70 years after the death of the author. If the work was a "work for hire", then copyright persists for 120 years after creation or 95 years after publication, whichever is shorter.
> A fork of cdrtools with this bug fixed is on GitHub: https://github.com/samboy/iso9660
I dedicate this repo this his memory. -->
I dedicate this repo to his memory.
Which is irrelevant as the code does not contain any GPL code, right?
 Youngdale at one point was one of the Yggdrasil Linux developers, for people using Linux long enough to remember that long since abandoned distro.
Cdrecord has even more options than ls.
Linux expanded and thrived thanks to CD copies and the support of CD recorders was often poor. His work surely affected many and he did his part in bringing Linux to where it is today.
Thanks, Jörg, for useful tools that have kept on being useful.
He was super specialized in C and Unix and I had a lot of respect that he used the same tech his whole career.
You could not ignore him when he was in a room, he had a strong presence. I always saw him joyful. He used to told me some stupid jokes regularly also.
My sincere condolences to everybody that will miss him.
I think people in the German nerdsphere had an affection for him because he was a fanatical fan of Solaris, which he liked to get into in all kinds of situations, notably in heated comments on heise.de. It was kind of cute to see such an obviously intelligent guy behave like that. Many geeks and nerds have things that they care much more about than would be considered "normal", after all.
Many of the things I made that machine do were only possible to me because of Shilling's shared knowledge. Thanks for that.
I shall burn a terminator in salute.
Unfortunately I don't know the other projects of Jörg Schilling.
But mainly I remember him for his work on SCCS. That code was AT&T proprietary for a long time, but it was open-sourced as part of OpenSolaris. Schilling made it portable and produced binaries for several platforms, including the Mac. He even gave some conference talks on this topic. By the time he did that work, most projects had already moved onto other version control systems. But there are older, closed-source histories of various projects (such as Java) that are still in SCCS, and I find his tools useful to this day for investigating those histories.
Condolences to his family.
I remember him from cdrtools. It was amazing because I recall that it ran everywhere in the late 90s. SunOS, Solaris, DEC UNIX, FreeBSD, Linux, etc. That was remarkable for a piece of software that interacted with hardware.
The same hardware on Windows was very hard to dedicate enough power to the recording software in the 95/98 era.
I will remember him for his CDDL flames and my invitation for him to answer the CDDL/GPL debate over at the brand new SE OSS site right at the launch in 2015, which he gladly accepted.
I vaguely recall making this question explicitly for him to answer, seeing that he was already on the site, and me needing a total of 10 QA entries to get an Area51 badge for a follow-through on the launch of the site as a founding member. He didn't disappoint and provided a great answer!
He was not shy of having a good argument and defending the position he thought was correct even if such position was extremely unpopular and futile to have and to defend:
Very sad to learn he's gone. RIP.
Of course, the difficulty of many GPL projects is in identifying the stakeholders, and getting them to agree on action.
The real risk comes from OpenZFS, where the majority of the copyright is held by Oracle (formerly Sun). Oracle is an evil, evil organization in regards to IP, so I can only assume their reason for not taking action is 1) it's not worth their time or 2) they're waiting until a big wealthy organization depends on it before they can spring their trap.
I don't think they can any more. The principle of laches applies:
This is why Microsoft's threats against the Linux desktop in around 2007 failed: the IP that they claimed, the Windows 95 desktop look and feel -- Start menu, taskbar etc. -- is stuff that Microsoft 100% did invent, but 12 years later is...
Well, _the Hitch-hiker's Guide to the Galaxy_ was published 42 years ago today, and it still rings true. To quote Chapter 3 of the Guide:
"You've had plenty of time to lodge any formal complaint and it's far too late to start making a fuss about it now."
ZFS has been included in Ubuntu since 16.04. Oracle has known and has had five years to raise an objection. It has not done so. It is now too late, by the principle of laches.
It may try, of course, but the lawsuit should be pretty brief because the defense is right there: why didn't Oracle file a complaint in 2016?
I should highlight that this is the reason the FSF has the "copyright assignement" clause, because they understand well that without it, the GPL is hard to enforce.
Sadly, such a clause has been co-opted by other companies to give them the power of relicensing the software under more closed terms.
Profile: Jörg Schilling (2005) - https://news.ycombinator.com/item?id=28827572
Will raise a glass to you tonight, friend.
I wish this was true just a bit. Software goes away with the time almost like no other human artifact.
I have a USB-3.1 BluRay writer I use for burning 50GB-100GB BDs with family photos/videos (alongside other media).
The downside is that buying a portable HDD is significantly cheaper TB for TB but I feel they'll fail quicker, who knows, so I keep copies on both.
It depends on your usage model. If you "burn" a HDD and store it in a drawer, then pull it back after 15 years, chances are it will work fine - whereas the CD might well have lost a lot of data. It might not be cheaper per TB, though.
As a practical matter, I can generally read 20-year-old CDRs I burned just fine (I have only had issues with cheap CDR blanks, such as Fry’s old house brand); for things I want to last long-term, I use archival grade CDR blanks.
Granted I have not been using archival grade Blu-ray's because the cost to store terabytes is prohibitive.
As someone who lost three close family members in the last five years, the last thing your relatives will want to do after you die is go through multiple terabytes of unorganized files to try and find relevant pictures and other heirlooms worth keeping (one relative had a nicely organized folder with relatively few important pictures on his hard disk, so I was able to fairly easily make a DVD of his photography for the family).
My “after my pass away” CD-R has one picture I took per month, starting in the mid-2000s decade when digital cameras started being widely available. There are notes about who is in each picture, where each picture is taken, and other relevant details about the pictures.
I also have 320k MP3 files of the better music I have composed over the years, since I am also an electronic musician.
In terms of open source software, it’s more likely than not that one of GitHub/GitLab/Sourceforge/Bitbucket or even Sourcehut will outlive me; my important projects are on multiple Git hosting services. Even if all of today’s Git repos go down, important software will be uploaded by others to what passes as Git to whatever repos exist in the future (See: The number of open source projects when never used Git mirrored on GitHub)
You make very good points and these are things I've put some thought into (particularly) since becoming a father.
The only stuff I consider really important is the photographs and videos, most of the things before our child(ren).
I think the interesting and most important point I've taken from you here is putting the "what/who/why/where".
We were looking through my childhood photos/videos at my parents recently but had no context for some of them and the people who might have known are no longer with us.
As for code, all of my code is open source when I finish a project (rare) but nothing that the world would miss (so far) so I haven't put any real effort into preserving it.
Second best option is an archival grade CD-R or DVD-R (but not Blu-Ray: There was/is not enough support for Blu Rays, but at one point, CD/DVD support was universal), with the contents clearly marked on the front of the disk so your loved ones can quickly know what is on the disk. Images should all be in .jpg format (converted as necessary), and notes should be in .txt files. (.webp will probably work long term, but I would use .jpg to ensure compatibility, since that is the lowest common denominator format for photos)
Music, if one is a composer, should be either 16/44.1 .wav files or 320k mp3 files; the music files should be in stereo.
I would have videos be 24p (24 frames per second) or 30p (30 frames per second) 720p resolution (hi-def: 1280x720) video in H264 .mp4 format. Be careful: Some open source applications will write a .mp4 they themselves can play, but won’t play (or won’t play well) on other video players. H264 format .mp4 looks to be pretty much universally compatible, however. I suggest keeping the resolution and frame rate down to minimize problems.
I guess I'll find out in 20 years or so which lasted longer.
The video cassettes my parents recorded my childhood on in the 80s and 90s are still going strong, I don't know if modern media will last as well.
The pen drive my wedding photographer gave us our photographs on was used exactly once, I tried it ~5 years later and it's was dead.
I suppose each form of media has its issues so I'm simply trying not to rely on any single technology.
You might be surprised. Vernor Vinge's A Deepness in the Sky (recently discussed here) describes in some detail the job position of programmer archaeologist (<https://en.wikipedia.org/wiki/Software_archaeology>).
We will of course also remember him for his flames.
Very sad to hear this news. RIP.
In Hebrew they say: חבל עד דאבדין ולא משתכחין
(well, technically it's part Aramaic)
Rest In Piece and honor for paving important stretches of the road on which the world of software marches on.
I'll continue to remember him fondly
There are also a few (one-way) bridge gateways.
So ... kind of.
My deepest condolences to the family and friends.
Uncompromising on software reliability, worthy of respect
I loved his opinionation.
We will miss you schilly.
Thanks for all your excellent software. May you code in peace with the *nix gods.
I agree that this is a more informative link.