mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Bart De Vos <bart.devos@eia.be>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] General Ptxdist usecase question
Date: Fri, 28 Oct 2011 11:37:51 +0200	[thread overview]
Message-ID: <4EAA77EF.1030602@eia.be> (raw)
In-Reply-To: <20111028093358.GC12223@pengutronix.de>



On 10/28/2011 11:33 AM, Michael Olbrich wrote:
> Hi,
>
> On Fri, Oct 28, 2011 at 10:38:00AM +0200, Bart De Vos wrote:
>    
>> We have some kind of similar setup in which we split our root file
>> system and the customers filesystem. In runtime the customers
>> filesystem is mounted on a fixed point (/opt). Off-course we have
>> designed this separation from the start, we have 2 separated
>> filesystems. For the second filesystem you can use just another
>> ptxdist configfile. I don't know whether you can merge 2 file system
>> images together with ptxdist. But for this purpose a simple script
>> can automate this.
>>      
> If the second file system is available as a tar-ball you can do:
> @$(call install_archive, otherfs, -, -, \
> 	$(PTXDIST_WORKSPACE)/local_src/otherfs.tar.gz, /)
>
>    
>> Another approach can be to support a list of configfiles in stead of
>> only one. This will give you a single image file which was what you
>> 'v been asking for in the first place.
>>
>> Are there any plans to support a list of configfiles?
>>      
> I don't understand what you mean with this.
>    
In the project directory I have a symlink 'selected_ptxconfig'. This 
points to only one file. Is it possible to have this separated in more 
than one file, for example let 'selected_ptxconfig' point to a directory 
and use all the files in there. Hope that's clear.
> Michael
>    
/Bart.

-- 
--------------------------------------------------
Bart De Vos
Development Engineer
mailto:bart.devos@eia.be

EIA Electronics
Vluchtenburgstraat  3
B-2630 Aartselaar  (Belgium)
phone	: +32(0)3 870 85 29
fax    	: +32(0)3 877 14 72
website	: http://www.eia.be/
--------------------------------------------------
Basically, perfect development is impossible.
Development can be fast, good and cheap. Pick two!
— Larry Wall
--------------------------------------------------


-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2011-10-28  9:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-28  8:21 Erwin Rol
2011-10-28  8:38 ` Bart De Vos
2011-10-28  8:46   ` Erwin Rol
2011-10-28  9:26     ` Bart De Vos
2011-10-28  9:33   ` Michael Olbrich
2011-10-28  9:37     ` Bart De Vos [this message]
2011-10-28  9:45       ` Michael Olbrich
2011-10-28  9:48         ` Bart De Vos
2011-10-28  9:29 ` Michael Olbrich
2011-10-28 10:05   ` Erwin Rol
2011-10-28 10:32     ` Michael Olbrich
2011-11-02 19:03       ` Flavio de Castro Alves Filho

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=4EAA77EF.1030602@eia.be \
    --to=bart.devos@eia.be \
    --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