Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

Thread: looking for installation media for SLES9 - s/390 (31-bit)

  1. #11

    Re: looking for installation media for SLES9 - s/390 (31-bit

    just to be clear, this was for test/evaluation/proof-of-concept/procedure development purposes. I have de-installed the software as per the SuSE's Intellectual Property license and will pursue a full purchase of the product from sales if I intend to run it for a longer duration at some point.

    Again, thanks to all for your collective assistance. I'm planning to write up all the details of the procedure developed bare metal -> SLES9 login if anyone is interested.

  2. #12

    Re: looking for installation media for SLES9 - s/390 (31-bit)

    asysad Wrote in message:

    > just to be clear, this was for
    > test/evaluation/proof-of-concept/procedure development purposes. I have
    > de-installed the software as per the SuSE's Intellectual Property
    > license and will pursue a full purchase of the product from sales if I
    > intend to run it for a longer duration at some point.


    I'll be surprised if SUSE will/can sell you a license for an old,
    unsupported release of SLES9.

    > Again, thanks to all for your collective assistance. I'm planning to
    > write up all the details of the procedure developed bare metal -> SLES9
    > login if anyone is interested.


    I'd certainly be interested. In the past I would have suggested
    submitting it as a Cool Solutions article but SUSE don't
    currently award credits for their equivalent communities
    site.

    HTH.
    --
    Simon Flood
    SUSE Knowledge Partner


    ----Android NewsGroup Reader----
    http://usenet.sinaapp.com/

  3. #13

    Re: looking for installation media for SLES9 - s/390 (31-bit)

    On 26/06/18 13:55, ab wrote:

    > For what it is worth, I too downloaded it and calculated the following
    > md5sum, just for comparison purposes:
    >
    > dc010329631b7d68ae2315f9d2ad2a54


    Snap! I also get

    dc010329631b7d68ae2315f9d2ad2a54

    as the MD5 checksum.

    For completeness I also generated SHA1 and SHA256 checksums:

    SHA1: 11e6a3118587b07e3dafc5525938bdb1bfc15b16
    SHA256: 6ff8e5c39061b5d7417b31a3ff57a8c6d6b4dbe01d07ea2e6d 3f31957a93683b

    Given that we're generating these checksums (as opposed to being
    officially published by SUSE) I'd be more inclined to check that the MD5
    checksums of the individual files within the archive match those which
    were noted and linked to[1] in the asysad's edited web post[2]. Which
    they do!

    HTH.

    [1]
    https://www.novell.com/documentation...ries-s390.html
    [2]
    https://forums.suse.com/showthread.p...3151#post53151
    --
    Simon
    SUSE Knowledge Partner

    ------------------------------------------------------------------------
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below. Thanks.
    ------------------------------------------------------------------------

Page 2 of 2 FirstFirst 12

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •