From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs/{at91sam9*, atmel*}: drop OpenSSH as it duplicates Dropbear
Date: Fri, 26 Oct 2018 14:20:18 +0200 [thread overview]
Message-ID: <20181026142018.62c47e7b@windsurf> (raw)
In-Reply-To: <9b5b2780-92cf-682a-7ada-f6af691652ad@microchip.com>
Hello,
On Fri, 26 Oct 2018 09:48:44 +0000, Nicolas.Ferre at microchip.com wrote:
> On 26/10/2018 at 11:40, Thomas Petazzoni wrote:
> > The "development" defconfigs for Atmel platforms enable both OpenSSH
> > and Dropbear, which doesn't make a lot of sense, as only one SSH
> > server can start on port 22.
> >
> > This commit therefore drops BR2_PACKAGE_OPENSSH=y from those
> > defconfigs, keeping Dropbear as an SSH server/client.
>
> A gut feeling is telling me that I would have preferred the other way
> around: Keeping OpenSSH.
I don't really care either way. Those defconfigs already have plenty of
packages enabled anyway (which is the whole point of those defconfigs).
Should I resend a v2 that keeps BR2_PACKAGE_OPENSSH=y and drops
BR2_PACKAGE_DROPBEAR=y ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-10-26 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 9:40 [Buildroot] [PATCH] configs/{at91sam9*, atmel*}: drop OpenSSH as it duplicates Dropbear Thomas Petazzoni
2018-10-26 9:48 ` Nicolas.Ferre at microchip.com
2018-10-26 10:08 ` Alexander Dahl
2018-10-26 10:18 ` Peter Korsgaard
2018-10-26 12:20 ` Thomas Petazzoni [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=20181026142018.62c47e7b@windsurf \
--to=thomas.petazzoni@bootlin.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