Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sun 18 Aug 2019, 09:04
All times are UTC - 4
 Forum index » Advanced Topics » Cutting edge
Minimal Init Overlay v14 (mio) - alternate "init" and utils
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 2 of 2 [16 Posts]   Goto page: Previous 1, 2
Author Message

Joined: 28 Oct 2008
Posts: 1631
Location: Brisbane, Australia

PostPosted: Sat 29 Jun 2019, 18:18    Post subject: Minimal Init Overlay v14 (mio) - alternate "init" and utilit  

Minimal Init Overlay v14 (mio) - alternate "init" and utilities

This release explores a couple of concepts, and so introduces some new utilities.

1. Files can be "removed" by simply forgetting to "save" them.
For the save layer:
On shutdown a tar archive of the current RW directory is written, but specifying an exclude file that contains a list of all files that need to be "removed".
In 'init' the RW directory is clobbered with this tar archive, and so the new stack is built without the "removed" files.

The new CLI utilities 'clear-save-list', 'clear-save-dir', 'clear-save-file', and 'clear-save-mi', implement this concept.

2. When writing to the save layer (or a '.sfs' file), process only files, and write them to the "real-directory" as it exists in the current file system (i.e. the stack).
If $ONE_FILE contains the /path/name of a file, then;
REAL_DIR="$(readlink -m "$(dirname "$ONE_FILE")")"
Symbolic links are treated as normal files, except when writing to the save layer, then symbolic links that point to a directory are processed before other files.
Actually the code never tries to write directly to a layer, it leaves that to the stack code, e.g. overlayfs.

The GUI utility "Menu->Utility->MI Save squash" uses implementations of both these concepts for both save layer and '.sfs' files.
It can move installed files between the save layer and adrv.
This is particularly useful for minimising the size of the tar file when using an "Archive" save mechanism.
In "bionicpup64" it can also move updated files between the save layer and ydrv.

Downloads available from http://www.mediafire.com/folder/q04fxq43exkfr/mio:

Downloads available from http://www.mediafire.com/folder/7y3c7eafptzao/zipboot:

Installing mio v14:

From running mio v13:
1. Download the appropriate 'mio14...tar' file.
2. From the menu, run "Setup->MI Update frugal".
3. Reboot.

Manual install, add "mio" to running "normal" 'bionicpup32_8.0' or 'bionicpup64_8.0':
1. Download the appropriate 'mio14...tar' file, and extract it's contents into the current Puppy install directory.
At this point, all you really need to do is boot using 'mio_initrd.gz' instead of 'initrd.gz', provided that your boot entry for the current Puppy defines the install location appropriately.
So I suggest you use the following method, even though it seems a little verbose.
2. Run 'SFS-Load on-the-fly' and load 'mio14_upupbb_19.03.sfs' (or 'mio14_bionicpup64_8.0.sfs') as an extra sfs.
3. Check that your boot entry is ok.
In a console issue a command like "bootentry /path/to/current/Puppy/install/directory mbr'.
Compare the "pdrv=" and "psubdir=" parameters with your currrent boot-entry and adjust appropriately.
Note: The 'init' in "mio" does not search, the location of the Puppy '.sfs' files must be specified.
4. From the menu, run "Setup->MI Boot config", and select 'Enable'.
This copies the current 'initrd.gz' to 'release_initrd.gz', and 'mio_initrd.gz' to 'initrd.gz'.
Subsequently, you can then use "Setup->MI Boot config->Disable" and reboot to "normal" Puppy.
5. When done, reboot. This will be a first boot using "mio".

The 23.MiB download 'zipboot' option:
If you already have a copy of 'mio13_bionicpup32_8.0.zip', download 'mio13_bionicpup32_8.0.zip___mio14_bionicpup32_8.0.zip.delta'.
Use that to create an 'mio13_bionicpup32_8.0.zip', then do the following process from step 2.

The 270.9MiB download 'zipboot' option:
1. Download 'mio14_bionicpup32_8.0.zip'.
2. Setup an empty fat32 usb stick with a volume label of "USBPBOOT", (without the quotes).
In Puppy, you should be able to use the CLI utility 'fatlabel' to set the volume label.
3. Unzip the contents of 'mio14_bionicpup32_8.0.zip' into the root of the usb stick.
4. If your machine requires a non-uefi boot, use the utilities in either /utils/lin or /utils/win to write an mbr to the stick.
5. Boot the usb stick, this is a first boot with "mio" active.

This provides the opportunity to either, explore the capabilities of this "mio" fat32 based installation,
or to use the "FrugalPup v14" in this "mio" Puppy, to install 'mio14_bionicpup32_8.0.zip' to a Linux partition.

Of course if you have a Puppy with a working "FrugalPup v13", you can use it to install 'mio14_bionicpup32_8.0.zip' however you choose.

Note - bionicpup64:
After updating with "Setup->Puppy Updates" or "quickpet->Bionicpup updates", you may find that the MI utilities show as v11.
This is because the downloaded file, 'bionic64fix.zip', contains "FrugalPup v11".
You can use "Utility->MI Save squash->save2ydrv" to move the files written by "Puppy Updates" to ydrv.

Note - bionicpup32:
It can still be updated from '.delta' files just like a "normal" bionicpup32.

Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 2 of 2 [16 Posts]   Goto page: Previous 1, 2
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Cutting edge
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum

Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0621s ][ Queries: 11 (0.0131s) ][ GZIP on ]