Miscellaneous porting hints
Additional tips for people used to SCO OpenServer 5:
To enter single user mode,
press <Enter> at the initial SCO logo screen
during the boot process to get a boot prompt (
the set the INITSTATE variable to 1:
You will get a console login prompt in init state 1.
Type ? or help at the
is the native SVR5 kernel debugger,
but a version of the SCO OpenServer 5
scodb kernel debugger
is also provided for SVR5.
Both debuggers can be installed
command then configured into the system;
kdb must be installed and configured
before you can run scodb,
but scodb is not required for kdb.
If both debuggers are configured into the kernel,
switch between them with the newdebug command.
For more information, see the following:
Dynamically Loadable Kernel Modules (DLKMs)
can be added to the kernel using the
Most DLKMs can be installed
with a command sequence such as the following,
executed from the directory that contains the driver's
# cd <directory_containing_DSP>
# /etc/conf/bin/idinstall -a -k -M <driver>
# /etc/conf/bin/idbuild -M <driver>
# modadmin -l <driver>
To unload the DLKM:
# modadmin -U <driver>
To show all loaded DLKMs, run:
# modadmin -S
All console messages that come from driver
calls are logged in the
When the system is rebooted,
this file is saved as
Panic dumps can be saved to a file
and analyzed with the
``Using crash and the kernel debuggers''
for general information about using crash.
``SCO crash quick reference''
provides a quick reference listing of the crash commands
that are supported on both platforms.
Note that you can write a module
to extend the SVR5 crash command.
For example, you could make it display structures
that are defined just for your driver. See the
manual page for more information.
© 2005 The SCO Group, Inc. All rights reserved.
OpenServer 6 and UnixWare (SVR5) HDK - June 2005