https://bugzilla.novell.com/show_bug.cgi?id=199054
User alpha096@virginbroadband.com.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=199054#c36
Scott Couston changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alpha096@virginbroadband.com.au
--- Comment #36 from Scott Couston 2008-04-03 23:53:51 MST ---
There are issues to consider here over and above the current KwikDisk which
appears in a KDE desktop when so installed. I am not able to find any same such
application in a Gnome Desktop and perhaps this is where most of the work needs
to be done.
Please bear in mind this bug was opened on 2006-08-12 03:49 MST.
This bug is an enhancement to the application KwikDisk and creation of a
similar application under Gnome. Your decision where to assign this request is
your choice together with bug title revision.
The application KwikDisk available in a KDE desktop which at the time of bug
creation was either not present/available and/or not installed as part of any
package; needs enhancements.
1. The application KwikDisk is an applet that is accessed from the system tray.
It has a different presentation when 'configure' is selected directly from a
left click on the applet AND 'configure' is selected after selecting 'Start
KDiskFree'.
2. The appearance of each device can be confusing where a mount point exists
for every local device and logical mount point - see attachment example.
3. The mount commands tab chosen from 'configure' from 'Start KwikDisk' or the
applet is not accessible from default user and not accessible if the
application is changed to run as root via a menu edit.
4. The application does work well and will notify when any device point
approaches its tolerance ??
5. The application does not report on the insertion of a 100% full device such
as a CD/DVD/??
6. The alert tolerance is unknown and not changeable as specified as
'critically full'
7. The option within 'configure' of 'kfmclient openURL %m' has an unknown value
as most newly established devices will launch konqueror. It is presumed that
when the low disk space tolerance is reached on any device that konqueror is
launched on the device now at tolerance??
8. The most important aspect of an enhancement to this application is
subsequent to its alert and the user needs to be able to free disk space space
quickly. A new device clean-up application needs to be launched together with
the called file manager.
9. The device cleaner needs to consider the following places for clean-up.
A. The /tmp directory under root.
B. The 'Trash' directory under bother root and user
C. The users /home/xxxxx/.beagle/TextCache directory.
Whilst the above 3 areas are predictable places to consider device cleaner this
is seen as a limiting factor being hard coded and not dynamically created -
your call here. The meaningful creation of either a dynamic 'clean-up- list
needs consideration OR needs to be an optional assignment the user selects as
being desirable to clean up on a specific device trigger.
It is important to realise the relevance of both deletion and visibility of
files and directories under the user root in bother the /tmp and //trash
directories and device.
The presence of any device reaching its tolerance is not reliable to trigger a
device clean-up. The trigger of either a removable device and or a non local
device tolerance cannot be resolved in hard coded list such as above.
The presence of an NFS device OR logical device reaching tolerance cannot be
resolved in hard coded list such as above.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.