".000" added to target name

[aewell]

Hi All,

I am using partimage-0.6.4-1.1.fc3.rf.i386.rpm on White Box Enterprise
Linux 4 (same as RHEL4).

When I use partimage from the command line, batch mode, I have noiticed
that part image adds ".000" to my target name.
That is:

partimage -z1 -o -d -b save /dev/sda2 /images/w2kImage.gz

will turn into "w2kImage.gz.000". Is there a way to stop this?

If not, how do I get it added to the "bug list?"

Many thanks,
--Tony

[ty2spot]

there is no need to list into the gz call unless you are going to be manually unpacking or other processes on the info that has been imaged.

The .000 designation is in order that if you were to want to make the image sizable for cdrom or dvd burning you could and it would look for the next in series when finished with current file on restore options. Usually this is how I use the CD's of images from greaterr than 2 yrs ago(not keeping them on the HDD). From terminals, I F2 into a new terminal and then umount the cdrom and insert the next disk and then mount it and give the filename. If it is a file that is already on my server or mounted on a unit that the client can reach it will automatically extend into them as long as you are not using ssl or login.

[aewell]

I use "gz" on the name as a crutch to remind me that I used the "-z1"
option. Just as I and others will use ".txt" on their files names to
denote text files, even though Linux has no stinkin' Windows registry
to contend with.

On the ".000" front, I think I understand what you are doing. You are
numbering the chunks such that you can burn them to CD's.

Compromise: If the command is not called that regulates the chuck size
(such that they can fit on individule CD's), DO NOT add the ".000"
(I am backing up to 200 GB removable SATA drives.)

Many thanks,
--Tony

[vladimirprieto]

has this issue (the .000 end filename) been solved?
is there's a workaround or somethig?

i ask cuz i c date posts are so old.

thanks

[nosilver4u]

No, the .000 syntax is still used, and probably always will be. Personally, I think it might be more confusing if it only did it when the files were being split. It's easy enough once you know that it always adds .000 to just always put that on the end.