From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Sam Voss <sam.voss@collins.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/busybox: add systemd service for telnetd
Date: Fri, 27 Aug 2021 23:28:29 +0200 [thread overview]
Message-ID: <20210827212829.GG2661@scaer> (raw)
In-Reply-To: <20210826210241.56201-1-sam.voss@collins.com>
Sam, All,
On 2021-08-26 16:02 -0500, Sam Voss via buildroot spake thusly:
> Signed-off-by: Sam Voss <sam.voss@collins.com>
> ---
> package/busybox/busybox.mk | 7 +++++++
> package/busybox/telnetd.service | 11 +++++++++++
> 2 files changed, 18 insertions(+)
> create mode 100644 package/busybox/telnetd.service
>
> diff --git a/package/busybox/busybox.mk b/package/busybox/busybox.mk
> index cfc06b0d78..fb427faf1c 100644
> --- a/package/busybox/busybox.mk
> +++ b/package/busybox/busybox.mk
> @@ -378,6 +378,13 @@ define BUSYBOX_INSTALL_TARGET_CMDS
> $(BUSYBOX_INSTALL_MDEV_CONF)
> endef
>
> +define BUSYBOX_INSTALL_INIT_SYSTEMD
> + if grep -q CONFIG_FEATURE_TELNETD_STANDALONE=y $(@D)/.config; then \
> + $(INSTALL) -D -m 0644 package/busybox/telnetd.service \
> + $(TARGET_DIR)/usr/lib/systemd/system/telnetd.service ; \
> + fi
> +endef
I've changed that to be handled in a fashion similar to the two other
init systems:
- added a macro right after BUSYBOX_INSTALL_TELNET_SCRIPT, and
similarly named BUSYBOX_INSTALL_TELNET_SERVICE
- use thatr macro in the newly introduced BUSYBOX_INSTALL_INIT_SYSTEMD
- move BUSYBOX_INSTALL_INIT_SYSTEMD alphabetically in-between openrc
and sysv.
Applied to next, thanks.
Regards,
Yann E. MORIN.
> # Install the sysvinit scripts, for the moment, but not those that already
> # have a corresponding one in openrc.
> define BUSYBOX_INSTALL_INIT_OPENRC
> diff --git a/package/busybox/telnetd.service b/package/busybox/telnetd.service
> new file mode 100644
> index 0000000000..3c1fa457b1
> --- /dev/null
> +++ b/package/busybox/telnetd.service
> @@ -0,0 +1,11 @@
> +[Unit]
> +Description=Telnetd Service
> +After=network.target
> +
> +[Service]
> +# busybox telnet doesn't support pidfile, so run in foreground
> +Type=simple
> +ExecStart=/usr/sbin/telnetd -F
> +
> +[Install]
> +WantedBy=multi-user.target
> --
> 2.17.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-08-27 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 21:02 [Buildroot] [PATCH 1/1] package/busybox: add systemd service for telnetd Sam Voss via buildroot
2021-08-26 22:01 ` Arnout Vandecappelle
2021-08-27 15:50 ` [Buildroot] [External] " Voss, Samuel M Collins via buildroot
2021-08-27 16:30 ` Arnout Vandecappelle
2021-08-27 21:28 ` Yann E. MORIN [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=20210827212829.GG2661@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=sam.voss@collins.com \
/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