[syslinux] Improving TAILS, WAS: Module Versioning

[Shao Miller]

Here are some thoughts:

 1. Customized Syslinux could be customized such that it refuses to boot
    from USB.  No amount of version-matching nor downloading from the
    same source can help with that scenario.  A different Syslinux would
    be needed, by definition (of the customizer)
 2. Slightly less bad is where an ISO or CD/DVD is made with a key piece
    of non-ISOLINUX Syslinux missing and completely unavailable.  This
    scenario emphasizes the challenges of compatibility, regardless of
    version-detail-helpers
 3. If you remove all binaries and leave only configuration-files, then
    install your favourite version of Syslinux (which you keep packaged
    with Rufus) to the USB, then fit the config-files into place, what
    are the disadvantages?  If one of the answers is "the CD version
    could be a customized Syslinux," then the worst-case argument
    against supporting it is #1, above
     1. You'd mentioned "the application size would explode, and as more
        version of Syslinux get releases", but perhaps there's a
        misunderstanding...  If Rufus chooses one and only one golden
        Syslinux, then Rufus doesn't need to keep more than one version
        of modules and ldlinux.sys.  That is, forget about whichever
        Syslinux (ISOLINUX) was on the original disc/ISO
 4. Assuming the last point leaves us wanting, if Rufus took the hash of
    key files, it could consult a database:
     1. If the Internet is available, it could check your web-site
         1. If your web-site recognizes the hash, it could send
            appropriate (exact or compatible) files
         2. If your web-site doesn't recognize the hash, it could
            request the user to report the miss
     2. If the Internet is unavailable, it could check a Rufus-integrated DB
         1. If the hash is recognized and an appropriate (exact or
            compatible) fileset is shipped with Rufus, those files could
            be used
         2. If the hash is recognized but an appropriate fileset is
            online, Rufus could report, "Sorry, but we need the Internet"
         3. If the hash isn't recognized, Rufus could request the user
            to report the miss
 5. Please remember that this is all in response to Rufus' needs,
    specifically.  I still agree that version-detail-helpers can yield
    benefits for more cases.  For the sake of this sub-thread
    discussion, let's please assume that's going to be improved and
    worry about the rest

--
- Shao Miller
(See next line.)
https://www.synthetel.com