TazPuppy 5.0 rc2
TazPuppy Beta 21 released
Changes:
* Improved modular design
* Faster boot when savefile is loaded subsequently
* Some fixes
New tool added in TazPuppy: tazcook-sfs
(Located at Menu>System Tools>Make SFS module package)
Create SFS module version of an app easily and accurately (requires internet connection) Just specify where to save the sfs modules, install packages using tazpkg shell. Exit the tazpkg shell and it will start creating sfs modules. It allows to install many apps as long the user does not quit tazpkg shell
NOTE: When SFS module created by tazcook-sfs is loaded in TazPuppy. The tazpkg sees it as installed an package but not visible for updating package.
Download: https://drive.google.com/file/d/1ndMJCN ... sp=sharing
MD5 Checksum: 89ff398b77575e5f2c19454d76798888
Build kit: https://drive.google.com/file/d/1hdGmNf ... sp=sharing
Changes:
* Improved modular design
* Faster boot when savefile is loaded subsequently
* Some fixes
New tool added in TazPuppy: tazcook-sfs
(Located at Menu>System Tools>Make SFS module package)
Create SFS module version of an app easily and accurately (requires internet connection) Just specify where to save the sfs modules, install packages using tazpkg shell. Exit the tazpkg shell and it will start creating sfs modules. It allows to install many apps as long the user does not quit tazpkg shell
NOTE: When SFS module created by tazcook-sfs is loaded in TazPuppy. The tazpkg sees it as installed an package but not visible for updating package.
Download: https://drive.google.com/file/d/1ndMJCN ... sp=sharing
MD5 Checksum: 89ff398b77575e5f2c19454d76798888
Build kit: https://drive.google.com/file/d/1hdGmNf ... sp=sharing
-
- Posts: 98
- Joined: Mon 17 Oct 2016, 05:11
Hello.
I have installed beta 21. I have tried loading 5 extra sfses as I did before.
Part of boot.log
After loading openoffice (sfs), I see the message "next boot will be faster!" at every boot.
Indeed, the message disappears sooner than before, but sfs_load is changing the mount point of openoffice (sfs) from /dev/loop4 to /dev/loop2. The boot.log says, "losetup-FULL."
I am afraid that this means the 5th extra sfs (openoffice) exceeds the number of loadable sfses.
So I have to conclude that it is safer to limit the number of extra sfses to 4 at most, in which case the message "next boot will be faster!" does not appear.
I think that there is nothing wrong with the openoffice (sfs), because it does not cause any trouble on other Puppies.
I have installed beta 21. I have tried loading 5 extra sfses as I did before.
Part of boot.log
Code: Select all
zram started
Starting pup_sfs_load...
sfs_load: Loading '/initrd/mnt/dev_save/OpenOffice415-ja-i386.sfs'...
umount: can't unmount /initrd/pup_z: Device or resource busy
losetup-FULL: /initrd/mnt/dev_save/OpenOffice415-ja-i386.sfs: failed to set up loop device: Device or resource busy
sfs_load: Do not assosiate /initrd/mnt/dev_save/OpenOffice415-ja-i386.sfs to /dev/loop4 but /dev/loop2.
Starting httpd...
Indeed, the message disappears sooner than before, but sfs_load is changing the mount point of openoffice (sfs) from /dev/loop4 to /dev/loop2. The boot.log says, "losetup-FULL."
I am afraid that this means the 5th extra sfs (openoffice) exceeds the number of loadable sfses.
So I have to conclude that it is safer to limit the number of extra sfses to 4 at most, in which case the message "next boot will be faster!" does not appear.
I think that there is nothing wrong with the openoffice (sfs), because it does not cause any trouble on other Puppies.
-
- Posts: 98
- Joined: Mon 17 Oct 2016, 05:11
mistfire wrote:
> By the way does your open office sfs sucessfully loaded upon boot?
What I did is as follows:
First, I loaded openoffice sfs as the 5th extra sfs by means of sfs_load.
(It took much longer than when I loaded other sfses.)
Openoffice started normally.
I rebooted tazpuppy. The message "next boot will be faster!" appeared.
(After that, I see the message at every boot.)
So openoffice itself works fine. But the behavior of tazpuppy when it loads extra sfses is different from those of other Puppies.
I wonder if other users of tazpuppy do not load as many as 5 or more extra sfses. It seems that some more tests are needed about this issue.
(As I stated before, it is my understanding that modern Puppies can load up to 6 extra sfses safely.)
> By the way does your open office sfs sucessfully loaded upon boot?
What I did is as follows:
First, I loaded openoffice sfs as the 5th extra sfs by means of sfs_load.
(It took much longer than when I loaded other sfses.)
Openoffice started normally.
I rebooted tazpuppy. The message "next boot will be faster!" appeared.
(After that, I see the message at every boot.)
So openoffice itself works fine. But the behavior of tazpuppy when it loads extra sfses is different from those of other Puppies.
I wonder if other users of tazpuppy do not load as many as 5 or more extra sfses. It seems that some more tests are needed about this issue.
(As I stated before, it is my understanding that modern Puppies can load up to 6 extra sfses safely.)
To eliminate the fdrv, have you thought about eliminating the fdrv and manually extracting the required firmware, which can be copied to /lib/firmware.thinkpadfreak wrote:mistfire wrote:
> if a certain loop device number is already use. It will automatically search for available loop device number which is not in use.
I wonder why zdrv must be mounted at /dev/loop4, instead of /dev/loop2 or dev/loop3. If /dev/loop4 is not in use, openoffice (sfs) will use it, so that depmod will not be run.
The fact that fdrv is listed in sfs_load is also strange. In case of UpupBB, for example, fdrv is not listed as an extra sfs.
(I do not know much about the mechanism of puppy, so what i am saying may be pointless.)
-
- Posts: 98
- Joined: Mon 17 Oct 2016, 05:11
Terry H wrote:
> To eliminate the fdrv, have you thought about eliminating the fdrv and manually extracting the required firmware, which can be copied to /lib/firmware.
Thank you for the advice.
I tried eliminating fdrv by merging fdrv and zdrv to make a new zdrv.
Naturally, fdrv is not listed in sfs_load any more.
But still, the message "next boot will be faster!" appears at every boot, and the 5th extra sfs is mounted at /dev/loop2.
The extra sfses are mounted at /dev/loop6 ~ /devloop9 and /dev/loop2.
/dev/loop5 is not in use, probably because it is reserved for fdrv.
It is clear that tazpuppy behaves differently from other Puppies. If it is the way tazpuppy should be, I will give up further discussion about this issue.
> To eliminate the fdrv, have you thought about eliminating the fdrv and manually extracting the required firmware, which can be copied to /lib/firmware.
Thank you for the advice.
I tried eliminating fdrv by merging fdrv and zdrv to make a new zdrv.
Naturally, fdrv is not listed in sfs_load any more.
But still, the message "next boot will be faster!" appears at every boot, and the 5th extra sfs is mounted at /dev/loop2.
The extra sfses are mounted at /dev/loop6 ~ /devloop9 and /dev/loop2.
/dev/loop5 is not in use, probably because it is reserved for fdrv.
It is clear that tazpuppy behaves differently from other Puppies. If it is the way tazpuppy should be, I will give up further discussion about this issue.
@thinkpadfreak I reviewed to init code of initrd which was responsible of loading sfs files prior to execution of sfs_load. According to the comments of init script. 6 sfs files is the limit that can be only loaded when the puppy boots up because the performance degrades as the number of sfs file loaded increase.
-
- Posts: 98
- Joined: Mon 17 Oct 2016, 05:11
mistfire wrote:
> According to the comments of init script. 6 sfs files is the limit that can be only loaded when the puppy boots up because the performance degrades as the number of sfs file loaded increase.
I wonder if the number 6 means the number including adrv, fdrv, etc.
UpupBB has adrv, fdrv, ydrv and zdrv. If we take main sfs and save file into account, they already make 6. But, of course, UpupBB can load extra sfses.
I also remember that older Puppies were able to load up to 3 extra sfses.
> According to the comments of init script. 6 sfs files is the limit that can be only loaded when the puppy boots up because the performance degrades as the number of sfs file loaded increase.
I wonder if the number 6 means the number including adrv, fdrv, etc.
UpupBB has adrv, fdrv, ydrv and zdrv. If we take main sfs and save file into account, they already make 6. But, of course, UpupBB can load extra sfses.
I also remember that older Puppies were able to load up to 3 extra sfses.
-
- Posts: 98
- Joined: Mon 17 Oct 2016, 05:11
mistfire wrote:
> yes its possible by editing the initrd. You need to modify the init script then create more pup_ro folders in initrd filesystem.
If tazpuppy does not support 6 extra sfses, I will use it as it is. I am not going to go so far as to edit the initrd.
I thank you for making boot faster. However, I do not want to see the message "next boot will be faster!" at every boot.
I have unloaded devx sfs. As a result, the extra sfses are 4 in total, and tazpuppy boots smoothly.
> yes its possible by editing the initrd. You need to modify the init script then create more pup_ro folders in initrd filesystem.
If tazpuppy does not support 6 extra sfses, I will use it as it is. I am not going to go so far as to edit the initrd.
I thank you for making boot faster. However, I do not want to see the message "next boot will be faster!" at every boot.
I have unloaded devx sfs. As a result, the extra sfses are 4 in total, and tazpuppy boots smoothly.
Hi ! mistfire
no work in with syslinux
booted from microsd with adapter
fatal error
puppy_tazpup_5.0.sfs not found
label TazPuppy
linux /Tazpuppy/vmlinuz
initrd /Tazpuppy/initrd.xz
append autologin pmedia=usbflash psubdir=/Tazpuppy
#append rootfstype=ramfs
menu label TazPuppy
text help
Start TazPuppy normally.
endtext
linux /Tazpuppy/vmlinuz load FINE
initrd /Tazpuppy/initrd.xz load FINE
but no puppy_tazpup_5.0.sfs
puppy have boot code like tiny core usbwait=5
thanks
no work in with syslinux
booted from microsd with adapter
fatal error
puppy_tazpup_5.0.sfs not found
label TazPuppy
linux /Tazpuppy/vmlinuz
initrd /Tazpuppy/initrd.xz
append autologin pmedia=usbflash psubdir=/Tazpuppy
#append rootfstype=ramfs
menu label TazPuppy
text help
Start TazPuppy normally.
endtext
linux /Tazpuppy/vmlinuz load FINE
initrd /Tazpuppy/initrd.xz load FINE
but no puppy_tazpup_5.0.sfs
puppy have boot code like tiny core usbwait=5
thanks
hi mistfire this is the file
- Attachments
-
- pupdebug-0215190159.tar.gz
- (19.94 KiB) Downloaded 128 times
@AndresC2 could please run TazPuppy from your sd card on sd card adapter in diag mode by adding this boot parameter pfix=diag. Then post the result of the diagnostics here especially the list of partition. This will find if your sd card adapter was slow to detect.
By the way I will revise the init script to support increasing the usb waiting time
By the way I will revise the init script to support increasing the usb waiting time