The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)


Category:Mic

From Mer Wiki
(Difference between revisions)
Jump to: navigation, search
(update links)
Line 5: Line 5:
 
mic uses [[:Category:kickstart|kickstart]] files (also known as .ks files) to determine what packages to include and how to configure them.
 
mic uses [[:Category:kickstart|kickstart]] files (also known as .ks files) to determine what packages to include and how to configure them.
  
mic provides several image types but the most useful for Mer are 'raw' or 'rootfs': ([[Category:FIXME]]FIXME: Is this enough?)
+
mic provides several image types but the most useful for Mer are 'raw' or 'fs': ([[Category:FIXME]]FIXME: Is this enough?)
 
; raw
 
; raw
 
: this format can be written directly onto a block device such as a usb stick or an mmc device.
 
: this format can be written directly onto a block device such as a usb stick or an mmc device.
; rootfs
 
: if a device can be mounted and have a filesystem made (eg N950) then writing just the file data is more efficient.
 
 
; fs
 
; fs
: a directory tree with the rootfs
+
: this writes to a local directory. If a device can be mounted and have a filesystem made (eg N950) then writing just the file data is more efficient. Add --compress-disk-image=tar.bz2 to create a tarball.
  
 
Note that some development versions of mic use the zypper package manager by default. Using --pkgmgr=yum is more reliable (19/Jan/2012)
 
Note that some development versions of mic use the zypper package manager by default. Using --pkgmgr=yum is more reliable (19/Jan/2012)

Revision as of 23:56, 21 February 2012

Mer images are made using a low-level tool called mic.

Some history: originally mic was the Moblin Image Creator, this evolved and was renamed mic2 for MeeGo, now the Tizen project is creating another, third, version of mic, but to avoid confusion (!) it will simply be called mic, not mic3.

mic uses kickstart files (also known as .ks files) to determine what packages to include and how to configure them.

mic provides several image types but the most useful for Mer are 'raw' or 'fs': (FIXME: Is this enough?)

raw
this format can be written directly onto a block device such as a usb stick or an mmc device.
fs
this writes to a local directory. If a device can be mounted and have a filesystem made (eg N950) then writing just the file data is more efficient. Add --compress-disk-image=tar.bz2 to create a tarball.

Note that some development versions of mic use the zypper package manager by default. Using --pkgmgr=yum is more reliable (19/Jan/2012)

Pages in category "Mic"

The following 3 pages are in this category, out of 3 total.

Personal tools