On Fri, Mar 04, 2005 at 01:16:54PM -0800, [EMAIL PROTECTED] wrote:
>
> From: Eric Lammerts <[EMAIL PROTECTED]>
>
> When I stat(2) a device node on a cramfs, the st_blocks field is bogus
> (it's derived from the size field which in this case holds the major/minor
> numbers). This makes du(1)
On Fri, Mar 04, 2005 at 01:16:54PM -0800, [EMAIL PROTECTED] wrote:
From: Eric Lammerts [EMAIL PROTECTED]
When I stat(2) a device node on a cramfs, the st_blocks field is bogus
(it's derived from the size field which in this case holds the major/minor
numbers). This makes du(1) output
From: Eric Lammerts <[EMAIL PROTECTED]>
When I stat(2) a device node on a cramfs, the st_blocks field is bogus
(it's derived from the size field which in this case holds the major/minor
numbers). This makes du(1) output completely wrong.
Signed-off-by: Eric Lammerts <[EMAIL PROTECTED]>
From: Eric Lammerts [EMAIL PROTECTED]
When I stat(2) a device node on a cramfs, the st_blocks field is bogus
(it's derived from the size field which in this case holds the major/minor
numbers). This makes du(1) output completely wrong.
Signed-off-by: Eric Lammerts [EMAIL PROTECTED]
4 matches
Mail list logo