The latest variant for RTU 6.1B is Variant 30. ================================================================================ RT-7000 Version 6.1BV30 Release Notes February 18, 1998 1. What's In This Kit The RT-7000 version 6.1BV30 kit includes the following items: 1. One 1/4-inch cartridge tape: Qty Label 1 RT-7000 V6.1BV30 2. These release notes. 2. Overview of Features RT-7000 Version 6.1BV30 is a variant release of RTU 6.1B that exists only for RT-7000 platforms. The 6.1BV30 release is intended to correct the following problems: o The kernel no longer panics with "page table walk failure" when trying to exec() programs with more than four megabytes of texts. (SCR 6746) o Modifications to executables on an NFS server are now properly reflected on the clients. (SCR 6397) o Several causes of segmentation faults in the kernel code for TCP/IP have been fixed. (SCR 6753) o Non-trapable SIGSEGV signals are no longer delivered when delivery of a ucb-style signal would cause the first reference of a user stack page. (SCR 6482, SCR 6785) o Fixed crashes in tcp_state. (SCR 6593) Situations which could cause a "duplicate soo_close" panic or could lead to kernel segmentation faults related to premature socket closure have been eliminated. (SCR 6803) Fixed the icmp_input message handling problem. (SCR 6811) RT-7000 Version 6.1BV30 Release Notes Page 1 o Fix the problem of 'mknod' when creating a device with major number > 127. (SCR 6835) o Fixed various tcp state machine problems that could leave a tcp connection in CLOSE_WAIT state and therefore prevent the same server process from being started as it says "Address already in use". (SCR 6843) o A potential source for rt-7000 kernel segmentation faults during data transfers between kernel and user spaces has been eliminated. (SCR 6817) o Fixed ssad driver so that write/rewind/read works as expected. (SCR 6601, SCR 6688). o MTIOCGET ioctl call will not return -1 when the drive is online. (SCR 6693) RT-7000 Version 6.1BV30 Release Notes Page 2 o Two new kernel configuration parameters sbmc_throttle and sbmc_blockmode have been added. The sbmc_throttle parameter can be used to reduce the VFSCSI/VSCSI throttle count calculated by the driver. The sbmc_blockmode parameter can be used to disable block mode. See comments in /etc/master.ex for details. (SCR 7082, SCR 7084) o Enable the reception of multicast packets over the lance driver. (SCR 7038) o A known problem exists where device numbers greater than 127 cannot be used. As a work around, the following major device numbers have been freed up for used by customers on the 7000 Series machines. Block devices: 64 through 126 Character devices: 6, 9, 11 through 16, 19, 22, 24, 29 through 34, 36 through 37, 48, 54 through 56, 60, 66, 74 through 78, 110 through 126. o Make tape 'rewind` and `retension` commands non-blocking. (SCR 6694) o Fix MP and parameter validation socket problems for send, sendmsg and sendto. (SCR 7183) The "make" command now supports file name longer than fourteen characters which may exist on xfs filesystems. (SCR 6598) o A system hang, sometimes caused by simultaneous, multiple attempts to change a process' pgrp, no longer occurs. (SCR 7132) o Fix SCCS get command to handle file name longer than 16 characters correctly. (SCR 6167) o Fix sockets to prevent ioctl's going downstream on all socket calls. (SCR 7181, SCR 7104, SCR 7157, SCR 7183) o Changed login(1) to run passwd(1) with the correct uid/gid so that the rules for password acceptance are enforced. (SCR 6705) RT-7000 Version 6.1BV30 Release Notes Page 3 o csh is fixed to handle a variable set to '/' when evaluating a 'if' statement. (SCR 6609) o When a UNIX socket is closed, a read at the other end of the socket was incorrectly returning an error (EIO). This fix ensures that a read in these circumstances returns 0 meaning other end has disconnected like it does for TCP sockets, other UNIXs and earlier versions of RTU. (SCR 7308) o Fix date(1) to handle year field correctly when year changes. (SCR 7130) o Prevent preemption of the exiting process after it sets it's state to S_EXITED or S_FREE because if preempted this process gets dropped from the runq and subsequent fork that receives this slot number for new process hangs because the exiting process did not exit completely. (SCR 7163) o Fix erratic Ethernet performance over the Integral Lance. (SCR 7452) RT-7000 Version 6.1BV30 Release Notes Page 4 o Allow the processing of closoure of lingering sockets in TCP (SCR 7462) Fix crash caused by corruption of stream service queue (BSQR 12162) o The tape operations, rewind and retension, are now configurable by the parameter noblock_tapeop. A value of one(1) implies non-blocking and a value of zero(0) implies blocking. By default it is set to non- blocking. To make it blocking enter a line as follows in your configuration file and reconfigure your system. (SCR 7447) noblock_tapeop 0 Please note: When these are set to non- blocking, other commands can be issued to the busy controller, which may generate "Device busy" message on the system console. This is not an error. o The config utility now generates valid code for more than 8 VME devices of the same type. (SCR 7483) o Fixes /bin/sh, so that it does not abort when wild card is used on nfs mounted IRIX partition. (SCR 7317) o Fixes deadlock in TCP code. (SCR 7659) o Direct I/O for small ( < 4KB ) files is repaired for consistent operation. o Fixed year 2000 and beyond date problems. 3. Corequisites If your system is running rt-unlu, you must install rt-unlu variant 6.0V1 with this variant. RT-7000 Version 6.1BV30 Release Notes Page 5 4. Prerequisites This kit is only to be loaded onto 7000 Series machines running version 6.1B of the RTU operating system. If you are installing RTU Version 6.1BV30 on a running system you will need approximately 6500 disk blocks on your system ("/") partition before you begin installing RTU Version 6.1BV30 on top of your current installation. RT-7000 Version 6.1BV30 Release Notes Page 6 5. Installation Procedure ** Read these release notes in their entirety before installing RT-7000 6.1BV30.** To install the RT-7000 6.1BV30 software kit, perform the following steps: 1. Login as root. 2. The /update directory, used to hold files from the cpio image previous to installation, must be empty. Change directory to /update and remove all the files and directories you find there. 3. Reboot to single-user mode using /etc/reboot: # /etc/reboot -s 4. Make sure you are in the AT&T universe: # universe att 5. Make sure your current directory is root: # cd / 6. Place the RT-7000 6.1BV30 tape into the drive and read it: # cpio -ivmCdu < /dev/rctp 7. Run the 6.1BV30 software installation script: # /install/i_rtu_6.1BV Successful installation will be indicated by the finished installation message of the install script. Original copies of certain files modified by the installation script are saved in the directory /PRE_RTU_6.1BV. To save space after the installation, you may remove this directory. RT-7000 Version 6.1BV30 Release Notes Page 7 RT-7000 Version 6.1BV30 Release Notes Page 8 CONTENTS 1. What's In This Kit............................................. 1 2. Overview of Features........................................... 1 3. Corequisites................................................... 5 4. Prerequisites.................................................. 6 5. Installation Procedure......................................... 7 RT-7000 Version 6.1BV30 Release Notes Page i