From: Juergen Borleis <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Ivor Kruger <ivor@veriline.co.za>
Subject: Re: [ptxdist] Where to find parameters for UBIFS creation
Date: Thu, 24 Apr 2014 10:49:51 +0200 [thread overview]
Message-ID: <201404241049.51429.jbe@pengutronix.de> (raw)
In-Reply-To: <CF7E9414.EE06%ivor@veriline.co.za>
Hi Ivor,
On Thursday 24 April 2014 10:13:42 Ivor Kruger wrote:
> In order to avoid having to do this, what is the easiest way to add a user
> application to the root/home folder?
You can build this application as a generic package like all other packages as
well. That's the main goal of PTXdist.
> Where do I add custom init.d scripts to get them as part of the image?
$ ptxdist newpackage file
This will generate a rule file to simply copy new files into the image.
But if you just want to replace a generic (=already provided by PTXdist) file
by your own specific version, just store your specific version into your
BSP's "projectroot/<regular-path>/<specific-file>"
PTXdist will prefer the local file the next time the corresponding package will
be generated.
Regards,
Juergen
--
Pengutronix e.K. | Juergen Borleis |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-04-24 8:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 6:22 Ivor Kruger
2014-04-24 7:46 ` Michael Olbrich
2014-04-24 7:58 ` Juergen Borleis
2014-04-24 8:13 ` Ivor Kruger
2014-04-24 8:49 ` Juergen Borleis [this message]
2014-04-24 8:49 ` Ivor Kruger
[not found] ` <CF7E914A.EE00%ivor@veriline.co.za>
2014-04-24 8:51 ` Juergen Borleis
2014-04-24 8:57 ` Josef Holzmayr
2014-04-24 9:09 ` Ivor Kruger
2014-04-24 9:22 ` Juergen Borleis
-- strict thread matches above, loose matches on Subject: below --
2014-04-24 5:50 Ivor Kruger
2014-04-24 7:46 ` 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=201404241049.51429.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=ivor@veriline.co.za \
--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