$ sudo unetbootin
Last edited by kyeshi98 (2013-04-28 12:00:39)
Last edited by notroot (2013-03-24 06:50:43)
Hey that would be great! The advantage of a file is you can back it up easily just by copying it and always get your system back the way it was when you made the copy. I do that right before installing new packages I'm not familiar with. Then you can compress the backups so they don't take up a lot of space. You can always mount the persistence file from another OS to get at your stuff that way if necessary.
A question in regards to:
Note: Persistence in this case does NOT appear on the "persistence" partition; instead, it actually appears as part of the root partition. Therefore, try making a file in your "home" folder, restart, and check to see if it remains.
Step 5: Put the USB back into a Linux system (not the LiveUSB system) and use your favorite partitioning tool to resize the first partition and make a new partition labeled "persistence" (not "live-rw"). Again, I used GParted.
Does the persistence partition need to be just big enough for the conf file, since the persistence is not stored there?
The way I understand from your post is that the persistence is stored on the root partition, so if my first partition is just big enough for the live image, then it won't have any room to store the persistent files.
Am I misinterpreting something?
Also in Step 6, is there supposed to be a space between the / and union?
Hi, thank you for this guide, I wanted to say it helped a lot and I'm writing this from a live boot of Waldorf right now thanks to it
I did want to add one thing though to step 5, which is that the second partition, "persistence", needs to be a Linux filesystem specifcally. I guess it might be obvious once you think about it, but since the first partition was a Fat32, I assumed the second would need to be too. After some TSing where every boot with persistence resulted the system looping repeatedly with an error that was too fast for me to catch, I found in one of your links an fdisk output that showed the second partition's info.
I deleted the second partition and created an ext2 one in it's place (I swear I choose ext3, but guess not) and now I can boot up without issue. I hope that can save other's a little time
Thanks again for the guide!
Thanks for the guide, I'd like to know if it's possible to mount the FAT32 partition (not the persistence partition, after all I already have access to it from within the OS). As it's so handy to use it as a storage drive with Windows and then use the USB key to boot a persistent CrunchBang session, I'd like to access those Windows files from within the OS: is this possible?
@provaprova - I've only just come across your post.
I don't think it will be possible to access anything on the pendrive directly from Windows.
When it runs, you are actually in a Linux file system, & the persistence is joined to it using the union file system, that is why it appears to all be under the same /.
If you installed a Linux compatible file system access program under Windows, you probably can mount the persistence partition to get at your files.
Last edited by fatmac (2013-09-10 08:19:02)
Last edited by Slowki (2013-09-21 06:12:58)
after more than 10 days spent searching in the forums
I could do it thanks to your howto!
I suppose there is big confusion around about the difference between wheezy and squeeze,
So this confusion I also had.
For Waldorf it's needed to label the partition "persistence".
Also the name of the file I suppose has to be "live-persistence.com".
At least it worked for me also.
I can also confirm that the live system cannot mount the partition and also gives some error message at boot,
But then everything works allright.
Oh. Perhaps, try choosing a specific flavor from the official website - as the different flavors are based off of different systems (Slackware, Ubuntu, not sure about Debian) while #! is based directly off of Debian. Therefore, the installation of persistent LiveUSB systems may also vary.
Thank you kyeshi98.
I'll try with CB first, see if it runs properly on 508 MB of RAM. If it doesn't, I'll go with Puppy.