[SATLUG] Help with tutorials

redpill-master toddwbucy at grandecom.net
Mon Jun 22 19:50:48 CDT 2009



thanks for the info command.  it works in ubuntu as well. it seems to
offer more options then the gui devhelp.

Todd

On Mon, 2009-06-22 at 19:35 -0500, Geoff wrote:
> redpill-master wrote:
> > I was searching through my /usr/share/doc looking for an interesting
> > tutorial to run myself through when I suddenly realized that there has
> > got to be a better way then doing this through my file manager.  I was
> > wondering if anyone knew if there was a app (within Ubuntu) which would
> > add a menu folder labeled tutorials which would have all of the various
> > tutorial packaged within the Ubuntu distro already listed.  this would
> > not necessarily need to be a menu option it could for instance modify my
> > firefox by adding bookmarks to the relavant html pages.
> >   
> 
> On my SuSE 10.3 box, there's a command called "info".
> 
> (pardon the past if the formatting doesn't come out right)
> 
> File: dir, Node: Top This is the top of the INFO tree
> 
> This (the Directory node) gives a menu of major topics.
> Typing "q" exits, "?" lists all Info commands, "d" returns here,
> "h" gives a primer for first-timers,
> "mEmacs<Return>" visits the Emacs manual, etc.
> 
> In Emacs, you can click mouse button 2 on a menu item or cross reference
> to select it.
> 
> * Menu:
> 
> Utilities
> * Enscript: (enscript). GNU Enscript
> * Gzip: (gzip). The gzip command for compressing files.
> * ZSH: (zsh). The Z Shell Manual.
> 
> Libraries
> * AA-lib: (aalib). An ASCII-art graphics library
> * History: (history). The GNU history library API.
> * Readline: (readline). The GNU readline library API.
> * libIDL2: (libIDL2). Interface Definition Language parsing library.
> 
> 
> Texinfo documentation system
> * Info: (info). How to use the documentation browsing system.
> * info standalone: (info-stnd). Read Info documents without Emacs.
> * infokey: (info-stnd)Invoking infokey. Compile Info customizations.
> 
> Individual utilities
> * aclocal: (automake)Invoking aclocal. Generating aclocal.m4.
> * autoconf: (autoconf)autoconf Invocation.
> How to create configuration scripts
> * autoheader: (autoconf)autoheader Invocation.
> How to create configuration templates
> -----Info: (dir)Top, 351 lines
> --Top----------------------------------------------------------------------------
> Welcome to Info version 4.9. Type ? for help, m for menu item.
> 
> or, how about... info mount?
> 
> File: *manpages*, Node: mount, Up: (dir)
> 
> MOUNT(8) Linux Programmer's Manual MOUNT(8)
> 
> NAME
> mount - mount a file system
> 
> SYNOPSIS
> mount [-lhV]
> 
> mount -a [-fFnrsvw] [-t vfstype] [-O optlist]
> mount [-fnrsvw] [-o options [,...]] device | dir
> mount [-fnrsvw] [-t vfstype] [-o options] device dir
> 
> DESCRIPTION
> All files accessible in a Unix system are arranged in one big tree, the
> file hierarchy, rooted at /. These files can be spread out over sev-
> eral devices. The mount command serves to attach the file system found
> on some device to the big file tree. Conversely, the umount(8) command
> will detach it again.
> 
> The standard form of the mount command, is
> mount -t type device dir
> This tells the kernel to attach the file system found on device (which
> is of type type) at the directory dir. The previous contents (if any)
> and owner and mode of dir become invisible, and as long as this file
> system remains mounted, the pathname dir refers to the root of the file
> system on device.
> 
> Three forms of invocation do not actually mount anything:
> mount -h
> prints a help message;
> mount -V
> prints a version string; and just
> mount [-l] [-t type]
> -----Info: (*manpages*)mount, 1506 lines
> --Top------------------------------------------------------------------
> Welcome to Info version 4.9. Type ? for help, m for menu item.
> 
> Let your imagination run wild, with what information you need.
> 
> -Geoff
> 



More information about the SATLUG mailing list