[kde-linux] deleted .kde

[david]

When I was using OS/2, I had a script (in IBM's standard scripting 
language, I forget what it's called) that would go through a specified 
directory tree (using a specified backup file size) and generate a 
series of file lists optimized to fit as many files into the backup size 
as it could. Then it could feed each file list to your preferred burning 
software and burn them to optical media. Or simply zip them individually 
and burn them later.

James Loughner wrote:
> I use Kdar it makes backup sets to the size you want. Then you can burn
> them with K2b or whatever. What surprises me is no one has combined the
> functionality so you can backup direct to CD/DVD. Yes you can make a
> script but a lot of people can't do it and it is tricky because you must
> prompt the user to  change disks and  for the next backup file then
> start the burn again for the new disk and it may not be obvious how many
> disks are needed when you start.
> 
> Jim
> 
> david wrote:
>> Kevin Krammer wrote:
>>   
>>> On Thursday 27 December 2007, david wrote:
>>>     
>>>> You'll also need to change ownership of your copied .kde folder - it
>>>> needs to belong to the correct user ID. On my Debian systems (using
>>>> private groups), that would be "chown -R your_user_ID:your_user_ID
>>>> ~.kde" for the .kde folder and everything in it.
>>>>       
>>> This is whyI always recommend using tar, because it creates the files with the 
>>> current user's identity on extraction.
>>>     
>> The problem with tar (for me) is it creates a single big file. In my 
>> case, about 36GB big for my home directory. Too big for the older SMB 
>> support to move around on the network (haven't tried Etch's CIFS support 
>> yet). Hard to keep offline backups on optical media.
>>
>> Of course, for the original poster's need to maintain a backup of his 
>> .kde folder, the backup file wouldn't be that large.
>>
>>   
> 


-- 
David
gnome at hawaii.rr.com
authenticity, honesty, community