From: Martin Str|mberg <ams AT ludd DOT luth DOT se>
Message-Id: <199811011543.QAA26577@father.ludd.luth.se>
Subject: df adventures
To: djgpp-workers AT delorie DOT com (DJGPP-WORKERS),
        eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Sun, 1 Nov 1998 16:43:32 +0100 (MET)
X-Mailer: ELM [version 2.4ME+ PL15 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

After a quick install of WINDOZE it has managed to make the bug in
(presumably) mntent show up. I usually don't have any labels.

All runs of df is under DOZE 6.22, Swedish.

Here's the output from df from fileutils 3.16 as precompiled:
"Filesystem         1024-blocks  Used Available Capacity Mounted on
Drive C:              256740  151196   105544     59%   c:/
Ar                    714656  680512    34144     95%   d:/
A.                   2096160 2059392    36768     98%   e:/
e:/djgpp.202/bin/df: f:/: No such device (ENODEV)
TURBODSK               16350       0    16350      0%   g:/
CD1                   569914  569914        0    100%   r:/"

The line with "f:" started to appear after I have two primary FAT16
partition. It doesn't bother me particularly. The intersting part is
that d: and e: is reported having labels #Ar# and "A.". This is
showing the bug of (presumably) mntent.c.

Here's the output from df and mntent.c from djdev201, compiled with
the 981027 beta:
"Filesystem         1024-blocks  Used Available Capacity Mounted on
Drive C:              256740  151196   105544     59%   c:/
Ar                    714656  713600     1056    100%   d:/
A.                   2096160 2059552    36608     98%   e:/
df1: f:/: No such device (ENODEV)
TURBODSK               16350       0    16350      0%   g:/
CD1                   569914  569914        0    100%   r:/"

As can be seen the label problem persist.

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:
"E:\TMP\DJGPP\GNU\FILUTIL3.16\SRC>df2 r:
Filesystem         1024-blocks  Used Available Capacity Mounted on
Exiting due to signal SIGSEGV
Page fault at eip=00001ab2, error=0004
eax=00000000 ebx=0009a358 ecx=00000005 edx=00000001 esi=00000000
edi=000019d7
ebp=00099aa0 esp=00099a00
program=E:\TMP\DJGPP\GNU\FILUTIL3.16\SRC\DF2.EXE
cs: sel=00a7  base=10000000  limit=0009ffff
ds: sel=00af  base=10000000  limit=0009ffff
es: sel=00af  base=10000000  limit=0009ffff
fs: sel=008f  base=00006520  limit=0000ffff
gs: sel=00bf  base=00000000  limit=0010ffff
ss: sel=00af  base=10000000  limit=0009ffff
App stack: [00099b40..00019b40]  Exceptn stack: [00019a10..00017ad0]

Call frame traceback EIPs:
  0x00001ab2   _show_dev+78, line 273 of df.c
  0x00001ff4   _show_point+168, line 512 of df.c
  0x00002057   _show_entry+47, line 529 of df.c
  0x00002cee   _main+1554, line 779 of df.c
  0x0000655e   ___crt1_startup+174

"

Pettersson, Symphony No. 12,

							MartinS