From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to enable inetd in buildroot
Date: Thu, 3 Apr 2014 15:08:00 +0200 [thread overview]
Message-ID: <20140403150800.22ef96a7@skate> (raw)
In-Reply-To: <CAKGbVbuLPuiEtCSNu9WpWfcnq4axdFFycmyCpXTBAo1jw6pNag@mail.gmail.com>
Dear Qiang Yu,
On Thu, 3 Apr 2014 18:24:19 +0800, Qiang Yu wrote:
> I'm trying to use some services provided by inetd. But can't find the
> configuration
> for enabling it and generating startup script and inetd.conf. I notice
> someone has
> already submit some patch for doing this:
> http://lists.busybox.net/pipermail/buildroot/2011-December/048207.html
> but not found in the latest buildroot.
>
> So can somebody tell me what's the state of inetd in buildroot?
> Do I have to apply this patch to use inetd, or there is another "official"
> way?
Are you using Busybox's inetd, xinetd, or another inetd implementation?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-03 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 10:24 [Buildroot] How to enable inetd in buildroot Qiang Yu
2014-04-03 13:08 ` Thomas Petazzoni [this message]
2014-04-03 13:19 ` Qiang Yu
2014-04-03 13:32 ` Thomas De Schampheleire
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=20140403150800.22ef96a7@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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