supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Torne Wuff <torne@wolfpuppy.org.uk>
Subject: Re: runit running under linux 2.4 with openwall patches
Date: Tue, 25 Jan 2005 10:58:51 +0000	[thread overview]
Message-ID: <1106650731.41f6266bcbe61@www.wolfpuppy.org.uk> (raw)
In-Reply-To: <BC8ECD7B-6E8C-11D9-9341-000A9598BFB2@annvix.org>

Quoting Vincent Danen <vdanen@annvix.org>:
> > Did you link the runit program statically with the dietlibc?  If so,
> > you
> > could try to compile it the same way as the working /sbin/init, to be
> > sure it's not the compiler or libc causing the problem.
>
> That's a good idea.  I did compile it statically with dietlibc.  I'll
> try without dietlibc and see what happens.  I haven't had a chance to
> dive back into it yet, but when I get a second I'll rebuild it and see
> if that clears it up.  If not, I'll recompile the kernel without the
> stack protection option enabled, just to make sure that it is what I
> think it is.

Yes, it's dietlibc. Dietlibc executes code from the stack during system calls,
afaict.

-- 
Torne


  reply	other threads:[~2005-01-25 10:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-20 22:14 Vincent Danen
2005-01-20 22:28 ` Charlie Brady
2005-01-20 22:52   ` Vincent Danen
2005-01-21 19:32 ` Gerrit Pape
2005-01-25  4:51   ` Vincent Danen
2005-01-25 10:58     ` Torne Wuff [this message]
2005-01-25 19:54       ` Vincent Danen
2005-01-25 23:33       ` Vincent Danen
2005-01-26  0:44         ` Csillag Tamás
2005-01-26  4:31           ` Vincent Danen
2005-01-26  8:52             ` Csillag Tamás
2005-01-27 19:52               ` Charlie Brady
2005-01-26 12:07             ` Milan P. Stanic
     [not found]             ` <20050205212555.GI20427@digitus>
2005-02-05 23:14               ` Vincent Danen
2005-03-14 14:11                 ` Csillag Tamás
2005-03-14 17:40                   ` Gerrit Pape

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=1106650731.41f6266bcbe61@www.wolfpuppy.org.uk \
    --to=torne@wolfpuppy.org.uk \
    /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).