You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I apologize for the length and lack of eloquency ahead. I have some questions regarding live persistency, update/upgrade/rolling up, packages preserving/installs concerns, brtfs in a theoretically future installed system and backups.
Background:
I have a relatively new live persistance system, I know we probably shouldn't install/update things usually there but I did.
It's already more functional by many means than the system I use (which I also like), though it's a bit bloated - only due to me overdoing it in a delight of an exploring newbie without much of a clue of what shouldn't be installed/upgraded.
I know it has limitations (Kernel should never get updated for example) and that the USB key itself has limitations though I don't know the details. (Issues like corruption, USB life time, other update issues? limited backup and restore options for the USB live persistence system.)
Level of "experty": an exploring newbie now, a relatively long time user of another linux OS "for starters", still at a newbie level.
No terminal knowledge beside a few very basic updating commands, wishing to learn. Created live persistent images for some OS according to detailed simple instructions, having a past of installing mutiple OS'es at a newbie level. Can follow basic instructions if detailed enough and not assuming prior knowledge/understanding/experty.
To my questions:
Can I install it as a working system with what I loaded on the USB? with my settings and installed packages etc (though prefferably with suggestions of what I may likely like to remove, but that's not a must. It works fine)
If yes, can I install while chosing btrfs and other partition table for a future HDD install (I don't use brtfs now, neither on the USB nor on any other system) while preserving what I want to preserve from question 1?
Meanwhile, I know I updated it (not dist, just update and upgrade) - how much of this can still be done assuming I'll probably have in a few months an option to install the system on the HD?
Also, relating to question 3, what are my "reasonable" options meanwhile regarding update/upgrade/package installs/change of image/backup/restore while still on the USB key? Noting I have enough place to mess around with things for now.
Forgot to add this - can I "clone" the USB key somehow?
This topic have been edited a lot for phrasing/trying to fix some typos and some additions.
P.S.
This SpiralLinux live persistence USB system was created by ping-wu's guide on topic number 8, with adjustments of adding /run just before /media for steps 2,3,3a and 3b as applicable - as it was needed in my system to prevent errors, mounting the iso from another place (not copying it as is by itself even solely for step 2. This helped with the space issue in the EFI partition) and just noting I did the rsync stage (after installing rsync as it was not yet installed then on my other linux OS) from within the USB's EFI partition if I recall correctly. Partitions "qualify" for the suggestion of ping-wu in that topic.
As a side note not needed for those questions but which maybe could help others, ventoy's debian related instructions (on the persistence plugin page) also worked
[tested on cinnamon with ventoy: this worked with the persistence .dat file [with the matching reference on the json file - note the persistence file accurate name], similar to kali's or clonezilla's instructions in ventoy's page and also the debian example bellow on the same page - which was what I used - it is the last sh exmple on the persistence page, (noting also the .dat file can be renamed. I kept the .dat saffix), but loaded slowly in my case as it tries and fail some virtuatization options, brtfs didn't work for this image IIRC (though I didn't use it anyway eventually) and maybe I had better started with a small persistence then extend it, which I eventually did in a later testing of ventoy's]
Ventoy's also has a resizable persistence image option - which can be used even in a multiboot option in a versatile way, which is very useful (and is used)
ping-wu's though worked for me much better as an individual "setup", I think that for me it's at least much faster than ventoy's in load and much more stable/it's much more clear how much space you have left, and ping-wu's is the current "setup" for my favorite USB persistence live "install", it's what I am testing now, and the one which those questions reffer to.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I apologize for the length and lack of eloquency ahead. I have some questions regarding live persistency, update/upgrade/rolling up, packages preserving/installs concerns, brtfs in a theoretically future installed system and backups.
Background:
I have a relatively new live persistance system, I know we probably shouldn't install/update things usually there but I did.
It's already more functional by many means than the system I use (which I also like), though it's a bit bloated - only due to me overdoing it in a delight of an exploring newbie without much of a clue of what shouldn't be installed/upgraded.
I know it has limitations (Kernel should never get updated for example) and that the USB key itself has limitations though I don't know the details. (Issues like corruption, USB life time, other update issues? limited backup and restore options for the USB live persistence system.)
Level of "experty": an exploring newbie now, a relatively long time user of another linux OS "for starters", still at a newbie level.
No terminal knowledge beside a few very basic updating commands, wishing to learn. Created live persistent images for some OS according to detailed simple instructions, having a past of installing mutiple OS'es at a newbie level. Can follow basic instructions if detailed enough and not assuming prior knowledge/understanding/experty.
To my questions:
This topic have been edited a lot for phrasing/trying to fix some typos and some additions.
P.S.
This SpiralLinux live persistence USB system was created by ping-wu's guide on topic number 8, with adjustments of adding /run just before /media for steps 2,3,3a and 3b as applicable - as it was needed in my system to prevent errors, mounting the iso from another place (not copying it as is by itself even solely for step 2. This helped with the space issue in the EFI partition) and just noting I did the rsync stage (after installing rsync as it was not yet installed then on my other linux OS) from within the USB's EFI partition if I recall correctly. Partitions "qualify" for the suggestion of ping-wu in that topic.
As a side note not needed for those questions but which maybe could help others, ventoy's debian related instructions (on the persistence plugin page) also worked
[tested on cinnamon with ventoy: this worked with the persistence .dat file [with the matching reference on the json file - note the persistence file accurate name], similar to kali's or clonezilla's instructions in ventoy's page and also the debian example bellow on the same page - which was what I used - it is the last sh exmple on the persistence page, (noting also the .dat file can be renamed. I kept the .dat saffix), but loaded slowly in my case as it tries and fail some virtuatization options, brtfs didn't work for this image IIRC (though I didn't use it anyway eventually) and maybe I had better started with a small persistence then extend it, which I eventually did in a later testing of ventoy's]
Ventoy's also has a resizable persistence image option - which can be used even in a multiboot option in a versatile way, which is very useful (and is used)
ping-wu's though worked for me much better as an individual "setup", I think that for me it's at least much faster than ventoy's in load and much more stable/it's much more clear how much space you have left, and ping-wu's is the current "setup" for my favorite USB persistence live "install", it's what I am testing now, and the one which those questions reffer to.
Beta Was this translation helpful? Give feedback.
All reactions