From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
Received: from mediacenter.hi.pengutronix.de ([2001:6f8:1178:2::65])
	by metis.ext.pengutronix.de with esmtp (Exim 4.72)
	(envelope-from <mol@pengutronix.de>) id 1RJip4-00067d-5E
	for ptxdist@pengutronix.de; Fri, 28 Oct 2011 11:33:58 +0200
Received: from mol by mediacenter.hi.pengutronix.de with local (Exim 4.72)
	(envelope-from <mol@pengutronix.de>) id 1RJip4-0003pp-4G
	for ptxdist@pengutronix.de; Fri, 28 Oct 2011 11:33:58 +0200
Date: Fri, 28 Oct 2011 11:33:58 +0200
From: Michael Olbrich <m.olbrich@pengutronix.de>
Message-ID: <20111028093358.GC12223@pengutronix.de>
References: <4EAA6602.9040105@erwinrol.com>
 <4EAA69E8.1080504@eia.be>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <4EAA69E8.1080504@eia.be>
Subject: Re: [ptxdist] General Ptxdist usecase question
Reply-To: ptxdist@pengutronix.de
List-Id: PTXdist Development Mailing List <ptxdist.pengutronix.de>
List-Unsubscribe: <http://metis.pengutronix.de/cgi-bin/mailman/options/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=unsubscribe>
List-Archive: <http://metis.pengutronix.de/pipermail/ptxdist>
List-Post: <mailto:ptxdist@pengutronix.de>
List-Help: <mailto:ptxdist-request@pengutronix.de?subject=help>
List-Subscribe: <http://metis.pengutronix.de/cgi-bin/mailman/listinfo/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ptxdist-bounces@pengutronix.de
Errors-To: ptxdist-bounces@pengutronix.de
To: ptxdist@pengutronix.de

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.

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