There is a bug in the init in BookwormPup64_10.0.6.iso

[liuzhaoyzz]

I compared Puppy9.5 with 10.0.6: fossapup64-9.5. iso, BookwormPup64_10.0.6. iso.
The startup script init maybe has issue, version 10.0.6 removed the overall startup function of iso. I feel like the official website doesn't understand what this feature is for.

Fossapup64-9.5. iso startup script, line 654:
##Set by/sbin/isoboot
If ["$ISO-LOOP"]; Then
TRY-PARTS=${ISO-PSAVE} | ${ISO-PSAVE-FS}
${ISO-LOOP # # */} | iso9660
${TRY-PARTS}“
Fi
##

BookwormPup64_10.0.6.iso is not available.
The result is that BookwormPup64_10.0.6.iso failed to start iso as a whole using grub4dos or grub2 and entered the command line.
screenshot: https://pan.baidu.com/s/1FdOmwG9NE65a6h ... A?pwd=1111 提取码: 1111

the menu,grub.cfg,UEFI
menuentry "/linux/puppy/BookwormPup64_10.0.6.iso" "/linux/puppy/BookwormPup64_10.0.6.iso" {
set gfxpayload=keep
search --no-floppy --set --file $2
loopback loop $2
linux (loop)/vmlinuz iso-scan/filename=$2 PSUBDIR=/ pmedia=cd pfix=fsck,fsckp
initrd (loop)/ucode.cpio (loop)/initrd.gz
}

menuentry "/linux/puppy/BookwormPup64_10.0.6.iso-loopback.cfg" "/linux/puppy/BookwormPup64_10.0.6.iso" {
terminal_output console
search --no-floppy --set --file $2
export iso_path=$2;loopback -d loop;loopback loop $2
set root=loop
configfile (loop)/boot/grub/loopback.cfg
}

6a45e7a305b7d3172ebd9eab5ca460e4 fossapup64-9.5. iso
http://mirrors.nju.edu.cn/puppy/puppy-fossa/
Nanjing University Open Source Mirror Station
Nanjing University Open Source Mirror Site

Tsinghua University Open Source Software Mirror Station | Tsinghua Open Source Mirror https://mirrors.tuna.tsinghua.edu.cn/

https://mirrors.tuna.tsinghua.edu.cn/puppy/puppy-fossa/

Fossapup64-9.5. iso
MD5: 6a45e7a305b7d3172ebd9eab5ca460e4 fossapup64-9.5. iso

Index of/kernels/data/ISO/Bookworm-Pup64
https://rockedge.org/kernels/data/ISO/Bookworm_Pup64/
BookwormPup64_10.0.6.iso 2024-03-04 23:58 762M
#MD5
6f3da7f6e8b916ffc7742cb5ac46ea01 BookwormPup64_10.0.6.iso

#SHA256
612135478abb3ad2fbb3f2c7f300cd1bf8cc475e83eaad1e19b0d8b965836493 BookwormPup64_10.0.6.iso

A netizen tested and added that code to start BookwormPup64_10.0.6.iso normally

[radky]

@liuzhaoyzz

Thanks for your report.

If I understand correctly, the isoboot code you describe was deprecated and removed from the upstream puppylinux-Woof-CE init on Oct 30, 2020.

Please see the following Woof-CE commit:

https://github.com/puppylinux-woof-CE/w ... aa90cde02e

Your bug report may receive more attention if submitted directly to the Woof-CE devs at the following link:

https://github.com/puppylinux-woof-CE/woof-CE/issues

Perhaps @gyrog and @dimkr will reply and address your bug report.

[Clarity]

This is a good report. I agree with @radky that WoofCE development should review this bug.

BUT, it has broader boot implications.

The developers in 2019, seeing a productivity gain in user use, adjusted booting to accommodate booting from all of the following

• CD/DVD

• Frugal

• SG2D launching WoofCE ISO files, matching similar boot operations of SG2D in other mainstream distros such as Debian, Ubuntu, MX, etc.

Other forum distros, namely KLs and DOGs have the ability to boot their ISO files directly too; and their GRUB2s support this. While they also boot without issues from SG2D in 2019+.

To me, the most interesting boot stanzas for their INITs is the simplicity in the one by @jamesbond used in @fatdog. (this post is NOT a request for any forum distro to adopt FD's approach, rather it merely demonstrates one that also works to boot their distros)

A LARGER issue of WoofCE booting
Environmental description
In addition to that reported by @liuzhaoyzz, another issue surfaces when a WoofCE boots when launched from Ventoy. There is NO problems when being launched from SG2D!

When booting from Ventoy, a WoofCE is unable to process the SAVESPEC feature. There is NO problems when being launched from SG2D!

As a result, the boot partition is and remains "LOCKED" thruout the running of the PUP. There is NO problems when being launched from SG2D!

An example of WHY this is a problem: A distro is being upgraded with a new ISO. It cannot be written to the boot partition where all of the other ISO files reside because of this lock. In other words, you cannot backup, correct, modify, or change ANYTHING on that partition while the WoofCE PUP is running. There is NO problems when being launched from SG2D!

This needs resolution to address WoofCE PUPs booting when being launched. I believe development, too, want their PUPs to boot no matter which environment it is launched: QEMU/DVD/SG2D/GRUB2 and Ventoy.

IF this is a WoofCE problem it begs correction. If it is a Ventoy problem (which in my testing suggest a WoofCE issue) then it needs reporting to Ventoy. Ventoy "fixes" reported problems from any/all distro developers.

LASTLY, this issue(s) does not exist in any DOG or KL. "There is NO problems when WoofCE PUPs are launched from SG2D/Ventoy or from their ISO files directly!"

[liuzhaoyzz]

@liuzhaoyzz

Thanks for your report.

If I understand correctly, the isoboot code you describe was deprecated and removed from the upstream puppylinux-Woof-CE init on Oct 30, 2020.

Please see the following Woof-CE commit:

https://github.com/puppylinux-woof-CE/w ... aa90cde02e

Your bug report may receive more attention if submitted directly to the Woof-CE devs at the following link:

https://github.com/puppylinux-woof-CE/woof-CE/issues

Perhaps @gyrog and @dimkr will reply and address your bug report.

It's really hard for me to enter github.com in China,because of the firewall.

There is a bug in the init in BookwormPup64_10.0.6.iso · Issue #4267 · puppylinux-woof-CE/woof-CE
https://github.com/puppylinux-woof-CE/w ... ssues/4267