Thank you, Is there someplace that we can find the list of packages that are specific to the Menlow configuration and the repositories that these packages might be available at.
As far as the .ks file is concerned, I agree, the syntax is simple, and we should not have much problem once we know what Menlow specific packages we need to reference and where to find them. I appreciate the help, Steve Hawkins --------------------------------------------------------------------------- This email and any files transmitted with it are confidential & proprietary to Systems and Software Enterprises, Inc. (dba IMS). This information is intended solely for the use of the individual or entity to which it is addressed. Access or transmittal of the information contained in this e-mail, in full or in part, to any other organization or persons is not authorized. --------------------------------------------------------------------------- -----Original Message----- From: Jian-feng Ding [mailto:jian-feng.d...@intel.com] Sent: Monday, May 04, 2009 2:49 AM To: Steve Hawkins Cc: dev@moblin.org Subject: Re: [Moblin Dev] Using MIC-1 vs MIC-2 for creating Menlow Images On Sat, Apr 25, 2009 at 06:33:30AM +0800, Steve Hawkins wrote: > I'm wondering if the MIC-2 tool can be used to create an image for a > menlow target. MIC-1 has specific options for creating menlow targets, > but I have not been able to figure out how to get MIC-2 to generate a > menlow image. Also, is it possible to use the same package cache with > both the MIC-1 and MIC-2 utilities? > > > > Any help in better understanding the differences between these two > imaging tools would be greatly appreciated. > For different platform, mic2 need different kickstart (*.ks) file to specify needed repo and packages. The syntax of kickstart is simple and there're several samples in the mic2 package. > > > Thank you, > > > > Steve Hawkins > > > > > ------------------------------------------------------------------------ --- > This email and any files transmitted with it are confidential & proprietary > to Systems and Software Enterprises, Inc. (dba IMS). This information is > intended solely for the use of the individual or entity to which it is > addressed. Access or transmittal of the information contained in this e-mail, > in full or in part, to any other organization or persons is not authorized. > ------------------------------------------------------------------------ --- > > _______________________________________________ > Moblin dev Mailing List > dev@moblin.org > > To manage or unsubscribe from this mailing list visit: > https://lists.moblin.org/mailman/listinfo/dev or your user account on http://moblin.org once logged in. > > For more information on the Moblin Developer Mailing lists visit: > http://moblin.org/community/mailing-lists _______________________________________________ Moblin dev Mailing List dev@moblin.org To manage or unsubscribe from this mailing list visit: https://lists.moblin.org/mailman/listinfo/dev or your user account on http://moblin.org once logged in. For more information on the Moblin Developer Mailing lists visit: http://moblin.org/community/mailing-lists
