User:MartinDengler/Commentaries:SoaSonXO: Difference between revisions

Mstone (talk | contribs)
 
(18 intermediate revisions by one other user not shown)
Line 1: Line 1:
= Some Discussion on SoaS and using it on the XO =
{{TOCright}}


Can I get SoaS (or "the latest Sugar") on my XO is a FAQ without a clear answer.  [[#Appendix_IRC_Discussion|an IRC discussion on #sugar]] raised the [[#Discussion|following questions for discussion]]:
== Some Discussion on SoaS and using it on the XO ==


== Discussion ==
'''Can I get SoaS on my XO?''' is a FAQ without a simple answer.
 
[[#Original_IRC_Discussion|An IRC discussion on #sugar]] raised the [[#Discussion_Items|following questions for discussion]]:
 
== Discussion Items ==
 
=== NAND images ===
 
* Should SoaS2's software artifacts include a XO-1 NAND .img/crc file?


# Should SoaS2's software artifacts include a XO-1 NAND .img/crc file at all?
:This would allow people to not have to convert the Soas2 .iso to a NAND .img (or to transfer the .iso to a USB key and run liveinst after booting from that stick).
:This would allow people to not have to convert the Soas2 .iso to a NAND .img (or to transfer the .iso to a USB key and run liveinst after booting from that stick).
# Should Soas2's software artifacts include non-Fedora (that is, non-upstream) bits or yum repositories?  For example: a) OLPC kernel (2.6.25); or b) via wireless drivers?
 
:This section is intentionally not titled "jffs2 images".
 
=== non-Fedora bits ===
 
* Should Soas2's software artifacts include non-Fedora (that is, non-upstream) bits or yum repositories?  For example: a) OLPC kernel (2.6.25); or b) Via wireless drivers?
 
:Though (and this is potentially a big "though") these bits/repos must be supported by SugarLabs without any upstream assistance (this statement is a bit less equivocal than strictly necessary), they would provide a solution with a lot more working features.  For example, it's hard to imagine an accepted XO-1 solution without power management, or an accepted Eee (is that Via???) solution without wireless.  However, these may not be enough of SoaS's target audience to merit the additional work.
:Though (and this is potentially a big "though") these bits/repos must be supported by SugarLabs without any upstream assistance (this statement is a bit less equivocal than strictly necessary), they would provide a solution with a lot more working features.  For example, it's hard to imagine an accepted XO-1 solution without power management, or an accepted Eee (is that Via???) solution without wireless.  However, these may not be enough of SoaS's target audience to merit the additional work.


=== OLPC-like update mechanism ===
* Should an [[OLPC:User:Mstone/Commentaries/Mass olpc-update|olpc-update-like]] mechanism be supported?  This is quite a lot of work.  There is still some [http://dev.laptop.org/git/projects/olpc-update/ work being done on olpc-update].


== Background ==
== Background ==
Line 15: Line 31:
=== Comparison ===
=== Comparison ===


Neither SoaS nor Rawhide XO currently support XO-1 power management, display management, or mesh networking.  SoaS2's next release will not; Rawhide XO will.
* Neither SoaS nor Rawhide XO currently support XO-1 power management, display management, or mesh networking.  SoaS2's next release will not; Rawhide XO will.
 
SoaS is being maintained by SugarLabs, Rawhide XO by OLPC. Both are built using the same (rawhide) RPM repos and common kickstart files.  They are both composed from a set of kickstart files in the same repo: http://git.sugarlabs.org/projects/soas
 
Soas2 and Rawhide-XO are built at different times by different groups, and this is expected to continue.


* SoaS is being maintained by SugarLabs, Rawhide XO by OLPC. Both are built using the same (rawhide) RPM repos and common kickstart files.  They are both composed from a set of kickstart files in the same repo: http://git.sugarlabs.org/projects/soas


=== General ===
* Soas2 and Rawhide-XO are built at different times by different groups, and this is expected to continue.


=== Sugar on a Stick ===
=== Sugar on a Stick ===


Codename: ''SoaS''.  See more about goals at [[Sugar on a Stick/Project Goals]].  Target audience: USB-stick instances of Sugar that are portable among different computers.  Also used to refer to the *next* version of Sugar on a Stick (as opposed to *any future* version).
Codename: ''SoaS''.  See more about goals at [[Sugar_on_a_Stick/Project_Goals]].  Target audience: USB-stick instances of Sugar that are portable among different computers.  Also used to refer to the *next* version of Sugar on a Stick (as opposed to *any future* version).


* Release date: (see [[]])
* SoaS target hardware: anything supported by Fedora 11 (and exactly Fedora 11 - for example XO-1s will run SoaS but, currently, without OLPC's power management and mesh networking patches.  See the Discussion section below.)
* SoaS target hardware: anything supported by Fedora 11 (and exactly Fedora 11 - for example XO-1s will run SoaS but, currently, without OLPC's power management and mesh networking patches.  See the Discussion section below.)
* SoaS current software: Fedora 11; Sugar 0.84
* SoaS current software: Fedora 11; Sugar 0.84
Line 36: Line 48:
=== Rawhide XO ===
=== Rawhide XO ===


latest OLPC software spin.  See more about goals at [[OLPC:Rawhide-XO]].  "Rawhide-XO" also refers to the as-yet-unnamed next OLPC release for the XO-1 (all details TBD, including target hardware)
Latest OLPC software spin.  See more about goals at [[OLPC:Rawhide-XO]].  "Rawhide-XO" also refers to the as-yet-unnamed next OLPC release for the XO-1 (all details TBD, including target hardware)


* Rawhide XO target hardware: XO-1, XO-1.5
* Rawhide XO target hardware: XO-1, XO-1.5
* Rawhide XO current software: snapshots based on Rawhide, approaching F11
* Rawhide XO current software: snapshots based on Rawhide, approaching F11
* Rawhide XO target software: Fedora 12, Sugar 0.86
* Rawhide XO target software: Fedora 12, Sugar 0.86
* codename: unknown.




== Appendix 1: Original IRC Discussion ==
== Original IRC Discussion ==


<pre>
<pre>