Printable View
I have a 2 Gb SD Chip of Knoppix 6.2.1 that works just about right.
My portable has a hard drive, a cdrw drive and a usb slot for
one-and-one-only SD Chip. I also have another physically identical
2 Gb SD Chip.
I'd like to end up with a second 2 Gb Chip identical to the first.
I don't want to go to all the trouble of re-mastering. Isn't there
some (simpler) way to utilize the capabilities I've indicated to
get what I want? Utilizing dd, toram and other majic words, perhaps?
One way to do it is to use (for instance)Quote:
Originally Posted by utu
Once that's running, you can unplug the flash drive and then plug in the new one, after which you could use the flash-install feature. There are lots of ways to skin that particular cat...Code:knoppix tohd=/dev/sda1
Cheers!
Krishna :mrgreen:
p.s. If your partition is NTFS-formatted, you run a small risk of glitching it if you write with Knoppix. I've done it many times, though, and only once had a serious (but recoverable) problem.
@krishna
Thanks, Krishna.
Keep in mind, I want the clone to boot, and I want it to remember
all my clever tweaks in persistant whatever.
AFAIK, this procedure will do that. Let us know how it goes!Quote:
Originally Posted by utu
Cheers!
Krishna :mrgreen:
I would create a directory on the hard disk and copy the persistent image from the first SD card to that directory. Afterwards I would boot Knoppix from CD and do a flash install on the second SD card. Then I would copy the persistent image from the hard disk to the KNOPPIX directory on the second SD card. The two SD cards should be identical.
Yes, this would certainly work, too.:-D If your CD is slow, though, it would probably be faster to do it from the first flash drive, as I described. And the caveat about the filesystem remains. One option is to create another partition for Knoppix, and/or a swap partition (using GParted, probably.)Quote:
Originally Posted by klaus2008
Cheers!
Krishna :mrgreen:
Greetings from a clone.
I ended up using Klaus2008's method, and that works just fine.
I did the cut and paste parts in Win7 with no ill effects,
at least none I've observed so far.
I also now have a Pearl Harbor .img file, albeit on ntfs premises.
Editing a Fat32 file on an ntfs system for use with Linux seemed
to me a juggle unlikely to come to a good end. But it did.
I struggled to get the reserved space size right, since I'd
forgotten a minor edit of the non-image part of the equation.
As a consequence, my clone didn't at first have enough room to
hold the original's .img
I suspect if the clone had more than enough room, that also might
have worked, but I've not proved this.
Thanks Klaus2008.
In essence, a file (in and of itself) is not tied to any particular filesystem - it's just stored under that filesystem (NTFS, FAT32, etc.) So copying files from one to another is perfectly kosher, albeit reputedly risky when the destination type is NTFS. But it works (mostly), as you showed.Quote:
Originally Posted by utu
Are you saying that you took too much room with the KNOPPIX file within the KNOPPIX folder? Or was the FAT partition itself too small? Just curious...Quote:
I struggled to get the reserved space size right, since I'd
forgotten a minor edit of the non-image part of the equation.
As a consequence, my clone didn't at first have enough room to
hold the original's .img
I suspect if the clone had more than enough room, that also might
have worked, but I've not proved this.
Thanks Klaus2008.
Ciao!
Krishna :mrgreen:
I decided when I made the original 6.2.1 that I didn't need isolinux, and could gain a few bites
for the persistent image by deleting isolinux before allocating the maximum space to the .img.
When I went to apply Klaus2008's idea, I'd forgotten about this edit, and as a consequence
was a few bites shy of enough room for the original's .img.
aka shooting yourself in the foot.
so the basic idea is to make a brand new fresh live install on the 2nd sd card.
and then just simply copy every thing inside the 1st sd card into the 2nd one.
am i right?
The "extra" file to be copied is in the KNOPPIX folder, called "knoppix-data.*" (depends on whether it's encrypted or not.)Quote:
Originally Posted by kcah
Ciao!
Krishna :mrgreen:
Klaus2008's idea is to make a new bootable USB, including providing persisent storage,
exactly the same way as the first was made. Presumably from a CD. The only difference
between the two USBs should be the persistent images. You then cut-and-paste with
the USB's unmounted. You erase the clone's new knoppix-data.img file and replace it
with a copy of the knoppix-data.img from the original USB. You can even do the cut-
and paste in Windows, as I did.
One idea - not quite in sync with your discussion, but worth mentioning. Since Utu uses Windows - there is a tool called USB Image Tool. Its available for free from http://www.alexpage.de/usb-image-tool/download/
It makes image of the entire USB including boot sectors and restores it on demand. I use it to back up my Knoppix under Windows. It has an option to compress the image for less space. What I know is, it works well with SD cards too
It can be used to transfer the entire image to another SD card
@ post#12
I don't know how to cut-and-paste anything unmounted, either.
My bad.
I was thinking about the dd bit-by-bit copy method.
I never got that to work, I might add.
hmm... so will this also work backwards?
do i get a fresh start if i just swap a fresh installed knoppix back to an old/used install?
You get a fresh flash install of Knoppix 6 if you remove the persistent image in the KNOPPIX directory. The system will ask you for the size of the persistent image file at next boot from that flash device.
You can boot with:Quote:
Originally Posted by klaus2008
to keep the system free of the effects of the image, copy it elsewhere, then create a new image on the next boot. It could then be loop-mounted to get stuff off of the old one, as well, if necessary.Code:knoppix noimage
Cheers!
Krishna :mrgreen:
In coming back to this topic in 6.4.3, I note the following problem situation:
Earlier, using 6.2.1, I had allotted 1160 or so for persistent storage, leaving
a few unused Mbs on the SD Card. In 6.4.3, I allotted 1181, leaving no unused Mbs.
What worked before as a backup scheme isn't working for me now.
Saving the img on Win7 and attempting to replace imgs did NOT work.
The process won't complete, because the SD Card has too little space.
Perhaps the imgs are a bit larger in ntsf than in FAT32.
Trying to do the same img replacement game in a Knoppix CD environment also
did NOT work. The process completed without complaint, but the persistent store
no longer worked at all.
There may be some small overhead requirement even here.
I haven't heard any independent complaints, but I'd suggest those interested
leave around 10Mb's unused in their persistent store operation if they intend
to rely on this switcheroo scheme.
More on this whenever I have to rebuild my current 6.4.3 setup.
Any useful comments in the meantime are welcome.