
QNX BACKGROUND INFORMATION
USING THE SYSTEM INITIALIZATION FILE
D - 4
I-E96-107-2N
®
They are optional in a machine that boots over the network,
since the machine inherits this information from the node it
boots from.
export TZ=EST5DST4,M4.1.0/3,M10.5.0/3
rtc hw
For more information, see the following section on
.
Starting device
drivers
The following lines start the Device Manager and the console
driver with eight virtual consoles, then instructs the Shell to
reopen its standard I/O through the new console device.
Dev &
Dev.con -n 8 &
reopen //0/dev/con1
The following lines start up any other device drivers you may
need. They start both a serial driver, which will look for COM1
and COM2, and a parallel driver. These drivers will terminate if
they cannot find the necessary hardware.
Dev.ser &
Dev.par &
If you started “Dev.ser” you might need to use the “stty” utility
to change the default line configuration. For example, the fol-
lowing lines change the baud rate to 19200:
stty baud=19200 < /dev/ser1
stty baud=19200 < /dev/ser2
etc ...
Starting the
floating-point
emulator
If your programs use floating point and you do not have an
80x87 chip, you need to start the floating-point emulator:
emu87 &
Loading node
mapping
When booting a node on a network, you must run the “net-
map” utility, which informs the Network Manager of node ID
mapping. You should place the following “netmap” command
in the “sysinit.
node
” file, even if the node is not currently run-
ning on a network (the command has no effect on a non-net-
worked machine):
netmap -f
Note that this command is included in the standard sysinit
files shipped by QNX.