Explorer09 wrote:If I were you, I'll try the version like '5.3a1'. I think it is fine to have a sequence like 5.2.0 -> 5.3a1 -> 5.2.1 . Personal opinion.
I don't know about others, but using "5.3" just to go back to "5.2" confuses me (not to mention that the current changes only "deserve" a future new 5.2.1 at most, not a 5.3 version). Additionally, "5.3a1" would be interpreted by many (including myself) as the first alpha of a future release "5.3". OTOH, what Victor proposed uniquely identifies each release (whether final or for testing). Under the "5.2" branch (or "line"), "5.2bn" is a testing version, and once in a while a new minor (non-testing) release gets out as "5.2.m". Note that this is different than using "5.2.mbn".
In other words, what Victor proposed is adequate IMO.
Now back on topic.
In ubcd/boot/cpustress/, can the old-readme.txt and the readme.txt be merged into one file?
The old readme file is just for historical reference. You can choose to not include it in the UBCD.
's decision (but generally speaking, I would be glad if some known-as unnecessary files and unnecessary directories wouldn't be included in UBCD).
Is there anything in the old readme that is currently relevant and that is not part of other included text files? For a hypothetical example
, if the only relevant info would be adequate credits, that should be easily merged, shouldn't it?
Explorer09 wrote:"/ubcd/boot/cpustress/bzImage" is the old kernel that is used in Icecube's cpustress image. Yes, it is useful when pmagic's bzImage doesn't boot, although that seldom happens.
OK. Is there any kind of hardware requirement that would be different between the two bzImage files that would affect CPUStress usage? For example, is it possible that an old system ("old" CPU, relatively small amount of RAM, yet CPU Stress programs are still able to run on such hardware) wouldn't boot with pmagic's bzImage but it would successfully boot with "
"? (Note: I wouldn't recommend running CPUStress on old hardware anyway, but that's not my concern regarding this question).
My focus regarding this question is about different hardware. I remember users reporting (in the past, not recently) that they were able to use CPUStress with pmagic's bzImage but not with the original, and other users stating exactly the opposite, depending on the hardware they were trying to test.
bzImage files are really useful and really necessary
, then maybe this should be mentioned somewhere. If only one bzImage is needed to cover all practical cases, then the unnecessary file should be only part of the package (for testing purposes for example) but not part of UBCD.
, just for convenience, in your text files you might want to express the boot lines (examples and help) in a slightly different way. For example, from you current:
Code: Select all
APPEND /pmagic/bzImage initrd=/ubcd/boot/cpustress/initrd.gz
root=/dev/ram0 ramdisk_size=12000 noapic ubcdcmd=cpuburn days=10
to something like:
Code: Select all
COM32 linux.c32 /pmagic/bzImage
APPEND root=/dev/ram0 ramdisk_size=12000 noapic ubcdcmd=cpuburn days=10
so the lines are shorter and easier to read. Both formats are equivalent.
If I do that, you'll need to edit the syslinux2grub4dos scripts. Would you do that?
I don't think there would be a need to change syslinux2grub2dos scripts, since Victor already uses a similar format in UBCD as I am suggesting here for your help files (it is not a direct copy from your help files). My suggestion was (is) for convenience and easier reading in your help files (there wouldn't be a need to clarify the artificial use of an extra line for 'append'). But, if the scripts are a concern regarding these lines, I am willing to test and report back if necessary.