Ed_P wrote:Sequence is still extramods, then porteus/base mods, then changes.

Yes I know, because I havent looked into yet . I would have to create your exact setup, so it would take some time to recreate your scenario. I have checked porteus extracted to a drive and porteus executed from a cd and both have the base modules loaded first and then the extramods.

I see you use the from=/path/to/iso cheatcode and your extramods are in some partition. What about the kernel and the initrd? Are they pre-extracted out of the iso for the bootloader?

I will also report the wrong path issue, since it also occurs on 3.2rc5. Now, if and when brokenman fixes this, this script would break (because of the workaround). So I would then suggest that you keep this version of your script for your 3.0.1 and use the previous version for 3.2 when it gets fixed there. Or, this same script on both versions.

Coming to you now live from Porteus RazorQT 3.0.1! I downloaded this iso from the archives of dl.porteus.org. I executed the script and saw that the base modules come first and then the extramods.http://imgur.com/a/jE9L1

EDIT: I did find a difference in your screenshot. While the containing directory field should show only directory names, your screenshot shows the xzm module name also.
eg: /mnt/live/mnt/isoloop/porteus/base/000-kernel.xzm

You are right, technically they are directories in /mnt/live/memory/images, but do not look good in the display. Probably have to strip it off in the script.

Hi Ed_P,

You have showed me /mnt/live/mnt/isoloop/porteus. Could you also go one level deeper and show me the output of ls -l /mnt/live/mnt/isoloop/porteus/base/

I see you also have cinnamon 3.2rc5 booted in similar way (isoloop). Does the script show the base modules at the end there too? Also, I saw your 3.0.1 razorqt iso has a -nu at the end. I did not find this in the server. Is that a recreated iso?