https://bugzilla.novell.com/show_bug.cgi?id=278451 ------- Comment #1 from jonharson@gmail.com 2007-05-26 02:20 MST ------- This behavior is only present during installation and not on installed system. Also note that it warn for low space on /home which is also kinda irrelevant for a update/install/whatever. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=278451 jonharson@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Enhancement |Minor ------- Comment #3 from jonharson@gmail.com 2007-05-26 13:50 MST ------- NOT reproducible except during installation, i repeat do NOT happen on installed system. This behavior has been there for some time never bothered to call it a bug myself. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=278451 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |lslezak@novell.com |screening@forge.provo.novell| |.com | -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=278451 lslezak@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|DUPLICATE | ------- Comment #6 from lslezak@novell.com 2007-05-30 02:06 MST ------- This problem happens in a running system and therefore it's not a duplicate. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=278451 bluedzins@wp.pl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|bluedzins@wp.pl | ------- Comment #8 from bluedzins@wp.pl 2007-05-30 02:57 MST ------- Ladislav, I cannot attach yast logs, they are too big (I already reported it). But it is fairly easy to reproduce this problem. Run yast -> software manager and ensure it does not show any warnings about disk space. Now, make (or download) iso file. Mount it in /media, for example /media/ISO. When you mount it you will be able to write in this file-partition. Ok, make there another, smaller iso-file. Mount it in /home, for example /home/ISO2. In my case the situation is this: I have external disk drive with iso-file on it. I mount (all manually) this external (USB) hard disk to /media/bigbox and then, the file from this disk to /home/CRY (the file is iso file). And since there is very little space in the latter one yast shows warning. You can see the result on the screenshot (in a second). -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=278451 ------- Comment #10 from bluedzins@wp.pl 2007-05-30 03:00 MST ------- PS. When I was taking a screenshot I had three more mount points used -- one for DVD disc, two for iso-files. I can see that yast is not interested in them. In the external drive it is not interested in too. And my mistake, it is /home/macias/CRY not /home/CRY as you can see. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=278451 ------- Comment #12 from sh@novell.com 2007-05-30 07:40 MST ------- (In reply to comment #11)

There are these possible solutions: - Display the warning only once at the first start of the package selector

That would be very useless and contrary to the idea of that disk space checker.

- Add "Do not show again" check box (so it can be turned off by user)

You only get warned once anyway, so such a check box would be counter-productive. Once you have been warned about any partition getting full, you will not be warned again about that one until you significantly free up space there. Only upon "Accept" there is another check if there is insufficient disk space, and that check is the most important. If you run out of disk space during package installation, you will be in a situation that is tricky to get out again.

- Display the warning before installing packages (when it's known where will be the packages installed) (But the reason for this warning is probably to warn the user in advance, before selecting packages to install.)

This is there anyway (anybody actually ever used this??). -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=278451 sh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|sh@novell.com |lslezak@novell.com ------- Comment #14 from sh@novell.com 2007-05-30 07:51 MST ------- This discussion what partitions to include in that disk space check is ages old. We had thrown out the Windows partitions, but then some users had complained because they had made very creative symlinks to use that partition, too for package installation. I would not recommend that, but you could for example symlink /opt/kde3 to /C/kde3, so that Windows partition would actually be used for package installation. I have no strong feelings towards or against including or excluding partitions from the disk check. But the problem is where to draw the line. A simplistic approach would be to try to check only partitions that are mounted to well-known paths -- paths that are known directories where packages will get installed to. But that might often fail. Whenever users make creative symlinks, for example. You might choose to redirect everything that goes to, say, /usr/share to /work/share. So we have to include mounted Linux file systems at the very least. Include or exclude FAT / VFAT / NTFS file systems? I don't know. Some users get very creative when disk space is running out -- see the first example above. The only safe approach is to include all partitions that are mounted read/write (Read-only partitions are excluded because you can't install anything there anyway, and mounted CD-ROMS or DVD-ROMs are always 100% full, thus would always trigger that warning). Bottom line: This is a lot more complex than you might think. And besides, what partitions to include in that check is the responsibility of the underlying DiskUsage class -> lslzezak. The UI only displays the results. -- 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, or are watching someone who is.