User:MartinDengler/Commentaries:SoaSonXO: Difference between revisions
add olpc-update commentary |
No edit summary |
||
| Line 1: | Line 1: | ||
== Some Discussion on SoaS and using it on the XO == | == Some Discussion on SoaS and using it on the XO == | ||
Can I get SoaS | '''Can I get SoaS on my XO''' is a FAQ without a clear answer. | ||
[[#Original_IRC_Discussion|An IRC discussion on #sugar]] raised the [[#Discussion_Items|following questions for discussion]]: | |||
== Discussion Items == | == Discussion Items == | ||
| Line 13: | Line 15: | ||
:This section is intentionally not titled "jffs2 images". | :This section is intentionally not titled "jffs2 images". | ||
=== non-Fedora bits === | === non-Fedora bits === | ||
| Line 20: | Line 21: | ||
: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 === | === OLPC-like update mechanism === | ||