bug-inetutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-inetutils] some notes on inetutils-1.8


From: melodramus
Subject: Re: [bug-inetutils] some notes on inetutils-1.8
Date: Wed, 18 Aug 2010 01:39:54 +0200

On Tue, 17 Aug 2010 17:13:10 -0400
"Alfred M. Szmidt" <address@hidden> wrote:

> Please CC address@hidden in the future.
> 
>    >    > The following should work to compile only syslogd, as per
>    >    > ./configure --help, INSTALL and README.
>    >    > 
>    >    > ./configure --disable-server --disable-clients
>    >    > --enable-syslogd
>    >    > 
>    >    > What `four lines' did you use?  Maybe something can be
>    >    > improved.
>    > 
>    >    i just disabled everything i didn't want, which made up four
>    >    text lines (rows?) on my monitor. if --enable-syslogd works,
>    >    --disable-syslogd=no should work too (by convention), like
>    >    --disable-syslogd should be substitutable with
>    >    --enable-syslogd=no. using --disable-syslogd=no has the
>    >    advantage that one can middle-click (Xorg quick copy/paste)
>    >    the option from the configure --help output.
>    > 
>    > Please show the exact command you used.  Did you try the one I
>    > suggested?
> 
>    i re-installed with --enable-xxx and it worked fine. however, the
>    command line scratched the fourth line on the monitor too (syslogd,
>    logger, ping, ping6, hostname, traceroute, encryption, auth,
>    shishi).  in other words: both ways part the package at about the
>    half.
> 
> I do not understand, can you _PLEASE_ just show me the command line
> you used? If it is not in your command history, you can get it from
> config.log.  Can you also just tell me wether the one I suggested for
> you works or not?

you are off track. there is no problem with the command-line itself. the
command-line works fine! i target at two very other problems. the first
is how --disable works. that's an autotools problem but can be
circumvented by using --enable. i wrote about that in an other email.
the second is that the package is a mixed bag and not used in full on a
'modern' home system so that one has to use *very long* command-lines
to turn off things. one can use --disable-servers and --disable-clients
and turn_on things, which is not shorter. but the real problem is the
mix of tools in inetutils. the content of the package is selected like
for an archive rather than for specific use cases or platform needs.


> 
> There is no harm in having inetd installed, likewise for the other
> daemons.  They are for one not started (unless your OS does something,
> which we cannot control anyway), and require root access to run.  Some
> programs do get installed as SUID root, like ping which require
> special access when creating ports, but that is it.

you don't see potential harm in unforeseen situations and in SUID root?
are you only a developer or do you also admin a system. i mean, do you
have some experience with administration? is the simple rule 'do not
leave stuff on the system that isn't needed and potentially dangerous!'
known to you? there is a simple reason for this rule. shit happens!
possibly because of oneself. possibly through the browser. one never
knows. is the firewall set correctly? are ports left open? things can
be checked, but the one who can start a daemon on your system can
possibly also open ports!

best wishes,
MeloDramus <address@hidden>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]