Date: Sun, 1 Nov 1998 19:24:03 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Martin Str|mberg <ams AT ludd DOT luth DOT se>
cc: DJGPP-WORKERS <djgpp-workers AT delorie DOT com>
Subject: Re: df adventures
In-Reply-To: <199811011543.QAA26577@father.ludd.luth.se>
Message-ID: <Pine.SUN.3.91.981101192206.8219C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com


On Sun, 1 Nov 1998, Martin Str|mberg wrote:

> Then I tried compiling df and mntent.c from djdev202 beta:
> "Filesystem         1024-blocks  Used Available Capacity Mounted on
> Drive C:              256740  151196   105544     59%   c:/
> Drive D:              714656  713600     1056    100%   d:/
> Drive E:             2096160 2059584    36576     98%   e:/
> df2: f:/: No such device (ENODEV)
> TURBODSK               16350       0    16350      0%   g:/"
> 
> Now the labels are all right. However my CDROM drive has
> disappered. A new bug.
> 
> Now, I thought how about "df r:" with this that don't show me my CDROM
> drive (df and mntent.c from djdev202 beta)?
> 
> Well, core dump:

All these problems don't happen to me: I still see my CDROM after the 
change, it doesn't core-dump, and I have never seen the No such device 
problem (but then I don't have two FAT-16 partitions).

Would you please try to debug this and suggest a patch?