[64studio-devel] 64 Studio book

[mmmmna]

What to put in it?
1] how to repair mission critical programs - Xorg, a lightweight
commandline browser, DHCP
2] Install and set up a network connection from ground zero (hence,
all referenced files must be included in the distro)
3] setup APT (and/or whatever front end) for using repositories
4] setup common sound devices as used in DAW.
5] setup video devices, scanners, printers.
6] concise overview of how JACK and ALSA interact with each other
7] concise overview of how JACK and ALSA interact with other programs
8] LADSPA / VST etc.

File format: Definitely NOT PDF:
a] something more rudimentary, something that can be read from a
commandline when a GUI is not working. Or break the file into sections
that ARE readable at commandline and sections that are better
formatted for GUI readers.
b] PDF readers are getting extremely bloated by features for revision
control, interoffice markups, etc. The simplest document formatting
allows the broadest reader capabilities.
c] 'info' system UI stinks for Linux newbies, so no help there.

Seriously... at one time, I saw this mail list mention something about
selecting Gnome as a UI because it is a UI that is friendly for
Windows/MacOS users coming to 64. I suspect that one use for an
instructional and official book would be to get the UI repaired or at
least reinstalled. I can't imagine a Linux newbie trying to navigate
the Linux info system.... Even more unlikely they could read a PDF
file from the command prompt. Years ago, I suffered trying to read
HTML 'how-tos' from a command prompt, as I had no browser to read HTML
because I had no GUI for the browser to run in. Whatever you decide,
remember the worst case for a newbie might just be no internet, no GUI
and no Lynx/Links/W3C/MC/Emacs/whatever Linux professionals are using
for commandline browsers (newbies to Linux don't know about these
tools, probably won't know how to use these even when told about
them). I know that sounds like I'm saying keep it as text, and sadly,
that might be realistic.
Whatever you choose, forget what you know how to use, if you want to
match the broken GUI user that is coming from Windows.