[Thincrust-devel] appliance-creator options

[Cameron Ross]

Thanks David.

I guess I'm looking at it from the perspective of embedded systems
development where the host platform (i.e. the developer's computer) is
typically different from the target platform (i.e. the embedded system).
Notwithstanding what appliance-tools and/or livecd-tools are doing at build
time, I'm would find it very useful to be able to build appliances for a
variety of target platforms from a single host.  Perhaps the target platform
could be specified within an input file?  Not sure how much of a stretch
this would be for the current toolchain.

Does anyone have thoughts on this?

Cameron.



On Tue, Sep 22, 2009 at 11:16 AM, David Huff <dhuff at redhat.com> wrote:

> On 09/22/2009 10:42 AM, Cameron Ross wrote:
> > Hi,
> >
> > I'm running appliance-creator on a Fedora 11 x86_64 host to create an
> image
> > for an i386 target.  However, the tool does not have an option to specify
> > the target architecture and so incorrectly uses the architecture of the
> host
> > within the generated xml file (i.e. x86_64 in my case).  Note that
> > appliance-creator does have options for other parameters that end up in
> this
> > configuration file such as --vmem.  Two questions come to mind:
> >
> > 1) Is the generated xml file the only place where this parameter needs to
> be
> > manually changed?
> > 2) Is this a planned feature?
> >
>
> The main way the appliance arch is specified is by the packages that are
> install via the yum repos specified in the kickstart file. They usually
> default to the arch of the machine you build on, ie:
>
> repo --name=rawhide
> --mirrorlist=
> http://mirrors.fedoraproject.org/mirrorlist?repo=rawhide&arch=$basearch
>
> You are correct that the xml is set to the arch of the machine:
>
> "xml += "        <arch>%s</arch>\n" % os.uname()[4]"
>
> This could possibly be changed to look for the arch of the packages
> installed on the appliance.  However I am not sure if there would be
> other repressions on building a appliance on a different arch then the
> target.
>
> My main areas of concern are the fact that during build time /proc and
> other dirs on the build host are temporarily mounted on the appliance. I
> am also not sure how the selinux relabel would react to this.
>
> Has anyone had any luck doing this? does livecd-tools support building
> different archs?  I personally have not tried this?
>
> comments....
>
> -D
>
> _______________________________________________
> Thincrust-devel mailing list
> Thincrust-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/thincrust-devel
>



-- 
Cameron Ross
Director of Technology Development
Symbotica Limited
705-929-1492
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/thincrust-devel/attachments/20091008/6385c41d/attachment.htm>