Thanks for the feedback!
Please try this new script anyway and report your experience relative to the previous scripts you are satisfied with! If you have time! But not too much 'WhINEing'
New Remaster script Working!!
-
stemsee
Hmmm
Using Ovprecise on bootable USB drive
Rand script in /root and got these error messages:
Do you want to work in ram? y or n
y
Cannot stat source directory "/tmp/OVPrecise" because No such file or directory
'OVPrecise Puppy.sfs has been created in /tmp. Where do you want to save it to?
Enter the path e.g. /mnt/sda2/
mv: cannot stat `/tmp/OVPrecise': No such file or directory
All done!
What did I do wrong ?
thanks,
Thom
Using Ovprecise on bootable USB drive
Rand script in /root and got these error messages:
Do you want to work in ram? y or n
y
Cannot stat source directory "/tmp/OVPrecise" because No such file or directory
'OVPrecise Puppy.sfs has been created in /tmp. Where do you want to save it to?
Enter the path e.g. /mnt/sda2/
mv: cannot stat `/tmp/OVPrecise': No such file or directory
All done!
What did I do wrong ?
thanks,
Thom
-
Jasper
Hi guys,
Your new code only worked partially with my multi-session-live-CD.
That is, it made a bootable sfs, but with much missing as only 183Mb versus expected 216MB and no internet connection.
I think tlchost needs to add a directory to his path (which, I think, was explained in the earlier version).
My regards
Addendum:
I used the download from your first post because of your recent edit, but, upon reflection, is your newly published code different and the edit merely added "SOLVED"?
Your new code only worked partially with my multi-session-live-CD.
That is, it made a bootable sfs, but with much missing as only 183Mb versus expected 216MB and no internet connection.
I think tlchost needs to add a directory to his path (which, I think, was explained in the earlier version).
My regards
Addendum:
I used the download from your first post because of your recent edit, but, upon reflection, is your newly published code different and the edit merely added "SOLVED"?
-
stemsee
@tlchost
I got the same result trying to remaster studio1337 (slacko5.7) Very strange! I am looking into it! But EmSeeV2.2 and Fatdog64 700 b1 worked fine. You can try this updated script and UnattendedRemaster.
@jasper
There are significant edits in the recent scripts. Install this pet for all three scripts and find them in menu.
I have spent most of today improving the three scripts which I call my remastering-suite; unresync, sfsdirect-remaster and unattendedremaster (which does more than the others including create iso, all unattended after two inputs.
EDIT:
EDIT: 29th September 2014
Here it is!
rc1 of StemSeeS-Remastering-Suite.sfs
MKSQUASHFS
'1' for a gz compressed EmSeeV2.2, Studio1337, Slacko etc
'2' for a fatdog sfs
'3' for DebianDog squashfs.
ISO
'4' for bootable iso re/make.
'5' for burning iso to cd/dvd.
'6' for writing iso to usb storage device (hybrid).
SAVEFILE
'7' for savefile/swpfile creation.
NEW REMASTER
'8' for New SFS-Unattended-Remaster.
'9' for EXIT from this script.
'0' for SFS-Direct-Remaster.
CD-RW / DVD-RW TOOLS
'12' for multisession/formatting/data-iso.
'1' BURNING A MULTISESSION DVD
'2' CREATE A DISC IMAGE (not bootable)
'3' BURN AN ISO IMAGE TO DVD
'4' FORMATTING A DVD+RW DISC
'5' FORMATTING A CD-RW DISC
'6' EXIT this menu and restart from beginning
29th September 2014
https://drive.google.com/file/d/0B4GhZV ... sp=sharing
I got the same result trying to remaster studio1337 (slacko5.7) Very strange! I am looking into it! But EmSeeV2.2 and Fatdog64 700 b1 worked fine. You can try this updated script and UnattendedRemaster.
@jasper
There are significant edits in the recent scripts. Install this pet for all three scripts and find them in menu.
I have spent most of today improving the three scripts which I call my remastering-suite; unresync, sfsdirect-remaster and unattendedremaster (which does more than the others including create iso, all unattended after two inputs.
EDIT:
EDIT: 29th September 2014
Here it is!
rc1 of StemSeeS-Remastering-Suite.sfs
MKSQUASHFS
'1' for a gz compressed EmSeeV2.2, Studio1337, Slacko etc
'2' for a fatdog sfs
'3' for DebianDog squashfs.
ISO
'4' for bootable iso re/make.
'5' for burning iso to cd/dvd.
'6' for writing iso to usb storage device (hybrid).
SAVEFILE
'7' for savefile/swpfile creation.
NEW REMASTER
'8' for New SFS-Unattended-Remaster.
'9' for EXIT from this script.
'0' for SFS-Direct-Remaster.
CD-RW / DVD-RW TOOLS
'12' for multisession/formatting/data-iso.
'1' BURNING A MULTISESSION DVD
'2' CREATE A DISC IMAGE (not bootable)
'3' BURN AN ISO IMAGE TO DVD
'4' FORMATTING A DVD+RW DISC
'5' FORMATTING A CD-RW DISC
'6' EXIT this menu and restart from beginning
29th September 2014
https://drive.google.com/file/d/0B4GhZV ... sp=sharing
Last edited by stemsee on Mon 29 Sep 2014, 02:24, edited 9 times in total.
Well, the updated script creates an sfs file....but I'm feeling really dumb....does it create and iso file? Or do I copy the new sfs file to the usb drive which is used for the boot?stemsee wrote:@tlchost
I got the same result trying to remaster studio1337 (slacko5.7) Very strange! I am looking into it! But EmSeeV2.2 and Fatdog64 700 b1 worked fine. You can try this updated script and UnattendedRemaster.
Not being very technical, I am easily confused by simpole things like power switches, lights, etc.
Thom
-
stemsee
@tclhost
there are three scripts
1) sfsdirect-remaster is the newest and so far it just creates an sfs which should replace your main sfs on a frugal install. Maybe just rename the old one first until you are sure the new one boots.
2) unattendedremaster is the most versatile with special functions, squash an existing remaster directory or make iso from previous remaster, or make new remaster and new iso without interaction, suitable for all puppies.
3) unresync, sync your live system with an existing remaster directory for updates, or create a new remaster directory only.
there are three scripts
1) sfsdirect-remaster is the newest and so far it just creates an sfs which should replace your main sfs on a frugal install. Maybe just rename the old one first until you are sure the new one boots.
2) unattendedremaster is the most versatile with special functions, squash an existing remaster directory or make iso from previous remaster, or make new remaster and new iso without interaction, suitable for all puppies.
3) unresync, sync your live system with an existing remaster directory for updates, or create a new remaster directory only.
Last edited by stemsee on Mon 22 Sep 2014, 08:09, edited 2 times in total.
-
stemsee
I just realised something .... namely the script assumes 'huge' kernel is used i.e. the modules and firmware are not included in the remaster. I will add code to differentiate! That is why Jasper's sfs is smaller then expected. oops simply remove /lib/modules /lib/firmware from mksquashfs command for now.
The script is now working with Studio1337. As the problem was with modules & firmware, also in /root/.cache/ there is a menu configuration file which is essential.
There is a need for each distribution to have a specific exclusion file (a txt file containing line by line list of folders and files to be excluded in the mksquashfs command). Currently the script uses mksquashfs source-1 source-2 destination.sfs -e 'excluded files and folders', but using -'f' instead of '-e' uses the distro specific txt file of exclusions. These would best be created by each distro's creator/maintainer (or anyone with know how and time to submit such a file to me for inclusion) with provision for likely-to-be-installed apps. Then the script would automatically select the appropriate exclusion file by matching the DISTRO_SPECS variables!
The script creates an sfs from a frugal install, but I see no reason why it would not also work from a full install also (simply have not tested!). But I used to mksquashfs my full drive install and that worked without any exclusions or finesse.
The script is now working with Studio1337. As the problem was with modules & firmware, also in /root/.cache/ there is a menu configuration file which is essential.
There is a need for each distribution to have a specific exclusion file (a txt file containing line by line list of folders and files to be excluded in the mksquashfs command). Currently the script uses mksquashfs source-1 source-2 destination.sfs -e 'excluded files and folders', but using -'f' instead of '-e' uses the distro specific txt file of exclusions. These would best be created by each distro's creator/maintainer (or anyone with know how and time to submit such a file to me for inclusion) with provision for likely-to-be-installed apps. Then the script would automatically select the appropriate exclusion file by matching the DISTRO_SPECS variables!
The script creates an sfs from a frugal install, but I see no reason why it would not also work from a full install also (simply have not tested!). But I used to mksquashfs my full drive install and that worked without any exclusions or finesse.
Hi stemsee,
I promised I would look into this but didn't due to lack of time and various reason, sorry
Anyway I'm glad that you manage to make it work.
cheers!
I promised I would look into this but didn't due to lack of time and various reason, sorry
Anyway I'm glad that you manage to make it work.cheers!
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
-
stemsee
Hi Jamesbond
No problem. But I got the scripts working for fatdog 700, studio1337, EmSeeV2.2 and DebianDog. For fatdog 700 when i remastered and got the sfs to 800mb and packed into the initrd, it wouldn't boot. So I wondered what is the limit of the initrd size and why?
Also where do i find the code to auto edit from remaster script the initrd and replace the old sfs with the new one and repack, for FatDog64 700 b1...
Cheers
No problem. But I got the scripts working for fatdog 700, studio1337, EmSeeV2.2 and DebianDog. For fatdog 700 when i remastered and got the sfs to 800mb and packed into the initrd, it wouldn't boot. So I wondered what is the limit of the initrd size and why?
Also where do i find the code to auto edit from remaster script the initrd and replace the old sfs with the new one and repack, for FatDog64 700 b1...
Cheers
The normal limit of initrd is about 30% to 50% of the RAM size by default, and increased to 80% if you use "rootfstype=ramfs" on the bootloader. I haven't tested an SFS of that size for a long time, but I remember I could get it to boot with 2GB of RAM in a qemu. I may be wrong, though, it was a long time ago.stemsee wrote:No problem. But I got the scripts working for fatdog 700, studio1337, EmSeeV2.2 and DebianDog. For fatdog 700 when i remastered and got the sfs to 800mb and packed into the initrd, it wouldn't boot. So I wondered what is the limit of the initrd size and why?
Look in /usr/bin/filemnt.Also where do i find the code to auto edit from remaster script the initrd and replace the old sfs with the new one and repack, for FatDog64 700 b1...
Of if you can't be bothered, this will expand the initrd:
Code: Select all
mkdir /tmp/xxx; cd /tmp/xxx
cpio -i < /path/to/your/initrdCode: Select all
cd /tmp/xxx
find . | cpio -o -H newc > /path/to/your/new/initrd
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
-
stemsee
@Jamesbond
Thanks for the code. It works great! I added the original FatDog and DebianDog boot files for iso and a generic set for 'usual' pups.
The sfs is 5MB.
To do = fine tune the exclude files for the perfectionists! Hopefully a user of each distro will submit an exclude file (-'f' - a line by line list of files and folders to exclude from the remaster for a pristine sfs/iso). But that depends on the take up/interest ... as clearly there is no 'need' for these new scripts, but for newbies to have one package that can remaster every pup/live-distro would be pretty cool.
Thanks for the code. It works great! I added the original FatDog and DebianDog boot files for iso and a generic set for 'usual' pups.
The sfs is 5MB.
To do = fine tune the exclude files for the perfectionists! Hopefully a user of each distro will submit an exclude file (-'f' - a line by line list of files and folders to exclude from the remaster for a pristine sfs/iso). But that depends on the take up/interest ... as clearly there is no 'need' for these new scripts, but for newbies to have one package that can remaster every pup/live-distro would be pretty cool.
Last edited by stemsee on Fri 26 Sep 2014, 20:51, edited 1 time in total.
-
stemsee
-
Jasper
Hi stemsee,
I only use Precise 5.6 in multi-session-live-CD/DVD mode and I'm pleased to report that your SFSDirect is working well.
I think I might need at least 1 GB of ram to take advantage of the super-fast ram option - so I chose not to make my remastered sfs in ram and I entered my chosen hard drive partition - some 5 minutes later my remastered sfs was on that partition and all I had to do was to reboot to use it.
The remaster does include all of your new 3-option-5MB-sfs most of which I don't have any need for.
My regards and thanks
If anyone else wants to make a multi-session-live-CD/DVD they can save to - they must include one dated-save-file, but that's not necessary for those who want their remaster set in stone.
I only use Precise 5.6 in multi-session-live-CD/DVD mode and I'm pleased to report that your SFSDirect is working well.
I think I might need at least 1 GB of ram to take advantage of the super-fast ram option - so I chose not to make my remastered sfs in ram and I entered my chosen hard drive partition - some 5 minutes later my remastered sfs was on that partition and all I had to do was to reboot to use it.
The remaster does include all of your new 3-option-5MB-sfs most of which I don't have any need for.
My regards and thanks
If anyone else wants to make a multi-session-live-CD/DVD they can save to - they must include one dated-save-file, but that's not necessary for those who want their remaster set in stone.
-
stemsee
Hi Jasper
So sfsdirect is slower or faster for you? You can edit the sfs and remove /boot/fd/efiboot.img that weighs 10mb by itself!!!
Dated savefile? please provide details so I can include it or the possibility to create it in the special functions section of the script.! I am also thinking about including kernel/modules/firmware upgrades from my personal repositories.
So sfsdirect is slower or faster for you? You can edit the sfs and remove /boot/fd/efiboot.img that weighs 10mb by itself!!!
Dated savefile? please provide details so I can include it or the possibility to create it in the special functions section of the script.! I am also thinking about including kernel/modules/firmware upgrades from my personal repositories.
-
stemsee
Hi Stemsee.
I was unclear which option to choose for my puppy so it ended up using the automatic default. It started doing its remaster when I noticed my memory was running dangerously low. I noticed the script was using root for all the remaster files. I don't recall if there was a directory option for workspace but if not, you might want to consider adding an option to choose a workspace other than root.
Best,
Slavvo67
I was unclear which option to choose for my puppy so it ended up using the automatic default. It started doing its remaster when I noticed my memory was running dangerously low. I noticed the script was using root for all the remaster files. I don't recall if there was a directory option for workspace but if not, you might want to consider adding an option to choose a workspace other than root.
Best,
Slavvo67
-
stemsee
Slavvo67
Download the latest uploaded 26th evening,. There is more time to read the options. Default is now on /sda2. The version you have has an error which occurred after I added burn to cd/dvd and write to usb functions.
sfsdirect is fastest and gives options for ram (/tmp) or on device (sda/sdb etc)
Download the latest uploaded 26th evening,. There is more time to read the options. Default is now on /sda2. The version you have has an error which occurred after I added burn to cd/dvd and write to usb functions.
sfsdirect is fastest and gives options for ram (/tmp) or on device (sda/sdb etc)
Hi Stemsee:
I just wanted to report back that though backup was fast, it didn't seem to work quite right. The first time I booted, I had garbled lettering under the menu and icons. The next time, the lettering appeared ok, however my wireless usb card wasn't being read so no wlan0. I'll will do more testing but so far, it looks like the remaster needs some tweaking.
Best,
Slavvo67
P.S. - Using OV Precise Retro 5.8
I just wanted to report back that though backup was fast, it didn't seem to work quite right. The first time I booted, I had garbled lettering under the menu and icons. The next time, the lettering appeared ok, however my wireless usb card wasn't being read so no wlan0. I'll will do more testing but so far, it looks like the remaster needs some tweaking.
Best,
Slavvo67
P.S. - Using OV Precise Retro 5.8
-
stemsee
slavvo67
thanks for feedback!
sfs-direct-remaster works from the running system if you happen to use the system while it is remastering that could cause errors. Also
after remaster and before reboot did you remove the savefile? or change the grub kernel boot argument to pfix=ram (or copy, but not fsck)?? As the contents of the savefile should then be included in the remastered .sfs. Also before installing the latest package did you properly remove the previous package?
However, I have again improved the scripts and removed the third script UnReSync which is already a function of the other two scripts.
Now I am testing, it should be ready soon.
thanks for feedback!
sfs-direct-remaster works from the running system if you happen to use the system while it is remastering that could cause errors. Also
after remaster and before reboot did you remove the savefile? or change the grub kernel boot argument to pfix=ram (or copy, but not fsck)?? As the contents of the savefile should then be included in the remastered .sfs. Also before installing the latest package did you properly remove the previous package?
However, I have again improved the scripts and removed the third script UnReSync which is already a function of the other two scripts.
Now I am testing, it should be ready soon.