- This topic has 8 replies, 3 voices, and was last updated Feb 24-7:43 pm by dolphin_oracle.
-
Posts
-
olsztyn
I want to clarify that this my question on ISO snapshot function may seem as just another angle of my dwelling on recent issue with Live USB Maker. It is not. ISO Snapshot behavior appears to be pre-existing – the same with old and new version of Live USB Maker, if we look at results.
Specifically:
As I previously assumed ISO Snapshot is to create an ISO image of the current working system, with the expectation that such image could be used to restore the original system.
Taking an ISO image of antiX Live USB however it does not seem to work out that way… If Live USB Maker (regardless of version it seems) is used to restore a Live USB antiX from such image the result looks at first visually the same as the original but all pre-existing in the original settings of persistence are lost and the such restored Live system is without any persistence which was in the original system. On top of this, any attempt to re-instate persistence of the restored system would wipe out all established previously settings rendering the resulting system vastly different than the original. Either way such restored antiX system is useless.
So what is good of ISO Snapshot if Live antiX cannot be restored to the original state from such image?
Any ideas of solution or a workaround will be greatly appreciated…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
anticapitalista
The primary function of iso-snapshot is to create an ISO image of the current INSTALLED working system.
When running live, since iso-snapshot does not recognize persistence files, it will not save them. It basically creates an iso of what is in the linuxfs. If you want the tool to save what you have in rootfs and/or homefs, you must remaster first.Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
If you want the tool to save what you have in rootfs and/or homefs, you must remaster first.
Understood. It is remastered. The point is that setting persistence afresh in such restored system wipes out all pre-existing settings due to failure in the boot step to copy existing file to new homefs. The error pops in red upon answering ‘y’ to question whether to copy existing files. Could not capture the entire message but it seems to refer to rsync. In result of this failure the resulting system seems all defaults, missing all previously existing settings and therefore vastly different than the original.
Due to error message it seems to me this behavior is unintentional rather than designed to not work with Live antiX. But if you say it is designed to not support Live regardless of this behavior I do accept it and I would like to kindly ask our community how to re-instate the original settings…- This reply was modified 3 years, 2 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parametersanticapitalista
I just tested this.
Made myself a live usb (of base) with encryption via live-usb-maker (gui).
Booted, set up persist_root, installed gimp, libreoffice and switched to using jwm.
Remastered and set up new rootfs.
Rebooted to jwm desktop with gim and libreoffice.
Ran iso-snapshot, saved file to external device, chose Personal option.
Once finished I also plugged in another usb stick, ran lum-gui clone without encryption and it finished without error.
(encryption fails as we know).Cloned usb devise is the same as the original without encryption of course.
Booted the snapshot iso in Virtualbox and it is the same as the original live usb.
I’m about to test how that snapshot boots on an encrypted live-usb via lum-gui.
Ok – used lum-gui to write an encrypted live-usb of my snapshot and it boots to jwm desktop plus gimp and libreoffice.So it seems to do what you want it to.(unless the issue is caused by the existence of homefs – I’ll test that later)
- This reply was modified 3 years, 2 months ago by anticapitalista.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
dolphin_oracle
IIRC there is a question at home persistence creation if an existing home folder exists inside the linuxfs file to copy the info from the linuxfs/home folder to the new homefs persistence file.
in any case, that does require saveing your /home into your remaster.
Thanks very much for your trouble. The way I remember I did not have issues with rootfs persistence, unless my memory is confused now due to multiple testing I performed and got lost in what is what. It is homefs that was a challenge as specifying Home (or All) persistence resulted in failure to copy existing files from /Home to the homefs in the relevant step during boot as mentioned in my post.
Specifically, to make myself clear:– If booted the restored image without persistence then desktop looks exactly like the original and app settings, desktop menus and /home content is there – files, etc. as in the original.
– If booted with Home persistence (or ALL) then during boot it sets up persistence file to my size I like and then asks whether to copy existing /home content (files) to new homefs. If answered ‘y’ (this is what I want – to have the same desktop as the original) then fails on this copy step with error pointing to rsync. It proceeds but the resulting system looks like defaults – all settings, app settings and personal menu and files in /home gone. Currently I am trying to find out how to manually save content of /home in Live-USB-Storage and then copy back to newly created homefs. Hopefully this would re-instate all settings and files and have home persistence working…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parametersdolphin_oracle
it would be nice to get that error message is possible.
it would be nice to get that error message is possible.
So, as this happens just once, when you set persistence to newly cut Live USB from ISO snapshot I re-created such fresh Live USB and went through the process and captured this message. I had to use camera as I could not find the log where it is recorded.
So retyping the relevant sequence of messages:
”
There are 615 MiB of files that will get hidden by home persistence
There are 2781 MiB free on the home persistence device
Do you want to copy the files to the home persistence device?
y=yes. n=no. The default is yes
>y
Error: /live/linux/usr//bin/rsync: error while loading shared libraries: li…
so.1: cannot open shared object file: No such file or directoryEnabled home persistence
”
I am afraid rightmost part of the error message got cut off in my capture…Also, just want to mention that my experiment to manually rectify this copy failure appears to work:
– Before setting the home persistence option above I copied the entire content of /home (615M) to Live-USB-Storage to save it before it is wiped out.
– After setting homefs persistence (actually Persistence=All), which resulted in default desktop with all settings wiped out, copied back the saved relevant files from Live-USB-Storage back to /Home, including some config folders, such as .fluxbox folder.
It appears this manual fix works such as I was able to restore the original fluxbox composition including menus, etc.
I am not sure what would be complete recommended set of config files though to make it a complete manual resolution…Also just to refresh: This was done on Live antiX restored from ISO snapshot using Live USB Maker version 2.41.17 using ‘Encrypt’ option. So this version of LUM (latest) works with ISO snapshot as input but fails with error when run with ‘From running system’ option. Both cases use ‘Encrypted’. The previous version LUM 2.41.16 was working fine with ‘From Running system’, so my saved older copy is my another option to use.
It appears to me that ISO Snapshot function should work fine with Live USB if home persistence / copy error is fixed. Otherwise manual copy seems to fix this deficiency.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parametersdolphin_oracle
thank you for the detailed procedure to duplicate.
- You must be logged in to reply to this topic.
