User:NeoAmsterdam/Notes to Self: Difference between revisions
Jump to navigation
Jump to search
NeoAmsterdam (talk | contribs) (Better version of overclock table than {{overclocktable}}) |
NeoAmsterdam (talk | contribs) (A few updates... nothing significant) |
||
(19 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
<div style="float: right;">__TOC__</div> |
<div style="float: right;">__TOC__</div> |
||
* A temping recipe for [http://gsoc.cat-v.org/people/ameya/blog/2007/08/10/1_Booting_plan9_on_OLPC/ booting Plan 9] (and the [http://gsoc.cat-v.org/people/ameya/blog/2007/08/19/1_Plan9_Kernel_Booting_on_OLPC/ evidence] to prove it's possible) |
|||
This page contains no useful, practical, or "actionable" information - only disorganized notes. |
|||
* XO won't boot RHEL 6 from a USB key created with Fedora's LiveUSB Creator (OpenFirmware gripes about a general protection error) |
|||
= Yum = |
|||
== Packages without Dependencies == |
|||
* elinks |
|||
* wget |
|||
* switchdesk |
|||
== Packages with Dependencies == |
|||
* icewm |
|||
** 946KB, but 8.2MB with dependencies |
|||
** bluecurve-icon-theme accounts for 5.2MB |
|||
* gcc |
|||
** 8.1MB, 14MB with dependencies: |
|||
*** binutils, glibc-{devel,headers},kernel-headers |
|||
* wine |
|||
** 29MB in dependencies |
|||
* <s>gnumeric</s> |
|||
** 11MB package, 26MB in deps... (I don't think so) |
|||
* <del>Rebuild [[Mini vMac]] (multiple drives, 576x448 or 1184x900 screen, max speed by default; X11 v. GTK builds)</del> |
|||
== Other == |
|||
** A rebuild requires steps not possible using the Mini vMac activity |
|||
* autoconf automake make cmake imake patch indent |
|||
** ~9.1MB; 9.6MB with m4 and xmlprc-c as dependencies |
|||
*** cmake accounts for 6.8MB |
|||
== Packages that Won't Install Nicely or at All == |
|||
* kile |
|||
** Needs texlive, which needs an up-to-date libpoppler, but sugar-evince won't let libpoppler update.<br />(Plus kile needs KDE base packages and that's way too much for an XO...) |
|||
* <del>Write a "hack ~/.sugar/default/config" note (builds before 852; after ~/.gconf/desktop.sugar/user/%gconf.xml)</del> fairly self-explanatory. |
|||
<s> |
|||
= <tt>/etc/event.d/</tt> = |
|||
== <tt>prefdm</tt> == |
|||
* Switch from Sugar to Ice? |
|||
== <tt>tty{1,2}</tt> == |
|||
* Nix paswordless logins? |
|||
== <tt>ttyS0</tt> == |
|||
* Nix serial console? |
|||
</s> |
|||
* Extracting XO splash sound (possibly replace) from w/in OFW |
|||
= <tt>/usr/bin/olpc-session</tt> = |
|||
*:'''Q''': is the <nowiki>[filesize|duration]</nowiki> an upper limit? Are the resolution, bit-depth, and channel count fixed? |
|||
* <tt># set mouse and keyboard speed</tt> |
|||
** Don't want to brick my lil' green Speak-n-Spell... |
|||
** turn on keyclick?? |
|||
* <tt># finally, run sugar</tt> |
|||
** a way to swap to Ice?? <span style="color:green;">Yes</span>, <span style="color:orange;"><b>but:</b></span> |
|||
*** <tt>0-boot-anim-start</tt> and <tt>0-boot-anim-start</tt> must be <b>off</b>! ( I hope I can keep <tt>ul-warning</tt>, though... kinda cute) |
|||
*** WiFi can't be operated ($PATH is busted and NetworkManager won't function) |
|||
* Graphic Calculator<br />...b/c TI isn't the XO way and GNUPlot requires a Ph.D.. |
|||
= Overclock = |
|||
* Radio streaming? (transmitting from "[http://www.thevoiceofpeace.co.il/gallery2/showphoto.php?photo=439_e3a0a0732ff8dc75d7dd77d26e72d22e.jpg ...somewhere in the mesh]"?) |
|||
<table class="wikitable" style="font-family: monospace; background: white; text-align: center;"> |
|||
** <del>A [[Skype|certain well-known VoIP app]] can't hack it on an XO. Considering that it's effectively the equivalent of audio streaming (albeit p2p), this might not be feasible. Then again, it's just was probably a half-***ed port of a known pile of slop...</del> Acquired by closed-source company; VoIP on Linux is still a pipe dream, so radio streaming will be too. |
|||
<tr style="font-weight: bold; background: rgb(90%,90%,90%);"> |
|||
* SOS/Post-catastrophe app (how to fit a collaborative documentation effort into =<512MB? or make it decentralized?) |
|||
<td colspan="5">7de009e ### 4c000014 wrmsr</td> |
|||
** Someone's partially addressing it with ham radio ([http://activities.sugarlabs.org/en-US/sugar/addon/4087])... |
|||
</tr> |
|||
<small> |
|||
<tr style="font-family: sans-serif; font-weight: bold; background: rgb(95%,95%,95%);"> |
|||
*# Each XO gathers info, establishes pt-2-pt comm links with nearest 2 neighbors (min. for msg. relay) |
|||
<td>CPU</td> |
|||
*#* Is there a way to make long-distance multi-node pt-2-pt contact? |
|||
<td colspan="4">Bus Speed</td> |
|||
*# As users enter information, suggestions could be given to the user (how much water x number of people need, how to recognize possible water-borne diseases, triage how-to) |
|||
</tr> |
|||
*# Once a relief center shows up (w/ hard drives), acts as XS/server...<br /><small>or a real one - it would make sense that schools would become impromptu first-aid and triage stations</small><br />...XOs spot it in the mesh (?) or by mesh-relay and U/L upon discovery (deltas thereafter) |
|||
<tr style="font-family: sans-serif; border-bottom: thin solid black;"> |
|||
*#* But how long until relief shows up? How much data captured in that time? What data would be the most urgent? |
|||
<td></td> |
|||
*# Comms are transient (vid/pic/voice), but written info (chat/DIY wiki) would need context awareness - geo/GPS, people/relations, needed items, status (Injured/killed/infirm)<br />Might be better served by smart-phones? Might too gruesome for kids to do, but parents would probably rely on the kids to do the data entry... hmm... :-/<!-- Plus, this sort of thing oughtn't be circulating - it might be too much even for 1st aid/responders to deal with... isn't the 'net gory enough already? --> |
|||
<td>133</td> |
|||
**Caveat emptor: Batteries might drain before relief arrives, and there might not be any power source. |
|||
<td style="background: rgb(95%,100%,95%);">166</td> |
|||
</small> |
|||
<td>200</td> |
|||
<td>233</td> |
|||
Didn't work ;-( |
|||
</tr> |
|||
* <del>Build KDE 3 from scratch (because KDE4 is almost Java-like in resource hogging).</del> |
|||
<tr> |
|||
** <del>Takes a whole day on a 2,5GHz G5 Quad; it'll probably take a week on an XO :-(</del> |
|||
<td style="font-family: sans-serif;">333</td> |
|||
** <del>I'll just grumble and GNOME it X-P</del> |
|||
<td>3d3</td> |
|||
<td style="background: rgb(95%,100%,95%);">4d3</td> |
|||
* Social network/cultural exchange/distance learning activity? o_O |
|||
<td>5d3</td> |
|||
* Self-sync/auto-backup the XO when it encounters its "corresponding" XS |
|||
<td>6d3</td> |
|||
** <del>I wonder if I can I get XS s/w running on my F14 box...</del> Not "nicely". |
|||
</tr> |
|||
<tr> |
|||
* gnash needs help with translating into es. |
|||
<td style="font-family: sans-serif;">366</td> |
|||
** HOW? |
|||
<td>3d5</td> |
|||
<td style="background: rgb(95%,100%,95%);">4d5</td> |
|||
<td>5d5</td> |
|||
<td>6d5</td> |
|||
</tr> |
|||
<tr> |
|||
<td style="font-family: sans-serif;">400</td> |
|||
<td>3d7</td> |
|||
<td style="background: rgb(95%,100%,95%);">4d7</td> |
|||
<td>5d7</td> |
|||
<td>6d7</td> |
|||
</tr> |
|||
<tr style="background: rgb(95%,100%,95%);"> |
|||
<td style="font-family: sans-serif;">433</td> |
|||
<td>3d9</td> |
|||
<td style="background: rgb(90%,100%,90%);">4d9</td> |
|||
<td>5d9</td> |
|||
<td>6d9</td> |
|||
</tr> |
|||
<tr> |
|||
<td style="font-family: sans-serif;">466</td> |
|||
<td>3db</td> |
|||
<td style="background: rgb(95%,100%,95%);">4db</td> |
|||
<td>5db</td> |
|||
<td>6db</td> |
|||
</tr> |
|||
<tr> |
|||
<td style="font-family: sans-serif;">500</td> |
|||
<td>3dd</td> |
|||
<td style="background: rgb(95%,100%,95%);">4dd</td> |
|||
<td>5dd</td> |
|||
<td>6dd</td> |
|||
</tr> |
|||
<tr> |
|||
<td style="font-family: sans-serif;">533</td> |
|||
<td>3df</td> |
|||
<td style="background: rgb(95%,100%,95%);">4df</td> |
|||
<td>5df</td> |
|||
<td>6df</td> |
|||
</tr> |
|||
<tr> |
|||
<td style="font-family: sans-serif;">566</td> |
|||
<td>3e1</td> |
|||
<td style="background: rgb(95%,100%,95%);">4e1</td> |
|||
<td>5e1</td> |
|||
<td>6e1</td> |
|||
</tr> |
|||
</table> |
Latest revision as of 07:25, 12 June 2011
- A temping recipe for booting Plan 9 (and the evidence to prove it's possible)
- XO won't boot RHEL 6 from a USB key created with Fedora's LiveUSB Creator (OpenFirmware gripes about a general protection error)
Rebuild Mini vMac (multiple drives, 576x448 or 1184x900 screen, max speed by default; X11 v. GTK builds)- A rebuild requires steps not possible using the Mini vMac activity
Write a "hack ~/.sugar/default/config" note (builds before 852; after ~/.gconf/desktop.sugar/user/%gconf.xml)fairly self-explanatory.
- Extracting XO splash sound (possibly replace) from w/in OFW
- Q: is the [filesize|duration] an upper limit? Are the resolution, bit-depth, and channel count fixed?
- Don't want to brick my lil' green Speak-n-Spell...
- Graphic Calculator
...b/c TI isn't the XO way and GNUPlot requires a Ph.D..
- Radio streaming? (transmitting from "...somewhere in the mesh"?)
A certain well-known VoIP app can't hack it on an XO. Considering that it's effectively the equivalent of audio streaming (albeit p2p), this might not be feasible. Then again, it's just was probably a half-***ed port of a known pile of slop...Acquired by closed-source company; VoIP on Linux is still a pipe dream, so radio streaming will be too.
- SOS/Post-catastrophe app (how to fit a collaborative documentation effort into =<512MB? or make it decentralized?)
- Someone's partially addressing it with ham radio ([1])...
- Each XO gathers info, establishes pt-2-pt comm links with nearest 2 neighbors (min. for msg. relay)
- Is there a way to make long-distance multi-node pt-2-pt contact?
- As users enter information, suggestions could be given to the user (how much water x number of people need, how to recognize possible water-borne diseases, triage how-to)
- Once a relief center shows up (w/ hard drives), acts as XS/server...
or a real one - it would make sense that schools would become impromptu first-aid and triage stations
...XOs spot it in the mesh (?) or by mesh-relay and U/L upon discovery (deltas thereafter)- But how long until relief shows up? How much data captured in that time? What data would be the most urgent?
- Comms are transient (vid/pic/voice), but written info (chat/DIY wiki) would need context awareness - geo/GPS, people/relations, needed items, status (Injured/killed/infirm)
Might be better served by smart-phones? Might too gruesome for kids to do, but parents would probably rely on the kids to do the data entry... hmm... :-/
- Caveat emptor: Batteries might drain before relief arrives, and there might not be any power source.
- Each XO gathers info, establishes pt-2-pt comm links with nearest 2 neighbors (min. for msg. relay)
Didn't work ;-(
Build KDE 3 from scratch (because KDE4 is almost Java-like in resource hogging).Takes a whole day on a 2,5GHz G5 Quad; it'll probably take a week on an XO :-(I'll just grumble and GNOME it X-P
- Social network/cultural exchange/distance learning activity? o_O
- Self-sync/auto-backup the XO when it encounters its "corresponding" XS
I wonder if I can I get XS s/w running on my F14 box...Not "nicely".
- gnash needs help with translating into es.
- HOW?