User:NeoAmsterdam/Notes in Progress

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
  2. Desktop settings seem to reset after a logout/restart/shutdown. Understandable (consistency), but an annoyance.
• VNC and/or SSH

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 ÷ 6³/₄ 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.)

TilEm.

This process, application, or procedure involves a ROM image.
ROMs are subject to copyright. If you do not own the ROM, then you are not entitled to the ROM image. Do not contact me about ROMs.

This procedure builds software from source code.
Developers’ tools must be installed. Your results may vary.

This process or procedure involves yum.
If misused, yum can render your XO unusable. Please read the documentation before using yum.

Most (all?) require ROMs; a CPU-hog (96% CPU according to top); 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.

1. yum install gtk2-devel
   Loads of deps.
2. wget & unpack tar.bz2 (pity there's no ln -S to latest)
3. ./configure --without-ticables
4. make
5. sudo make install installs tilem to /usr/local/bin - Good Thing, perhaps, or Bad Thing given $PATH's limited scope?
6. Copy over roms (gottta write the ROM snippet) to ~/.TilEm

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.

Doing

Kile

• yum shows 82MB in deps, but that doesn't count deps installed from gedit's latex plugin.
  • Does a freshly-installed Kile still suffer from DPI ditzyness? Yes, but not as bad as I'd've thought. kcontrol or systemsettings should do the trick (there's gotta be a more expedient way...)

    I take it all back - it's worse: kcontrol 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 systemsettings 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

• 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).

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?