From: "Bruno Lustosa" <bruno.lists@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] where's good old inetd ?
Date: Wed, 21 Jun 2006 12:06:19 -0300 [thread overview]
Message-ID: <b9e0c3fe0606210806o6dd67698uf0501f9e09efea03@mail.gmail.com> (raw)
In-Reply-To: <20060621145318.GB8517@nibiru.local>
On 6/21/06, Enrico Weigelt <weigelt@metux.de> wrote:
> well, I've already been using it for over 10 years, I never had
> serious problems with it, and has all I need.
> So why should I now switch to xinetd ?
The answer to this 'why' can be found here:
http://www.xinetd.org/faq.html#why
> Wouldn't it make more sense to let "inetd" be an virtual package
> which can be configured by some useflag to get either classic inetd
> or xinet in, maybe xinet as default ?
inetd is way too old. I tried googling for it, and I couldn't even
find source downloads for it.
It's like wanting to use in.telnetd and telnet instead of ssh because
the former has always served well.
However, if you can find the sources to it, you can always compile and
use it, can't you?
--
Bruno Lustosa <bruno@lustosa.net>
http://www.lustosa.net/
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-21 15:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 12:18 [gentoo-user] where's good old inetd ? Enrico Weigelt
2006-06-21 12:28 ` Arturo 'Buanzo' Busleiman
2006-06-21 12:30 ` Alexander Skwar
2006-06-28 21:18 ` Enrico Weigelt
2006-06-21 12:33 ` Bruno Lustosa
2006-06-21 14:53 ` Enrico Weigelt
2006-06-21 15:06 ` Bruno Lustosa [this message]
2006-06-21 15:17 ` Bruno Lustosa
2006-06-28 21:28 ` Enrico Weigelt
2006-06-21 17:20 ` kashani
2006-06-21 20:01 ` Alexander Skwar
2006-06-28 21:33 ` Enrico Weigelt
2006-06-28 22:16 ` Daniel da Veiga
2006-06-28 22:34 ` Neil Bothwick
2006-06-28 22:26 ` Nick Rout
2006-06-28 22:54 ` kashani
2006-06-21 13:01 ` Bo Ørsted Andresen
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=b9e0c3fe0606210806o6dd67698uf0501f9e09efea03@mail.gmail.com \
--to=bruno.lists@gmail.com \
--cc=gentoo-user@lists.gentoo.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