Need a way to tell what .iso a SoaS was built from

[CarolineM]

As we collect testing data we need a way from Sugar to know what build we are working with.

[mungewell]

For Ubuntu based systems:
It is convention to include an info file in the '.disk/' directory of the LiveCD;
---
$cat .disk/info
Ubuntu 8.10 "Intrepid Ibex" - Release i386 (20081029.5)
---

Whilst running the CD will be mounted under /cdrom, so look in '/cdrom/.disk/info'

This unfortunately won't help if you are creating the live disk by adding an additional squashfs archive to an existing CD. I'm not sure whether you can overwrite a file, or know which order the squashfs archives will be loaded.

The other problem is that a LiveCD/USB is actually a full system, given a large enough persitance file one could actually update the whole system to a newer release of the distribution (just an 'apt-get' away).

So an activity might actually be a newer release than that on the LiveCD/USB image/distribution.

The only sure fire way is to dump the package lists.... 'dpkg --list'.

Cheers,
Mungewell.

[tomeu]

I think this is more for Marco.

[marcopg]

This might actually be primarily a sugar bug, if we want something in the UI. Caroline, what do you think? I guess we might a control panel page about this (if I remember correctly there is already something XO specific that we should generalize).

[dfarning]

The gnome->about panel has a nice Version, Distribution, Build panel that could used as a model to create consistency across various Sugar versions, distros, and builds for Sugar.

[CarolineM]

yes, as Sugar goes everywhere we'll want this.

[CarolineM]

I think this is still an active request

[sdz]

This is fixed in GIT now: We're displaying the date the image got composed in the "About my Computer" screen now. Will be in the next snapshot!

[sascha_silbe]

Bulk change distribution=SoaS -> component=SoaS

[dnarvaez]

Milestone Blueberry deleted