supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Gerrit Pape <pape@smarden.org>
Subject: Re: Problem with debian runit package / libowfat
Date: Tue, 5 Dec 2006 10:52:03 +0000	[thread overview]
Message-ID: <20061205105203.30922.qmail@ca2d9b8e62a85c.315fe32.mid.smarden.org> (raw)
In-Reply-To: <20061122040858.GF12058@mikebell.org>

On Tue, Nov 21, 2006 at 08:08:58PM -0800, Mike Bell wrote:
> runit on debian is linked against libowfat which doesn't understand
> large device nums. EOVERFLOW. As a result a root on something with a
> large num (like AoE devices on any shelf other than 0) won't be able to
> start up runsvdir.

It's linked against the dietlibc, not libowfat.

> Perhaps a runit-dynamic package linked against glibc could be created?

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?

Thanks, Gerrit.


  reply	other threads:[~2006-12-05 10:52 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 [this message]
2006-12-07 18:43   ` Mike Bell
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=20061205105203.30922.qmail@ca2d9b8e62a85c.315fe32.mid.smarden.org \
    --to=pape@smarden.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).