TCP/IP 4.25 Patch D for QNX® 4.25

Release Notes

Date of this edition: February 25, 2003

Host OS: QNX® 4.25


Note: This release note includes Runtime and Toolkit patches, but the patch letters aren't always in sync.

Contents...

Changes & fixes

Initial 4.25 release

The initial 4.25 release includes changes to the runtime and toolkit, as described below.

Initial 4.25 runtime

Initial 4.25 toolkit

Patch A release

In addition to the above changes, Patch A also includes changes to the runtime and toolkit, as described below.

Patch A runtime

Patch A toolkit

Patch B release

In addition to Patch A's changes, Patch B also includes changes to the runtime and toolkit, as described below.

Patch B runtime

nfsd
Patch A isn't compatible with nfsd, so a new nfsd has been included in Patch B. It corrects a problem where nfsd terminates with no explanation. It also corrects a problem where an attempt by a client to mount or use exported directories would fail or hang.

Patch B toolkit

socket3r.lib, socket3s.lib, socket_s.lib
Corrected a problem related to the processing of the hosts.equiv and rhosts files.
snmp3r.lib, snmp3s.lib, snmp_s.lib
Corrected a memory leak.
rpc3r.lib, rpc3s.lib, rpc_s.lib
Corrected a problem where sending a request too fast would cause a SIGSEGV.

Patch C release

In addition to Patch B's changes, Patch C also includes the following changes to the runtime:

Static linked utils
A small set of static link utilities was to be included with this release for use in embedded systems. This was because a few TCP/IP utilities and the shared libraries would require a lot more resources to store than the same utilities linked against the static libraries. The shared libraries in this case weren't as small as they could be.

But the new versions of the shared libraries are significantly smaller, so we believe that the static utilities are no longer needed.

Socket
The socket() function now returns EPFNOSUPPORT for AF_UNIX.
Sock(l)et
Sockppp
dhcp.client
lpd
lprrm
Corrected a problem related to reading directory entries.
lpr
Works with "vdir" manager.
portmap
Corrected a condition that may fail to detect a request from remote machine to register.
pppd
Corrected a race condition that may cause pppd to fail to detach itself from Sock(l)et.
rlogind and rshd
Both rlogin and rshd now support the + symbol in the hosts.equiv or rhosts file.
rtelnet
Corrected a SIGSEGV problem.
slinger
snmp_so.100
Corrected a memory leak.
snmpd
Obtained a new enterprise number for QNX.
socket_so.100
Corrected a problem related to the processing of the host.equiv and rhosts files.
telnetd
Corrected a problem related to an unnecessary controlling terminal FD passed to child process.
mib.txt
Added the new QNX enterprise number.
rpc_so.100
Corrected a condition that may fail to detect a request from remote machine to register.
mountd
nfsd
Corrected a problem with the parent's exiting when the -t option was specified to accept TCP connections only.
ping
Now returns the correct exit status.
tftp and tftpd
Corrected a bug where the size of data transferred was limited within 16M bytes.

Patch D release

In addition to Patch C's changes, Patch D also includes changes to the runtime and toolkit, as described below.

Patch D runtime

Socket, Socklet, and socket_so.100

Patch C toolkit

The following corrections were made to the socket libraries, socket3r.lib, socket3s.lib, and socket_s.lib:

Known issues


Caution: If you're updating from a version earlier than 4.23, note that the pathnames of some of the standard TCP/IP runtime executables have changed. During the install procedure, you'll be given an opportunity to have the paths to these executables corrected automatically in your inetd.conf file. You'll also be prompted to remove the old executables. Please check your inetd.conf file to make sure that all the entries are reasonable.

named.conf replaces named.boot

A named.conf file is now used instead of named.boot. If a named.boot file is found on the target system during the installation, you're asked if you want to automatically convert the file with the named-bootconf utility, or wait until the installation is complete to convert it manually or with the utility.


Note: If you use the utility, you must check the named.conf file to ensure it's converted properly.

You can find a sample named.conf file in /etc/config/socket.

Items no longer shipping

These items have been removed from the TCP/IP 4.25 runtime:

Symlinks

The 4.25 TCP/IP runtime isn't shipped with certain programs and configuration files that were part of earlier releases. If you've upgraded from an earlier release, see the following list of deleted symlinks and the location of the files:


Note: The X in tcprt/X/ is the location of your previous version (e.g. tcprt/4.23/).

Deleted symlink File location
/usr/ucb/ripquery /usr/tcprt/X/usr/ucb/ripquery
/usr/ucb/gated /usr/tcprt/X/usr/ucb/gated
/bin/Net.atm200 /usr/tcprt/X/bin/Net.atm200
/etc/config/socket/named.boot /usr/tcprt/X/etc/config/socket/named.boot
/etc/config/socket/gated.conf.anl /usr/tcprt/X/etc/config/socket/gated.conf.anl
/etc/config/socket/gated.conf.aarnet /usr/tcprt/X/etc/config/socket/gated.conf.aarnet
/etc/config/socket/gated.conf.bgp-simple /usr/tcprt/X/etc/config/socket/gated.conf.bgp-simple
/etc/config/socket/gated.conf.concert-net /usr/tcprt/X/etc/config/socket/gated.conf.concert-net
/etc/config/socket/gated.conf.egp-simple1 /usr/tcprt/X/etc/config/socket/gated.conf.egp-simple1
/etc/config/socket/gated.conf.egp-simple2 /usr/tcprt/X/etc/config/socket/gated.conf.egp-simple2
/etc/config/socket/gated.conf.rip-simple /usr/tcprt/X/etc/config/socket/gated.conf.rip-simple

Network drivers

There's a report that if you start multiple Net.epic drivers and then start Sock(l)et, then Sock(l)et faults. This might happen if the drivers initialize themselves slowly.

The solution is to put a short sleep after starting your network drivers.

Documentation

To read our HTML-based online documentation, use the Photon Helpviewer, our Voyager HTML browser, or any HTML browser.

If you don't have Photon, you can use tmhv, a text-mode help viewer that we've posted in /usr/free/utils on QUICS. This will let you view the online docs, but with some limitations (for example, tmhv can't display images and doesn't handle tables properly).

Technical support

To obtain technical support for any QNX product, visit the Technical Support section in the Support area on our website (www.qnx.com). You'll find a wide range of support options, including our free, web-based Developer's Network.