From: Mike Bell <mike@mikebell.org>
Subject: Re: Problem with debian runit package / libowfat
Date: Thu, 7 Dec 2006 10:43:30 -0800 [thread overview]
Message-ID: <20061207184330.GA2716@mikebell.org> (raw)
In-Reply-To: <20061205105203.30922.qmail@ca2d9b8e62a85c.315fe32.mid.smarden.org>
On Tue, Dec 05, 2006 at 10:52:03AM +0000, Gerrit Pape wrote:
> It's linked against the dietlibc, not libowfat.
Oops, think-o.
> Hmm, I would prefer to adapt the dietlibc. Do you know what the glibc
> does differently?, on what system/architecture are you having this
> failure?, where does the EOVERFLOW happen?
Linux. Architecture doesn't matter.
The stat syscall can return a 32bit device number now that linux has
16bit majors and 16bit minors. Fixing it would involve expanding struct
stat by two bytes for every user, which is why I didn't report it on the
dietlibc list, I'm not sure it belongs in _diet_libc.
dietlibc returns EOVERFLOW whenever the major or minor is too big to fit
in an 8bit int.
next prev parent reply other threads:[~2006-12-07 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 4:08 Mike Bell
2006-12-05 10:52 ` Gerrit Pape
2006-12-07 18:43 ` Mike Bell [this message]
2006-12-07 18:46 ` Paul Jarc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061207184330.GA2716@mikebell.org \
--to=mike@mikebell.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).