Minimal Init Overlay v20 (mio) - alternate "init" and utilities
This is a feature release.
It includes FrugalPup v20:
see http://www.murga-linux.com/puppy/viewto ... 66#1052566.
a new utility InitrdModules:
see http://www.murga-linux.com/puppy/viewto ... 22#1053822
a new feature:
A "save query" option that works for all mio pupmodes including pupmode=12.
It utilises the 'asktosave_func' that already exists in 'rc.shutdown'.
This adds to the current "no save" option that also works in all mio pupmodes including pupmmode=12.
A demonstration that you don't need pupmode=13 to have flexible save options.
Downloads available from http://www.mediafire.com/folder/q04fxq43exkfr/mio:
'mio20_bionicpup32_8.0.tar' (4.1 MiB)
'mio20_bionicpup64_8.0.tar' (4.1 MiB)
Download available from http://www.mediafire.com/folder/7y3c7eafptzao/zipboot:
'mio20_bionicpup32_8.0.zip' (276.8 MiB)
gyro
Minimal Init Overlay v22 (mio) - alternate "init" and utils
Minimal Init Overlay v21 (mio) - alternate "init" and utilities
This is a feature release.
A re-vamped sfs file support:
Sfs files are condidered to be either "Puppy system" sfs files, (adrv...sfs, ydrv...sfs, pdrv...sfs, fdrv...sfs, zdrv...sfs) or "Extra" sfs files.
"Puppy system" sfs files are automatically loaded by 'init' if they exist, they are not specified by the user.
They reside in only the current install directory, using their pre-defined filenames,
although they can be a relative symbolic link to an sfs on the same partition,
e.g. "ln -s ../linux_firmware_20200328.sfs fdrv_upupbb_19.03.sfs"
"Extra" sfs files have to be selected using the "MI Extra SFS List manager" utility.
They are selected into either the ABOVE list or the BELOW list.
Files in the ABOVE list are loaded into the stack above the "Puppy system" sfs files.
Files in the BELOW list are loaded into the stack below the "Puppy system" sfs files.
They can reside anywhere in the available filesystem, even on another device, with any filename.
A special case is the mio...sfs file in the current install directory, which is always included in the ABOVE list.
If your sfs file needs to "update" files that exist in the "Puppy system" sfs files, add it into the ABOVE list.
If your sfs contains files that do not exist in the "Puppy system" sfs files, add it to the BELOW list.
e.g. any devx...sfs should be added to the BELOW list.
If you are not sure, it's best to try it in the BELOW list first.
Note:
The previous EXTRA list is now the BELOW list.
The previous MAIN list nolonger exists.
Downloads available from http://www.mediafire.com/folder/q04fxq43exkfr/mio:
'mio21_bionicpup32_8.0.tar' (4.1 MiB)
'mio21_bionicpup64_8.0.tar' (4.1 MiB)
Download available from http://www.mediafire.com/folder/7y3c7eafptzao/zipboot:
'mio21_bionicpup32_8.0.zip' (276.8 MiB)
gyro
This is a feature release.
A re-vamped sfs file support:
Sfs files are condidered to be either "Puppy system" sfs files, (adrv...sfs, ydrv...sfs, pdrv...sfs, fdrv...sfs, zdrv...sfs) or "Extra" sfs files.
"Puppy system" sfs files are automatically loaded by 'init' if they exist, they are not specified by the user.
They reside in only the current install directory, using their pre-defined filenames,
although they can be a relative symbolic link to an sfs on the same partition,
e.g. "ln -s ../linux_firmware_20200328.sfs fdrv_upupbb_19.03.sfs"
"Extra" sfs files have to be selected using the "MI Extra SFS List manager" utility.
They are selected into either the ABOVE list or the BELOW list.
Files in the ABOVE list are loaded into the stack above the "Puppy system" sfs files.
Files in the BELOW list are loaded into the stack below the "Puppy system" sfs files.
They can reside anywhere in the available filesystem, even on another device, with any filename.
A special case is the mio...sfs file in the current install directory, which is always included in the ABOVE list.
If your sfs file needs to "update" files that exist in the "Puppy system" sfs files, add it into the ABOVE list.
If your sfs contains files that do not exist in the "Puppy system" sfs files, add it to the BELOW list.
e.g. any devx...sfs should be added to the BELOW list.
If you are not sure, it's best to try it in the BELOW list first.
Note:
The previous EXTRA list is now the BELOW list.
The previous MAIN list nolonger exists.
Downloads available from http://www.mediafire.com/folder/q04fxq43exkfr/mio:
'mio21_bionicpup32_8.0.tar' (4.1 MiB)
'mio21_bionicpup64_8.0.tar' (4.1 MiB)
Download available from http://www.mediafire.com/folder/7y3c7eafptzao/zipboot:
'mio21_bionicpup32_8.0.zip' (276.8 MiB)
gyro
Minimal Init Overlay v22 (mio) - alternate 'init' and utilities.
This is a feature release.
1. The sfs file system has had an extra tweek.
The 'mio...sfs' file is now considered a Puppy system file, and so no longer appeas in the ABOVE list.
The name of this file no longer contains the mio version, so it will remain unchanged across mio updates.
Both the ABOVE and BELOW lists are now empty by default.
Clicking on any sfs file and choosing "Install SFS" will now provide an option to add it to the ABOVE or the BELOW list.
2. Perhaps the most obvious new feature is that download files are now sfs files instead of tar files,
With a new stand alone implementation script 'to-mio22'.
With an sfs file, the 'to-mio22' is included in this single download file,
but it can still be executed with just a few clicks.
3. The "MI Update frugal" utility has been withdrawn.
4. The 'README.txt' file in 'initrd.gz' has been updated to reflect the current way of processing sfs files.
5. The file '/initrd/tmp/bootinit.log' can now be found as '/initrd/bootinit.log', beside the other "interesting" files.
6. 'mio22_up_bionicpup64_8.0.sfs' includes a patched "/usr/local/quickpet/bionicupdate" that does not clobber FrugalPup files.
Downloads available from http://www.mediafire.com/folder/q04fxq43exkfr/mio:
'mio22_up_bionicpup32_8.0.sfs' (4.1 MiB)
'mio22_up_bionicpup64_8.0.sfs' (4.1 MiB)
'mio22_up_xenialpup_7.5.sfs' (4.2 MiB)
'README.txt' (10.6 KiB)
To use:
1. Download an appropriate mio22 sfs file.
2. Click on the downloaded sfs file and select "View contents", to mount it.
3. Click on the upgrade script 'to-mio22' to execute it.
4. Click on the "Ok" button of the "Done" message.
5. Click on the downloaded sfs file again, to unmount it.
6. Reboot into new mio.
This process should work for both,
upgrading a "normal" Puppy to using "mio", and upgrading mio21 to mio22.
The downloaded sfs file can be stored anywhere.
The utility 'to-mio22' always attempts to upgrade the current running Puppy.
Issue:
If you try to run 'to-mio22' on a Puppy other than the one defined by the download sfs file's name,
it will complain that it cannot find the mio...sfs file for the current Puppy and exit.
To work around, you could 'unsquashfs' the downloaded sfs file,
then open the 'squashfs-root' directory and rename the included sfs file to match the current Puppy,
then run the 'to-mio22' utility in the 'squashfs-root' directory.
gyro
This is a feature release.
1. The sfs file system has had an extra tweek.
The 'mio...sfs' file is now considered a Puppy system file, and so no longer appeas in the ABOVE list.
The name of this file no longer contains the mio version, so it will remain unchanged across mio updates.
Both the ABOVE and BELOW lists are now empty by default.
Clicking on any sfs file and choosing "Install SFS" will now provide an option to add it to the ABOVE or the BELOW list.
2. Perhaps the most obvious new feature is that download files are now sfs files instead of tar files,
With a new stand alone implementation script 'to-mio22'.
With an sfs file, the 'to-mio22' is included in this single download file,
but it can still be executed with just a few clicks.
3. The "MI Update frugal" utility has been withdrawn.
4. The 'README.txt' file in 'initrd.gz' has been updated to reflect the current way of processing sfs files.
5. The file '/initrd/tmp/bootinit.log' can now be found as '/initrd/bootinit.log', beside the other "interesting" files.
6. 'mio22_up_bionicpup64_8.0.sfs' includes a patched "/usr/local/quickpet/bionicupdate" that does not clobber FrugalPup files.
Downloads available from http://www.mediafire.com/folder/q04fxq43exkfr/mio:
'mio22_up_bionicpup32_8.0.sfs' (4.1 MiB)
'mio22_up_bionicpup64_8.0.sfs' (4.1 MiB)
'mio22_up_xenialpup_7.5.sfs' (4.2 MiB)
'README.txt' (10.6 KiB)
To use:
1. Download an appropriate mio22 sfs file.
2. Click on the downloaded sfs file and select "View contents", to mount it.
3. Click on the upgrade script 'to-mio22' to execute it.
4. Click on the "Ok" button of the "Done" message.
5. Click on the downloaded sfs file again, to unmount it.
6. Reboot into new mio.
This process should work for both,
upgrading a "normal" Puppy to using "mio", and upgrading mio21 to mio22.
The downloaded sfs file can be stored anywhere.
The utility 'to-mio22' always attempts to upgrade the current running Puppy.
Issue:
If you try to run 'to-mio22' on a Puppy other than the one defined by the download sfs file's name,
it will complain that it cannot find the mio...sfs file for the current Puppy and exit.
To work around, you could 'unsquashfs' the downloaded sfs file,
then open the 'squashfs-root' directory and rename the included sfs file to match the current Puppy,
then run the 'to-mio22' utility in the 'squashfs-root' directory.
gyro