Code: Select all
cp -a -v --remove-destination
Also by doing it your way it leaves a directory in the /mnt call +(whatever the name of the sfs file is).
but that is a good tip for getting to see what is in a sfs file.
Code: Select all
cp -a -v --remove-destination
Hi DesertPuppy,DesertPuppy wrote:In 4.12 you don't need the line added to rc.modules because that file is not in there anymore I think it's call modulesconfig or somthing like that.
I hope this small contribution to DesertPuppy's excellent work will help those using more recent versions of Puppy.STEP 1.
First make sure you have downloaded the devx_431.sfs
NOTE: I always download it to / - that is the top directory not /root but /
STEP 2.
There is no step 2 as Puppy431 seems to have sfs support built-in. The 'modprobe squashfs' command is in /etc/rc.d/rc.sysinit
STEP 3:
Double-clicking on the sfs file mounts it as /mnt/+devx_431.sfs
In the /mnt directory you should see +devx_431.sfs, and in there you should be able to see all the contents of the sfs
STEP 4:
open up a terminal window from the / directory and type the following:
NOTE: there is a space between --remove-destination and /mntCode: Select all
cp -a -v --remove-destination /mnt/+devx_431.sfs/* / >devcopy.txt
Also there is a space between /mnt/+devx_431.sfs/* and /
And a space between / and >devcopy.txt
it will seem like puppy has paused for a few seconds
(depends on speed of computer) just wait , when you see the # sign
again you are good to go.
NOTES:
At this point I got an errorbut since the model directory in the sfs is empty I don't think it matters (BTW the model directory on the HD is a symlink to the ppd directory)Code: Select all
cp: cannot overwrite non-directory '/usr/share/cups/model' with directory '/mnt/+devx_431.sfs/usr/share/cups/model'
The devcopy.txt file will show you everything
that got copied over and where it went to.[/b]
STEP 5:
now type:
that will unmount the sfs file and if youCode: Select all
#umount /+devx_431.sfs #sync
check /mnt/+devx_431.sfs will now be empty again.
STEP 6:
This next step may or may not be needed but I do it just to be sure:
type:
STEP 7:Code: Select all
#ldconfig
to test to make sure it all worked type:
and you should get a response like:Code: Select all
#gcc
Code: Select all
gcc: no input files