From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Init scripts for Busybox daemons?
Date: Tue, 4 Jun 2024 21:25:29 +0200 [thread overview]
Message-ID: <Zl9qKai-hMy4xPIe@landeda> (raw)
In-Reply-To: <904c1a18-623f-45c1-af36-f6b661a86a54@gmx.de>
Fiona, All,
On 2024-06-04 21:20 +0200, Fiona Klute via buildroot spake thusly:
> for a system I'm working on I've needed to create init scripts for
> Busybox daemons, specifically crond and ifplugd. The scripts are fairly
> generic, so I'm wondering if it'd make sense to send a patch to
> optionally install them (similar to BR2_PACKAGE_BUSYBOX_WATCHDOG).
>
> Is that something that could be merged? If yes, I'll look at preparing
> patches.
Sure.
You may wish to do like S01syslogd, which only gets installed if no
other syslogd package provides it.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| 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@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-06-04 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 19:20 [Buildroot] Init scripts for Busybox daemons? Fiona Klute via buildroot
2024-06-04 19:25 ` 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=Zl9qKai-hMy4xPIe@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=fiona.klute@gmx.de \
/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.