(→Official Meego .ks files) |
(→Modify your .ks) |
||
| Line 15: | Line 15: | ||
== MeeGo Patterns == | == MeeGo Patterns == | ||
== Modify your .ks == | == Modify your .ks == | ||
| + | Developers may want to modify the .ks files to create their own custom images. Here are the main options and sections within the .ks file. | ||
| + | |||
| + | You can also find in-depth .ks option information here: http://fedoraproject.org/wiki/Anaconda/Kickstart#Chapter_2._Kickstart_Options | ||
| + | |||
== Kickstarter == | == Kickstarter == | ||
KickStart (.ks) configuration files are passed to MIC2 to create tailored images. KickStart files specify what repos to pull from, what packages to include, what post-scripts to run and what type of images to create.
For more details about the kickstart format, see http://fedoraproject.org/wiki/Anaconda/Kickstart.
Note that not all KickStart directives and options are supported for creating Meego images. MIC2 also adds some specific directives and options. More explained below
Contents |
The official Meego .ks files are here:
For ARM based Nokia N900: http://repo.meego.com/MeeGo/builds/trunk/ <version>/handset/images/meego-handset-armv7l-n900/ For Intel Atom based netbook and handset (Moorestown): http://repo.meego.com/MeeGo/builds/trunk/ <version>/{netbook,handset,ivi}/images/<respective directory>/
You can download and use them as a base for the Meego images you create. Modify these .ks files as you wish to create tailored images.
Developers may want to modify the .ks files to create their own custom images. Here are the main options and sections within the .ks file.
You can also find in-depth .ks option information here: http://fedoraproject.org/wiki/Anaconda/Kickstart#Chapter_2._Kickstart_Options