StemseeS-Remastering-Suite-V5.4 pet 22/05/15
hi Jasper
The swap savefile feature is just a mechanical illusion, using 3 savefiles. The original, the new-empty, and the desired one, followed by restartX or something. Just shifting the contents around the triangle, rather than actually mounting and un-mounting, but that would be the preferred option. I will experiment with both methods, and I see a third also, but I lack the technical know-how to script it.
The reason I add it to StemseeS-Remastering-Suite (with post remaster utilities) rather than a separate pet/sfs is because only need to add a few lines of code, packaging is already done! And the create a savefile option with mounting and syncing is already in the Menu. The user is welcome to separate it if desired or just download the entire 1.14mb pet/sfs.
stemsee
The swap savefile feature is just a mechanical illusion, using 3 savefiles. The original, the new-empty, and the desired one, followed by restartX or something. Just shifting the contents around the triangle, rather than actually mounting and un-mounting, but that would be the preferred option. I will experiment with both methods, and I see a third also, but I lack the technical know-how to script it.
The reason I add it to StemseeS-Remastering-Suite (with post remaster utilities) rather than a separate pet/sfs is because only need to add a few lines of code, packaging is already done! And the create a savefile option with mounting and syncing is already in the Menu. The user is welcome to separate it if desired or just download the entire 1.14mb pet/sfs.
stemsee
Similar to?
Code: Select all
mv save zzsave && sleep 1 && mv zsave save && sleep 1 && mv zzsave zsave
rsync or cp not mv
present savefile contents backed-up to new-savefile, copy wanted savefile contents to present (empty) savefile. restartX see if it works?
Actually mv should do it.
Code: Select all
mv /initrd/pup_rw/* /initrd/pup_a/ && cp /initrd/desired-save/* /initrd/pup_rw/
Actually mv should do it.
the command to unmount savefile seems to be
the code to mount the savefile seems to be
Is there something else to it?
Code: Select all
umount -l /initrd/pup_rw
Code: Select all
mount -t ext4 $path$SAVEPART$SAVEFILE /initrd/pup_rw
Hello @StemSee. Considering the work you have done in both Remaster and Save-session, does this effort by @Gyro offer an extension/option to your work? (I saw your post on your reorganization potential)
Edited: missing PLDF thread's URL
Edited: missing PLDF thread's URL
Last edited by gcmartin on Tue 02 Dec 2014, 08:31, edited 1 time in total.
I tested Option 3 on Unattended Remaster and the following occurred:
For the drive, I chose SDA3. I had it mounted.
I received an error: /usr/bin/sfs-unattended-remaster: line 473
/mnt/sda3/apupsys/etc/DISTRO-SPECS:
No such file or directory.
After checking my SDA3, most of the files were moved into bpupiso directory.
For the drive, I chose SDA3. I had it mounted.
I received an error: /usr/bin/sfs-unattended-remaster: line 473
/mnt/sda3/apupsys/etc/DISTRO-SPECS:
No such file or directory.
After checking my SDA3, most of the files were moved into bpupiso directory.
@slavvo67
You would normally have run sfs-unattended-remaster, menu option 8, first, choosing sda3 as the word drive! So I assume that you didn't do that and therefore there was no existing apupsys directory, or that you selected the option to delete that directory at the end of the previous remaster, which means you attended the remasterbecause default is to leave the folder , apupsy, in existence! Looking at the script I see that I need to put a better test in place for the apupsys folder. The script looks for /etc/DISTRO_SPECS in apupsys, but doesn't stop if not found. Then the script offers to rsync with running system ... at this point if apupsys doesn't exist then it could be created, or a path to the remaster section should be made.
Have you completed any successful remasters during this time?
Thanks for the feedback!
You would normally have run sfs-unattended-remaster, menu option 8, first, choosing sda3 as the word drive! So I assume that you didn't do that and therefore there was no existing apupsys directory, or that you selected the option to delete that directory at the end of the previous remaster, which means you attended the remasterbecause default is to leave the folder , apupsy, in existence! Looking at the script I see that I need to put a better test in place for the apupsys folder. The script looks for /etc/DISTRO_SPECS in apupsys, but doesn't stop if not found. Then the script offers to rsync with running system ... at this point if apupsys doesn't exist then it could be created, or a path to the remaster section should be made.
Have you completed any successful remasters during this time?
Thanks for the feedback!
I'm working on it as I write this. It seems to be working quite slow when creating the sfs file. That might be because my distro is packed with LibreOffice, Truecrypt, PhotoRec/Testdisk, Seamonkey, Opera, MPlayer, to name a few. I'll let you know of the outcome. I'm doing a backup of the Puppy OV Precise Retro 5.8.
Sorry that I haven't been quicker responding to this. Barry's QU has spoiled me a bit, as it shuts down quickly and saves on the fly. It would be nice if his backup system created smaller backups but it seems to work well.
Sorry that I haven't been quicker responding to this. Barry's QU has spoiled me a bit, as it shuts down quickly and saves on the fly. It would be nice if his backup system created smaller backups but it seems to work well.
My initial results
Ok. Results were good when using (8 or 10). I believe 10 produced the .sfs file only, which was easily dragged and dropped into place on my USB. It renamed the .sfs the exact same as what was on the USB... I knew you were working on this ... NICE TOUCH!
I believe choosing 8 created other files but I wasn't sure what they were for? I originally thought for an .iso but burning the directory gave me a kernal error (could not find kernal VM Linux). It booted to your splash screen but items 2 and 3 would not work due to this kernal error. If they were supposed to be a recreation of the USB, this seems to have failed as the names of the files differed. I didn't boot to test this.
You'll notice from the attached photo that the count is different between the top and the bottom (one at 84%, one at 52% - not sure why).
Your menu was a little confusing for those of us that don't read very closely so I would suggest changing some of the options; putting the more likely important options on top and the "add ons" below. I would also put a 'q' for quit other than another number.
Overall, it seems pretty cool. I need to play around with it more. I believe item 10 gave me the best result (creating an sfs only, with the exact name of my distro .. just drag and drop onto the usb and reboot - provided you are not running that usb live at the time).
I will certainly be testing this one more as there are plenty of different options here. Maybe you can make a brief "how to" html or txt file?
All the best and thanks for the nice product!
Slavvo67
I believe choosing 8 created other files but I wasn't sure what they were for? I originally thought for an .iso but burning the directory gave me a kernal error (could not find kernal VM Linux). It booted to your splash screen but items 2 and 3 would not work due to this kernal error. If they were supposed to be a recreation of the USB, this seems to have failed as the names of the files differed. I didn't boot to test this.
You'll notice from the attached photo that the count is different between the top and the bottom (one at 84%, one at 52% - not sure why).
Your menu was a little confusing for those of us that don't read very closely so I would suggest changing some of the options; putting the more likely important options on top and the "add ons" below. I would also put a 'q' for quit other than another number.
Overall, it seems pretty cool. I need to play around with it more. I believe item 10 gave me the best result (creating an sfs only, with the exact name of my distro .. just drag and drop onto the usb and reboot - provided you are not running that usb live at the time).
I will certainly be testing this one more as there are plenty of different options here. Maybe you can make a brief "how to" html or txt file?
All the best and thanks for the nice product!
Slavvo67
thanks slavvo67
There are one or two bugs to squash and some improvements to make.
The reason it took long to make the squashfs was that you chose either rxm or dxm compression. For a speedy result choose either rg or dg, that will be the quikest.
SFS-direct-remaster will be developed to produce a bootable iso as well as sfs-unattended-remaster.
regards
stemsee
There are one or two bugs to squash and some improvements to make.
The reason it took long to make the squashfs was that you chose either rxm or dxm compression. For a speedy result choose either rg or dg, that will be the quikest.
SFS-direct-remaster will be developed to produce a bootable iso as well as sfs-unattended-remaster.
regards
stemsee
Things I never ever thought of!
As you can see there is a lot of repeated code that should be reduced to functions. I am planning to rewrite.
So Just create your functions and after testing I will add them to the menu, or replace the existing faulty entries.
If you search for nluug-get.pet aftter installing run fixmenus then restart x. In the menu will be gdrive-get. Run that and explore stemsee pet files, you will find the latest remastering -suite.pet
As you can see there is a lot of repeated code that should be reduced to functions. I am planning to rewrite.
So Just create your functions and after testing I will add them to the menu, or replace the existing faulty entries.
If you search for nluug-get.pet aftter installing run fixmenus then restart x. In the menu will be gdrive-get. Run that and explore stemsee pet files, you will find the latest remastering -suite.pet