[SOLVED] Maybe a Bug on md5sum!?

[nixlower0]

Hello forum mates!
I liked very much Slax and Slax Remix Porteus. But I have a lil' problem with check sum. When I tried to create a booting USB flash drive with Porteus on it from my Ubuntu by using a command:

Code: Select all

$ sh ./lin_start_here.sh

I got an error advertisement after "Checking md5sums - wait a while...":

Code: Select all

checking md5sum for  boot/vmlinuz    ok
checking md5sum for  boot/initrd.xz    ok
checking md5sum for  porteus/base/000-kernel.xzm   fail!
checking md5sum for  porteus/base/001-core.xzm   fail!
checking md5sum for  porteus/base/002-xorg.xzm   fail!
checking md5sum for  porteus/base/003-lxde.xzm   fail!
checking md5sum for  porteus/base/004-tde.xzm   fail!
checking md5sum for  porteus/base/005-tdeapps.xzm   fail!
checking md5sum for  porteus/base/006-abiword.xzm   fail!
checking md5sum for  porteus/base/007-devel.xzm   fail!
checking md5sum for  porteus/base/008-firefox.xzm   fail!

Some md5sums doesn't match or some files from default ISO are missing,
please check above...
Be aware that vmlinuz, initrd.xz, 000-kernel.xzm and 001-core.xzm are
most important and booting wont be possible when they are missing.
Press enter to continue or ctrl+c to exit

I decided to continue. Then when the installation was done I checked the sums from failed fails. I found all the files have correct sums, excluding one 004-tde.xzm, the sum wasn't correct. Why that happened? It will cause any problem on Porteus booting and using?
Thank you for your answers in advance! I appreciate any answer!

[beny]

which version?

Posted after 1 minute 9 seconds:
tde? 32 bit have you downloaded the last version of porteus?

[nixlower0]

Sorry, I forgot to mention I'm using a x32 bit version - Porteus-v1.2-i486.iso

[beny]

you can boot system,the boot installer give you a warning but i think work well try to continue in

[nixlower0]

OK, I will try now to boot, then I'll post here what happened

[bigbass]

Post by nixlower0 » 08 Sep 2012, 17:39
Sorry, I forgot to mention I'm using a x32 bit version - Porteus-v1.2-i486.iso

looks like that file slipped though the coffee filter without getting updated these are the md5sums
its a minor thing to fix

if you upgrade the kernel and initrd it would look like this

http://pastebin.com/PiWCfjfT

you could generate a new md5sum.txt the official way by running this make_iso.sh


here is one with no filters for any file(s)

Code: Select all

:> CHECKSUMS.md5
    find .  -exec md5sum {} \; >> CHECKSUMS.md5
  cat CHECKSUMS.md5 

check it easily with this

Code: Select all

md5sum -c CHECKSUMS.md5

if you want a script to do it for you for "packages and modules " here is one run it from inside the base directory
this will cover many formats I added xzm


Joe

Code: Select all

:> CHECKSUMS.md5
    find . -type f -regextype posix-egrep -regex '.*\.[tgblzikxm]+$' -exec md5sum {} \; >> CHECKSUMS.md5
  cat CHECKSUMS.md5 

[nixlower0]

...
you could generate a new md5sum.txt the official way by running this make_iso.sh

if you want a script to do it for you for "general use" here is one run it from inside the base directory
this will cover many formats I added xzm

Code: Select all

:> CHECKSUMS.md5
    find . -type f -regextype posix-egrep -regex '.*\.[tgblzikxm]+$' -exec md5sum {} \; >> CHECKSUMS.md5
  cat CHECKSUMS.md5 

Do I need to run this script from other OS or I can run it from the same "problematic" Porteus?

P.S.: Here an image of booting screen:

[bigbass]

your are adding another question

Code: Select all

Do I need to run this script from other OS or I can run it from the same "problematic" Porteus?

The first question was how to fix the md5sums you would simply replace the file md5sums.txt with the one I posted in paste bin and if you didnt upgrade the kernel use your md5sums for the kernel and initrd since they were ok

it looks as though that was a minor problem since you got it to boot up
what you need to do now is make a save.dat following the directions in the image you posted

someone can walk you though the steps since there are many USB users here
http://porteus.org/info/docs/57-general ... d-one.html

Joe

[brokenman]

Disregard the failed md5sums during install. This was my fault and is because the path of the files it is checking is incorrect. Already addressed and will be fixed in next major update. Apologees for my insolence.

[nixlower0]

Disregard the failed md5sums during install. This was my fault and is because the path of the files it is checking is incorrect. Already addressed and will be fixed in next major update. Apologees for my insolence.

Thank you for your answer! You don't have to apologize I'm not so new in GNU/Linux, but my knowledges are low, that's why I answered if a message about md5sum was normal or I need to worry about it.
Also I was worried about "save session" message, now I know if I want to use a file system different from Linux, then a "save.dat" container need to be created as answered to me comrade - bigbass
Thanks for you help. When I will have some time to read more Porteus, Slax and Slackware documentation, I will do.

[Hamza]

Also I was worried about "save session" message, now I know if I want to use a file system different from Linux, then a "save.dat" container need to be created as answered to me comrade - bigbass

It's only a suggestion very recommended. You may uses changes under FAT/NTFS but it's not recommended due to some symlinks problems and also some permissions problems. It's true and it's much better to uses a container file (.dat file) as it's a virtual "devices/partition" formatted for linux uses and he can saves all your symlinks and permissions.

[Ahau]

Hamza, that is incorrect. A save.dat is required (not suggested) in order to run Porteus with saved changes on non-posix filesystems (e.g. FAT and NTFS). The only way to do this was posixovl, which we dropped due to massive corruption issues.

Another option to avoid the need for a save.dat would be to customize the system without saved changes, and build a module with those changes. No changes would be saved beyond those on subsequent boots, but it would capture configuration tweaks, etc.

[Hamza]

Sorry

[nixlower0]

Ok, I'm marking as solved.
Now I'm a happy user of Porteus 2.0 x86