User:NeoAmsterdam/Notes in Progress: Difference between revisions

From OLPC
Jump to navigation Jump to search
(Ugh)
 
(4 intermediate revisions by 2 users not shown)
Line 3: Line 3:
* Install <tt>[[:File:OLPC_icc.zip|olpc.icc]]</tt>, then figure out what's the color correction system
* Install <tt>[[:File:OLPC_icc.zip|olpc.icc]]</tt>, then figure out what's the color correction system
* Notes to document:
* Notes to document:
*# there's a menu-related panel thingie package that'll prevent menubars for appearing at all
*# there's a menu-related panel thingie package that'll <del>prevent menubars for appearing at all</del> makes menubars act in ways not entirely expected (fixed in later versions).
*# Desktop settings seem to reset after a logout/restart/shutdown. Understandable (consistency), but an annoyance.
*# <del>Desktop settings seem to reset after a logout/restart/shutdown. Understandable (consistency), but an annoyance.</del> A <tt>sudo nano</tt> should fix that
* VNC and/or SSH
* VNC and/or SSH
** yum install x11vnc (libvncserver, lzo-minilzo, xorg-x11-server-Xvrfb)
** /etc/avahi/services to b'cast/advertise
** still needs vncpasswding

=== Alt. OSs ===
* <del><tt>''FreeDOS'':\isolinux\data\memdisk</tt> identified as "<tt>Linux kernel x86 boot executable bzImage</tt>" but OFW claims "<tt>Invalid Opcode</tt>" - [[Talk:Our software#FreeDOS|known not to work]], but worth trying anyway.</del> Doesn't work ;-(
* <del>'''''Extremely''''' tempted to install RHEL6 (Sci Linux, actually): LiveCD-to-USB, then install to SD card??</del> OpenFirmware crashes with "<tt>General Exception Fault</tt>" and "<tt>General Protection Failure</tt>" (depending on the phase of the moon). Looks like these distros are expecting BIOS/EFI despite purporting XO support (or perhaps they're having conniptions with XO anti-theft?)


== Done ==
== Done ==
Line 33: Line 40:
Warning: Geo.Loc., D/L Loc., privacy settings, lame "oops" messages when there's a Flashy page (y'shouldda asked, Goo... y'shouldda asked first.)
Warning: Geo.Loc., D/L Loc., privacy settings, lame "oops" messages when there's a Flashy page (y'shouldda asked, Goo... y'shouldda asked first.)


=== TilEm. ===
{{User:NeoAmsterdam/Snippets/ROMs}}{{User:NeoAmsterdam/Snippets/Source Code}}{{User:NeoAmsterdam/Snippets/Yum}}
Most (all?) require ROMs; a CPU-hog (96% CPU according to <tt>top</tt>); caveat: Won't read saved memory files from other platforms

'''Note:''' tilem is a lot of trackpad and clicking. Very annoying, but far more useable than MetaFont's math system or GNUPlotz.
# yum install gtk2-devel<br />Loads of deps.
# wget & unpack [http://sourceforge.net/projects/tilem/files/tilem-devel/0.973/tilem-0.973.tar.bz2/download tar.bz2] (pity there's no <tt>ln -S</tt> to latest)
# <tt><B>./configure</B> <i>--without-ticables</i></tt>
# <tt>make</tt>
# <tt>sudo make install</tt> installs tilem to <tt>/usr/local/bin</tt> - Good Thing, perhaps, or Bad Thing given $PATH's limited scope?
# Copy over roms (<del>gottta write the ROM snippet</del>) to ~/.TilEm


=== Gnome Screenshot ===
=== Gnome Screenshot ===
* yum install gnome-utils (deps. libgtop2)<br /><del>I wonder if I can change the keystroke for snapshotting to "frame" (and alt-tab to the key next to it?)</del>Yep.
* yum install gnome-utils (deps. libgtop2)<br /><del>I wonder if I can change the keystroke for snapshotting to "frame" (and alt-tab to the key next to it?)</del>Yep.


== Doing ==
=== Office ===
* Very tricky installation (read: plethora of annoying "oops" boxes from wine) from command line, but works. Apps' bootsplashes will obscure a dialog box asking for first-time user ID info, so it looked like the apps were hanging. DPI issue resolved (use Wine Config to set DPI)
<!--

=== Einstein ===
* <del>Jam</del> done (yum)...
* What is "K" of which the readme speaks, and why the h**l does this yutz rely on libraries that have been yanked?!?
=== Android SDK ===
Because (a) given the option, I'd rather have Sugar on my cell phone (at least Sugar's got a consistent UI!), and (b) it's the only system I've got that can run their SDK. Just imagine the "Made with real sugar!" label on the packaging! !-D
* grab the .tgz, unpack
* Needs Java )-: yum -y install java-1.6.0-openjdk{,-plugin,-devel} (needs more than just J''R''E), but the de-<tt>tgz</tt>ed setup/installer works (not the emulator/simulator).
* yum install "eclipse-jdt*" -x "*-nls*" ; # 125MB of deps!
-->
=== Kile ===
=== Kile ===
'''Note:''' Fuhgeddaboudit - Resource hog.
* yum shows 82MB in deps, but that doesn't count deps installed from gedit's latex plugin.
* <del>yum shows 82MB in deps, but that doesn't count deps installed from gedit's latex plugin. yum doesn't install KDVI, which Kile will complain about during a systems check. </del>
** <del>Does a freshly-installed Kile still suffer from [[User:NeoAmsterdam/10.1.2/Gallery#Oops.21|DPI ditzyness]]? Yes, but not as bad as I'd've thought. <tt>kcontrol</tt> or <tt>systemsettings</tt> should do the trick (there's gotta be a more expedient way...)</del>
* <del>Still suffers from DPI ditziness, but it's not as bad as it was with 10.1.2.</del>
**: I take it all back - it's ''worse'': <tt>kcontrol</tt> would have been the answer if it weren't KDE '''4'''. You have to yum install kdebase-workspace with its 70/80/90MB deps just to get <tt>systemsettings</tt> installed. Ideally you'd just run it, set the dpi in a way that QT/KDE understands/expects, and be done with it. But, no: systemsettings won't even launch...
**: Why must resolution independence be so b****y difficult to attain?!?


=== Office ===
=== Android SDK ===
In the end... '''no''': The SDK is wonky using the "open" Java, and running the "official" Java is like wading through tar.
* Very tricky installation (read: plethora of annoying "oops" boxes from wine) from command line, but works. Apps' bootsplashes will obscure a dialog box asking for first-time user ID info, so it looked like the apps were hanging. Also doesn't respect DPI, so it looks squished all over (Wine problem, probably).

== Doing ==


=== yum ===
=== yum ===
Seems that if you run it from command line as user olpc, it'll trigger the "out of space" error - even if you su to root afterwards. Bug? Or feature?
If you run it from command line as user olpc, it'll trigger the "out of space" error - even if you su to root afterwards. Seems to be a failsafe, acts like a nasty bug.

Latest revision as of 06:36, 28 May 2011

To Do

  • yum inst. linux-wacom .o0(please, please, please work?)
  • Install olpc.icc, then figure out what's the color correction system
  • Notes to document:
    1. there's a menu-related panel thingie package that'll prevent menubars for appearing at all makes menubars act in ways not entirely expected (fixed in later versions).
    2. Desktop settings seem to reset after a logout/restart/shutdown. Understandable (consistency), but an annoyance. A sudo nano should fix that
  • VNC and/or SSH
    • yum install x11vnc (libvncserver, lzo-minilzo, xorg-x11-server-Xvrfb)
    • /etc/avahi/services to b'cast/advertise
    • still needs vncpasswding

Alt. OSs

  • FreeDOS:\isolinux\data\memdisk identified as "Linux kernel x86 boot executable bzImage" but OFW claims "Invalid Opcode" - known not to work, but worth trying anyway. Doesn't work ;-(
  • Extremely tempted to install RHEL6 (Sci Linux, actually): LiveCD-to-USB, then install to SD card?? OpenFirmware crashes with "General Exception Fault" and "General Protection Failure" (depending on the phase of the moon). Looks like these distros are expecting BIOS/EFI despite purporting XO support (or perhaps they're having conniptions with XO anti-theft?)

Done

  • yum install "gedit*plugin*" installs texlive as dep (∑75MB).
    • Could use TeXLive 2010 install (from ISO).

VM

512MB is a must for any GNOME-work.

fonts

  • liberation-{sans,serif,mono}, sil-gentium-fonts
  • FixedSys Excelcior or PR fonts are ok, but there just isn't a "must-have" monospaced font that's legible, appealing, and has character (pun not intended).
    sudo cp whatever to /usr/share/fonts
    108 DPI for GNOME is just about right 133.333333 dpi, actually - Thanks to AuntiMame for providing the width and height of the XO's screen (among other troves), and to whoever it was who made ◊1 produce screenshots. Hence:
  • 1200px ÷ 9 inches = 133.333333 px per inch
  • 900px ÷ 63/4 inches = 133.333333 px per inch
    (just making sure)
  • 133.333333 px per inch ≈ 5.249343 dots per mm (for our metric friends)

Goog Chrome

Ugh, but it's leaner than FiFox. It also suffers from DPI-ditziness (why, oh, why?)

  • requires LSB≥3.2
    1. yum install redhat-lsb
      gives that @#$%ing "out of space" error (not with a 16GB SD you aren't!!!!)
    2. console: -> /sbin/init 3 ... yum install redhat-lsb
      ditto >_<
    3. #ed "/var" mounts; restart
    4. Gnome: yum install redhat-lsb
      Works! Dependencies: m4 make patch pax
  • Grab Goog's rpm (where's the SRPM you "let's not be evil" b*****ds?!)
  • rpm -ivh g...rpm OK
    As sluggish as FiFox, as alien as M$Office 12

Warning: Geo.Loc., D/L Loc., privacy settings, lame "oops" messages when there's a Flashy page (y'shouldda asked, Goo... y'shouldda asked first.)


Gnome Screenshot

  • yum install gnome-utils (deps. libgtop2)
    I wonder if I can change the keystroke for snapshotting to "frame" (and alt-tab to the key next to it?)Yep.

Office

  • Very tricky installation (read: plethora of annoying "oops" boxes from wine) from command line, but works. Apps' bootsplashes will obscure a dialog box asking for first-time user ID info, so it looked like the apps were hanging. DPI issue resolved (use Wine Config to set DPI)

Kile

Note: Fuhgeddaboudit - Resource hog.

  • yum shows 82MB in deps, but that doesn't count deps installed from gedit's latex plugin. yum doesn't install KDVI, which Kile will complain about during a systems check.
  • Still suffers from DPI ditziness, but it's not as bad as it was with 10.1.2.

Android SDK

In the end... no: The SDK is wonky using the "open" Java, and running the "official" Java is like wading through tar.

Doing

yum

If you run it from command line as user olpc, it'll trigger the "out of space" error - even if you su to root afterwards. Seems to be a failsafe, acts like a nasty bug.