From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3] busybox: improve support for telnetd
Date: Sun, 12 Jul 2015 12:35:16 +0200 [thread overview]
Message-ID: <55A242E4.1000903@mind.be> (raw)
In-Reply-To: <20150712080330.GA4008@free.fr>
On 07/12/15 10:03, Yann E. MORIN wrote:
> Thomas, Alexey, All,
>
> On 2015-07-12 02:20 +0200, Thomas Petazzoni spake thusly:
>> From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
>>
>> If target has connection to the network it might be pretty useful to
>> have telnet connection to it instead of serial console or even in
>> addition to serial console.
> [--SNIP--]
>> diff --git a/package/busybox/busybox.mk b/package/busybox/busybox.mk
>> index 92874cd..35f1e96 100644
>> --- a/package/busybox/busybox.mk
>> +++ b/package/busybox/busybox.mk
> [--SNIP--]
>> +define BUSYBOX_ADJUST_TELNET_SECURETTY
>> + if grep -q CONFIG_FEATURE_TELNETD_STANDALONE=y $(@D)/.config; then \
>> + for i in `seq 0 3` ; do \
>> + grep -q "pts/$$i" $(TARGET_DIR)/etc/securetty || \
>> + echo "pts/$$i" >> $(TARGET_DIR)/etc/securetty ; \
>
> Why don't we simply add those four in our securetty, directly in our
> skeleton?
That renders securetty even more useless than it already is.
Why don't we just remove CONFIG_FEATURE_SECURETTY from our default busybox
config and get rid of all the securetty hacks?
Regards,
Arnout
[snip]
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
prev parent reply other threads:[~2015-07-12 10:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-12 0:20 [Buildroot] [PATCHv3] busybox: improve support for telnetd Thomas Petazzoni
2015-07-12 8:03 ` Yann E. MORIN
2015-07-12 10:35 ` Arnout Vandecappelle [this message]
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=55A242E4.1000903@mind.be \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.