From: "Yu, Mingli" <mingli.yu@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
"Yu, Mingli" <mingli.yu@eng.windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] openssh: Add SSHD_SERVICE_TYPE variable
Date: Tue, 5 Dec 2023 10:51:08 +0800 [thread overview]
Message-ID: <ef31fe38-2390-ecb8-405a-570895ef1ab9@windriver.com> (raw)
In-Reply-To: <6170bfa781bf455736f763a3bc4e4978f916c96a.camel@linuxfoundation.org>
Hi Richard,
On 12/4/23 19:07, Richard Purdie wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Mon, 2023-12-04 at 16:54 +0800, Yu, Mingli wrote:
>> From: Mingli Yu <mingli.yu@windriver.com>
>>
>> There are two types of sshd server now, one is based on socket
>> activation(sshd.socket) and another is service activation(sshd.service).
>> And the default sshd service type is based on socket by default as below.
>
> Firstly, I'm a little frustrated about how these changes are being
> proposed in pieces. The original patches made no mention that this was
> eventually going to be controlled by a new variable. I did wonder if
> something like this was going to happen but the didn't push back. Now
> we're "pinned" into a corner with the direction this code takes now
> we've already merged the on target configuration change.
>
>> But it's more convenient to determine the service type at build time
>> if there are so many devices.
>
> Why did we merge a patch which made this an on target decision then?
Maybe usage requirement change? sorry for noise!
>
>> So add SSHD_SERVICE_TYPE variable to enable sshd.socket or sshd.service
>> at build time and we still enable sshd.socket by default now.
>
> No, we're not adding randomly named variables which take magic options.
>
> I cannot look at SSHD_SERVICE_TYPE and know that "1" means socket
> activation and not setting it means service activation (or whatever,
> the fact I can't check what I've written easily proves my point). What
> happens if I set it to "true", or "socket", or "apples"?
>
> I'd suggest thinking about a PACKAGECONFIG option such as systemd-sshd-
> socket-mode and systemd-sshd-service-mode which at least uses naming
> users are mode used to and says what it does.
Will sent v2 to use the common PACKAGECONFIG option to control the sshd
type.
Thanks,
>
> Cheers,
>
> Richard
next prev parent reply other threads:[~2023-12-05 2:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 8:54 [PATCH] openssh: Add SSHD_SERVICE_TYPE variable mingli.yu
2023-12-04 11:07 ` [OE-core] " Richard Purdie
2023-12-05 2:51 ` Yu, Mingli [this message]
2023-12-05 5:52 ` [PATCH v2] openssh: Add PACKAGECONFIG option to customize sshd mode mingli.yu
2023-12-05 7:43 ` [OE-core] " Alexandre Belloni
2023-12-06 5:44 ` [PATCH v3] " mingli.yu
2023-12-06 8:56 ` [PATCH v4] " mingli.yu
2023-12-06 10:37 ` [OE-core] " Alex Kiernan
2023-12-07 2:10 ` Yu, Mingli
2023-12-07 12:11 ` Alex Kiernan
2023-12-13 3:37 ` Yu, Mingli
[not found] ` <179E3241B25BBB7C.1352@lists.openembedded.org>
2023-12-18 6:16 ` Yu, Mingli
2023-12-06 22:34 ` [OE-core] [PATCH v2] " Peter Kjellerstedt
2023-12-07 1:53 ` Yu, Mingli
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=ef31fe38-2390-ecb8-405a-570895ef1ab9@windriver.com \
--to=mingli.yu@windriver.com \
--cc=mingli.yu@eng.windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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