Christian Jones <[EMAIL PROTECTED]> writes: > Whereas clearly (in the above case), it doesn't. The aforementioned > thread also notes (in fact, stresses) the fact that the capacity is > incorrect for /dev/discs/disc0/part3 after something has been mounted > "over" it. Unfortunately, the consensus on that report seemed to be that > there wasn't an obvious way to fix it. Is there an obvious solution to > this one, such as reporting the filesystem mounted *last* instead of the > one mounted first?
??? This is what df is doing. And there is no way to get the attributes of the hidden mount point, since it is, in fact, hidden. That becomes more apparent if you mount over a directory that has another mountpoint in some subdirectory. The other mountpoint is simply not reachable any more. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." _______________________________________________ Bug-coreutils mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-coreutils
