-
Copying customizations from USB to USB; backing up customizations
Until recently, I was using Knoppix on a USB key with a persistent data store as a large normal file, which I would back up frequently so that if I screwed something up, I could just restore that one file and get back to where I was without having to redo all my customizations from scratch. However, I'm now interested in experimenting with VirtualBox, which uses files that are larger than can be contained in a FAT32 filesystem, let alone a virtual filesystem file within that filesystem.
I tried using the "experimental" script to make a new USB key with large file capabilities, but now I realized that 1) I don't know how to transfer my customizations to this new type of persistent data store, and 2) once I figure out how to do this, backing up these customizations will go from being a minor inconvenience to being a major chore, since most of my computers cannot natively read this new filesystem. Does anyone here have any suggestions for a simple backup procedure I could use?
And why does the script use this "ReiserFS" filesystem, anyway? From the little I've read about it, development on it has ground to a halt. Wouldn't it be better to have the install script ask the user what filesystem it should use?
I also tried pre-formatting the new USB with NTFS, only to find that Knoppix won't install on NTFS. Why not? Is there an easy way for me to get it onto an NTFS USB key?
-
ad 1) You can try to start your Knoppix - with persistent memory in an overlay file - without activating the persistent memory (cheatcode: knoppix noimage). To get access to the content of the persistent memory you have to create a directory on a partition with available free space; I used in this example '/mnt/repair'. Start in a terminal:
Code:
su
mkdir /mnt/repair
losetup /dev/loop1 /mnt-system/KNOPPIX/knoppix-data.img
mount /dev/loop1 /mnt/repair
Copy all of '/mnt/repair' to partition#2 of the other USB stick you've already prepared to use persistent memory in an overlay partition.
Don't forget to shutdown your stick with:
Code:
umount /dev/loop1
losetup -d /dev/loop1
ad 2) http://www.wp-schulz.de/summary/summary-backup.html
And why does the script use this "ReiserFS" filesystem, anyway? From the little I've read about it, development on it has ground to a halt.
ReiserFS is a proven Linux filesystem since many years; which development do you exspect?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
Western Digital 1TB WD Blue PC Desktop 3.5'' Internal CMR Hard Drive - WD10EARZ
$44.99
Western Digital 1TB WD Blue SA510 SATA SSD Internal 2.5”/7mm Cased - WDS100T3B0A
$79.99
### MZ-7KE1T0 Samsung 850 Pro Series 1TB 2.5 inch SATA3 SSD ###
$105.00
Western Digital 1TB WD Gold Enterprise Class SATA Internal HDD - WD1005FBYZ
$84.99
Samsung - 980 PRO 1TB Internal Gaming SSD PCIe Gen 4 x4 NVMe
$109.99
Patriot P210 128GB 256GB 512GB 1TB 2TB 2.5" SATA 3 6GB/s Internal SSD PC/MAC Lot
$19.99
Crucial MX500 SSD 1TB SATA III 6Gb/s 2.5" Internal Solid State Drive
$40.00
Samsung - Geek Squad Certified Refurbished 870 EVO 1TB SATA Solid State Drive
$67.99
1TB/2TB USB 3.0 Flash Drive Thumb U Disk Memory Stick Pen PC Laptop Storage lot
$580.99
Apple 1TB Solid State Drive for Apple MacBook Pro
$80.00