......, 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').

I'll update the help files for this, plus other code cleanups.

But, I don't know whether I should wait for BusyBox 1.21.1 bug fix release as well. I was hoping I could update BusyBox in the next version of CPUstress image, because it has an important bug fix for me .

I don't want to post as off-topic in Explorer's CPUStress dev. topic, and I have some doubts (not necessarilly reports) regarding 52b5.

In the blacklist.sed file, there are two consecutive lines with "$!N". Is this OK?

***

In the pmagic.sed file, there are two consecutive lines with "$!N". Is this OK?

***

In linux.sed, the example:# LINUX /ubcd/boot/cpustres/bzImagemight be better as# LINUX /pmagic/bzImageto reflect the real path in use in UBCD? (I'm not sure which path is best as documented example.)

In linux.sed, are the new sed replacement lines (that start with "s|") requiring the key words to be the initial word of the line in the cfg files (without any other character before, not even spaces)? This requirement should be met. I am asking because I don't know whether this sed code actually is checking this or not. This requirement is the reason to put all “text help” with one initial space on every line.

***

I was not successful when I tried to run syslinux2grub4dos.cmd (Windows script). I am not sure if the problem is in my system or in the recent changes (I might try to find out in the next few days). This failure is one of the reasons, among others, for the above questions.

***Please change the line endings of lst files back to Windows style, as they used to be.***

In the blacklist.sed/pmagic.sed file, there are two consecutive lines with "$!N". Is this OK?

That was supposed to remove the consecutive newlines after masking out the blacklisted entries (by removing the newline after the target entry). But I have removed that after finding a better way of doing it in syslinux2grub4dos.sh.

Quote:

In linux.sed, the example:# LINUX /ubcd/boot/cpustres/bzImagemight be better as# LINUX /pmagic/bzImageto reflect the real path in use in UBCD? (I'm not sure which path is best as documented example.)

Changed.

Quote:

In linux.sed, are the new sed replacement lines (that start with "s|") requiring the key words to be the initial word of the line in the cfg files (without any other character before, not even spaces)? This requirement should be met. I am asking because I don't know whether this sed code actually is checking this or not. This requirement is the reason to put all “text help” with one initial space on every line.

Fixed.

Quote:

I was not successful when I tried to run syslinux2grub4dos.cmd (Windows script). I am not sure if the problem is in my system or in the recent changes (I might try to find out in the next few days). This failure is one of the reasons, among others, for the above questions.

What is the error? I run the scripts on Win7 without any problems. If there were problems, I wouldn't be able to build the ISO image at all!

CPUstress now uses a kernel built by myself rather than the one from Parted Magic. The custom kernel (3.8.5-cpustress) fixes two bugs below and is more friendly to old processors (i486). It supports SMP but not PAE.

eglibc updated to 2.17-r22665 (from 2.17-r22243).

BusyBox is rebuilt (same version). Now "modprobe", "lsmod", and "uname" are added.

The new eglibc now require Linux kernel 3.7.5 or above. (Parted Magic 2013_01_29 has such kernel.)

Add /etc/mdev.conf which allows loading modules on hotplug.

Notes:

I do not test the lockup problem (viewtopic.php?t=3390) that happened in the old kernel, so I'm not sure whether it was fixed or not. If anyone has the hardware and can test it, then I appreciate for your help.

Since Linux kernel 3.8, the i386 architecture is no longer supported. If you have 80386 you'll probably need to build a 3.7.x Linux kernel.

@Victor Chew: Please update not only the kernel and initrd image, but also the text files. (That is, everything except build.txz) Because I've changed all references of '/pmagic/bzImage' to '/ubcd/boot/cpustress/bzImage' in them.

@Icecube: I'm requesting you permission to release this image under the name 'CPUstress'. If you're reading this, please answer me if you permit me or not. (If not, then I'll rename my project.) This question is to avoid copyright problems in the future.

@Victor Chew: Please update not only the kernel and initrd image, but also the text files. (That is, everything except build.txz) Because I've changed all references of '/pmagic/bzImage' to '/ubcd/boot/cpustress/bzImage' in them.

@Icecube: I'm requesting you permission to release this image under the name 'CPUstress'. If you're reading this, please answer me if you permit me or not. (If not, then I'll rename my project.) This question is to avoid copyright problems in the future.

You can use the same name.

I don't have time to look closely at it, but a small remark:

Because now CPUstress doesn't use a filesystem image anymore as initial ramdisk (now: initramfs = cpio archive), we don't and shouldn't use "root=/dev/ram0 ramdisk_size=12000" as parameter anymore.

Another thing that might be nice, is to have a 64-bit version (kernel and programs).In the 64-bit version I would exclude old programs like cpuburn and mprime v2.3.

I also seemed to remember that someone wanted to be able to read the CPU temperature.This should be possible with lm-sensors:http://www.lm-sensors.org/

Who is online

Users browsing this forum: No registered users and 4 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum