Posted: Wed 29 Aug 2018, 03:09
Hi Perdido.
Going back to your screen cap on page 1, and please correct me if I'm
wrong, I notice that you are trying to create an sfs archive from a pinstall.sh
script in a fully installed Puppy.
Yoo-hoo!!!
Conceptually, that's an extreme sport of sorts for a Puppy distro !!!
Let me explain:
One thing is certain: using sfs's in a full install is iffy. -- If you have a full
install, you go all the way, you install the apps whether through a pet or a
deb or rpm archive and that is it. You try not to use sfs's.
Here's why:
sfs's are meant to be used in frugal installs. IIRC, fully installed Pups do NOT
have the "au" layer-unifying whachamacallit utility, whereas frugally
installed Pups depend on it, it's vital for frugal installs.
Sorry for the "mouse" imagery , but the "au" layer-unifying
whachamacallit utility manages the "gruyere cheese holes" the sfs's fit into.
In a full install, there are no "gruyere cheese holes to fit sfs's into" and no
layers; all programs and libs, etc., are on the same level. So the "au" layer-
unifying whachamacallit utility either is not there or has no" gruyere cheese
layers" to manage.
Look at the PUPSTATE # for a full install and look at BarryK's diagram for it,
it's pretty clear, I think.
~~~~~
2nd point, IMO -- and as I said, I have never done a full install of Puppy.
You may be asking too much of the Puppy system: install a BBIIGG pet
archive AND then immediately afterwards start a squashfs compression?
If you run htop or a similar diagnostics app, and then start the mksquashfs
compression app, you'll see that mksquashfs grabs almost all the computer's
resources for the job it's doing.
I'm not sure if you and rockedge are talking about the same pet file, but if
that pet file is 252 Mg, as rockedge mentions, I would suggest you do one
operation and give the Pup a "bone break" (You can have coffee or tea or
a pop or a beer!) And then, when the Pup is rested, ask it to do the
squashing operation.
But again, AFAIK, sfs's do not play well in full installs. So in the context of
a full install, maybe creating an sfs is not the way to go. Why not provide
another pet, simply?
My 2 ยข, but IHTH.
Going back to your screen cap on page 1, and please correct me if I'm
wrong, I notice that you are trying to create an sfs archive from a pinstall.sh
script in a fully installed Puppy.
Yoo-hoo!!!
Conceptually, that's an extreme sport of sorts for a Puppy distro !!!
Let me explain:
One thing is certain: using sfs's in a full install is iffy. -- If you have a full
install, you go all the way, you install the apps whether through a pet or a
deb or rpm archive and that is it. You try not to use sfs's.
Here's why:
sfs's are meant to be used in frugal installs. IIRC, fully installed Pups do NOT
have the "au" layer-unifying whachamacallit utility, whereas frugally
installed Pups depend on it, it's vital for frugal installs.
Sorry for the "mouse" imagery , but the "au" layer-unifying
whachamacallit utility manages the "gruyere cheese holes" the sfs's fit into.
In a full install, there are no "gruyere cheese holes to fit sfs's into" and no
layers; all programs and libs, etc., are on the same level. So the "au" layer-
unifying whachamacallit utility either is not there or has no" gruyere cheese
layers" to manage.
Look at the PUPSTATE # for a full install and look at BarryK's diagram for it,
it's pretty clear, I think.
~~~~~
2nd point, IMO -- and as I said, I have never done a full install of Puppy.
You may be asking too much of the Puppy system: install a BBIIGG pet
archive AND then immediately afterwards start a squashfs compression?
If you run htop or a similar diagnostics app, and then start the mksquashfs
compression app, you'll see that mksquashfs grabs almost all the computer's
resources for the job it's doing.
I'm not sure if you and rockedge are talking about the same pet file, but if
that pet file is 252 Mg, as rockedge mentions, I would suggest you do one
operation and give the Pup a "bone break" (You can have coffee or tea or
a pop or a beer!) And then, when the Pup is rested, ask it to do the
squashing operation.
But again, AFAIK, sfs's do not play well in full installs. So in the context of
a full install, maybe creating an sfs is not the way to go. Why not provide
another pet, simply?
My 2 ยข, but IHTH.