From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.12) Gecko/20050921 Red Hat/1.0.7-1.4.1 Firefox/1.0.7
Description of problem:
df -h show the correct amount of free space for nfs shares.
Nautilus shows incorrect values. Most of the time it shows that there is 1,2 Gigabyte Space left.
And a screenshot of this behavior:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. mount nfs share
2. use df -h in console
3. open nautilus and copy file bigger than the shown free space
Actual Results: Error window.
Expected Results: Show the _REAL_ free space and copy the files.
This bug has been fixed in Gnome since then, and the fixed packages are in
rawhide, meaning it will be in FC5 and eventually RHEL5.
However, given the limited problems this causes its very unlikely that we will
release an update for RHEL4 fixing this, so I'm closing this bug.
You are not serious about this? Are you?
What is this exactly? Stay aware from RHEL and use Fedora?
RHEL is _STABLE_ and for _PRODUCTION_USE_.
Closing this bug is not acceptable. Fix it. We are paying Customers and we have
the need for this. Or why should i buy an RHEL license? This is the second time
when an RH employee is not willing to do what they contract says: Do Support and
fix Problems within the Life time of an RHEL Series.
RHEL5 is released somewhere next year.
What exactly do you mean with "limited Problems". You mean i should still go to
the command line to move files to the NFS Server cause i can't do it with
nautilus? Nice for an Enterprise Desktop. Really.
As this is fixed in Mainstream and you are one of the Mainstream Authors of
Nautilus, as far as i can see in CVS, it should be easy for you to get things
done. So why this annoiance of customers? If you do so with Fedora Users, maybe
they are told when they download the CDRoms from a local mirror. But please,
remember: This is RHEL and there is no will be fixed in next Version of RHEL.
I'm just a developer, that I have the patch for something doesn't mean its easy
to get it into an update. We're very limiting in what sort of changes goes into
the updates. If you think this is really important to get fixed you should
contact red hat support, they are the ones that could decide something like this.
I'm not interested in fighting over this issue.