supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Problem with debian runit package / libowfat
Date: Thu, 07 Dec 2006 13:46:15 -0500	[thread overview]
Message-ID: <m3y7pj7ddd.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <20061207184330.GA2716@mikebell.org> (Mike Bell's message of "Thu, 7 Dec 2006 10:43:30 -0800")

Mike Bell <mike@mikebell.org> wrote:
> 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.

The "diet" refers to the goal of small *code* size, not data.  I
wouldn't expect any objections on those grounds, and even the
transition should be relatively painless, since dietlibc is usually
linked statically.


paul


      reply	other threads:[~2006-12-07 18:46 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
2006-12-07 18:46     ` Paul Jarc [this message]

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=m3y7pj7ddd.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    /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).