These tips are for people who are already comfortable with the
    GNU/Linux command line - in INX, this means the Bash shell.
    
    This information is first about using INX, and second about the
    actual underlying code itself. Note that the INX-specific code
    is all in Bash - the menus and scripts are therefore accessible
    to anyone with some understanding of the Bash shell.
    
    You can also read this information for instance in the 
    "less" pager:
    
    less /usr/local/share/doc/inx/doc.advanced
    
    If the menus are in your way, you can remove the "case" statement
    sourced from ~/.profile by removing or renaming ~/.auto-menus
    
    Logging out will then result in an autologin without a menu on
    any tty, on the live CD. In a virtual machine a new login will be
    required.
    
    You can still start menus using commands.    [See also: "man inx"]
    

    Various applications are set to associate with particular formats:
    
    This is mostly set in ~/.mailcap or /etc/mailcap (~/.mailcap takes
    precedence).
    
    Specific INX tweaks are mostly set in user dot files. To see the
    full collection of such files 
    
    ls -Al /etc/skel/ | less
    
    Or just look in /home/inx
    
    Specific GNU Screen sessions are configured through .screenrc*
    files - ~/.screenrc-music , ~/.screenrc-intro, and so on.
    
    The Mutt mail settings use ~/.msmtprc, and build on ~/.muttrc-base,
    which contains the parts of ~/.muttrc that require no change.
    The files are created for use with the mail settings questions 
    from the mail menu.
    
    If you want a clearer picture of the tweaks done to make INX,
    reading the "buildinx" and "inxtaller" scripts is recommended.
    
    (See /usr/local/sbin/buildinx and /usr/local/sbin/inxtaller)

    Buildinx:
    
    The "buildinx" script is the script used to actually build
    the current version of INX. You will need the Internet :)
    
    It uses "wget","debootstrap" and "apt"to create a file system 
    and populate it, then converts it to "squashfs" and copies all 
    needed files to a "master" directory, then finally makes an ISO.
    
    This just makes a clone of the INX you are already running -
    but Buildinx gives you the option to add or remove packages
    from the CD, or make configuration changes in the chroot that it
    creates. Thus you can make your own custom version of INX using 
    Buildinx. Obviously, you don't run this in a "live CD" session.
    
    You can re-run the script after making changes - it will back up
    your previous ISO image and make a new one.
    [See also: "man buildinx"]
    
    Inxtaller: (very much a work in progress - you have been warned)
    
    This is a very basic and experimental hard-drive installer.
    Currently it requires a single blank hard drive, and makes swap 
    and / partitions on it. It's fine for installing to a virtual 
    machine like Virtual Box or Qemu etc. - but needs further 
    development for most installation options.
    
    Don't use this on actual machines unless you read and understand 
    the script!                            [See also: "man inxtaller"]

    There are of course various methods for installing an "INX" on a
    hard drive. These are left as an exercise for the reader ;-) 
    
    But... briefly:
    
    You can make a command-line install of Ubuntu 8.04, then add all  
    the applications by using the "selections" file that you will find
    in /usr/local/share/doc/inx/selections
    
    dpkg --set-selections < selections
    apt-get dselect-upgrade
    
    You can use debootstrap as an installation method, then add
    applications/packages as above.
    
    In each case you will need to edit /boot/grub/menu.lst to add
    framebuffer options. (For example, vga=788, vga=791 etc.)
    
    Specific INX tweaks, scripts and additions are in a tarball 
    available in the "buildinx" directory on the INX website.
    
    http://inx.maincontent.net/buildinx/
    
    

    There are bzipped virtual machines for either Virtual Box or Qemu
    on the INX site. The most recent will be in the "devel" directory.
    
    All you have to do is bunzip2, and point your vbox or qemu at the 
    resulting image. The "machine images" are expandable to 8GB.
    
    If you prefer, you can easily use the "Inxtaller" to roll your own
    virtual machine - that's how these are made.
    
    The "ready-made" images have password-less sudo, since these are
    virtual machines. You can of course alter this if you wish by 
    running "visudo". If you "roll your own", sudo will by default
    require a password.
    
    INX will also run in VMware, of course, but there is no 
    "ready-made" VMWare image on the site, so you would need to
    make your own and use the Inxtaller to install INX on it.
    
    You can of course run INX directly from the iso in any virtual
    machine, but this is not very flexible, and probably only worth
    doing for testing purposes or playing around.
    
    

    There is an INX development team on launchpad.net.
    
    Team members need not be coders - for example, several existing
    team members are relatively new users with intermediate skills,
    whose testing and feedback are helpful.
    
    The author (hello!) is still, and always, learning Bash, so be 
    gentle with him.
    
    *grin*
    
    An outline of how the code is structured can be read in 
    "man inx-development" 
    
    Briefly, many of the executable scripts are very short, and
    call /usr/local/lib/inx/main-inx , which acts as a kind of 
    "switchboard" accessing the relevant function for that "menu".
    
    Most of the actual code is in /usr/local/lib/inx/ .
    
    Future development will probably clean this up somewhat, since
    as part of the process of making INX the author has learnt a bit 
    more, and now cringes at some of his earlier code ;-)
    
    It mostly works, though. Send bugs to the mailing lists :)