From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2] initramfs-tools: Restore package
Date: Wed, 11 Jul 2018 09:55:36 +0200 [thread overview]
Message-ID: <20180711075536.qs23ftiguooez2zv@pengutronix.de> (raw)
In-Reply-To: <CAMwGMjz=y_L15O4r5ikyHqjLz2Y25EVwy1YPVbwUfrWx_H7mEw@mail.gmail.com>
On Wed, Jul 11, 2018 at 12:58:44AM -0400, Jon Ringle wrote:
> On Tue, Jul 10, 2018 at 3:48 AM Michael Olbrich
> <m.olbrich@pengutronix.de> wrote:
> If you look into the `init` script and the `scripts/local` and
> `scripts/nfs` scripts, you'll see that there are predefined hooks
> where it call `run_scripts ...` with some predetermined directory
> names. The package only provides some scripts in `scripts/init-top`,
> and `scripts/local-premount`, but the hooks in the scripts allow for
> the user to provide scripts in any of these directories:
> init script calls:
> run_scripts /scripts/init-top
> run_scripts /scripts/init-premount
> mount_top (depending on ${BOOT} value which should be either "local"
> or "nfs", will call the function of that name in `local` or `nfs`
> scripts, which will call either: `run_scripts /scripts/local-top` or
> `run_scripts /scripts/nfs-top`)
> mount_premount (same logic as mount_top... resolving to either
> `run_scripts /scripts/local-premount` or `run_scripts
> /scripts/nfs-premount`)
> mount_bottom (ditto)
> mountroot (defined in /scripts/local or /scripts/nfs)
>
> In all the following are the possible trees of user defined scripts
> that could be installed:
> /scripts/init-top
> /scripts/init-premount
> /scripts/init-bottom
> /scripts/local-top
> /scripts/local-block
> /scripts/local-premount
> /scripts/local-bottom
> /scripts/nfs-top
> /scripts/nfs-premount
> /scripts/nfs-bottom
>
> I could just do an $(install_alternative_tree ...) for each of the above?
That sounds good. Note, that install_alternative_tree will fail if no
source directory is found. So you either need to make them optional or
create empty directories.
Michael
--
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:[~2018-07-11 7:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-07 7:22 [ptxdist] [PATCH] image-root-tgz: Add IMAGE_ROOT_TGZ_LABEL option jon
2018-07-07 7:22 ` [ptxdist] [PATCH v2] initramfs-tools: Restore package jon
2018-07-10 7:48 ` Michael Olbrich
2018-07-11 4:58 ` Jon Ringle
2018-07-11 7:55 ` Michael Olbrich [this message]
2018-07-10 7:29 ` [ptxdist] [PATCH] image-root-tgz: Add IMAGE_ROOT_TGZ_LABEL option Michael Olbrich
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=20180711075536.qs23ftiguooez2zv@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