Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joachim Wiberg <troglobit@gmail.com>
To: buildroot@buildroot.org
Cc: Joachim Wiberg <troglobit@gmail.com>
Subject: [Buildroot] [PATCH 2/2] package/mrouted: add /var/lib/misc for systemd builds
Date: Sun,  4 Jun 2023 17:48:18 +0200	[thread overview]
Message-ID: <20230604154818.3681851-3-troglobit@gmail.com> (raw)
In-Reply-To: <20230604154818.3681851-1-troglobit@gmail.com>

Similar to dnsmasq, mrouted saves state data across reboots in the
/var/lib/misc/ directory.  In the case of mrouted it is the unique
generation id (used by neighboring mrouted routers to identify any
router restarting).  This file 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/mrouted/mrouted.mk | 1 +
 1 file changed, 1 insertion(+)

diff --git a/package/mrouted/mrouted.mk b/package/mrouted/mrouted.mk
index 3e2f49dc10..0d2071c4f0 100644
--- a/package/mrouted/mrouted.mk
+++ b/package/mrouted/mrouted.mk
@@ -18,6 +18,7 @@ define MROUTED_INSTALL_INIT_SYSV
 endef
 
 define MROUTED_INSTALL_INIT_SYSTEMD
+	mkdir -p $(TARGET_DIR)/var/lib/misc/
 	$(INSTALL) -D -m 644 $(@D)/mrouted.service \
 		$(TARGET_DIR)/usr/lib/systemd/system/mrouted.service
 endef
-- 
2.34.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2023-06-04 15:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-04 15:48 [Buildroot] [PATCH 0/2] mrouted upgrade with systemd build fix Joachim Wiberg
2023-06-04 15:48 ` [Buildroot] [PATCH 1/2] package/mrouted: bump for v4.5 release Joachim Wiberg
2023-06-04 15:48 ` Joachim Wiberg [this message]
2023-07-30 10:38 ` [Buildroot] [PATCH 0/2] mrouted 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=20230604154818.3681851-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