1. Forum
  2. Usenet
  3. LINUX.DEBIAN.MAINT.BOOT

  • Re: d-i bug: spurious checksum error?

    From john doe@21:1/5 to Charles Curley on Wed Apr 19 09:20:01 2023
    On 4/18/23 23:52, Charles Curley wrote:
    I started a test installation with a preseed file. I launched d-i with
    the following command line:

    expertgui auto file=/media/preseed.cfg DEBCONF_DEBUG=developer

    When I told d-i to get the preseed file, it replied with a screen about
    an incorrect checksum for the preseed file. The screen showed a
    checksum string of "". (I took a screen shot of the error message, then failed to preserve it. Sorry.)

    I had recently added several items to my preseed file, one of which was:


    # The installer can optionally verify checksums of preconfiguration files
    # before using them. Currently only md5sums are supported, list the md5sums
    # in the same order as the list of files to include.
    #d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d

    I deleted those lines entirely, and re-ran the installation. I did not
    get the checksum error on the second try, and the preseed file was
    properly located and run.

    Did I hit a bug? I doubt it is the way the last line is commented out, because there are plenty of other lines that are similarly commented
    out (no space between the # and the d).

    syslog and preseed.cfg files are attached.




    Unless I'm missing something, the file is to be checksummed before the
    content is available to d-i, the lines would simply be there to
    document what the installer can do.

    I would assume that it would work as kernel boot parameter.

    --
    John Doe

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Philip Hands@21:1/5 to Charles Curley on Wed Apr 19 12:40:01 2023
    Charles Curley <[email protected]> writes:

    I started a test installation with a preseed file. I launched d-i with
    the following command line:

    expertgui auto file=/media/preseed.cfg DEBCONF_DEBUG=developer

    According to the log, you actually invoked it with file=preseed.cfg:

    Kernel command line: BOOT_IMAGE=/install.386/vmlinuz priority=low vga=788 initrd=/install.386/gtk/initrd.gz --- auto file=preseed.cfg DEBCONF_DEBUG=developer

    which appears to have confused the installer into looking for it in '/usr/lib/fetch-url//preseed.cfg':

    /bin/fetch-url: .: line 35: can't open '/usr/lib/fetch-url//preseed.cfg': No such file or directory

    which isn't exactly helpful, and it certainly could have done better
    when telling you what was wrong, but it's not at all clear that it was
    going to be able to guess that you meant '/media/preseed.cfg' when you
    said 'preseed.cfg'.

    So, I'd say there's perhaps a bug in what it should guess the user meant
    when specifying a relative path as a value for preseed/file, but
    probably more likely it should just reject a relative path at that point
    with an error about it needing a path that is somehow anchored.

    Cheers, Phil.
    --
    |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd.
    |-| http://www.hands.com/ http://ftp.uk.debian.org/
    |(| Hugo-Klemm-Strasse 34, 21075 Hamburg, GERMANY

    --=-=-Content-Type: application/pgp-signature; name="signature.asc"

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCgAdFiEE3/FBWs4yJ/zyBwfW0EujoAEl1cAFAmQ/wIgACgkQ0EujoAEl 1cBxKRAArll9xbD5pYij1q2vbVKABjFZhFS/FDQLRX83Auc9tVeKY6axmf75kh8D L5ziba8q4VfXzoJ7sZXXLQx9ulBnPtVudHk/PNCQkpdwy4xoNlzeYc0ozuuAMklD c0XttK395BBd4sEs38Qh1OV4DjapuiKaXQ+N5iIE+0Mx9bRYtN8zIUasA36n6a49 DX9rWoPFD6aQaSHBH34JM/kDqIfYsMXJTnATyjOFBU5vVG8byAw6cxAaum2am+Br Aothilde9YGrYwHgpdHrKFg6i+8gQdNnkDeywtz9aJMOy9ml1UoYXJAwtQixsQ69 oS6tweO3DWLs820E8JmpMrbEyX08SMpuGKDYGCB41BK+dV90fDjhR/liL20dANRu Nwd6SnGZRL7JWmCKFq7H5RAlzkJCqiY2urEixA6GZMTPrhKjTm/OjVFm5BxZjg6/ jzpTy+HMEqcgCsVu4lLI7PzTF2B5gUhfGk1m29lrjMV6g7WPSlaJ+Bx8OmKVEX5V eRAaJewccV6khtX8KocJZySgeG4FwVTvR/rG4p/1gqjlBWfUPhi+hzpMdnUNoAk9 Zwbugo7FnUONnzxpfVGfNdlRG7NjVSCFEOyLsjNW7bIl1Du3/rGnBGZ7/6N9+JbX 259UIZ+tsreigX8
  • From Charles Curley@21:1/5 to Philip Hands on Wed Apr 19 19:20:01 2023
    On Wed, 19 Apr 2023 12:20:56 +0200
    Philip Hands <[email protected]> wrote:

    According to the log, you actually invoked it with file=preseed.cfg:

    Kernel command line: BOOT_IMAGE=/install.386/vmlinuz priority=low
    vga=788 initrd=/install.386/gtk/initrd.gz --- auto file=preseed.cfg DEBCONF_DEBUG=developer


    Aha! Thank you for that catch. I re-ran the installation, double
    checking my command line, and did not get that error.


    --
    Does anybody read signatures any more?

    https://charlescurley.com
    https://charlescurley.com/blog/

    -----BEGIN PGP SIGNATURE-----

    iQGzBAEBCgAdFiEEON3On5clQt3imusRdRRtN6MyEMsFAmRAHJkACgkQdRRtN6My EMvZYwwAhajshknjy8aCwcznYzP+XzWnwTU0AbuJncztg9TsUj/U+bEpZx4XU8c/ 60MANOy8cRSG+9RbxLKplL/ugUhU06szqnwFXC92XH1BdEMVKhy80HMCESZPgnMY jBXvJETeOdpLtw4V7bfZU4OAWUQwXM7+abUeJDYDVti4QKUFuQ574tmhp3Tn34VB whqkipHMAfkPmH1Gm46K2lyh5NpJ7NARUlq/0aZ/VM2NnfhR3Uo6SGLyNPkpK1kn 5SZHjuiVb/dTPfRczAbrtTXNMWipmwXmF8ekcjAk1NXmrPT5dr04uLqd0RrTbmho 9nIU3sLfeCnh5WtqJU2wPNjC4kxUxlmQ9rwOnlnItw1xYnia4thEijXYn0EI2YNx eoBSpltsh+2Ge3dm7veupjf1Vfdfdlk8UPHLKrotfaWDsoUupYLB1aAv4o21zltj QZKmDle9YB4PjDLLHSoxGh/3bTlk6T2n96VcNd07tMz43a8oQ8Q6BsrrniqeeT1T
    fb8+MfKN
    =SLKT
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)