Re: Clarification of Dselect & script question

[servis@purdue.edu]

*- Cristov Russell wrote about "Clarification of Dselect & script question"
| > Subject: Dselect & script
| > 
| > Recently I read somewhere (possibly on this list) that there is a way
| > to capture what was done during dselect using something like
| > /.../script but they did not go into much detail.  Could someone
| > explain to me how to do this?
| 
[snip]
| 
| I would use man to read the documention but I can't seem to get it
| working with the base installation.  Can anyone explain exactly how to
| do this.  I'm very new to Linux and totally green with Unix.
| 
| My thanks to those who replied to the earlier message. :-)
| 

% script /tmp/dselect.txt
Script started, output file is /tmp/dselect.txt
# dselect

[run as normal]


# exit(or ctrl-d)
%

Then you can review the output in the file /tmp/dselect.txt.  Since
dselect uses screen codes to move around the screen there will be lots
of garbage but the text from the install phase will all be normal.

The man page for script is short so I have included it below. 

-- 
Brian 
---------------------------------------------------------------------
"Never criticize anybody until you have walked a mile in their shoes,  
 because by that time you will be a mile away and have their shoes." 
							   - unknown  

Mechanical Engineering                              servis@purdue.edu
Purdue University                   http://www.ecn.purdue.edu/~servis
---------------------------------------------------------------------


SCRIPT(1)                    UNIX Reference Manual                   SCRIPT(1)

NAME
     script - make typescript of terminal session

SYNOPSIS
     script [-a] [file]

DESCRIPTION
     Script makes a typescript of everything printed on your terminal.  It is
     useful for students who need a hardcopy record of an interactive session
     as proof of an assignment, as the typescript file can be printed out lat­
     er with lpr(1).

     If the argument file is given, script saves all dialogue in file. If no
     file name is given, the typescript is saved in the file typescript.

     Option:

     -a      Append the output to file or typescript, retaining the prior con­
             tents.

     The script ends when the forked shell exits (a control-D to exit the
     Bourne shell (sh(1)),  and exit, logout or control-d (if ignoreeof is not
     set) for the C-shell, csh(1)).

     Certain interactive commands, such as vi(1),  create garbage in the type­
     script file.  Script works best with commands that do not manipulate the
     screen, the results are meant to emulate a hardcopy terminal.

ENVIRONMENT
     The following environment variable is utilized by script:

     SHELL  If the variable SHELL exists, the shell forked by script will be
            that shell. If SHELL is not set, the Bourne shell is assumed.
            (Most shells set this variable automatically).

SEE ALSO
     csh(1) (for the history mechanism).

HISTORY
     The script command appeared in 3.0BSD.

BUGS
     Script places everything in the log file, including linefeeds and
     backspaces.  This is not what the naive user expects.

4th Berkeley Distribution        June 6, 1993                                1