From: Joachim Wiberg <troglobit@gmail.com>
To: buildroot@buildroot.org
Cc: Joachim Wiberg <troglobit@gmail.com>
Subject: [Buildroot] [PATCH 2/2] package/ssdp-responder: add /var/lib/misc for systemd builds
Date: Sun, 4 Jun 2023 13:06:47 +0200 [thread overview]
Message-ID: <20230604110647.3418706-3-troglobit@gmail.com> (raw)
In-Reply-To: <20230604110647.3418706-1-troglobit@gmail.com>
Similar to dnsmasq, ssdp-responder saves state data across reboots in
the /var/lib/misc/ directory. In the case of ssdp-responder it is the
(per-device unique) UUID that is generated on first boot.
Workaround only needed for systemd builds, the sysv skeleton already has
the /var/lib/misc/ directory.
Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
---
package/ssdp-responder/ssdp-responder.mk | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/package/ssdp-responder/ssdp-responder.mk b/package/ssdp-responder/ssdp-responder.mk
index ddd87bc599..bb17641a9f 100644
--- a/package/ssdp-responder/ssdp-responder.mk
+++ b/package/ssdp-responder/ssdp-responder.mk
@@ -25,4 +25,8 @@ define SSDP_RESPONDER_INSTALL_INIT_SYSV
$(TARGET_DIR)/etc/init.d/S50ssdpd
endef
+define SSDP_RESPONDER_INSTALL_INIT_SYSTEMD
+ mkdir -p $(TARGET_DIR)/var/lib/misc/
+endef
+
$(eval $(autotools-package))
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-06-04 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 11:06 [Buildroot] [PATCH 0/2] ssdp-responder upgrade with systemd build fix Joachim Wiberg
2023-06-04 11:06 ` [Buildroot] [PATCH 1/2] package/ssdp-responder: bump to v2.1 Joachim Wiberg
2023-06-04 11:06 ` Joachim Wiberg [this message]
2023-07-30 10:38 ` [Buildroot] [PATCH 0/2] ssdp-responder upgrade with systemd build fix Thomas Petazzoni via buildroot
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=20230604110647.3418706-3-troglobit@gmail.com \
--to=troglobit@gmail.com \
--cc=buildroot@buildroot.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