If you want to capture the output from a command line session you might like to use the script command.
dsl@box:~$ script
Script started, file is typescript
dsl@box:~$ date
Wed Jan 19 15:26:43 EST 2005
dsl@box:~$ Script done, file is typescript
You hit CTRL+D to stop the recording and you will find a file called 'typescript' in the local directory that contains a log of what was recorded.
If you want to be able to replay these files then you need to record timing information as well as the typescript. Use the -t option to do this...
dsl@box:~$ script -t 2> timing.log
Script started, file is typescript
dsl@box:~$ date
Wed Jan 19 15:26:43 EST 2005
dsl@box:~$ Script done, file is typescript
You will see 2 files in the local directory; typescript and timing.log. You can now playback the files in realtime using the 'replay' command...
replay timing.log typescript
(By Robert Shingledecker)
The timezone shoud be working for US zones.
If you don't do anything the default is EST and setting your BIOS to local
time is OK for most uses.
Now, if you want to try setting your timezone, must be in US, the others
were cut for space reasons. Try this at the first boot prompt:
dsl tz=US/Pacific
This will set the timezone to PST8PDT with an offset based on EST.
or use this
dsl tz=US/Pacific utc
Then the offest will be based on the hardware, BIOS, clock set to UTC time.
You can easily add these boot options during the execution mkmydsl script,
so that your "custom" cd won't require typing them in everytime.
Also useful is the date command to set the system time
# date mmddhhmm (see date --help for all the options )
and then update the hardware clock with this command
# hwclock --systohc
Doing this you won't have to figure out the offsets.
You can query the hardware clock with this command:
#hwclock --show
To see the US zones that are supported take a peek at:
ls -l /usr/share/zoneinfo/US
The choice is yours on what time is to be store in the BIOS hardware clock.