MeeGo wiki - User contributions [en]

ARM/N900/Install/MMC

2010-10-31T23:14:31Z

Auke: /* Images */

= Installing MeeGo to N900 on external MMC card =

'''NOTE: Read the whole guide before doing any steps from this guide to make sure you understand everything.'''

If you do not want to erase the NAND partition or the internal 32G eMMC from the N900 device, this installation is for you. What you need for this installation is a raw image that can be put to the MMC card and kernel (same kernel that is installed to the MMC).

=== Images ===

Raw images and corresponding kernel images can be found at http://repo.meego.com/MeeGo/builds/ (development builds) and http://repo.meego.com/MeeGo/releases/ (stable releases)

Find official release images here ([[ARM/N900#Releases]])

You may want to check for the most recent N900 test reports at [[Quality#MeeGo_Handset_Testing]] to see how much functionality is known to work on the N900.

== Installing Rootfs on external MMC card ==

First what you need, is a microSD memory card which does not contain any information that you need, as it will be erased during this operation.

The steps in this guide require an MMC card of at least 2gb, however some cards offer slight variations in capacity, so better to take a 4gb card to be on the safe side :)

=== Linux ===

When inserting the microSD memory card in the card reader, you need to find out what the proper device for the card is. This can be done with for example fdisk:
sudo fdisk -l

An example output ('''NOTE: The /dev/sdX is used as an example on your PC this might be also called /dev/mmcblk0, /dev/sdd or something else''')
$ sudo fdisk -l
...
Disk /dev/sdX: 3965 MB, 3965714432 bytes
194 heads, 30 sectors/track, 1330 cylinders
Units = cylinders of 5820 * 512 = 2979840 bytes
Disk identifier: 0x0001ab40

Device Boot Start End Blocks Id System
/dev/sdX1 1 588 1708984 83 Linux

'''NOTE: The .raw image contains the partition table as well. So the image needs to be written to /dev/sdX not /dev/sdX1.'''

After you are 100% sure that the /dev/sdX is the microSD memory card you just inserted in the card reader, you can use for example dd to put the image to the card:
$ sudo dd bs=4096 if='''<raw_image>''' of=/dev/sdX

If you are low on disk space, you can use

$ bzcat <raw_image>.bz2 | sudo dd bs=4096 of=/dev/sdX

to decompress the compressed raw image on the fly without having to unpack it on you computer first. And if you have pv(1) installed, you can add it in between to display the progress (the image is ~ 2GB in size as of 2010-10-04):

$ bzcat <raw_image>.bz2 | pv | sudo dd bs=4096 of=/dev/sdX

The dd does not show any progress until the file is written to the device, so be patient.

Although sending a USR1 signal to a running dd process makes it print I/O statistics to standard error and then resume copying:
$ dd if=/dev/zero of=/dev/null& pid=$!
from another term:
$ kill -USR1 $pid

dd will output:

328356+0 records in
328356+0 records out
1344946176 bytes (1.3 GB) copied, 105.625 s, 12.7 MB/s

After this, you can insert the card in the N900.

=== Windows ===

# Download and install bzip2 to Windows http://gnuwin32.sourceforge.net/packages/bzip2.htm
# Uncompress raw image in command prompt "bunzip2.exe <compressed raw image>"
# Download the Win32DiskImager.exe program: https://launchpad.net/win32-image-writer/+download (zip file)
# Unzip the file and extract the contents to a known directory
# Run W32DiskImager.exe
# Select the MeeGo image file (note you must write *.* file name to see all files)
# Select the drive letter which corresponds to the microSD memory card.
# Click the "Write" button to byte-copy the image to the microSD memory card.

=== On the N900 itself ===

This should be a last resort solution.

# Download and unpack the raw image to a desktop computer (see above).
# un-mount the microSD memory card
sudo gainroot
umount /dev/mmcblkXpY
dd if=/home/user/MyDocs/'''<raw_image>''' of=/dev/mmcblk1

==== Notes ====
* X, Y in umount command should be the device number and partition number, usually 1, 1, but maybe 0, 1 or something else, use:
cat /proc/partitions
for detailed information.
* There might be more than one partition on the microSD memory card, though it is unlikely.
* It is possible to download the compressed image to your N900 but it is not recommended as it takes very long to unpack.
* `dd` does not give any output while it is copying, so be patient.

== Load or flash kernel on N900 ==

Before the MeeGo is able to boot you need also load the kernel (vmlinuz) provided with the raw image to the device. This can be done with the [[ARM/N900/tools/flasher|flasher]].

===Prerequisites===

* the flasher application needs to be installed on your computer. You can get it from [http://tablets-dev.nokia.com/maemo-dev-env-downloads.php here].
On 64-bit Ubuntu/Debian this command would do the trick, after downloading the .deb file:

$ sudo dpkg --force-architecture -i maemo_flasher-*i386.deb

===Running Meego===

'''NOTE: First open the back cover of N900 and insert the MMC card to the slot, reinstall the back cover again.

'''NOTE: Back cover must be closed to boot from MMC.'''

'''NOTE: If you have a flashing jig, you will need to put a magnet at the red location marked [http://www.daimi.au.dk/~cvm/magnet.png here]'''

You need to execute the following command on your host system.

'''NOTE: the device must be turned off and disconnected from the computer. Connect it to the computer using the USB cable only after executing the command'''

$ sudo flasher-3.5 -l -k '''<kernel>''' -b

A message like:
flasher v2.5.2 (Oct 21 2009)
Suitable USB device not found, waiting.
is shown on the terminal of the computer.

Then connect N900 to the computer via the USB cable and Meego OS will be booted.
You may need to keep 'U' key pressed (on the phone's keyboard) when connecting the cable.

'''NOTE: The command above will only load the kernel to the device, so next time you boot the device the original kernel should be used and your Maemo 5 OS should boot normally.'''

If you want to flash the kernel to your device so that it is not forgotten when it is powered off use option -f instead of option -l on command above.

'''NOTE: It's highly recommended NOT to flash the kernel on your device unless you really know what you're doing (so please use -l instead of -f). Don't blame us if you brick your device, you have been warned!'''

{| border="1" cellpadding="5"
|+ Examples of files that can be used with this guide
! MeeGo Version
! <kernel>
! <raw_image>
|-
| 1.0.99.2.20101019.1
| [http://repo.meego.com/MeeGo/builds/1.0.99/1.0.99.2.20101019.1/handset/images/meego-handset-armv7l-n900/meego-handset-armv7l-n900-1.0.99.2.20101019.1-vmlinuz-2.6.35.3-10.3-n900 meego-handset-armv7l-n900-1.0.99.2.20101019.1-vmlinuz-2.6.35.3-10.3-n900]
| [http://repo.meego.com/MeeGo/builds/1.0.99/1.0.99.2.20101019.1/handset/images/meego-handset-armv7l-n900/meego-handset-armv7l-n900-1.0.99.2.20101019.1-mmcblk0p.raw.bz2 meego-handset-armv7l-n900-1.0.99.2.20101019.1-mmcblk0p.raw.bz2]

|}

Upgrading MeeGo Versions

2010-10-31T21:24:22Z

Auke:

== So you want to upgrade your MeeGo system from 1.(x) to 1.(x+1) ==

There's been a lot of questions recently on the forums and IRC about how to upgrade an existing MeeGo installation
from e.g. 1.0 to 1.1 without reinstalling. This isn't something that's easy right now, and certainly not supported.
However, it is very much so possible with zypper, and requires special attention to the process in order to not
end up with a non-booting system, or worse (data loss).

=== Warning: do not try this at home ===

The procedure described below assumes that you know what packages do and which ones you can (probably) miss, upgrade
or temporary break while you upgrade your system. It's not a short procedure, it's not safe, it's not guaranteed to
work. If you have any chance to do a reinstall, do that instead.

=== Please reinstall instead ===

Yes, this is the supported method. Take the time to backup your data, or convert your box to use a /home partition
so that the next upgrade you can just rewrite your root partition without losing your personal data. Copy your
data to something safe, like another computer, or a usb hard drive.

=== Make Backups ===

I'm not responsible for you losing your data. You are yourself.

== Ok, get on with it already ==

Upgrading a live and running installation of MeeGo 1.0 to 1.1 can be accomplished by forcing zypper to reinstall all
packages and package groups from the 1.1 repo's instead of the 1.0 repo's.

In essence, one needs to delete all the 1.0 repo files, and add the 1.1 repo files:

# cd /etc/zypp/repo.d/
# rm -f *.repo

Then you need to get the new repo's and keys:

Find the .ks file for the image you want to install, for instance over here: [[http://repo.meego.com/MeeGo/releases/1.1/netbook/images/meego-netbook-ia32/meego-netbook-ia32-1.1.ks]]

Open the kickstart file, and look for the lines that add repo files to the kickstart. These are the new repo files you should import on your system: ('''Note: you need to add "repodata/" after the link found in the kickstart files''')

# zypper addrepo --type rpm-md --check --name adobe http://linuxdownload.adobe.com/linux/i386/repodata/ adobe
# zypper addrepo --type rpm-md --check --name=core http://repo.meego.com/MeeGo/releases/1.1/core/repos/ia32/packages/ core
# zypper addrepo --type rpm-md --check --name=netbook http://repo.meego.com/MeeGo/releases/1.1/netbook/repos/ia32/packages/ netbook
# zypper addrepo --type rpm-md --check --name=non-oss http://repo.meego.com/MeeGo/releases/1.1/non-oss/repos/ia32/packages/ non-oss
# zypper addrepo --type rpm-md --check --name=updates-core http://repo.meego.com/MeeGo/updates/1.1/core/repos/ia32/packages/ updates-core
# zypper addrepo --type rpm-md --check --name=updates-netbook http://repo.meego.com/MeeGo/updates/1.1/netbook/repos/ia32/packages/ updates-netbook
# zypper addrepo --type rpm-md --check --name=updates-non-oss http://repo.meego.com/MeeGo/updates/1.1/non-oss/repos/ia32/packages/ updates-non-oss

(add any repo that you think you might need here, such as handset or IVI).

clearing zypper's cache:

# zypper clean --all
# zypper refresh

That should make zypper forget all about the old repositories. The refresh step forces zypper to get the new repo data, and since we don't have the key installed yet,
it will prompt for temporarily accepting it.

The following step installs the GPG key as /etc/pki/rpm-gpg/RPM-GPG-KEY-meego01:

# zypper install --force --from core meego-release

You can follow up by repeating the 'clear' and 'refresh' step to confirm zypper now accepts the signed key.

=== Then what? ===

Well, that was the easy part. Now zypper knows nothing but the new repository files and whatever we get
it to install, it will be from the new 1.1 repositories.

This is where the hard and dangerous part starts: We need to tell zypper to basically reinstall every
package, but from the new repositories. Just running a 'zypper update' will not work, as zypper refuses
to downgrade packages. Yes, you will be "downgrading" packages because version numbers between 1.0 and
1.1 are not consistent. Don't worry, you'll get newer software, not old stuff.

=== The easy method ===

# zypper dup

This calls `zypper dist-upgrade`. It basically tries to do what the manual procedure below is. If it
works for you, awesome. I have not yet had too much experience with the automated way but it seems to
work well.

=== Upgrading all your packages manually ===

Now we need to upgrade all the installed packages. There are several ways of doing this, but my favorite
method is to clean the system from old packages first that are not needed to do the upgrade:

# init 3

that's right, drop to the console. This way we can just remove a ton of packages, which makes the
critical part of the upgrade a bit easier. At least you won't be stuck in an Xorg session that froze up
leaving you unable to go to the console and forcing you to reboot a machine that was just reinstalling
glibc making all your programs unrunnable because ldconfig wasn't run (yeah, it's happened to me).

# zypper remove mutter
# zypper remove gtk+-2
# ...

Check the list properly and make sure you're not deleting vital libraries and packages. Although this
step is optional, pruning the update list is highly recommended.

Next we'll make a list of packages that need upgrading to the new repo versions, and install those one
by one:

# for p in `zypper pa| grep ^v |cut -d '|' -f3`; do zypper -n install --force $p l done

Repeat this until nothing happens anymore, possibly followed by:

# zypper refresh

Also, check the output of

# zypper pa

and look for packages that have a '''v''' at the start of the line:

# zypper pa| grep ^v
v | core | build | 2010.04.15-1.3 | noarch
v | core | evolution-data-server | 2.30.2~20100629-1.11 | i586
v | netbook | gcalctool | 5.25.91-1.88 | i586

those still need to be forced to update, or removed.

Some packages refuse to be upgraded even so, they might need to be forced with repo, like this:

# zypper install --force --from core sample-media

If zypper refuses to upgrade a package marked with '''v''' after a few tries, try removing the package, and reinstalling
it. Or see if the package is now under a new name and the newly named package needs to be installed instead.

=== Conclusion ===

While dangerous and a lot of work, it's possible with zypper to force reinstallation of all the packages against a new
repository one-by-one with --force. This is definitely not recommended for anyone who wants their system to be
stable and/or safe. Please use at your own risk.

Upgrading MeeGo Versions

2010-10-29T18:19:43Z

Auke: /* Ok, get on with it already */

== So you want to upgrade your MeeGo system from 1.(x) to 1.(x+1) ==

There's been a lot of questions recently on the forums and IRC about how to upgrade an existing MeeGo installation
from e.g. 1.0 to 1.1 without reinstalling. This isn't something that's easy right now, and certainly not supported.
However, it is very much so possible with zypper, and requires special attention to the process in order to not
end up with a non-booting system, or worse (data loss).

=== Warning: do not try this at home ===

The procedure described below assumes that you know what packages do and which ones you can (probably) miss, upgrade
or temporary break while you upgrade your system. It's not a short procedure, it's not safe, it's not guaranteed to
work. If you have any chance to do a reinstall, do that instead.

=== Please reinstall instead ===

Yes, this is the supported method. Take the time to backup your data, or convert your box to use a /home partition
so that the next upgrade you can just rewrite your root partition without losing your personal data. Copy your
data to something safe, like another computer, or a usb hard drive.

=== Make Backups ===

I'm not responsible for you losing your data. You are yourself.

== Ok, get on with it already ==

Upgrading a live and running installation of MeeGo 1.0 to 1.1 can be accomplished by forcing zypper to reinstall all
packages and package groups from the 1.1 repo's instead of the 1.0 repo's.

In essence, one needs to delete all the 1.0 repo files, and add the 1.1 repo files:

# cd /etc/zypp/repo.d/
# rm -f *.repo

Then you need to get the new repo's and keys:

Find the .ks file for the image you want to install, for instance over here: [[http://repo.meego.com/MeeGo/releases/1.1/netbook/images/meego-netbook-ia32/meego-netbook-ia32-1.1.ks]]

Open the kickstart file, and look for the lines that add repo files to the kickstart. These are the new repo files you should import on your system: ('''Note: you need to add "repodata/" after the link found in the kickstart files''')

# zypper addrepo --type rpm-md --check --name adobe http://linuxdownload.adobe.com/linux/i386/repodata/ adobe
# zypper addrepo --type rpm-md --check --name=core http://repo.meego.com/MeeGo/releases/1.1/core/repos/ia32/packages/ core
# zypper addrepo --type rpm-md --check --name=netbook http://repo.meego.com/MeeGo/releases/1.1/netbook/repos/ia32/packages/ netbook
# zypper addrepo --type rpm-md --check --name=non-oss http://repo.meego.com/MeeGo/releases/1.1/non-oss/repos/ia32/packages/ non-oss
# zypper addrepo --type rpm-md --check --name=updates-core http://repo.meego.com/MeeGo/updates/1.1/core/repos/ia32/packages/ updates-core
# zypper addrepo --type rpm-md --check --name=updates-netbook http://repo.meego.com/MeeGo/updates/1.1/netbook/repos/ia32/packages/ updates-netbook
# zypper addrepo --type rpm-md --check --name=updates-non-oss http://repo.meego.com/MeeGo/updates/1.1/non-oss/repos/ia32/packages/ updates-non-oss

(add any repo that you think you might need here, such as handset or IVI).

This last step installs the GPG key as /etc/pki/rpm-gpg/RPM-GPG-KEY-meego01:

# zypper install --force meego-release

=== Then what? ===

Well, that was the easy part. Now zypper knows nothing but the new repository files and whatever we get
it to install, it will be from the new 1.1 repositories.

This is where the hard and dangerous part starts: We need to tell zypper to basically reinstall every
package, but from the new repositories. Just running a 'zypper update' will not work, as zypper refuses
to downgrade packages. Yes, you will be "downgrading" packages because version numbers between 1.0 and
1.1 are not consistent. Don't worry, you'll get newer software, not old stuff.

Start with clearing zypper's cache:

# zypper clean --all
# zypper refresh

That should make zypper forget all about the old repositories, and check and use the new key we just
installed. If everything is OK, you will not get warnings about keys here anymore.

=== The easy method ===

# zypper dup

This calls `zypper dist-upgrade`. It basically tries to do what the manual procedure below is. If it
works for you, awesome. I have not yet had too much experience with the automated way but it seems to
work well.

=== Upgrading all your packages manually ===

Now we need to upgrade all the installed packages. There are several ways of doing this, but my favorite
method is to clean the system from old packages first that are not needed to do the upgrade:

# init 3

that's right, drop to the console. This way we can just remove a ton of packages, which makes the
critical part of the upgrade a bit easier. At least you won't be stuck in an Xorg session that froze up
leaving you unable to go to the console and forcing you to reboot a machine that was just reinstalling
glibc making all your programs unrunnable because ldconfig wasn't run (yeah, it's happened to me).

# zypper remove mutter
# zypper remove gtk+-2
# ...

Check the list properly and make sure you're not deleting vital libraries and packages. Although this
step is optional, pruning the update list is highly recommended.

Next we'll make a list of packages that need upgrading to the new repo versions, and install those one
by one:

# for p in `zypper pa| grep ^v |cut -d '|' -f3`; do zypper -n install --force $p l done

Repeat this until nothing happens anymore, possibly followed by:

# zypper refresh

Also, check the output of

# zypper pa

and look for packages that have a '''v''' at the start of the line:

# zypper pa| grep ^v
v | core | build | 2010.04.15-1.3 | noarch
v | core | evolution-data-server | 2.30.2~20100629-1.11 | i586
v | netbook | gcalctool | 5.25.91-1.88 | i586

those still need to be forced to update, or removed.

Some packages refuse to be upgraded even so, they might need to be forced with repo, like this:

# zypper install --force --from core sample-media

If zypper refuses to upgrade a package marked with '''v''' after a few tries, try removing the package, and reinstalling
it. Or see if the package is now under a new name and the newly named package needs to be installed instead.

=== Conclusion ===

While dangerous and a lot of work, it's possible with zypper to force reinstallation of all the packages against a new
repository one-by-one with --force. This is definitely not recommended for anyone who wants their system to be
stable and/or safe. Please use at your own risk.

Upgrading MeeGo Versions

2010-10-29T18:11:39Z

Auke:

== So you want to upgrade your MeeGo system from 1.(x) to 1.(x+1) ==

There's been a lot of questions recently on the forums and IRC about how to upgrade an existing MeeGo installation
from e.g. 1.0 to 1.1 without reinstalling. This isn't something that's easy right now, and certainly not supported.
However, it is very much so possible with zypper, and requires special attention to the process in order to not
end up with a non-booting system, or worse (data loss).

=== Warning: do not try this at home ===

The procedure described below assumes that you know what packages do and which ones you can (probably) miss, upgrade
or temporary break while you upgrade your system. It's not a short procedure, it's not safe, it's not guaranteed to
work. If you have any chance to do a reinstall, do that instead.

=== Please reinstall instead ===

Yes, this is the supported method. Take the time to backup your data, or convert your box to use a /home partition
so that the next upgrade you can just rewrite your root partition without losing your personal data. Copy your
data to something safe, like another computer, or a usb hard drive.

=== Make Backups ===

I'm not responsible for you losing your data. You are yourself.

== Ok, get on with it already ==

Upgrading a live and running installation of MeeGo 1.0 to 1.1 can be accomplished by forcing zypper to reinstall all
packages and package groups from the 1.1 repo's instead of the 1.0 repo's.

In essence, one needs to delete all the 1.0 repo files, and add the 1.1 repo files:

# cd /etc/zypp/repo.d/
# rm -f *.repo

Then you need to get the new repo's and keys:

Find the .ks file for the image you want to install, for instance over here: [[http://repo.meego.com/MeeGo/releases/1.1/netbook/images/meego-netbook-ia32/meego-netbook-ia32-1.1.ks]]

Open the kickstart file, and look for the lines that add repo files to the kickstart. These are the new repo files you should import on your system: ('''Note: you need to add "repodata/" after the link found in the kickstart files''')

# zypper addrepo --type rpm-md --check --name adobe http://linuxdownload.adobe.com/linux/i386/repodata/ adobe
# zypper addrepo --type rpm-md --check --name=core http://repo.meego.com/MeeGo/releases/1.1/core/repos/ia32/packages/ core
# zypper addrepo --type rpm-md --check --name=netbook http://repo.meego.com/MeeGo/releases/1.1/netbook/repos/ia32/packages/ netbook
# zypper addrepo --type rpm-md --check --name=non-oss http://repo.meego.com/MeeGo/releases/1.1/non-oss/repos/ia32/packages/ non-oss
# zypper addrepo --type rpm-md --check --name=updates-core http://repo.meego.com/MeeGo/updates/1.1/core/repos/ia32/packages/ updates-core
# zypper addrepo --type rpm-md --check --name=updates-netbook http://repo.meego.com/MeeGo/updates/1.1/netbook/repos/ia32/packages/ updates-netbook
# zypper addrepo --type rpm-md --check --name=updates-non-oss http://repo.meego.com/MeeGo/updates/1.1/non-oss/repos/ia32/packages/ updates-non-oss

(add any repo that you think you might need here, such as handset or IVI).

This last step installs the GPG key as /etc/pki/rpm-gpg/RPM-GPG-KEY-meego01:

# zypper install --force meego-release

=== Then what? ===

Well, that was the easy part. Now zypper knows nothing but the new repository files and whatever we get
it to install, it will be from the new 1.1 repositories.

This is where the hard and dangerous part starts: We need to tell zypper to basically reinstall every
package, but from the new repositories. Just running a 'zypper update' will not work, as zypper refuses
to downgrade packages. Yes, you will be "downgrading" packages because version numbers between 1.0 and
1.1 are not consistent. Don't worry, you'll get newer software, not old stuff.

Start with clearing zypper's cache:

# zypper clean --all
# zypper refresh

That should make zypper forget all about the old repositories, and check and use the new key we just
installed. If everything is OK, you will not get warnings about keys here anymore.

=== Upgrading all your packages ===

Now we need to upgrade all the installed packages. There are several ways of doing this, but my favorite
method is to clean the system from old packages first that are not needed to do the upgrade:

# init 3

that's right, drop to the console. This way we can just remove a ton of packages, which makes the
critical part of the upgrade a bit easier. At least you won't be stuck in an Xorg session that froze up
leaving you unable to go to the console and forcing you to reboot a machine that was just reinstalling
glibc making all your programs unrunnable because ldconfig wasn't run (yeah, it's happened to me).

# zypper remove mutter
# zypper remove gtk+-2
# ...

Check the list properly and make sure you're not deleting vital libraries and packages. Although this
step is optional, pruning the update list is highly recommended.

Next we'll make a list of packages that need upgrading to the new repo versions, and install those one
by one:

# for p in `zypper pa| grep ^v |cut -d '|' -f3`; do zypper -n install --force $p l done

Repeat this until nothing happens anymore, possibly followed by:

# zypper refresh

Also, check the output of

# zypper pa

and look for packages that have a '''v''' at the start of the line:

# zypper pa| grep ^v
v | core | build | 2010.04.15-1.3 | noarch
v | core | evolution-data-server | 2.30.2~20100629-1.11 | i586
v | netbook | gcalctool | 5.25.91-1.88 | i586

those still need to be forced to update, or removed.

Some packages refuse to be upgraded even so, they might need to be forced with repo, like this:

# zypper install --force --from core sample-media

If zypper refuses to upgrade a package marked with '''v''' after a few tries, try removing the package, and reinstalling
it. Or see if the package is now under a new name and the newly named package needs to be installed instead.

=== Conclusion ===

While dangerous and a lot of work, it's possible with zypper to force reinstallation of all the packages against a new
repository one-by-one with --force. This is definitely not recommended for anyone who wants their system to be
stable and/or safe. Please use at your own risk.

Upgrading MeeGo Versions

2010-10-29T17:47:58Z

Auke: Created page with "== So you want to upgrade your MeeGo system from 1.(x) to 1.(x+1) == There's been a lot of questions recently on the forums and IRC about how to upgrade an existing MeeGo instal…"

== So you want to upgrade your MeeGo system from 1.(x) to 1.(x+1) ==

There's been a lot of questions recently on the forums and IRC about how to upgrade an existing MeeGo installation
from e.g. 1.0 to 1.1 without reinstalling. This isn't something that's easy right now, and certainly not supported.
However, it is very much so possible with zypper, and requires special attention to the process in order to not
end up with a non-booting system, or worse (data loss).

=== Warning: do not try this at home ===

The procedure described below assumes that you know what packages do and which ones you can (probably) miss, upgrade
or temporary break while you upgrade your system. It's not a short procedure, it's not safe, it's not guaranteed to
work. If you have any chance to do a reinstall, do that instead.

=== Please reinstall instead ===

Yes, this is the supported method. Take the time to backup your data, or convert your box to use a /home partition
so that the next upgrade you can just rewrite your root partition without losing your personal data. Copy your
data to something safe, like another computer, or a usb hard drive.

=== Make Backups ===

I'm not responsible for you losing your data. You are yourself.

== Ok, get on with it already ==

Upgrading a live and running installation of MeeGo 1.0 to 1.1 can be accomplished by forcing zypper to reinstall all
packages and package groups from the 1.1 repo's instead of the 1.0 repo's.

In essence, one needs to delete all the 1.0 repo files, and add the 1.1 repo files:

# cd /etc/zypp/repo.d/
# rm -f *.repo

Then you need to get the new repo's and keys:

Find the .ks file for the image you want to install, for instance over here: [[http://repo.meego.com/MeeGo/releases/1.1/netbook/images/meego-netbook-ia32/meego-netbook-ia32-1.1.ks]]

Open the kickstart file, and look for the lines that add repo files to the kickstart. These are the new repo files you should import on your system: ('''Note: you need to add "repodata/" after the link found in the kickstart files''')

# zypper addrepo --type rpm-md --check --name adobe http://linuxdownload.adobe.com/linux/i386/repodata/ adobe
# zypper addrepo --type rpm-md --check --name=core http://repo.meego.com/MeeGo/releases/1.1/core/repos/ia32/packages/ core
# zypper addrepo --type rpm-md --check --name=netbook http://repo.meego.com/MeeGo/releases/1.1/netbook/repos/ia32/packages/ netbook
# zypper addrepo --type rpm-md --check --name=non-oss http://repo.meego.com/MeeGo/releases/1.1/non-oss/repos/ia32/packages/ non-oss
# zypper addrepo --type rpm-md --check --name=updates-core http://repo.meego.com/MeeGo/updates/1.1/core/repos/ia32/packages/ updates-core
# zypper addrepo --type rpm-md --check --name=updates-netbook http://repo.meego.com/MeeGo/updates/1.1/netbook/repos/ia32/packages/ updates-netbook
# zypper addrepo --type rpm-md --check --name=updates-non-oss http://repo.meego.com/MeeGo/updates/1.1/non-oss/repos/ia32/packages/ updates-non-oss

(add any repo that you think you might need here, such as handset or IVI).

This last step installs the GPG key as /etc/pki/rpm-gpg/RPM-GPG-KEY-meego01:

# zypper install --force meego-release

=== Then what? ===

Well, that was the easy part. Now zypper knows nothing but the new repository files and whatever we get
it to install, it will be from the new 1.1 repositories.

This is where the hard and dangerous part starts: We need to tell zypper to basically reinstall every
package, but from the new repositories. Just running a 'zypper update' will not work, as zypper refuses
to downgrade packages. Yes, you will be "downgrading" packages because version numbers between 1.0 and
1.1 are not consistent. Don't worry, you'll get newer software, not old stuff.

Start with clearing zypper's cache:

# zypper clean --all
# zypper refresh

That should make zypper forget all about the old repositories, and check and use the new key we just
installed. If everything is OK, you will not get warnings about keys here anymore.

=== Upgrading all your packages ===

Now we need to upgrade all the installed packages. There are several ways of doing this, but my favorite
method is to clean the system from old packages first that are not needed to do the upgrade:

# init 3

that's right, drop to the console. This way we can just remove a ton of packages, which makes the
critical part of the upgrade a bit easier. At least you won't be stuck in an Xorg session that froze up
leaving you unable to go to the console and forcing you to reboot a machine that was just reinstalling
glibc making all your programs unrunnable because ldconfig wasn't run (yeah, it's happened to me).

# zypper remove mutter
# zypper remove gtk+-2
# ...

Check the list properly and make sure you're not deleting vital libraries and packages. Although this
step is optional, pruning the update list is highly recommended.

Next we'll make a list of packages that need upgrading to the new repo versions, and install those one
by one:

# for p in `zypper pa| grep ^v |cut -d '|' -f3`; do zypper -n install --force $p l done

Repeat this until nothing happens anymore, possibly followed by:

# zypper refresh

Also, check the output of

# zypper pa

and look for packages that have a '''v''' at the start of the line:

# zypper pa| grep ^v
v | core | build | 2010.04.15-1.3 | noarch
v | core | evolution-data-server | 2.30.2~20100629-1.11 | i586
v | netbook | gcalctool | 5.25.91-1.88 | i586

those still need to be forced to update, or removed.

If zypper refuses to upgrade a package marked with '''v''' after a few tries, try removing the package, and reinstalling
it. Or see if the package is now under a new name and the newly named package needs to be installed instead.

=== Conclusion ===

While dangerous and a lot of work, it's possible with zypper to force reinstallation of all the packages against a new
repository one-by-one with --force. This is definitely not recommended for anyone who wants their system to be
stable and/or safe. Please use at your own risk.

Installing MeeGo on the HP mini 5102

2010-09-21T17:40:44Z

Auke:

The EFI BIOS in some hardware like HP Mini 5102 doesn't support booting our MeeGo isohybrid images. Until either isohybrid or the EFI BIOS is fixed there is a simple workaround that involves modifying the image with the isohyrbid tool.

On any linux machine that has the isohybrid tool, execute:

'''$ isohybrid -offset 64 <image-name.img>'''

This modifies the isohybrid image signature inside the image to a deeper offset and allows most EFI BIOSes to properly recognize the boot sectors as plain iso9660, and subsequently boot normally.

Booting isohybrids

2010-09-21T17:38:21Z

Auke: moved Booting isohybrids to Installing MeeGo on the HP mini 5102: Descriptive title

#REDIRECT [[Installing MeeGo on the HP mini 5102]]

Installing MeeGo on the HP mini 5102

2010-09-21T17:38:21Z

Auke: moved Booting isohybrids to Installing MeeGo on the HP mini 5102: Descriptive title

The EFI BIOS in some hardware like HP Mini 5102 doesn't support booting our MeeGo isohybrid images. Until the isohybrid/BIOS is fixed this is the workaround.

On the host machine,

'''$ isohybrid -offset 64 <image-name.img>'''

dd this image and then boot normally.

BOSS/Todo

2010-09-14T19:57:51Z

Auke: Redirected page to Release Infrastructure/BOSS/Todo

#REDIRECT [[Release Infrastructure/BOSS/Todo]]

BOSS/Presentation

2010-09-14T19:57:35Z

Auke: Redirected page to Release Infrastructure/BOSS/Presentation

#REDIRECT [[Release Infrastructure/BOSS/Presentation]]

BOSS/Design

2010-09-14T19:57:16Z

Auke: Redirected page to Release Infrastructure/BOSS/Design

#REDIRECT [[Release Infrastructure/BOSS/Design]]

BOSS/Code

2010-09-14T19:56:59Z

Auke: Redirected page to Release Infrastructure/BOSS/Code

#REDIRECT [[Release Infrastructure/BOSS/Code]]

BOSS/AIR

2010-09-14T19:56:41Z

Auke: Redirected page to Release Infrastructure/BOSS/AIR

#REDIRECT [[Release Infrastructure/BOSS/AIR]]

BOSS

2010-09-14T19:56:18Z

Auke: Redirected page to Release Infrastructure/BOSS

#REDIRECT [[Release Infrastructure/BOSS]]

SDK 1st Kickoff Meeting Agenda

2010-09-14T19:02:43Z

Auke: Redirected page to SDK/1st Kickoff Meeting Agenda

#REDIRECT [[SDK/1st Kickoff Meeting Agenda]]

MeeGo Core Test Suites Development Guidelines

2010-09-14T19:02:26Z

Auke: Redirected page to Quality/TestSuite/MCTS/MCTS Development Guideline

#REDIRECT [[Quality/TestSuite/MCTS/MCTS Development Guideline]]

Build Infrastructure

2010-09-11T18:58:04Z

Auke: /* MeeGo Build Infrastructure */ updated OBS versions

== MeeGo Build Infrastructure ==

The heart of the Build Infrastructure of MeeGo is the upstream project [http://wiki.opensuse.org/Portal:Build_Service openSUSE Build Service (OBS)]. It is an automated system used for building software packages, collaboration of developers, release management, maintenance, and much more. Moblin started using OBS in June 2008 and released Moblin 2.0 and Moblin 2.1, as well as other derivative releases. OBS has proven to be a very reliable infrastructure that is quickly evolving. It is rich with features for distribution building and maintenance. The Linux Foundation is dedicated to the further development of OBS and has a team, including two full-time OBS maintainers, contributing to its development and its use by MeeGo and the Ecosystem.

MeeGo currently uses version 2.0.x of OBS and will soon switch to version 2.1. To learn more about version 2.1 and the additional features in it, see the upstream project details: [http://wiki.opensuse.org/openSUSE:Build_Service_Roadmap roadmap].

=== Overview - What does it do? ===
Let's set out some basics about the OBS.

# It's a build system. You put source on it and say "use this repository" and it builds a minimal SDK-like chroot using the deb/rpms it finds in that repository
# It has packages - a package corresponds to a tarball and a spec/dsc
# It has projects - a project is like a directory with packages
# When a package is built it is "published" from the project where it was uploaded into a corresponding repository (which can be used to build other projects)
# The repositories can also be used by devices to download binary packages.

Choose one of the different tracks and guides for:

[[File:Splash-garage.png|right|300px]]
=== [[Build_Infrastructure/Packagers_Developers|Packagers/Developers]] ===
* [[Build_Infrastructure/Packagers_Developers#How_to_use_the_webinterface|How to use the web interface to view, manage and build your packages.]]
* [[Build_Infrastructure/Packagers_Developers#How_to_use_the_commandline_client|How to use the command line client for daily operations]]
* [[Build_Infrastructure/Packagers_Developers#MeeGo_Packaging_guidelines_and_Howto|MeeGo Packaging guidelines and howto]]
* [[Build_Infrastructure/Packagers_Developers#QA_Processes_around_the_OBS|QA Processes around the OBS]]
* [[Build_Infrastructure/Packagers_Developers#Multi-Architecture_and_Multi-Distribution_packaging|Multi-Architecture and Multi-Distribution packaging]]
* [[Build_Infrastructure/Packagers_Developers#Tips_.26_Tricks|Tips & Tricks]]
* [[Build_Infrastructure/Packagers_Developers#Troubleshooting|Troubleshooting]]
* [[Build_Infrastructure/Packagers_Developers#IRC_.2F_mailinglists_.2F_contact|irc / mailing lists / contact]]

[[File:Splash-community.png|right|300px]]
=== [[Build_Infrastructure/Community_Builder|Community Build System]] ===
* Also see the Packagers/Developer information above
* The community OBS is located in the maemo.org area until HW arrives at OSU
* QA Processes around the Community OBS
* [[Build_Infrastructure/Community_Builder|Details and status updates]]

[[File:peep_skate.png|right]]

=== [[Build_Infrastructure/Sysadmin_Distro|System Administrators/Distribution Managers/On-site]] ===
* How to set up a Build Service locally for testing
* Advanced setup topics
* [[Build_Infrastructure/Sysadmin_Distro#Seamless_cross-compilation.2C_cross-toolchain_integration|Seamless cross-compilation, cross-toolchain integration]]
* Whats the metadata (prjconf/prj), attributes, admin-tools for.
* Troubleshooting
* irc / mailinglists / contact

[[File:peep_netbook.png|right]]

=== [[Build_Infrastructure/Developing_OBS|Developing for the openSUSE Build Service]] ===
* Upstream URLs
* irc / mailing lists / contact
* Roadmap
* MeeGo feature wishlist

[[Category:Build Infrastructure]]

OSCON 2010

2010-07-13T17:46:48Z

Auke: /* Attending and Interested in a MeeGo Meetup */

'''[http://www.oscon.com OSCON 2010]: July 19 - 23 in Portland, Oregon'''

== MeeGo Activities ==
* Wednesday, 07/21/2010:
** '''[http://www.oscon.com/oscon2010/public/schedule/detail/15553 Imad Sousou's Keynote: Got MeeGo?]'''
** [http://www.oscon.com/oscon2010/public/schedule/detail/15455 Introduction to Developing MeeGo Applications and Taking Advantage of the Intel Atom Developer Program & Intel’s AppUp Center]
* Thursday, 07/22/2010:
** [http://www.oscon.com/oscon2010/public/schedule/detail/15453 MeeGo Technical Overview]
** [http://www.oscon.com/oscon2010/public/schedule/detail/14256 MeeGo - The Mobile Linux Platform]
* Exhibition Hall:
** Intel will have some MeeGo demos in the booth.

== Attending and Interested in a MeeGo Meetup ==
Note: Please include your arrival and departure dates
* [[User:Dawnfoster|Dawn Foster]] - In Portland all week (happy to organize something if people are interested).
* [[User:margie|Margie Foster]] - In Portland all week and eager to talk to the localization/translation folks.
* [[User:auke|Auke Kok]] - Will be attending sessions

Netbook Forum Triage

2010-06-17T18:25:51Z

Auke: /* Netbook Forum Posts Needing an Answer */

This page contains a list of netbook forum questions that have not received sufficient answers. Anyone with knowledge of the MeeGo netbook should feel free to answer these questions. After you have answered the question, please remove it from this list.

Questions should be considered answered when instructions have been provided or when a bug has been filed. If you file a bug or if there is already an existing bug filed, please include the bug number and a link that we can use to track it.

You might also find it helpful to point to the answers in the [http://wiki.meego.com/MeeGo_1.0_Netbook_FAQ Netbook FAQ] that we have been compiling.

== Netbook Forum Posts Needing an Answer ==
* http://forum.meego.com/showthread.php?t=260
* http://forum.meego.com/showthread.php?t=560
* http://forum.meego.com/showthread.php?t=549
* http://forum.meego.com/showthread.php?t=529
* http://forum.meego.com/showthread.php?p=3384#post3384
* http://forum.meego.com/showthread.php?t=552
* http://forum.meego.com/showthread.php?t=547
* http://forum.meego.com/showthread.php?t=523
* http://forum.meego.com/showthread.php?t=519
* http://forum.meego.com/showthread.php?t=572
* http://forum.meego.com/showthread.php?t=584
* http://forum.meego.com/showthread.php?t=586

== Other Questions ==

[http://forum.meego.com/forumdisplay.php?f=6&daysprune=-1&order=asc&sort=replycount&pp=20&page=1 Any posts with zero replies] might also be unanswered, but not yet added to the list. [http://forum.meego.com/forumdisplay.php?f=6&daysprune=-1&order=asc&sort=replycount&pp=20&page=1 Here is a link directly to a sorted netbook forum with posts with no replies at the top].

Netbook Forum Triage

2010-06-17T18:23:01Z

Auke: /* Netbook Forum Posts Needing an Answer */

This page contains a list of netbook forum questions that have not received sufficient answers. Anyone with knowledge of the MeeGo netbook should feel free to answer these questions. After you have answered the question, please remove it from this list.

Questions should be considered answered when instructions have been provided or when a bug has been filed. If you file a bug or if there is already an existing bug filed, please include the bug number and a link that we can use to track it.

You might also find it helpful to point to the answers in the [http://wiki.meego.com/MeeGo_1.0_Netbook_FAQ Netbook FAQ] that we have been compiling.

== Netbook Forum Posts Needing an Answer ==
* http://forum.meego.com/showthread.php?t=260
* http://forum.meego.com/showthread.php?t=478
* http://forum.meego.com/showthread.php?t=560
* http://forum.meego.com/showthread.php?t=549
* http://forum.meego.com/showthread.php?t=529
* http://forum.meego.com/showthread.php?p=3384#post3384
* http://forum.meego.com/showthread.php?t=552
* http://forum.meego.com/showthread.php?t=547
* http://forum.meego.com/showthread.php?t=523
* http://forum.meego.com/showthread.php?t=519
* http://forum.meego.com/showthread.php?t=572
* http://forum.meego.com/showthread.php?t=584
* http://forum.meego.com/showthread.php?t=586

== Other Questions ==

[http://forum.meego.com/forumdisplay.php?f=6&daysprune=-1&order=asc&sort=replycount&pp=20&page=1 Any posts with zero replies] might also be unanswered, but not yet added to the list. [http://forum.meego.com/forumdisplay.php?f=6&daysprune=-1&order=asc&sort=replycount&pp=20&page=1 Here is a link directly to a sorted netbook forum with posts with no replies at the top].

Netbook Forum Triage

2010-06-17T18:21:22Z

Auke: /* Netbook Forum Posts Needing an Answer */

This page contains a list of netbook forum questions that have not received sufficient answers. Anyone with knowledge of the MeeGo netbook should feel free to answer these questions. After you have answered the question, please remove it from this list.

Questions should be considered answered when instructions have been provided or when a bug has been filed. If you file a bug or if there is already an existing bug filed, please include the bug number and a link that we can use to track it.

You might also find it helpful to point to the answers in the [http://wiki.meego.com/MeeGo_1.0_Netbook_FAQ Netbook FAQ] that we have been compiling.

== Netbook Forum Posts Needing an Answer ==
* http://forum.meego.com/showthread.php?t=343
* http://forum.meego.com/showthread.php?t=260
* http://forum.meego.com/showthread.php?t=478
* http://forum.meego.com/showthread.php?t=560
* http://forum.meego.com/showthread.php?t=549
* http://forum.meego.com/showthread.php?t=529
* http://forum.meego.com/showthread.php?p=3384#post3384
* http://forum.meego.com/showthread.php?t=552
* http://forum.meego.com/showthread.php?t=547
* http://forum.meego.com/showthread.php?t=523
* http://forum.meego.com/showthread.php?t=519
* http://forum.meego.com/showthread.php?t=572
* http://forum.meego.com/showthread.php?t=584
* http://forum.meego.com/showthread.php?t=586

== Other Questions ==

[http://forum.meego.com/forumdisplay.php?f=6&daysprune=-1&order=asc&sort=replycount&pp=20&page=1 Any posts with zero replies] might also be unanswered, but not yet added to the list. [http://forum.meego.com/forumdisplay.php?f=6&daysprune=-1&order=asc&sort=replycount&pp=20&page=1 Here is a link directly to a sorted netbook forum with posts with no replies at the top].

Netbook Forum Triage

2010-06-17T18:20:36Z

Auke: /* Netbook Forum Posts Needing an Answer */

This page contains a list of netbook forum questions that have not received sufficient answers. Anyone with knowledge of the MeeGo netbook should feel free to answer these questions. After you have answered the question, please remove it from this list.

Questions should be considered answered when instructions have been provided or when a bug has been filed. If you file a bug or if there is already an existing bug filed, please include the bug number and a link that we can use to track it.

You might also find it helpful to point to the answers in the [http://wiki.meego.com/MeeGo_1.0_Netbook_FAQ Netbook FAQ] that we have been compiling.

== Netbook Forum Posts Needing an Answer ==
* http://forum.meego.com/showthread.php?t=277
* http://forum.meego.com/showthread.php?t=343
* http://forum.meego.com/showthread.php?t=260
* http://forum.meego.com/showthread.php?t=478
* http://forum.meego.com/showthread.php?t=560
* http://forum.meego.com/showthread.php?t=549
* http://forum.meego.com/showthread.php?t=529
* http://forum.meego.com/showthread.php?p=3384#post3384
* http://forum.meego.com/showthread.php?t=552
* http://forum.meego.com/showthread.php?t=547
* http://forum.meego.com/showthread.php?t=523
* http://forum.meego.com/showthread.php?t=519
* http://forum.meego.com/showthread.php?t=572
* http://forum.meego.com/showthread.php?t=584
* http://forum.meego.com/showthread.php?t=586

== Other Questions ==

[http://forum.meego.com/forumdisplay.php?f=6&daysprune=-1&order=asc&sort=replycount&pp=20&page=1 Any posts with zero replies] might also be unanswered, but not yet added to the list. [http://forum.meego.com/forumdisplay.php?f=6&daysprune=-1&order=asc&sort=replycount&pp=20&page=1 Here is a link directly to a sorted netbook forum with posts with no replies at the top].

Netbook Forum Triage

2010-06-17T18:18:56Z

Auke: /* Netbook Forum Posts Needing an Answer */

This page contains a list of netbook forum questions that have not received sufficient answers. Anyone with knowledge of the MeeGo netbook should feel free to answer these questions. After you have answered the question, please remove it from this list.

Questions should be considered answered when instructions have been provided or when a bug has been filed. If you file a bug or if there is already an existing bug filed, please include the bug number and a link that we can use to track it.

You might also find it helpful to point to the answers in the [http://wiki.meego.com/MeeGo_1.0_Netbook_FAQ Netbook FAQ] that we have been compiling.

== Netbook Forum Posts Needing an Answer ==
* http://forum.meego.com/showthread.php?t=379
* http://forum.meego.com/showthread.php?t=380
* http://forum.meego.com/showthread.php?t=277
* http://forum.meego.com/showthread.php?t=343
* http://forum.meego.com/showthread.php?t=260
* http://forum.meego.com/showthread.php?t=478
* http://forum.meego.com/showthread.php?t=560
* http://forum.meego.com/showthread.php?t=549
* http://forum.meego.com/showthread.php?t=529
* http://forum.meego.com/showthread.php?p=3384#post3384
* http://forum.meego.com/showthread.php?t=552
* http://forum.meego.com/showthread.php?t=547
* http://forum.meego.com/showthread.php?t=523
* http://forum.meego.com/showthread.php?t=519
* http://forum.meego.com/showthread.php?t=572
* http://forum.meego.com/showthread.php?t=584
* http://forum.meego.com/showthread.php?t=586

== Other Questions ==

[http://forum.meego.com/forumdisplay.php?f=6&daysprune=-1&order=asc&sort=replycount&pp=20&page=1 Any posts with zero replies] might also be unanswered, but not yet added to the list. [http://forum.meego.com/forumdisplay.php?f=6&daysprune=-1&order=asc&sort=replycount&pp=20&page=1 Here is a link directly to a sorted netbook forum with posts with no replies at the top].

Netbook Forum Triage

2010-06-17T18:17:08Z

Auke: /* Netbook Forum Posts Needing an Answer */

This page contains a list of netbook forum questions that have not received sufficient answers. Anyone with knowledge of the MeeGo netbook should feel free to answer these questions. After you have answered the question, please remove it from this list.

Questions should be considered answered when instructions have been provided or when a bug has been filed. If you file a bug or if there is already an existing bug filed, please include the bug number and a link that we can use to track it.

You might also find it helpful to point to the answers in the [http://wiki.meego.com/MeeGo_1.0_Netbook_FAQ Netbook FAQ] that we have been compiling.

== Netbook Forum Posts Needing an Answer ==
* http://forum.meego.com/showthread.php?t=290
* http://forum.meego.com/showthread.php?t=379
* http://forum.meego.com/showthread.php?t=380
* http://forum.meego.com/showthread.php?t=277
* http://forum.meego.com/showthread.php?t=343
* http://forum.meego.com/showthread.php?t=260
* http://forum.meego.com/showthread.php?t=478
* http://forum.meego.com/showthread.php?t=560
* http://forum.meego.com/showthread.php?t=549
* http://forum.meego.com/showthread.php?t=529
* http://forum.meego.com/showthread.php?p=3384#post3384
* http://forum.meego.com/showthread.php?t=552
* http://forum.meego.com/showthread.php?t=547
* http://forum.meego.com/showthread.php?t=523
* http://forum.meego.com/showthread.php?t=519
* http://forum.meego.com/showthread.php?t=572
* http://forum.meego.com/showthread.php?t=584
* http://forum.meego.com/showthread.php?t=586

== Other Questions ==

[http://forum.meego.com/forumdisplay.php?f=6&daysprune=-1&order=asc&sort=replycount&pp=20&page=1 Any posts with zero replies] might also be unanswered, but not yet added to the list. [http://forum.meego.com/forumdisplay.php?f=6&daysprune=-1&order=asc&sort=replycount&pp=20&page=1 Here is a link directly to a sorted netbook forum with posts with no replies at the top].

Image Creation

2010-04-05T21:47:52Z

Auke: s/moblin/meego/

= Overview =

This is the main Image Creator developer's guide. For a more simplistic, step-by-step document, go to: Image_Creation_For_Beginners.

MIC is composed of a series of tools to create images and provide an easy-to-use development environment for MeeGo. MIC is based primarily on Fedora LIVE CD tools and other related open-source projects.

With MIC tools, users can create different types of images for different purposes, including live images, raw images for KVM, VMDK images for Vmware, and NAND images for NAND boot on Moorestown platforms. Also, users can use MIC tools to manipulate images like transforming an image from a virtual machine to a live image, and providing a chroot environment based on an existing live image. With these great features, developers can do development work on a host virtual machine running MeeGo or a Meego chroot environment, and transfer the resulting new live image to a target device for final debug/verification.

This document discusses only features, usage guide, and known issues.

= Features =
MIC is primarily a command line utility, with a GUI that can be used on top of MIC (MIM).

MIC offers these major tools:
* mic-image-creator: to create many types of images.
* mic-image-convertor: to convert a raw image or vmdk image to a live image.
* mic-chroot: to provide a chroot MeeGo environment from a live image and translate that chroot file system into a live image.
* mic-image-writer: writes a MeeGo image to a USB disk. It is a safe alternative to dd.

The following support is provided as well:

* Supports mainstream Linux distros. MIC has been thoroughly tested on these three major distributions:
** Meego
** Fedora (Fedora 10 and above)
** Opensuse (> OpenSUSE 11.1)
** and Ubuntu > 9.04
* Supports various types of images: livecd, liveusb, loop, KVM, VMDK, NAND
* Supports image coversion among different types.
* Uses kickstart (.ks) files for image creation. Through this, users can specify which software repositories to use, which packages to install and basic system configuration directives. Please refer to http://fedoraproject.org/wiki/Anaconda/Kickstart for more information about kickstart configuration files.

= Usage =

== Requirements ==

To be able to use MIC, the following packages must be available on your system. (Most of the packages are installed by default, depending on the distribution.):

* yum
* rpm
* kpartx
* parted
* syslinux
* isomd5sum
* kvm
* zlib-devel(for compiling)
* python-devel(for installation)

You should load these modules as well, if not loaded automatically by the kernel:

* squashfs
* squashfs-tools
* dm_snapshot
* loop

Specific packages for Fedora:

* pykickstart
* device-mapper

Specific packages for Ubuntu 8.10:

* python-celementtree
* python-elementtree
* dmsetup

== Installation ==

'''From Binary Packages'''

We currently build MIC binary rpms for many popular Linux distributions. Please check here if your distribution is currently supported and available for download: http://repo.meego.com/tools/repo/.

'''From Stable Git Source Releases'''

You can get the latest stable release of MIC from the tag section in http://meego.gitorious.org/meego-developer-tools/image-creator. Click on the "Source tree" link on the top of the screen. There will be a list of tags on the right hand side.

You should follow the below steps to install it:

<pre>
git clone git://gitorious.org/meego-developer-tools/image-creator.git
cd image-creator
git checkout 0.17 #check Gitorious for the most recent tag
make
sudo make install
</pre>

'''From Development Git Tree'''

Note: MIC GIT tree has latest-and-greatest source, so stability is not guaranteed. If you run into errors, please use a 'Stable Release' instead before filing a bug.

You need to follow the below steps to git clone MIC:

<pre>
git clone git://gitorious.org/meego-developer-tools/image-creator.git
</pre>

Build and install:

<pre>
cd image-creator
make clean
make
sudo make install
</pre>

== Running mic-image-creator ==

Configuration of images is based on kickstart, the format used for unattended installation in Fedora and Redhat.

Super user privileges are needed. The tool is more or less self-documented, use the --help option to see options.
<pre>
sudo mic-image-creator --help
</pre>

=== Creating Supported Image Types ===

KickStart (.ks) configuration files are passed to MIC 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.

To obtain the official Meego .ks files, go here: TO-DO-LINK

'''Create Livecd Image'''

<pre>
sudo mic-image-creator --config=default.ks --format=livecd --cache=mycache
</pre>

This tells image-creator to use the kickstart file default.ks to obtain info about which packages to download and include in the image, and --cache is the directory on your local machine which will host a cache of these packages. The cache is very useful if you are remote to the server and reduces the amount of downloaded packages next time you create an image. Next time the command is run, this cache will simply be 'updated' if there are changes, rather than re-downloading from the repositories again.

The output of this command will be a file named meego-1.0-default-XX.iso created. This ISO image is a hybrid image and can be either written to a disk device or burned onto a cd.

To burn it onto a USB stick, just run the following command, assuming the USB stick is /dev/sdb in your system:

<pre>
sudo mic-image-writer meego-1.0-default-XX.iso
</pre>

'''Create Moorestown NAND Image'''

Please refer to the section dedicated to this topic below.

'''Create Liveusb Image'''

<pre>
sudo mic-image-creator --config=default.ks --format=liveusb --cache=mycache
</pre>

A file named meego-1.0-default-XX.usbimg will be created. To burn it onto a USB stick, run the following command, assuming the USB stick is /dev/sdb in your system:

<pre>
sudo mic-image-writer meego-1.0-default-XX.usbimg
</pre>

This image has a FAT file system and can be mounted easily on Windows and other OSes.

'''Create Liveusb Image Interactively'''

<pre>
sudo mic-image-creator --config=default.ks --format=liveusb --interactive --cache=mycache
</pre>

It directly creates a MeeGo live usb stick.

Liveusb image can be created in two different ways, interactive and non-interactive (default). When running MIC in a non-interactive mode, MIC creates a USB images file that can be copied directly into a USB stick. The non-interactive mode can be used for daily build or automated testing. The interactive mode will write the images onto a USB disk, it will detect if a USB stick is available and detects and verifies a partition is available. If two or more USB devices are present, you will be asked to select the target device. This way won't destroy existing content of USB stick unless it founds no appropriate partition, end user should use it to create live USB.

'''Create Loop Image'''

This is the simplest image format available. Such images can be loop mounted and chrooted into, for example, to build applications or for debugging purposes.

<pre>
sudo mic-image-creator --config=default.ks --format=loop --cache=mycache
</pre>

A file named meego-1.0-default-XX.img is created. You can use below to mount it and chroot into it.

<pre>
sudo mount -o loop meego-1.0-default-XX.img /mnt
sudo chroot /mnt su -
</pre>

'''Create KVM Image'''

Can be used with QEMU or other VMM applications to launch MeeGo as a virtualized instance.

<pre>
sudo mic-image-creator --config=default.ks --format=raw --cache=mycache
</pre>

A file named meego-1.0-default-XX folder with a meego-1.0-default-XX-sda.raw image is created. For optimal results, use this feature in a machine with VT support and enable it in the BIOS.

If you use Fedora or openSUSE, run the following command to launch the image into MeeGo KVM virtual machine:

<pre>
sudo qemu-kvm -m 512 -boot c -hda meego-1.0-default-XX-sda.raw -std-vga
</pre>

If you use Ubuntu, run the following command launch image:

<pre>
sudo kvm -m 512 -boot c -hda meego-1.0-default-XX-sda.raw
</pre>

'''Create VMDK Image'''

VMDK images can be loaded into Vmware or Vmware player. MIC also generates a VMX file that has image configuration and can be used to launch the image in Vmware by just clicking the file. If you have vmplayer, it should open automatically.

<pre>
sudo mic-image-creator --config=default.ks --format=vmdk --cache=mycache
</pre>

A file named meego-1.0-default-XX folder with both meego-1.0-default-XX-sda.vmdk image and meego-1.0-default-XX-sda.vmx is created. Just run vmware or vmware player, and select the generated vmx file.

=== KickStart Files (configuration files used for image creation) ===

KickStart (.ks) configuration files are passed to MIC 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. MIC also adds some specific directives and options. More explained below.

====Official Meego .ks files====

The official Meego .ks files are here: TO-DO-LINK

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.
====Modifying 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.

The Meego .ks files reside here: TO-DO-LINK

You can also find in-depth .ks option information here: http://fedoraproject.org/wiki/Anaconda/Kickstart#Chapter_2._Kickstart_Options

'''''Partition, Setup and Bootloader options'''''

''E.g.''

<pre>
lang en_US.UTF-8
keyboard us
timezone --utc America/New_York
auth --useshadow --enablemd5
part / --size 1500 --ondisk sda --fstype=ext3
rootpw meego
xconfig --startxonboot
bootloader --timeout=0 --append="quiet"
desktop --autologinuser=meego --defaultdesktop=xfce
user --name meego --groups audio,video --password meego
</pre>

These are mostly self-explanatory and set up important things such as partition size, filesystem type, kernel paramters, etc. You can change these depending on what your needs are.

'''''Repos'''''

This is where you can specify the yum repositories that you want MIC to search and pull your packages from to make up your image. You can add official Meego repos, other remote repos, or your own local repos on your dev machine.

''E.g.''

<pre>
# This is a comment

# My first repo
repo --name=trunk --baseurl=http://mytrunk.myrepo.com

# My second repo
#repo --name=<repo-name-2> --baseurl=< url | local-repo-dir >
</pre>

'''NOTE:''' --name of the repo can be any unique alphanumeric name you give your repo, it can be anything. Just make sure you don't use the same name twice for any of the listed repos, remember they have to be unique.

To create a repo you can point to on your local developer machine, you can run the following command:

<pre>
createrepo -d <local-dir>
</pre>

Where 'local-dir' is a local directory on your machine that contains the rpms you want include in your local directory.

'''''Adding Packages and Package Groups'''''

''E.g.''

<pre>
%packages

# Example adding pkg groups

@Core
@X for Netbooks
@Base
@Development Tools
@<my-PkgGroup1>
@<my-PkgGroup2>

# Example adding individual pkgs

kernel-netbook
xorg-x11-server-Xorg-setuid
carrick
xorg-x11-drv-evtouch
<my-pkg-1>
<my-pkg-2>
%end

</pre>

This specifies exactly what packages will be included in your image. Package groups can be specified with a "@" preceding it, as you can see from the examples above. Package groups are defined in the 'repodata' section of a repo, under a 'comps*.xml' file. Defined therein are package group names, and what packages are included in each package group. The Meego package groups are standard, and cannot be changed. You can, however, define your own package groups in your own non-Meego repos if you are using those.

Please see here for more info on defining package groups in repositories: TO-DO-LINK

You can also add individual package names to be included in the image as you can see from the second part in the above example.

'''''Important Note about how MIC picks a package when difference version are available'''''

A common problem is that, let's say, a packageA has more than one version residing in a repo(s) that your .ks is pointing to.

How will the MIC know which one to pick?

''E.g''

There exists in the repo(s) these different versions of PackageA:

PackageA-1.0

PackageA-2.0

PackageA-3.0

MIC will pick the PackageA with the highest version number (PackageA-3.0 in this case).

There is one way to get around that, and that is to set the 'Epoch' version within a package .spec file.

<pre>
Example (works in both .spec and .yaml file)

Name: <name>
Summary: <summary>
Epoch: 1
Version: <version>

</pre>

MIC will first look to compare the 'Epoch' version of the packages. All Meego official packages do not include an 'Epoch' version, so if you set the 'Epoch' number within your .spec file to any positive integer, no matter if your package version is smaller, MIC will choose your package.

So back to our example.

''E.g''

PackageA-1.0 (Epoch not set)

PackageA-2.0 (Epoch = 1)

PackageA-3.0 (Epoch not set)

MIC will choose PackageA-2.0 in this case. And it follow that:

''E.g''

PackageA-1.0 (Epoch=100)

PackageA-2.0 (Epoch = 1)

PackageA-3.0 (Epoch not set)

MIC will choose PackageA-1.0.

Remember that Meego packages do not have 'Epoch' set by default, so chances are that if you set 'Epoch' in your own package to any positive integer, it will be the one MIC chooses to pull down and include in an image.

'''''Removing Packages'''''

If you would like to make sure that a pkg is _not_ included, you can specify that with a '-' preceding the package name.

''E.g.''
<pre>
%packages

# Example pkg groups

@Core

# Example adding individual pkgs

kernel-netbook

# Example removing individual pkgs

-carrick
-package-xyz

%end
</pre>

with the above example, packages 'carrick' and 'package-xyz' will _not_ be included in the image.

'''Note:''' all packages that depend on the package you want to remove should also be removed, or else MIC will ignore your request to remove that package from an image. E.g. if 'carrick' depends on 'package-xyz', and you specified only to remove 'package-xyz', and keep carrick, MIC will ignore the request to remove package-xyz (since carrick depends on it), and it includes both of these pgks in the image.

'''''Post scripts'''''

You can also specify post-scripts to be run after the image is installed.

''E.g.''
<pre>
%post

# Example - saving some space
rm -f /boot/initrd*
rm -f /core*

# Example - Install working xorg.conf
if [ -f /usr/share/my.conf ]; then
cp /usr/share/my.conf /etc/X11/xorg.conf
fi

# Example - Tell alsa the correct audio card to use for your platform
echo -e "options snd-hda-intel index=0\noptions snd-timbi2s index=1" > /etc/modp
robe.d/alsa.conf

%end
</pre>

====Proxy settings for the repos in .ks====

An option you might find useful if you're behind a firewall is the --proxy flag for the "repo" definition. You can specify it in the .ks as follows:

repo --name=meego --baseurl=http://repo.meego.com/trunk/repo/ia32/os/ --proxy=http://proxyhost:proxyport/ --proxyuser=proxyusername
--proxypaswd=proxyuserpassword

If you are behind a firewall, you don't need to set proxyuser and proxypasswd, like:

repo --name=meego --baseurl=http://repo.meego.com/trunk/repo/ia32/os/ --proxy=http://proxyhost:proxyport

'''Note:''' You can also insert this in your sudoers config:

<pre>
$ sudo visudo

Add: Defaults env_keep += " no_proxy http_proxy ........."
</pre>
so sudo will adhere to the no_proxy and proxy settings.

=== MIC Configuration file ===

~/.mic2_site.conf is a configuration file that can make your life easier by specifying proxy settings, cache directories, and other variables that you normally would have to re-type in your command-line.

Below is an example you can cut-and-paste, and reuse for your needs:

<pre>
[main]
cachedir=/home/user1/mycache
tmpdir=/home/user1/mystorage/tmp
outdir=/home/user1/mystorage
proxy=http://my.proxy.com:911/
no_proxy=localhost,127.0.0.0/8,.mysite.com,172.16.0.0/16
</pre>

''cachedir'' = directory where the cached repo(s) will reside. With this variable set, you do not need to pass the --cache flag in the command-line.

''tmpdir'' = temporary directory used by mic when creating images. With this variable set, you do not need to pass the --tmpdir flag in the command-line.

''outdir'' = where your images will reside once they are created. With this variable set, you do not need to pass the --outdir flag in the command-line.

''proxy'' = specify your proxy if you're behind a behind a firewall.

''no_proxy'' = specify what domains should not sure the proxy setting.

'''Note:''' When specifying proxy and no_proxy, you do not need to use the --proxy flag in your .ks files when referring to repos.

== Running mic-image-writer ==

mic-image-writer writes a Meego image to a USB disk. It is a safe alternative to dd. dd is really a very dangerous tool.

mic-image-writer can run in both console mode and GUI mode. It can decide which mode to run, according to current system environment. You can also use a given option to force it to run in some other mode. Run 'mic-image-writer --help' to get usage information:

<pre>
Usage: mic-image-writer [options] [image file]

Options:
-h, --help Show this help message and exit
-c, --console Run in console mode
-g, --gui Run in GUI mod
</pre>
Here is a run example in console mode:

<pre>
$ sudo mic-image-writer meego-xxx.img
Available usb disk:
[1] /dev/sdc: SanDisk USB Flash Drive
[2] /dev/sdb: SanDisk U3 Cruzer Micro
Please choice [1..2] ? 2
Source: /myhome/meego-xxx.img
Target: /dev/sdb
Image size: 559 MB
Estimated time: 55 seconds
Elapsed time: 64, progress: 100% 8944+0 records in
8944+0 records out
586153984 bytes (586 MB) copied, 63.0486 s, 9.3 MB/s
</pre>

mic-image-writer can estimate how long it will take to write the given image to your USB disk and reports current writing progress. It automatically unmounts your USB disk, if it is mounted. If your USB can't be unmounted, it will terminate.

If you love UI mode, you can run it in X enviroment. The command with the added -g flag:

<pre>
sudo mic-image-writer -g meego-xxx.img
</pre>

Image name is optional.

== Running mic-image-convertor ==

It's very easy to use:

<pre>
sudo mic-image-convertor --source-image=InputImage --target-format=Targegformat

sudo mic-image-convertor -I InputImage -T Targegformat
</pre>

For example, to translate a KVM raw image to livecd image, just type:

<pre>
sudo mic-image-convertor --source-image=meego-core-200902200545/meego-core-200902200545-sda.raw --target-format=livecd
</pre>

A new livecd image of meego-converted-from-raw-200902201804.iso is generated. The tool can detect the type of input image, either raw or vmdk.

This tool is very useful. For example, the developer can launch a virtual machine running MeeGo v2 and make whatever changes on the virtual system like yum install/remove a package, scp a source tarball to VM and build and try, and etc. Then with a simple "sync" or shutdown of VM, the VM image now contains his changes. With this tool, the VM image can be transformed to a live image and burned to a USB flash disk. Now developers can have final verifications in a target device, with changes in the live system.

== Running mic-chroot ==

There are two major usage models for mic-chroot for developers.

'''chroot directly into the image to use it as a development environment, then optionally create a new image based off of your changes'''
<pre>
sudo mic-chroot -c livecd meego-core-200903131337.iso
</pre>

The above command would present a chroot, using the livecd image, to developers with some bind mounts like /proc /sys /dev/pts and /parentroot. With those bind mounts, developers now can easily exchange files in chroot env with host /parentroot, and conduct yum install, yum remove and any other network related operations. After done and typing "exit", a new live ISO image is created from the chroot env with the changes developers made.

'''Unpack and modify the image's filesystem (which you can save), and create a new image based off of your changes'''

Sometimes developers want to keep the chroot env so that they can do multiple changes in that root file system at different times. So they want to execute following:

<pre>
sudo mic-chroot -s my-chroot-fs --unpack-only meego-core-200903131337.iso --bind-mounts=/proc:/proc;/:/parentroot;/sys:/sys;/dev/pts:/dev/pts
</pre>

The above creates a folder 'my-chroot-fs' in the current directory, using the chroot env from the livecd image. Of course if developers forget add the --bind-mounts options, they must manually do some bind mounts themselves like for /proc /sys /dev/pts to use network and run many commands. Don't forget copying /etc/reslov.conf into my-chroot-fs to use DNS. Now at any time developers think is time to create an image from the chroot env, just execute following to create a livecd image

<pre>
sudo mic-chroot -c livecd --convert-only my-chroot-fs/
</pre>

== Enabling Autoinstallation ==

You need to copy a kickstart file into /root/mic2-ks.cfg which is used for
automated installation of the image. To activate autoinstall mode, boot with autoinst on the command line
or add --menus=autoinst to the bootloader directive in the kickstart file you use to
create the image.

= Known issues =

* MIC is not compatible with Ubuntu 8.04 (Yum package compatibility)

= Troubleshooting =
===libgcc related issues===
<pre>
libgcc_s.so.1 must be installed for pthread_cancel to work"

"Error: failed to create image : '/sbin/mksquashfs /var/tmp/imgcreate-FKCSsk/iso-u8xCPh/LiveOS/osmin /var/tmp/imgcreate-FKCSsk/iso-u8xCPh/LiveOS/osmin.img' exited with error (-6)
</pre>

This error occurs when MIC is unable to find the proper version of libgcc. This usually happens on x84_64 systems - MIC is looking for the 32 bit version of libgcc, but only the 64 bit version is installed. Installing the 32 bit version of libgcc should resolve this.

===General squashfs issues===
<pre>
"Error: failed to create image : '/sbin/mksquashfs /var/tmp/imgcreate-FKCSsk/iso-u8xCPh/LiveOS/osmin /var/tmp/imgcreate-FKCSsk/iso-u8xCPh/LiveOS/osmin.img' exited with error (-6)
</pre>

This error can also be an issue with the syslinux package. Try updating to the latest version for your distro.

===device-mapper issues===
<pre>
unable to remove open device
</pre>

This is a race condition with device-mapper in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=506644. Usually rerunning the MIC command will resolve this.

Community Office

2010-03-24T21:04:54Z

Auke: /* Contributors */

The role of MeeGo working groups are explained at http://meego.com/about/governance

This is a request to the Technical Steering Group to approve the creation of a Community working group. There is no procedure defined but we can can improvise with some common sense.

=== Announcement ===

There is an upcoming meeting on http://meego.com/community/irc-channel as well. The scheduled time is Wednesday, March 24th 2010 at 20:00 UTC. Please note that the channel chosen for this meeting is #meego-meeting. An agenda for the meeting is [http://meego.com/community/events/2010/meego-technical-steering-group-meeting here]. This working group proposal will be considered by the Technical Steering Group during the meeting.

Current and older meetings can be found [http://wiki.meego.com/Community_website_meeting_2010_2_24 here].

=== How to contribute ===

To discuss and plan the MeeGo community, subscribe to the MeeGo community mailing list: http://lists.meego.com/listinfo/meego-community. You can also subscribe from your account page on meego.com.

=== Mission ===

The Community working group defines the strategy for collaboration tools and processes within the MeeGo project, and observes its implementation.

=== Areas ===

The main areas within the scope of the working group are (in no particular order):

* '''Maemo/Moblin transition''': bringing the best from maemo.org and moblin.org to meego.com (urgent now, until the mission here is fulfilled).
* '''Web administration''': server maintenance, team of admins and other users with special permissions.
* '''Platform infrastructure''': selection and administration of online tools for collaborative software development: build infrastructure, code repositories, bugzilla, localization...
** [[Forum]]
* '''Community infrastructure''': selection and administration of online tools for non-technical community collaboration: planet, wiki, [http://wiki.meego.com/Forum_/_Talk forum], brainstorm, downloads, [http://wiki.meego.com/metrics metrics and reporting] ...
* '''Community marketing''': identity, merchandising, events, evangelism...

=== Contributors ===

MeeGo members interested in taking an active role in this working group. Please detail your interests and what you can contribute to the group:

* [http://meego.com/users/qgil Quim Gil] - regular Nokia contact with the Maemo community, and maemo.org contributor myself. One of the people responsible of the maemo.org transition from Nokia's hands to a fully community-driven site. Submitter of this proposal and happy to take an active role. Full disclosure: Nokia pays me to take care of open source / community matters in maemo.org and now meego.com. I can put time here.

* [http://meego.com/users/Jeremiah Jeremiah C. Foster] - maemo.org's current debmaster. Recently I've taken on a role in the [http://genivi.org/ GENIVI Alliance] as Core Integration team lead. I would like to participate actively in helping develop MeeGO, keeping it open with a thriving community.

* [http://meego.com/users/xfade Niels Breet] - maemo.org webmaster and long time maemo.org community member. Liberated by Nokia to work on community infra and community repository infrastructure for maemo.org. Interested in doing the same for meego.com.

* [http://meego.com/users/lbt David Greaves/lbt] - Mer build guy and maemo.org member. Introduced OBS to Maemo and working on Nokia build infrastructure.

* [http://meego.com/users/Jaffa Andrew Flegg/Jaffa] - Long term Maemo community member and developer and twice Maemo Community Council member. Interested in bringing the best of the Maemo and Moblin communities together in the nascent MeeGo community and ensuring that cross-community facilitation happens.

* [http://meego.com/users/ksanjeet Sanjeet Kumar] Willing to contribute as server admin.

* [http://meego.com/users/Elliot Elliot Smith/townxelliot] - meego.com websites techie, worked on moblin.org Moblin SDK materials, contributor to Moblin SDK tools. Intel pays me. Can get time to rework content from moblin.org for this site.

* [http://meego.com/users/bergie Henri Bergius] - contributor to the maemo.org community infrastructure, behind services like Brainstorm, Karma and Social News. Working on maemo.org projects through Nemein, and interested in doing the same for meego.com

* [http://meego.com/users/amby Gabor Ambrozy/amby] - recently joined maemo.org community member; would like to contribute to transition, community infrastructure and community marketing. Can bring virtual project mgmt and organization transition experience; IT system integration, sw development and learning projects practices. And a lot of end-user enthusiasm ;)

* [http://meego.com/users/lm Lucas Maneos/lm] - member of the maemo.org bugsquad, happy to contribute in any way to the bugzilla transition.

* [http://meego.com/users/tekojo Tero Kojo] - One of the Nokia people involved in the Maemo community and maemo.org. My area has been working with the liberated community members and the infrastructure for maemo.org. Interested in making sure that MeeGo.com provides the necessary tools and services to both developers and active users. I work in Nokia Maemo developer platform team as project manager responsible for communities.

* [http://meego.com/users/margie Margie Foster] - I am the localization project manager for Moblin and also work on the MeeGo website. I am an Intel employee. I am really looking forward to helping create and maintain a vibrant MeeGo localization community using Transifex.
[[Category:Community]]

* [http://meego.com/users/revdkathy Kathy Smith] - maemo.org community member, non-technical end user. Special interest in community building, project management and channeling the input of end users.

* [http://meego.com/users/w00t Robin Burchell] - maemo fan as of n900, wide variety of technical skills from C++ (yes, including Qt)/PHP to server administration. happy to help the community, however I can.

* [http://meego.com/users/qole Qole] - Two-term Maemo Community Council member, enthusiastic hacker and Linux user, primary maintainer of the Easy Debian project, and very active in the Maemo forums. Interested in helping out where I can to make MeeGo have the kind of powerhouse community that has made Maemo so special.

* [http://meego.com/users/vdvsx VDVsx] - Maemo Community Council member and developer, willing to keep helping everybody inside this new community from developers to end users.

* [http://meego.com/users/texrat Randall Arnold/Texrat] - Maemo Community Council member, former Nokia QA engineer for Maemo devices, originator of maemo.org community outreach efforts, maemo.org forum moderator and best practices blogger. Ready to translate lessons learned from maemo.org to whatever develops here!

* [http://meego.com/users/generalantilles Ryan Abel] - Long-term Maemo Community member and former two-term Maemo Community Council member. Interested in leveraging the strengths of the large maemo.org community into the growing MeeGo community. Also interested in helping to develop strong web infrastructure and tooling.

* [http://meego.com/users/mshaver Mike Shaver/mshaver] - Moblin.org webmaster and developer behind the current meego.com site. I am an Intel employee. Would love to see this list of people contributing and directing what we build and support for the meego.com community.

* [http://meego.com/users/sulamita Sulamita Garcia] - MeeGo Technical Marketing Engineer. I work at Open Source Technology Center at Intel and I've involved with Moblin from the beginning. I produce documentation, training and support for costumers and developers.

* [http://meego.com/users/sjgadsby Stephen Gadsby/sjgadsby] - Maemo community member, poster of weekly Bugzilla activity reports, and forum moderator. Interest in community building and communication channels between users and developers.

* [http://meego.com/users/reggie Reggie Suplido] - [http://wiki.maemo.org/Maemo.org_team#Talkmaster maemo.org Talkmaster], primary administrator of [http://talk.maemo.org/ talk.maemo.org]. Founded [http://www.internettablettalk.com/ Internet Tablet Talk] where it's forum later on became talk.maemo.org. Can help run the forums section of MeeGo, or perform integration with talk.maemo.org if the need arises.

* [http://meego.com/users/timeless timeless] - regular Nokia Browser contact with the Maemo community, contributor to Maemo, Mer, Mozilla.

* [http://meego.com/users/danielwilms danielwilms] - working in Nokia on the maemo.org community developer support. Taking over community tasks, working on documentation and support. Interested in helping out, by working on MeeGo.com services, support developers and users, and documentation.

* [http://meego.com/users/th0br0 Andreas Osowski/th0br0] - Interested in helping with infrastructure and community marketing. Currently working in Fedora as Ambassador and packager. ~4 years of C++ experience (with some Qt), RoR and Java experience

* [http://meego.com/users/niqt Nicola De Filippo] - maemo Qt4 contributor; technical skills: Qt (from 1997), C++, Javascript, Php, Java, Python

* [http://meego.com/users/timsamoff Tim Samoff / timsamoff] - Designer (graphic, UI, interaction, web), long-time Maemo Community member (two-term Maemo Community Council Member), and forever open source advocate

* [http://meego.com/users/gadgety Gadgety] - maemo.org community member, business end user; I'd like to contribute to making the MeeGo community an easy place to join for newbies, fans, enthusiasts and creating a community where everyone feels welcome to contribute regardless of technical skill level

* [http://meego.com/users/mikael Mikael Söderberg/mksoderberg] - I am Chair of the [http://genivi.org/ GENIVI Alliance] Reference System Work Group. I would like to contribute by assisting in development of the MeeGo Platform Infrastructure.

* [http://meego.com/users/dneary Dave Neary/dneary] - maemo.org community developer support with a specific documentation slant. Experienced community development consultant. I want to make sure that MeeGo makes the right strategic decisions related to transparency and participation guidelines at the project inception to avoid major issues later.

* [http://meego.com/users/dawnfoster Dawn Foster/dawnfoster] - Intel's MeeGo community manager. I'm interested in helping out on a variety of community activities. I have past experience managing open source, developer and other types of online communities.

* [http://meego.com/users/solt Marcin Sołtysiak/solt] - Open to help with community. Aligned with l10n efforts I would see a place for language/country sub sections. Also, have experience with Midgard. I could help with geek-to-human relations :)

* [http://meego.com/users/vilvo Ville Ilvonen/vilvo] - Nokia's Maemo Test Tools - responsible for advocating and coordinating development of test tools and test automation inside Maemo. Looking forward to continue with MeeGo. I can help with tools contribution and evangelism within this working group. Nokia pays me to spend time with this.

* [http://meego.com/users/dannybe Danny Bennett] - maemo.org community member, Nokia application architect for maemo sw. I'm interested in architecture and the technology components that make up the MeeGo distro. This is where and how I can contribute.

* [http://meego.com/users/auke Auke Kok] - Intel MeeGo developer, working on releases, fastboot, l10n project.

Language specific working groups

2010-03-04T18:43:10Z

Auke:

== Language Specific Working Groups ==

If your language is not mentioned here, add a section for it, copy a table and list your name as shown.

----
== Brazil::Brazilian Portuguese ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|Og Maciel
|OgMaciel
|[[http://www.ogmaciel.com/?page_id=428]]
|-
|Frederico Schardong
|
|
|-
|Sergio Correia
|sergio
|
|}

== France::French ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|Farid Ziani
|
|
|}

== Hindi ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|GTalk
|Bio
|-
|Kiran Vaka
|kiran.vaka
|[[http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=kiran+vaka]]
|}

== Israel::Hebrew ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|Sivan Greenberg
|sivang
|[[http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=sivan+greenberg]]
|}

== Marathi ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|GTalk
|Bio
|-
|Amit Bapat
|amitbapat
|[[http://www.linkedin.com/in/amitbapat]]
|}

== The Netherlands::Dutch ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|Auke Kok
|auke
|(Intel MeeGo developer)
|}

== Poland::Polish ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|Michał Sawicz
|Saviq
|[[http://www.google.com/search?q=saviq+michał+sawicz]]
|}

== Chinese (Taiwan) ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|Cheng-Chia Tseng
|zerng07
|[[http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=cheng-chia+tseng]]
|}

== Simplified Chinese ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|Ryan Lee
|
|[[http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=ryan+lee]]
|}

== Slovenian ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|Jure Repinc
|JLP
|[[http://www.google.com/search?ie=UTF-8&q=jure+repinc]]
|}

== Telugu ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|Skype
|Bio
|-
|Kiran Vaka
|kiran.waka
|[[http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=kiran+vaka]]
|}

== Walloon ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|GTalk
|Bio/Website
|-
|Djan Cayron
|jean "dot" cayron
|[[http://wa.wikipedia.org/wiki/Jean_Cayron]] [[http://walotux.walon.org/]]
|}

== Russian ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|Jabber
|Bio
|-
|Serg Vergun
|shad0w@jabber.spbu.ru
|
|}

Who's who

2010-02-19T19:41:16Z

Auke: /* MeeGo developers */

== Technical Steering Group ==
''Members of the [http://meego.com/about/governance TSG]''

* [http://meego.com/users/imad Imad Sousou/imad] - Benevolent dictator
* [http://meego.com/users/valhalla Valtteri Halla] - Benevolent dictator
* ???

== Maemo community stakeholders ==
'' Official representatives of the Maemo community''

* [http://meego.com/users/qgil Quim Gil/qgil] - Nokia's Maemo Community Manager
* [http://meego.com/users/tekojo Tero Kojo/tekojo] - Nokia's Maemo Technical Project Manager
* [http://meego.com/users/xfade Niels Breet/X-Fade] - maemo.org webmaster
* Dave Neary/dneary - maemo.org docmaster
* [http://meego.com/users/andre André Klapper/andre__] - maemo.org bugmaster
* [http://meego.com/users/jeremiah Jeremiah Foster/jeremiah] - maemo.org debmaster
* [http://meego.com/users/reggie Reggie Suplido] - maemo.org talkmaster
* [http://meego.com/users/stskeeps Carsten Munk/Stskeeps] - maemo.org distmaster & Mer project lead
* [http://meego.com/users/bergie Henri Bergius/bergie] - maemo.org web/Midgard developer
* [http://meego.com/users/vdvsx Valerio Valerio/VDVsx] - Maemo Community Council chair
* [http://meego.com/users/texrat Randall Arnold/Texrat] - Maemo Community Council member
* [http://meego.com/users/qole Alan Bruce/qole] - Maemo Community Council member
* [http://meego.com/users/penguinbait Matthew Lewis/penguinbait] - Maemo Community Council member
* Graham Cobb - Maemo Commnunity Council member

== Moblin community stakeholders ==
''Representatives of the Moblin community''

* [http://meego.com/users/dirkhh Dirk Hohndel/dirkhh] - Chief Linux and open source technologist at Intel
* [http://meego.com/users/townxelliot Elliot Smith/townxelliot] - Moblin.org & meego.com website techy
* [http://meego.com/users/mshaver Michael Shaver/mshaver] - Moblin.org webmaster & meego.com website developer
* [http://meego.com/users/margie Margie Foster/mlfoster] - Localization project manager for Moblin & meego.com website developer

== MeeGo developers ==
'' People paid to contribute to MeeGo and/or have commit rights''

* [http://meego.com/users/nashif Anas Nashif/anaZ] - Distribution developer.
* [http://meego.com/users/auke Auke Kok/auke] - Release developer, fast boot.
* [http://meego.com/users/hbons Hylke Bons/hbons] - User Experience Designer
* [http://meego.com/users/jku Jussi Kukkonen/jku] - Developer
* [http://meego.com/users/nmcgovern Neil McGovern/nmcgovern] - Developer
* [http://meego.com/users/pohly Patrick Ohly/pohly] - Developer
* [http://meego.com/users/quang Quang Pham/quang] - Developer

== MeeGo community ==
''Anyone not in the above sections'' (Please keep this list alphabetically-ordered, as it will make finding people easier.)

* [http://meego.com/users/ab Alexander Bokovoy/ab] - Senior Architect, Media applications, Nokia, Samba Team member
* [http://meego.com/users/aboaboit Andrea Borgia/aboaboit] - Maemo community member
* [http://meego.com/users/andrewfblack Andrew F Black/AndrewFBlack] - Community Member / Theme Designer / talk.maemo.org Moderator and Theme Designer.
* [http://meego.com/users/jaffa Andrew Flegg/Jaffa] - Long term gadget freak & Maemo community member
* [http://meego.com/users/lbt David Greaves/lbt] - Mer OBS build guy
* [http://meego.com/users/glezos Dimitris Glezos/glezos] - Localization Engineer ([http://www.transifex.net/ Transifex])
* [http://borasky-research.net M. Edward (Ed) Borasky] - Linux capacity planning / audio / openSUSE / Twitter geek
* [http://meego.com/users/debernardis Ernesto de Bernardis/debernardis] - Maemo community member, mobile device tinkerer
* [http://meego.com/users/fabo Fathi Boudra / fabo] - Debian developer, Maemo community member, software engineer
* [http://meego.com/users/slaine Glen Gray / slaine] - Moblin community member, software engineer
* [http://meego.com/users/dl9pf Jan-Simon Möller / dl9pf ] - Build service developer, Linux Foundation
* [http://meego.com/users/zerojay Jason Carter/zerojay] - Long term Maemo community member
* [http://meego.com/users/jak Julian Andres Klode / jak] - Debian developer, Ubuntu member
* [http://meego.com/users/lpotter Lorn Potter/lpotter/ljp] - QDF, Mobility, Nokia,
* [http://meego.com/users/martinmohring Martin Mohring / ScriptRipper] - Buildservice developer, Linux Foundation
* [http://meego.com/users/niqt Nicola De FIlippo/niqt] - Qt4 Maemo Contributor, Maemo community member, software engineer
* [http://meego.com/users/rhertzog Raphaël Hertzog / buxy ] - Debian developer, [http://www.freexian.com self-employed] as free software consultant/developer.
* [http://meego.com/users/w00t Robin Burchell/w00t] - Developer of random things, gadget enthusiast, Maemo community member
* [http://meego.com/users/generalantilles Ryan Abel/GeneralAntilles] - Long term Maemo community member
* [http://meego.com/users/slauwers Sebastian Lauwers/crashanddie] - Community member, talk.maemo.org moderator / ActivIdentity Professional Services Technical Consultant
* [http://meego.com/users/timeless timeless/timeless] - Mozilla contributor, Nokia employee.
* [http://meego.com/users/timsamoff Tim Samoff / timsamoff] - Designer (graphic, UI, interaction, web), long-time Maemo Community member (two-term Maemo Community Council Member), and forever open source advocate
* [http://meego.com/users/corsac Yves-Alexis Perez / Corsac] - Debian developer, Maemo community member, security engineer
__NOTOC__ 

[[Category:Community]]

Who's who

2010-02-18T23:45:31Z

Auke: /* MeeGo developers */

== Technical Steering Group ==
''Members of the [http://meego.com/about/governance TSG]''

* [http://meego.com/users/imad Imad Sousou/imad] - benevolent dictator
* [http://meego.com/users/valhalla Valtteri Halla] - benevolent dictator
* ???

== Maemo community stakeholders ==
'' Official representatives of the Maemo community''

* [http://meego.com/users/qgil Quim Gil/qgil] - Nokia's Maemo Community Manager
* [http://meego.com/users/tekojo Tero Kojo/tekojo] - Nokia's Maemo Technical Manager
* [http://meego.com/users/xfade Niels Breet/X-Fade] - maemo.org webmaster
* Dave Neary/dneary - maemo.org docmaster
* [http://meego.com/users/andre André Klapper/andre_] - maemo.org bugmaster
* Jeremiah Foster/jeremiah - maemo.org debmaster
* [http://meego.com/users/reggie Reggie Suplido] - maemo.org talkmaster
* [http://meego.com/users/stskeeps Carsten Munk/Stskeeps] - maemo.org distmaster & Mer project lead
* [http://meego.com/users/bergie Henri Bergius/bergie] - maemo.org web/Midgard developer
* [http://meego.com/users/vdvsx Valerio Valerio/VDVsx] - Maemo Community Council chair
* [http://meego.com/users/texrat Randall Arnold/Texrat] - Maemo Community Council member
* [http://meego.com/users/qole Alan Bruce/qole] - Maemo Community Council member
* Matthew Lewis/penguinbait - Maemo Community Council member
* Graham Cobb - Maemo Commnunity Council member

== Moblin community stakeholders ==
''Representatives of the Moblin community''

* [http://meego.com/users/dirkhh Dirk Hohndel/dirkhh], chief Linux and open source technologist at Intel
* [http://meego.com/users/townxelliot Elliot Smith/townxelliot] - moblin.org & meego.com website techy
* [http://meego.com/users/mshaver Michael Shaver/mshaver] - moblin.org webmaster & meego.com website developer
* [http://meego.com/users/margie Margie Foster/mlfoster] - localization project manager for Moblin & meego.com website developer

== MeeGo developers ==
'' People paid to contribute to MeeGo and/or have commit rights''

* [http://meego.com/users/nashif Anas Nashif/anaZ] - Random developer
* [http://meego.com/users/hbons Hylke Bons/hbons] - User Experience Designer
* [http://meego.com/users/auke Auke Kok/auke] - developer

== MeeGo community ==
''Anyone not in the above sections''

* [http://meego.com/users/jaffa Andrew Flegg/Jaffa] - long term gadget freak & Maemo community member
* [http://meego.com/users/generalantilles Ryan Abel/GeneralAntilles] - long term Maemo community member
* [http://meego.com/users/lbt David Greaves/lbt] - Mer OBS build guy.
* [http://meego.com/users/zerojay Jason Carter/zerojay] - long term Maemo community member
* [http://meego.com/users/debernardis Ernesto de Bernardis/debernardis] - Maemo community member, mobile device tinkerer
* [http://meego.com/users/timeless timeless/timeless] - Mozilla contributor, Nokia employee.
__NOTOC__ 
[[Category:Community]]