From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 17/20] minicoredumper: adapt package's '/var/cache' requirements
Date: Fri, 7 Jun 2019 09:27:51 +0200 [thread overview]
Message-ID: <20190607072751.6m3gop6nro3z2sn5@pengutronix.de> (raw)
In-Reply-To: <20190605125421.20087-18-jbe@pengutronix.de>
On Wed, Jun 05, 2019 at 02:54:18PM +0200, Juergen Borleis wrote:
> Signed-off-by: Juergen Borleis <jbe@pengutronix.de>
> ---
> rules/minicoredumper.in | 4 ++++
> rules/rootfs.in | 7 +++++++
> rules/rootfs.make | 3 +++
> 3 files changed, 14 insertions(+)
>
> diff --git a/rules/minicoredumper.in b/rules/minicoredumper.in
> index cc8008d1c..9fc3b63ed 100644
> --- a/rules/minicoredumper.in
> +++ b/rules/minicoredumper.in
> @@ -5,6 +5,7 @@ config MINICOREDUMPER
> prompt "minicoredumper"
> select LIBELF
> select JSON_C
> + select ROOTFS_VAR_CRASH if RUNTIME
> help
> The minicoredumper project provides a program that handles the
> creation of core dump files on Linux. It can produce much smaller
> @@ -19,3 +20,6 @@ config MINICOREDUMPER
> echo '|/usr/sbin/minicoredumper %P %u %g %s %t %h %e' > /proc/sys/kernel/core_pattern
>
> by hand to actually make use of it.
> +
> + Note: on a read-only root filesystem this package still requires a
> + writable '/var/crash'.
> diff --git a/rules/rootfs.in b/rules/rootfs.in
> index 3ea4bde60..2ec7104c2 100644
> --- a/rules/rootfs.in
> +++ b/rules/rootfs.in
> @@ -226,6 +226,13 @@ config ROOTFS_VAR_CACHE
> This directory is intended for application cache data. Say 'y' here
> to ensure a '/var/cache' directory is available at run-time.
>
> +config ROOTFS_VAR_CRASH
> + bool
> + prompt "/var/crash"
> + help
> + This directory is intended for core dumps. Say 'y' here to ensure a
> + '/var/crash' directory is available at run-time.
> +
No, this is not LSB or otherwise used by different packages. minicoredumper
should just create it directly.
Michael
> config ROOTFS_VAR_SPOOL
> bool
> prompt "/var/spool"
> diff --git a/rules/rootfs.make b/rules/rootfs.make
> index 8183d0288..a1002cfcd 100644
> --- a/rules/rootfs.make
> +++ b/rules/rootfs.make
> @@ -112,6 +112,9 @@ endif
> ifdef PTXCONF_ROOTFS_VAR_CACHE
> @$(call install_copy, rootfs, 0, 0, 0755, /var/cache)
> endif
> +ifdef PTXCONF_ROOTFS_VAR_CRASH
> + @$(call install_copy, rootfs, 0, 0, 0755, /var/crash)
> +endif
> ifdef PTXCONF_ROOTFS_VAR_SPOOL
> @$(call install_copy, rootfs, 0, 0, 0755, /var/spool)
> endif
> --
> 2.20.1
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-06-07 7:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 12:54 [ptxdist] More collected changes Juergen Borleis
2019-06-05 12:54 ` [ptxdist] [PATCH 01/20] rootfs: keep /var writable, even if the rootfs is read-only Juergen Borleis
2019-06-24 6:48 ` [ptxdist] [PATCH] fixup! " Michael Olbrich
2019-06-24 6:57 ` Michael Olbrich
2019-06-05 12:54 ` [ptxdist] [PATCH 02/20] rootfs: keep '/var/tmp' permissions in sync with 'systemd' Juergen Borleis
2019-06-05 12:54 ` [ptxdist] [PATCH 03/20] rootfs: '/var' is a mandatory directory according to FHS Juergen Borleis
2019-06-05 12:54 ` [ptxdist] [PATCH 04/20] conman: adapt package's '/var/lib' requirements Juergen Borleis
2019-06-11 8:17 ` Michael Olbrich
2019-06-05 12:54 ` [ptxdist] [PATCH 05/20] networkmanager: " Juergen Borleis
2019-06-05 12:54 ` [ptxdist] [PATCH 06/20] ntp: adapt package's '/var/lib' and '/var/log' requirements Juergen Borleis
2019-06-05 12:54 ` [ptxdist] [PATCH 07/20] dnsmasq: version bump 2.79 -> 2.80 Juergen Borleis
2019-06-05 12:54 ` [ptxdist] [PATCH 08/20] dnsmasq: clean up rule file Juergen Borleis
2019-06-05 12:54 ` [ptxdist] [PATCH 09/20] dnsmasq: adapt package's '/var/lib' requirements Juergen Borleis
2019-06-05 12:54 ` [ptxdist] [PATCH 10/20] mariadb: " Juergen Borleis
2019-06-05 12:54 ` [ptxdist] [PATCH 11/20] samba: adapt package's '/var/lib' and '/var/cache' requirements Juergen Borleis
2019-06-07 7:15 ` Michael Olbrich
2019-06-05 12:54 ` [ptxdist] [PATCH 12/20] polkit: adapt package's '/var/lib' requirements Juergen Borleis
2019-06-05 12:54 ` [ptxdist] [PATCH 13/20] nfsutils: " Juergen Borleis
2019-06-07 7:25 ` Michael Olbrich
2019-06-05 12:54 ` [ptxdist] [PATCH 14/20] logrotate: " Juergen Borleis
2019-06-05 12:54 ` [ptxdist] [PATCH 15/20] systemd: adapt package's '/var/lib' and '/var/cache' requirements Juergen Borleis
2019-06-05 12:54 ` [ptxdist] [PATCH 16/20] sysstat: adapt package's '/var/log' requirements Juergen Borleis
2019-06-05 12:54 ` [ptxdist] [PATCH 17/20] minicoredumper: adapt package's '/var/cache' requirements Juergen Borleis
2019-06-07 7:27 ` Michael Olbrich [this message]
2019-06-05 12:54 ` [ptxdist] [PATCH 18/20] opkg: move opkg-database to a read-only location Juergen Borleis
2019-06-11 8:19 ` Michael Olbrich
2019-06-05 12:54 ` [ptxdist] [PATCH 19/20] dbus: adapt run-time socket path Juergen Borleis
2019-06-05 12:54 ` [ptxdist] [PATCH 20/20] Update and sync autotools based package templates Juergen Borleis
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=20190607072751.6m3gop6nro3z2sn5@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox