Partially automated remastering of sfs files
Posted: Sun 12 Jan 2014, 20:34
I used manual remastering info from here:
http://www.smokey01.com/coolpup/remastering.html
to create machine specific remasters of frugal installs, including
personal Save files that include installs of the latest Firefox
browser, my bookmarks, Flash player, Sylpheed, Pan, wireless
setup, and the Freecell game. Included also is the MVPS hosts file
in /etc which makes browsing and internet searches much more
sane (ad free). The following script includes merging of the entire
personal Save file. Typically, the new sfs is about 60 meg
larger in size. I have no interest in trying to remove anything.
Sda2 is a 10 gig ext2 partition I use for strictly for this purpose:
-------------- Save this text as makesfs.sh ----------------------------
echo "Please wait. Copying files from original squash file ..."
mkdir -p /mnt/sda2/work
cp -a /initrd/pup_ro2/* /mnt/sda2/work
echo "Merging files from personal Save file ..."
cp -a /initrd/pup_rw/* /mnt/sda2/work
echo "Creating remaster ..."
mkdir -p /mnt/sda2/remaster
cd /mnt/sda2
mksquashfs work remaster/puppy.sfs -noappend
echo "Finished! Remastered file puppy.sfs is in /mnt/sda2/remaster"
---------------------------------------------------------------------------------------
Make sure sda2 is mounted, and then open a terminal. If you locate
the file in /root then type:
sh /root/makesfs.sh
When it finishes, rename puppy.sfs to the particular
name of the puppy .sfs file. I rename the old .sfs and
.2fs files before copying the remastered .sfs file to
their directory. If all is well, I then delete the old
renamed files.
I find I create new .sfs files in four to six minutes using this
script, which is fast enough that I don't mind using it when
a new version of Firefox is available. I manually delete the
/work and /remaster directories when finished with them
so I'm ready to run the script again in the future.
01micko's article on remastering (above link) includes a long line
of text used to create a new iso file that contains the new .sfs
file. I've used that (modified) line in a script I named makeiso.sh
which I run in a terminal. The creation of a new .iso (if that's
your goal) just takes another few seconds. However, I have
little use for remastered .iso files. My interest is strictly in
protecting the work I put into personalizing a frugal installed
pup.
Art
http://www.smokey01.com/coolpup/remastering.html
to create machine specific remasters of frugal installs, including
personal Save files that include installs of the latest Firefox
browser, my bookmarks, Flash player, Sylpheed, Pan, wireless
setup, and the Freecell game. Included also is the MVPS hosts file
in /etc which makes browsing and internet searches much more
sane (ad free). The following script includes merging of the entire
personal Save file. Typically, the new sfs is about 60 meg
larger in size. I have no interest in trying to remove anything.
Sda2 is a 10 gig ext2 partition I use for strictly for this purpose:
-------------- Save this text as makesfs.sh ----------------------------
echo "Please wait. Copying files from original squash file ..."
mkdir -p /mnt/sda2/work
cp -a /initrd/pup_ro2/* /mnt/sda2/work
echo "Merging files from personal Save file ..."
cp -a /initrd/pup_rw/* /mnt/sda2/work
echo "Creating remaster ..."
mkdir -p /mnt/sda2/remaster
cd /mnt/sda2
mksquashfs work remaster/puppy.sfs -noappend
echo "Finished! Remastered file puppy.sfs is in /mnt/sda2/remaster"
---------------------------------------------------------------------------------------
Make sure sda2 is mounted, and then open a terminal. If you locate
the file in /root then type:
sh /root/makesfs.sh
When it finishes, rename puppy.sfs to the particular
name of the puppy .sfs file. I rename the old .sfs and
.2fs files before copying the remastered .sfs file to
their directory. If all is well, I then delete the old
renamed files.
I find I create new .sfs files in four to six minutes using this
script, which is fast enough that I don't mind using it when
a new version of Firefox is available. I manually delete the
/work and /remaster directories when finished with them
so I'm ready to run the script again in the future.
01micko's article on remastering (above link) includes a long line
of text used to create a new iso file that contains the new .sfs
file. I've used that (modified) line in a script I named makeiso.sh
which I run in a terminal. The creation of a new .iso (if that's
your goal) just takes another few seconds. However, I have
little use for remastered .iso files. My interest is strictly in
protecting the work I put into personalizing a frugal installed
pup.
Art