public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Daniel da Veiga" <danieldaveiga@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] where's good old inetd ?
Date: Wed, 28 Jun 2006 19:16:37 -0300	[thread overview]
Message-ID: <342e1090606281516h922a48vcb75c93234684277@mail.gmail.com> (raw)
In-Reply-To: <20060628213322.GC25767@nibiru.local>

On 6/28/06, Enrico Weigelt <weigelt@metux.de> wrote:
> * Alexander Skwar <listen@alexander.skwar.name> wrote:
> > Enrico Weigelt wrote:
> > >* Bruno Lustosa <bruno.lists@gmail.com> wrote:
> > >
> > ><snip>
> > >
> > >>anyway, why use old inetd at all? xinetd is way more powerful and secure!
> > >
> > >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 ?
> >
> > It's more modern.
>
> Ah. Interesting argument.
> Because it's quite modern (for the kids) to wear overwide pants,
> there's no need to produce tight ones anylonger ?
> Great.

Modern in the computer world = more efficient, robust, better support,
continue developing, more features, less security holes.

Modern in the fashion world = no one can ever put it in words.

>
> > >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 ?
> >
> > Why? The current way is quite fine, IMO. You can easily select
> > which package to install, why depend on some USE flag?
>
> Following you line of argumentation, the virtual package "inetd"
> should be dropped, since people can directly choose "xinetd".
>

<begin MHO>
Its not even in portage, people just stopped using it... xinetd has
all the functions of it, its like using the old bsh because bash is
"modern". I run xinetd in a pentium 100, there's no need for the old
inetd unless you still have an old (already installed and configured)
workstation running an old OS (but still serving its purpose). Its
evolution baby!
<end MHO>

-- 
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-06-28 22:31 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
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 [this message]
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=342e1090606281516h922a48vcb75c93234684277@mail.gmail.com \
    --to=danieldaveiga@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