Porteus

I have equal my Porteus-KDE4-v3.1-x86_64.iso that i have download ca. December 2014 and that are in use.
With http://dl.porteus.org/x86_64/current/Po ... x86_64.iso

and i am really confused, because i have a differenz in md5sum.

md5sum of my Old Porteus CD:
Porteus-KDE4-v3.1-x86_64.iso 6004bfe56dc87968af2e40946a7429b7
the Old Kernel: d142590400c884289c2100fc20621980 [old_CD]/boot/syslinux/vmlinuz

md5sum of current (19.01.2017) Porteus-KDE4
Porteus-KDE4-v3.1-x86_64.iso d5b16ffebb537c23a948e22c5c986ef4
(equals with the http://dl.porteus.org/x86_64/current/md5sums.txt)
the current Kernel: 38e7a4946214b5ef74c6d22b2672ff21 [old_CD]/boot/syslinux/vmlinuz

have everybody a idea what is going on ?

hmm
I have equal some iso Files and found two versions:

My old ISO File
Porteus-KDE4-v3.1-x86_64.iso md5=6004bfe56dc87968af2e40946a7429b7
from 12.12.2014 / 12:40

and the current ISO File
Porteus-KDE4-v3.1-x86_64.iso md5=d5b16ffebb537c23a948e22c5c986ef4
from 14.12.2014 / 7:31

was here a change between ?
Or i am a extremly important person and the secret service hunt me ?

Yes, one of them is sponsored by the 3 letter agency....you have to guess which one.

Seriously:
I could not find a md5sum.txt containing the "6004bfe5.." md5sum
https://web.archive.org/web/*/http://dl ... d5sums.txt
https://web.archive.org/web/20140101000 ... d5sums.txt
do you have such a md5sum file?
imho it's a good idea to save the matching md5sum file for every (iso) download.

imho it's a good idea to save the matching md5sum file for every (iso) download.

no i have not, have you?

Both ideas from you are smart.
Thanks.

But it is possible that the changes was only to short so that it is not in archiv.org ?
I Searching on the Internet for "6004bfe5.." and found this:
http://iso.linuxquestions.org/porteus/porteus-3.1
http://linuxiarze.pl/download_porteus
Both link the current "d5b16ffe.." ISO but refer to md5sum of "6004bfe5.."
The other md5sums on this sites are differ too.

I equal the md5sums of single packages and found differenz in:
my Old ISO:
d142590400c884289c2100fc20621980 /mnt/loop/boot/syslinux/vmlinuz
32135d96fd1232162477975a628e44b7 /mnt/loop/porteus/base/04-firefox.xzm

to current ISO:
38e7a4946214b5ef74c6d22b2672ff21 /mnt/loop/boot/syslinux/vmlinuz
46f0b5f4c86ea98389ef98cac722035b /mnt/loop/porteus/base/04-firefox.xzm

It is a littlebit creepy.

so I have 2,5 Theories:
1a.) After publishing Porteus, the Developer found and fix a small problem and reupload without documenting.
1b.) it is documented but i m to stupid and i can not find this.
2.) The current Iso is Infected.

here is the "Old ISO"

1a.) After publishing Porteus, the Developer found and fix a small problem and reupload without documenting.
Correct - it was almost a tradition that after release we found something to fix and done it without version bump in the ISO.

@fanthom
Thanks for the statement.

@KnallKopf
I was already sure it was 1a, and now we/you know for sure it is.
however, because you have already found the differences between the 2 isos
there is no need to compare them again, no?
and yes, I save the md5sums when downloading something because I often move Files around between different media etc. and when I need them I want to be sure they are not damaged.
btw
the 1st link (linuxquestion.org) gives a 404.
have a nice weekend...

donald wrote:the 1st link (linuxquestion.org) gives a 404.
have a nice weekend...

Try this link: http://iso.linuxquestions.org/porteus/ MANY Porteus ISOs available. Based on fanthom's comment I wonder if all the files are the current versions.

^
Many isos are listed but the download links lead to a 404.
( most of them refer to ponce.cc )

^

Thanks for reply too.
This solve my problem.

Have you checked the archive folder on the server? I believe it contains all releases since 1.0.