From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 9150cbddeb913ce093f2f7e0669e4a8ab3265bb0
Date: Tue, 30 Sep 2025 15:09:44 +0000 (UTC) [thread overview]
Message-ID: <4cbhLJ641Mz2xqQ@people01.haj.ipfire.org> (raw)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, master has been updated
via 9150cbddeb913ce093f2f7e0669e4a8ab3265bb0 (commit)
from a950be6cd698adb9d16c458c0189c7ec2bf7494c (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 9150cbddeb913ce093f2f7e0669e4a8ab3265bb0
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Tue Sep 30 15:09:23 2025 +0000
core198: Ship the cleanfs initscript
This is required to create /var/run/suricata at boot time.
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/198/filelists/files | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/rootfiles/core/198/filelists/files b/config/rootfiles/core/198/filelists/files
index ff40a305f..44d8182e9 100644
--- a/config/rootfiles/core/198/filelists/files
+++ b/config/rootfiles/core/198/filelists/files
@@ -1,3 +1,4 @@
+etc/rc.d/init.d/cleanfs
etc/rc.d/init.d/suricata
var/ipfire/graphs.pl
var/ipfire/ids-functions.pl
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2025-09-30 15:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4cbhLJ641Mz2xqQ@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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