Curt, > Huh. > > The copy of du I got, via > > http://gnuwin32.sourceforge.net/packages.html
I am sorry. You did not say you were using the gnuwin32 port. I therefore assumed you were using Cygwin since Cygwin is probably the best known of the GNU ports. Pardon me and let me amend my message and request that you report this problem directly to the gnuwin32 folks instead. > had these two addresses for bugs: > > [EMAIL PROTECTED], [EMAIL PROTECTED] > > So, I am glad to take the bug elsewhere -- but -- > someone should correct these addresses. Perhaps > they are inherited -- but -- I wouldn't know that. I see Andries followed up saying that address did not appear in the package available from gnuwin32. The 'bug-fileutils' address is inherited from the upstream source. The source code is part of the GNU Project. You can find out all of the details of here: http://www.gnu.org/ If the bug you were reporting was something in the software common to all then it would make sense to handle it here. But the bug as you report it reads to me like a problem on MS-Windows only and a problem with the port to it. Therefore we can't help you, sorry. > Further, the gnuwin32 site does say that they > have taken over from cygwin. So, would love a > better address. It appears to me that gnuwin32 is an independent effort from cygwin. I had never heard of gnuwin32 before your message. Since you did not say I had assumed cygwin. I browsed the gnuwin32 web site and found a bug reporting link from this page. Look midway down on the left. http://gnuwin32.sourceforge.net/ That makes me assume that they would accept bug reports through that forum. Bob > Thanks for responding. > > Regards, > > Curt > > Bob Proulx wrote: > > > > W. Curtiss Priest wrote: > > > OS: win95b (OSR 2.0) > > > > > > File partitions: FAT16 and FAT32 > > > > Thank you for your bug report. However we over on this list do not > > use nor have access to MS-Windows systems. It would be most > > appreciated if you made your bug report directly to the cygwin folks. > > They are the experts there. > > > > http://cygwin.com > > > > Thanks > > Bob > > > > > If du starts in the root directory, it does not > > > appear to see any sub-directories under either > > > FAT16 or FAT32. > > > > > > e.g. du e:\ > > > where e: is a 32 gig HD, single FAT32 partition > > > > > > gives a single line: > > > > > > 0 e:\ > > > > > > or du c:\ > > > where c: is the first primary (and boot) FAT16 partition of > > > a 20 gig drive, partitioned to 2 gigs. > > > > > > 0 c:\ > > > > > > If du starts at any sub-directories, it behaves > > > as expected, such as: > > > > > > du c:\windows > > > > > > And running du under XP with NTFS and FAT32, behaves > > > as expected in the root. > > > > > > If you wish an ISO image of the Windows install CD, > > > I would be glad to provide it under "fair use." > > > > > > Regards, > > > > > > Dr. Priest > > > -- > > > > > > > > > W. Curtiss Priest, Director, CITS > > > Research Affiliate, Comparative Media Studies, MIT > > > Center for Information, Technology & Society > > > 466 Pleasant St., Melrose, MA 02176 > > > 781-662-4044 [EMAIL PROTECTED] http://Cybertrails.org _______________________________________________ Bug-fileutils mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-fileutils
