I will have to take it a bit easy, family activity is increasing and grandad does not have an escape any longer. I will return to try and figure out what is going on.
A fix for the time being has now allowed me to write this post from Firefox on a running liveHDD where the bootloader.pm is fixed up but no time to test if it can install, this is the now the burning question. I am scrambling through the manual for mkisofs
, pheeew that is heavy going not understanding more than 5%.
From that I applied option -r
and this seems to make the destination livecd.sqfs
proper, ie now the .sqfs
is back to 4 characters and it is totally read only.
I will use another new install of KDE32 and do it your way, as I did make a quick run keeping everything in the B-20 partition but that did not help. Added:
Running the liveHDD with edited bootloader.pm I installed the ISO to an empty partition-07 on my 3rd HDD, it worked bar minor fumblings like getting totally wrong password to what I normally use. I will scrap the install later.
I used the installed KDE32-2012.12 after fully updating and adding a few smaller treats of my own, to experiment with your suggestion. I almost managed to do exactly but I had actually made the directory
[root@localhost gert]# mkdir /home/user/test-iso/unsquash
not sure what happened here as when I came to do the unsquash, complaining that directory existed, quickly just added /expand
and the process proceeded.
[root@localhost gert]# unsquashfs -d /home/gert/test-iso/unsquash/expand /za/livecd.sqfs
I have my original ISO loop mounted on /za
so I could point to the livecd.sqfs
Shortly afterwards this succeeded.
[root@localhost gert]# mksquashfs /home/gert/test-iso/unsquash/expand livecd.sqfs
I followed up with a second run where the destination file was on /media/B-20
, seems moving to another copy of the OS may have paid off.
Though I am niggled by why I had the trouble on the previous system, so I probably will go back and investigate a bit more.