

System Software
Hi,
1. *Please* give all dialogs parents! Its silly when a messagebox gets a taskbar entry! (For example, configure shortcuts and configure toolbars appear as top-level windows, and can be minimized - but when they are, KDar is not usable)
--> Hadn't noticed. I'll look into it.
2. Your config dialog seems to be a Qt one, and not a KDE one. It'd be better to use KJanusWidget, KDialogBase, KPushButton, etc. to get a better KDE look.
--> Yeah, I'm working on this. See the News items at kdar.sf.net. There are some screenshots of recent development work there.
3. Fonts. Is it really necessary to be able to configure these?
--> Yes :). For example, I can't stand being able to print from a program's window and be stuck with something that might look great on screen (big letters, say) but takes up tons of paper to print. If you don't like it, ignore the option. If you have an alternative that solves that issue without font configuration, I'd love to have it.
4. Is it possible to exclude directory patterns? For example I'd like to exclude .libs and .deps wherever they're located.
--> It's broken, but is ostensibly a feature. Please file a bug report.
Sorry to be seento complain, but they're only minor points...
--> Are you kidding? That's how free software gets better, in large part to active users like yourself! ;)
Cheers,
JB
P.S. Feel free to contribute to the KDar developers or users mailing lists, so others who follow those lists, but not necessarily this one, can comment too. Thanks. - Apr 05 2005
1. *Please* give all dialogs parents! Its silly when a messagebox gets a taskbar entry! (For example, configure shortcuts and configure toolbars appear as top-level windows, and can be minimized - but when they are, KDar is not usable)
--> Hadn't noticed. I'll look into it.
2. Your config dialog seems to be a Qt one, and not a KDE one. It'd be better to use KJanusWidget, KDialogBase, KPushButton, etc. to get a better KDE look.
--> Yeah, I'm working on this. See the News items at kdar.sf.net. There are some screenshots of recent development work there.
3. Fonts. Is it really necessary to be able to configure these?
--> Yes :). For example, I can't stand being able to print from a program's window and be stuck with something that might look great on screen (big letters, say) but takes up tons of paper to print. If you don't like it, ignore the option. If you have an alternative that solves that issue without font configuration, I'd love to have it.
4. Is it possible to exclude directory patterns? For example I'd like to exclude .libs and .deps wherever they're located.
--> It's broken, but is ostensibly a feature. Please file a bug report.
Sorry to be seento complain, but they're only minor points...
--> Are you kidding? That's how free software gets better, in large part to active users like yourself! ;)
Cheers,
JB
P.S. Feel free to contribute to the KDar developers or users mailing lists, so others who follow those lists, but not necessarily this one, can comment too. Thanks. - Apr 05 2005
Beta testers are needed to put KDar-2.0.0-beta2 through its paces as we prepare for the official release of 2.0.0.
KDar-2.0.0 has several new features, including a detailed progress dialog for archive creation, and the ability to cancel any archive operation cleanly and swiftly, without having to "killall kdar" from a shell. See the release notes and Changelog at the sf.net/projects/kdar website for details.
KDar-2.0.0-beta2 depends on dar-2.2.0_pre3. Both programs are in "testing" phase, so DO NOT USE IN YOUR PRODUCTION SYSTEM, and do not rely on KDar-2.0.0-beta2 for your critical backups.
KDar-2.0.0-beta2 can be downloaded at
http://sourceforge.net/project/showfiles.php?group_id=96947&package_id=103671&release_id=299965
Thanks,
JB - Jan 27 2005
KDar-2.0.0 has several new features, including a detailed progress dialog for archive creation, and the ability to cancel any archive operation cleanly and swiftly, without having to "killall kdar" from a shell. See the release notes and Changelog at the sf.net/projects/kdar website for details.
KDar-2.0.0-beta2 depends on dar-2.2.0_pre3. Both programs are in "testing" phase, so DO NOT USE IN YOUR PRODUCTION SYSTEM, and do not rely on KDar-2.0.0-beta2 for your critical backups.
KDar-2.0.0-beta2 can be downloaded at
http://sourceforge.net/project/showfiles.php?group_id=96947&package_id=103671&release_id=299965
Thanks,
JB - Jan 27 2005
Look at the contents of the config.log. (search for libdar.hpp). What are the details of the error?
Please move this discussion over to the
kdar-users@lists.sourceforge.net mailing list.
I prefer not to entertain "comments" like this. The mailing list is a more centralized place for these things, where hopefully more people can benefit from the discussion.
Thanks and Cheers,
JB - Aug 15 2004
Please move this discussion over to the
kdar-users@lists.sourceforge.net mailing list.
I prefer not to entertain "comments" like this. The mailing list is a more centralized place for these things, where hopefully more people can benefit from the discussion.
Thanks and Cheers,
JB - Aug 15 2004
KDar-1.2.0-beta4 is out at sourceforge:
http://sf.net/projects/kdar
DO NOT USE THIS RELEASE FOR PRODUCTION-SYSTEM BACKUPS.
It is still beta software. Instead,
use kdar-1.1.1 or dar-2.1.4 for backups.
Includes many bugfixes from beta3, and
many new features, including a progress
bar for archive creation.
Please report bugs to the sourceforge bugtracker.
Enjoy,
JB - Aug 01 2004
http://sf.net/projects/kdar
DO NOT USE THIS RELEASE FOR PRODUCTION-SYSTEM BACKUPS.
It is still beta software. Instead,
use kdar-1.1.1 or dar-2.1.4 for backups.
Includes many bugfixes from beta3, and
many new features, including a progress
bar for archive creation.
Please report bugs to the sourceforge bugtracker.
Enjoy,
JB - Aug 01 2004
I just noticed that you're running libdar 2.4. My version of dar shows libdar 2.3:
dar version 2.1.3, Copyright (C) 2002-2052 Denis Corbin
Using libdar 2.3 built with compilation time options:
Extended Attributes support: NO
Large files support (> 2GB): YES
ext2fs NODUMP flag support : YES
Special allocation scheme : YES
Integer size used : 64 bits
Get libdar version 2.3.
JB - Jul 23 2004
dar version 2.1.3, Copyright (C) 2002-2052 Denis Corbin
Using libdar 2.3 built with compilation time options:
Extended Attributes support: NO
Large files support (> 2GB): YES
ext2fs NODUMP flag support : YES
Special allocation scheme : YES
Integer size used : 64 bits
Get libdar version 2.3.
JB - Jul 23 2004
Backup profiles are now a feature of KDar in release 1.2.0-beta1.
This is a beta version, so don't run it as your primary backup utility on production systems. Use KDar-1.1.1, or dar-2.1.3, or something else.
More info at http://kdar.sf.net, and http://sf.net/projects/kdar
Expect to see the official 1.2.0 release within a few weeks.
Cheers,
JB - Jul 14 2004
This is a beta version, so don't run it as your primary backup utility on production systems. Use KDar-1.1.1, or dar-2.1.3, or something else.
More info at http://kdar.sf.net, and http://sf.net/projects/kdar
Expect to see the official 1.2.0 release within a few weeks.
Cheers,
JB - Jul 14 2004
Have a look at your config.log, and search for libdar64. The error messages should indicate why the configure script failed to find the required library.
You can send the config.log to jerrb@sourceforge.net if you want me to have a look at it.
JB - Jul 13 2004
You can send the config.log to jerrb@sourceforge.net if you want me to have a look at it.
JB - Jul 13 2004
Chris,
Pass the same configuration options to kdar as you did for dar.
In particular, the integer versions must be the same.
The main options to look for are
./configure --enable-mode=64 --enable-largefile --disable-debug
Change the 64 to a 32 if you are using the 32-bit integer version. Leave the --enable-mode out if you're using the infinite integer version.
Check which version you are running with "dar -V".
JB - Jul 06 2004
Pass the same configuration options to kdar as you did for dar.
In particular, the integer versions must be the same.
The main options to look for are
./configure --enable-mode=64 --enable-largefile --disable-debug
Change the 64 to a 32 if you are using the 32-bit integer version. Leave the --enable-mode out if you're using the infinite integer version.
Check which version you are running with "dar -V".
JB - Jul 06 2004
Hi Jason,
>asked it to make 4.7 GB slices, so
>that I can backup to DVD. However, it
>just finished the archive, and it's a
>single slice that is 9 GB in size.
Looks like you have found a bug in kdar. I think what happened is that the slice size can only be an integer, not a float. I'll have to change this in the next release to only allow integers. The float was probably converted to "0" integer, and a slice size of 0 means "infinitely large" to the dar library.
By the way, according to a DVD-howto, 4.7 GB is not actually 4.7*1024*1024*1024, it is rather 4.7*1000*1000*1000 = 4700000000 Bytes!
The howto called this the salesman's GB.
I have recently bought a DVD burner, and it took awhile to figure out how to actually backup on DVD's:
0) The DVD can store 4700000000 bytes. Some might be able to handle more but I leave it to you to find that out for your drive.
1) ISO9660 filesystems cannot handle files larger than 2GB without patching various code, including the kernel. The ext2 filesystem can handle larger files, so I created a loopback ext2 filesystem with a size of 4700000000 bytes. i.e.
"dd if=/dev/zero of=dvd.ext2 bs=47000000 count=100"
"mke2fs -m 0 -T largefile4 dvd.ext2"
"mount -o loop dvd.ext2 /mnt/dvd"
"rm -r /mnt/dvd/lost+found"
You'll put your slices here (but not all at once!).
2) The dvd filesystem uses some space to store inodes, etc. I guesed that 4.3 GB slices would fit. Indeed they did, with about 70MB left to spare.
Now 4.3*1024=4403.2 MB, so I just put "4400 MB" as the slice sizes in the kdar settings dialog.
3) I had enough room on my HD to store all the dar slices at once, so I unchecked the "pause between slices checkbox".
4) I moved the first slice onto the mounted loopback dvd.ext2 filesystem:
"mv /opt/backups/backup.1.dar /mnt/dvd/."
5) k3b wouldn't burn a non-iso DVD image (I wonder why?) so I did it by hand:
"growisofs -dvd-compat -speed=4 -Z /dev/sr0=dvd.ext2"
6) Then I mounted the DVD ext2 filesystem and diffed the DVD slice and the one on the HD:
"mount /dev/sr0 /mnt/dvd-ext2"
"diff /mnt/dvd-ext2/backup.1.dar /mnt/dvd/backup.1.dar"
If the files are the same then unmount the DVD and remove the slice from the HD:
"umount /mnt/dvd-ext2"
"rm /mnt/dvd/dvd.ext2"
7) Start the process again at step (4) with the next slice if there is one.
If you want the convenience of k3b for burning (although I think the commandline is very convenient), then you'll have to generate 2GB slices and burn only 2 per DVD.
> Any idea why it didn't slice it? Can
>k3b span a single file onto two discs,
>or will I need to delete it and try
>again?
AH! use dar_xform to split the big slice into smaller ones that will fit on your DVD.
If you figure out a way to burn 4700000000-byte slices instead of 4400000000-byte slices, please let me know. I think however, this is about as much as the DVD can handle on the ext2 filesystem.
> thanks,
> Jason
Cheers,
JB - Apr 01 2004
>asked it to make 4.7 GB slices, so
>that I can backup to DVD. However, it
>just finished the archive, and it's a
>single slice that is 9 GB in size.
Looks like you have found a bug in kdar. I think what happened is that the slice size can only be an integer, not a float. I'll have to change this in the next release to only allow integers. The float was probably converted to "0" integer, and a slice size of 0 means "infinitely large" to the dar library.
By the way, according to a DVD-howto, 4.7 GB is not actually 4.7*1024*1024*1024, it is rather 4.7*1000*1000*1000 = 4700000000 Bytes!
The howto called this the salesman's GB.
I have recently bought a DVD burner, and it took awhile to figure out how to actually backup on DVD's:
0) The DVD can store 4700000000 bytes. Some might be able to handle more but I leave it to you to find that out for your drive.
1) ISO9660 filesystems cannot handle files larger than 2GB without patching various code, including the kernel. The ext2 filesystem can handle larger files, so I created a loopback ext2 filesystem with a size of 4700000000 bytes. i.e.
"dd if=/dev/zero of=dvd.ext2 bs=47000000 count=100"
"mke2fs -m 0 -T largefile4 dvd.ext2"
"mount -o loop dvd.ext2 /mnt/dvd"
"rm -r /mnt/dvd/lost+found"
You'll put your slices here (but not all at once!).
2) The dvd filesystem uses some space to store inodes, etc. I guesed that 4.3 GB slices would fit. Indeed they did, with about 70MB left to spare.
Now 4.3*1024=4403.2 MB, so I just put "4400 MB" as the slice sizes in the kdar settings dialog.
3) I had enough room on my HD to store all the dar slices at once, so I unchecked the "pause between slices checkbox".
4) I moved the first slice onto the mounted loopback dvd.ext2 filesystem:
"mv /opt/backups/backup.1.dar /mnt/dvd/."
5) k3b wouldn't burn a non-iso DVD image (I wonder why?) so I did it by hand:
"growisofs -dvd-compat -speed=4 -Z /dev/sr0=dvd.ext2"
6) Then I mounted the DVD ext2 filesystem and diffed the DVD slice and the one on the HD:
"mount /dev/sr0 /mnt/dvd-ext2"
"diff /mnt/dvd-ext2/backup.1.dar /mnt/dvd/backup.1.dar"
If the files are the same then unmount the DVD and remove the slice from the HD:
"umount /mnt/dvd-ext2"
"rm /mnt/dvd/dvd.ext2"
7) Start the process again at step (4) with the next slice if there is one.
If you want the convenience of k3b for burning (although I think the commandline is very convenient), then you'll have to generate 2GB slices and burn only 2 per DVD.
> Any idea why it didn't slice it? Can
>k3b span a single file onto two discs,
>or will I need to delete it and try
>again?
AH! use dar_xform to split the big slice into smaller ones that will fit on your DVD.
If you figure out a way to burn 4700000000-byte slices instead of 4400000000-byte slices, please let me know. I think however, this is about as much as the DVD can handle on the ext2 filesystem.
> thanks,
> Jason
Cheers,
JB - Apr 01 2004