Bug#88163: acknowledged by developer (Bug#88163: fix

[Karl Pauls <kpauls@eecs.wsu.edu>]

On Sat, 17 Mar 2001, Carlos Laviola wrote:

> I don't understand, do you have some problem with xdiskusage? The bug I closed
> was the ITP (intent to package). What is your problem with xdiskusage?

Oh yet, sorry I forgot to add a full description of the "little bug" I
mentioned in my ITP


xdiskusage takes the output of du and processes that correct? The version of
du I have ends its output with this:


225124  ./home/andross
24      ./home/sleeze
241388  ./home
4       ./mnt/e
4       ./mnt/smb
4       ./mnt/loop
4       ./mnt/liz
20      ./mnt
4       ./floppy
4       ./cdrom
4       ./initrd
4       ./dvd
4       ./cdr
1944432 .


If xdiskusage incorrectly interperets the last entry to be "/" instead of ""
(nothing) and computes it as part of the subdirectories. This problem persists
when listing all files.

I believe this causes the size of the used space to be twice what it should
be! This may also cause my second problem: when descending from the root
directory on my "one big filesystem" installation (i.e. no /home /usr or any
other partitions except old windoze ones) the program segaults and terminates.
If xdiskusage uses the output of df to determine the disk capacity then the
error might stem from the fact that the used space seems to be greater than
the disk capacity!

I have taken a screen shot of the first problem. You may view it here:
http://www.eecs.wsu.edu/~kpauls/xdiskusage.jpg

Note it still reports some free space, which clashes with my theory...

Thanks for packaging xdiskusage! I probably wouldn't have been able to have
done a good job since it would have been my first.


-karl