i have dug into how memtest86 / memtest86+ are handled in catalyst and i have a few suggestions: 1) Update both memtest86 & memtest86+ to the latest versions memtest86 has been at version 3.1a since 2004/03/11 and includes significant new fixes and enhancments memtest86+ has been at version 1.30 since today (grin) see bug# 70499 Even the currently masked V1.27 has been avaliable since 2004/10/12 and also includes significant fixes and enhancements assuming that these will be available on the the 2004.3 iso it would make sense that the were the latest versions 2) Make both (or none) an option Currently it is misleading - given the following files: isolinux-2.08-cdtar.tar.bz2 isolinux-2.08-memtest86-cdtar.tar.bz2 isolinux-2.08-memtest86+-cdtar.tar.bz2 as options for the the "livecd/cdtar" option for the livecd-stage2.spec one may be inclined to assume that the first file doesn't include memtest86 (actually it has the exact same contents as isolinux-2.08-memtest86-cdtar.tar.bz2) It should be changed so that none/either/both are options This will require changes to: /usr/lib/catalyst/livecd/files/x86-help.msg (there will need to be 3 versions of the help message) /usr/lib/catalyst/livecd/runscript/x86-archscript.sh The changes to x86-help.msg will have to track the "livecd/cdtar" option in the specfile which will require a change to: /usr/lib/catalyst/livecd/runscript/x86-archscript.sh Reproducible: Always Steps to Reproduce: i will attach proposed changes after submitting the bug
so.... where are the submissions? *grin*
I'm just curious, but what are the major differences between memtest86 and memtest86+ anyway?
i believe that memtest86+ runs on amd64. Other than that, I don't think that there are any other diffs
Well, memtest86, by default, won't compile on amd64. I changed that by editing 2 lines in the Makefile. I now have packages for isolinux-2.11, isolinux-2.11-memtest86, isolinux-2.11-memtest86+, and isolinux-2.11-memtest86-both on my machine at home. I have not commited them, as I was going to make sure they still function. As for the x86-help.msg file, I am not sure what method would be best for detecting the proper file to use. After all, a user could use their own cdtar and not use one of ours, or they could be using the released catalyst, or a cvs snapshot (if they're a developer), so how exactly would you "detect" the proper one? I mean, we could add a new option to catalyst to select which file to use, something like livecd/help_msg, but do we need to go there?
ick, another spec file option just for a help msg? it would be nice if we could detect it somehow ... i don't like the cdtar concept to begin with, it seems so static. perhaps we should look into how to eliminate the cdtar concept all together.
Honestly, we should have the option to be able to change the help message anyway. As for removing the cdtar, there's not really a problem with that. It just adds one more thing that is relatively unchanging (and doesn't have compile options) that needs to be compiled every time you perform a livecd-stage2. Personally, I would keep the cdtar stuff. Anyway, I'll figure out something. I'm honestly inclined to simply pick one of the memtest versions and stick with it, since there's nothing stopping someone from providing their own cdtar, if they wanted to use something else.
i'm fine with making an option to change the help message. have you decided upon a cdtar yet?
Yeah... I'm updating to isolinux 2.11 and memtest86+ 1.40 in catalyst. I'll add the help message selection in a few...
Catalyst 1.1.2 is now out!
catalyst 1.1.10 is out .. this is an old bug. Closing
