Update Pack 1 was delivered with the following features. See the section Problems Fixed for the maintenance fixes included in the current Update Pack, and the section Known Problems for limitations and workarounds.
The DocView documentation server displays the UnixWare documentation set on port 8458, and is enabled by default for network access. Point any browser on your network at http://hostname:8458, where hostname is the network node name of the UnixWare system, or localhost if you are logged into the system running DocView.
Two enhancements have been made to DocView:
A crontab file entry that generates the DocView index automatically when changes are made to the installed documentation has been added to the root crontab file. The crontab entry runs indexing every day at 0310 hours (3:10 AM local time), and is enabled by default. This process can take a significant amount of time depending on the amount of documentation being indexed and available system resources. The crontab entry is enabled and disabled using the following commands:
# /usr/lib/docview/conf/set.rundig.cron --add # /usr/lib/docview/conf/set.rundig.cron --remove
To change the time that the script is run, log in as root and enter:
# EDITOR=/bin/vi crontab -e
The command above edits the root crontab file using the vi(1) editor. The crontab entry that starts DocView indexing looks like this:
10 3 * * * /usr/lib/docview/conf/rundig.crontab > /dev/null 2>&1
Change the time as needed, following the file format shown on the crontab(1) manual page. Save your changes to the file, and exit the editor.
A new printing interface has been added that allows you to pick a group of topics to be printed as a book.
Selecting the Print Book button at the top of the DocView screen opens a copy of the DocView Site Map, from which you can select topics by turning on the check boxes next to the listed topics. At the top of the Print Service screen, select whether you want to generate a PostScript or PDF file. Specify a title for the book, and the heading level to be used in the table of contents.
Select the Submit button to collect the selected topics and format them for printing. The cover and custom table of contents are generated and added to the beginning of the document, and the results are paginated appropriately.
When DocView is finished preparing the file, it displays a screen telling you the size of the file and the number of pages in the document. Select the Proceed with download button to start downloading the file to your browser (this requires appropriate plug-in support in the browser), or save it to a file on your local system.
The resulting files can be viewed with any PostScript or PDF viewer; this includes xpdf and gs (GhostScript) under UnixWare or the Linux Kernel Personality (LKP), and Adobe Acrobat on Windows) or any PDF-enabled browser. PostScript files can be printed to any UnixWare PostSript printer via lp, as in this example:
$ lp -T PS -d printer file
Note that the assembled PDF or PostScript file is limited to about 1.5MB of HTML text, or about 600 pages. If your selections exceed this limit, an error message is displayed. Select your browser's Back button to go back to the Print Service screen and turn off some of your selections.
Also note that the Print Book interface works only with non-multibyte text; multibyte text, such as that found in Asian-language files, can be printed using the browser's Print interface (if the proper language support is installed on your system and in your the browser). Display the document either by navigating to it through the DocView menus, or using the DocView Site Map button (which is organized the same as the Print Book interface). Then, print the document using the browser's Print command (File > Print in Netscape and Mozilla).
The emergency_disk(1M) command supports creating an emergency recovery boot CD, as an alternative to using boot floppies. In previous releases, a set of emergency recovery floppy disks was required to boot the system. This meant that your system had to have a 3.5-inch floppy disk drive in order to be restored from emergency recovery media. This is a problem for newer systems that do not support IDE floppy drives. Now, emergency_disk can create a boot CD using CD-R or CD-RW media on an IDE, SCSI, or USB recordable CD drive, so that boot floppies are no longer required. See the emergency_disk(1M) manual page for more information.
Note that the cdrtools package (found on the UnixWare 7.1.3 Optional Services CD #3) is required to create an emergency recovery boot CD, and that only CD-R, CD-RW, and DVD+RW drives that work with cdrtools are supported for emergency recovery.
To test a particular drive to see if it will work with emergency_disk, enter the cdrecord commands shown below. The first command returns the arguments you need in the second command. The second invocation of cdrecord should return the string shown as part of its output:
# /bin/cdrecord -scanbus # /bin/cdrecord -inq dev=scsibus,target,lun ... Device seems to be: Generic mmc CD-RW. ...
The following CD drives are known to work with emergency recovery:
Problems have been observed with the IOMEGA ZIPCD USB drive and the OPTORITE CD-RW CW4802 IDE drive.
To prevent a timeout problem when burning a CD using an IDE CD-RW drive, the following value in /etc/conf/pack.d/ide/space.c is changed by the installation of the Update Pack from:
int atapi_timeout=10;
to:
int atapi_timeout=1000;
If you use cdrtools to burn CDs on an IDE hard drive but do not install the Update Pack, you can edit /etc/conf/pack.d/ide/space.c to make the above change, rebuild the kernel (idbuild -B), and then reboot (shutdown -i6 -g0 -y).
When restoring the system using emergency recovery boot media (CD or floppy), a new option to
write the master boot record (MBR) of the primary hard disk is displayed.
This option writes the UnixWare MBR to the boot sector of the primary hard disk.
This option is useful if the disk is known to have a valid operating system (OS) on it,
yet the error No OS found, No operating system,
or a similar message is displayed when you attempt to boot from the disk.
Writing the MBR may permit the disk to boot without further recovery.
Note: any other OS boot loader in the boot sector (such as grub, lilo,
or System Commander) will be overwritten by this option.
The following Host Bus Adapter (HBA) drivers are new or updated:
A new LSI Logic PCI to SCSI and Fibre Channel host adapter driver for LSI Logic Ultra320 and Fibre Channel chipsets. For supported devices and other information, see mpt(7).
Updated QLogic PCI FC host adapter driver to fix problems reported when removing disks from an IBM ESS Storage Area Network (SAN) Cabinet. For supported devices and other information, see qlc2200(7).
These drivers are not installed by the Upgrade Wizard (uli), unless (in the case of qlc2200), a previous version exists on the system. To install them, use the pkgadd command as shown in the section Installing Additional Packages after the Update Pack Set.
Also see the Compatible Hardware Page for the latest supported HBAs and drivers.
The nd package on the Update Pack CD contains updated versions of the following network interface card (NIC) drivers, which now support the indicated network cards:
PRO/100+ Management Adapter (PILA8900) PRO/100 Server (PILA8480) Pro/100B T4 (PILA8475B) PRO/100 S Server (PILA8474B) PRO/100 S Server (PILA8474BUS) PRO/100+ Dual Port Server Adapter (PILA8472) PRO/100+ Server Adapter (PILA8470) PRO/100+ Server Adapter (PILA8470B) PRO/100+ Dual Port Server Adapter (61PMCA00) PRO/100 (PILA8465) PRO/100B Adapter (PILA8465B) InBusiness 10/100 Adapter (SA101TX) PRO/100 S Management (PILA8464B) Pro/100+ Management Adapter (PILA8461) Pro/100+ (PILA8460) Pro/100+ Management Adapter (PILA8460B) Pro/100+ (PILA8460BN) PRO/100 S Management (PILA8460BUS) Pro/10+ (PILA8500) Pro/10+ (PILA8520)
PRO/1000 Gigabit Server Adapter PWLA8490 PRO/1000 Gigabit Server Adapter PWLA8490G1 PRO/1000 F Server Adapter PWLA8490SX PRO/1000 Gigabit Adapter PWLA8490SXG1P20 PRO/1000 T Server Adapter PWLA8490T PRO/1000 T Server Adapter PWLA8490TG1P20 PRO/1000 XT Server Adapter PWLA8490XT PRO/1000 XT Server Adapter PWLA8490XTL PRO/1000 XT Lo Profile Server Adapter PWLA8490XTL PRO/1000 XF Server Adapter PWLA8490XF IBM Netfinity Gigabit Ethernet SX Adapter 09N3599 IBM Netfinity Gigabit Ethernet SX Adapter 30L7076 IBM Gigabit Ethernet SX Server Adapter 06P3718 IBM Gigabit Ethernet Server Adapter 22P4618 PRO/1000 MT Desktop Adapter PWLA8390MT PRO/1000 MT Server Adapter PWLA8490MT PRO/1000 MT Dual Port Server Adapter PWLA8492MT PRO/1000 MF Server Adapter PWLA8490MF PRO/1000 MF Dual Port Server Adapter PWLA8492MF
You can select the nd package when you use the Upgrade Wizard to install the Update Pack CD. To add the nd package separately, see the instructions in the section Installing Additional Packages after the Update Pack Set.
The UnixWare 7.1.3 nd package can also be installed on Release 7.1.1 and Release 7.1.2 (also known as OpenUNIX 8.0.0) to update the network drivers or to take advantage of the enhanced tcpdump functionality (see tcpdump Enhancements).
Please note the following when installing the Release 7.1.3 nd package on Release 7.1.1:
You will also need to install ptf7689b
(
view text file |
download) on Release 7.1.1 before installing the updated nd package; otherwise
the latest tcpdump fails on Release 7.1.1 with the message
dynamic linker: tcpdump: binder error: symbol not found: strlcpy.
During installation on Release 7.1.1, the error UX:grep: ERROR: cannot open
/etc/inst/nd/mdi/shrkudi/Master: No such file or directory is displayed.
This error affects the UDI shrk driver only, which is not supported on
Release 7.1.1.
Use the MDI version of the shrk driver instead.
See the Compatible Hardware Page for the latest supported network cards and drivers.
Poor system and network performance has been observed on some systems when one or more of the Network Interface Cards (NICs) attached to the system is unplugged from the network. This was due to repeated failure indications being sent to the dlpid(1M) daemon.
In Release 7.1.3, a change was made to dplid to correct this problem. dlpid was changed to check the time between successive hardware failure indications. If the time difference is less than 10 seconds, dlpid sleeps for a 10 second interval before trying the device again.
dlpid has been further extended to sleep for a configurable duration between successive hardware failure indications, to allow the NIC to reset and come out of the failure mode, in cases where the default 10-second wait is not enough time for the NIC to reset. A new dlpid option, -r, is added to wait for the specified time. By default it is set to 10 seconds. If the pre-7.1.3 behavior is required (i.e., no wait between successive hardware failure indications), then dlpid can be started with the -r option set to 0.
Various enhancements were made to the pppd(1M) daemon to enhance the reliability and scalability of Point-to-Point Protocol (PPP) connections. Most of these improvements were made to driver code, and so are not visible at the user level. Some are listed in the section Problems Fixed.
A System V lp(1) filter has been added to allow printing of PostScript files (such as those created by Netscape) to be printed on PCL Printers (such as Hewlett-Packard). To enable this feature:
Check to see if GhostScript is already installed, by entering:
pkginfo gs
If it is not installed, install the gs package from the Update Pack as shown in the section Installing Additional Packages after the Update Pack Set.
Define a PCL printer using the scoadmin printer interface.
Enter a command like the following to print a PostScript file on the printer.
lp -TPS -d pcl_printer file.ps
Where pcl_printer is the name of the printer and file.ps
is the name of the PostScript file.
This command (without the file name) can be specified in your browser's
preferences to print files automatically to this printer.
Version 3.7.1 of tcpdump(1M) is provided, along with its supporting library, libpcap(3) (version 0.7). The tcpdump utility allows you to view and save TCP headers passing through a particular network interface. Boolean expressions can be used to select only those headers that match the criteria given by the expression.
This version of tcpdump has many enhancements over the version (3.4a5) provided in UnixWare 7.1.3. Most notably, the new version does not require a dedicated network card for tcpdump. Multiple instances of tcpdump can be started to monitor the same card. See the tcpdump(1M) and pcap(3) manual pages. Also see the tcpdump web site for libpcap tutorials, as well as tcpdump and libpcap source code.
A number of changes to the MDI and DLPI interfaces were made to support the new version of tcpdump.
Two new MDI ioctl commands are added for MDI2.2 drivers, to turn promiscuous mode
on and off: MACIOC_PROMISCON and MACIOC_PROMISCOFF.
MACIOC_PROMISCON is compatible with MACIOC_PROMISC in MDI2.1.
The following DLPI2.0 features are also implemented:
DL_PROMISCON_REQ and DL_PROMISCOFF_REQ primitives.To support the above changes, updated header files dlpimod.h and mdi.h are provided in the nics package, as well as the updated support for running tcpdump on a non-dedicated network card. tcpdump, libpcap, and related header files are provided by the nd package. If the nd package is installed without the updated nics package, the updated tcpdump, etc., are installed, but must be used with a dedicated network controller as in previous releases.
The updated nd package can also be installed on Release 7.1.1 and Release 7.1.2 (Open UNIX 8.0.0) if the latest version of tcpdump is desired. The nics package is not supported and will not install on these earlier releases, however, so tcpdump on Release 7.1.1 and 7.1.2 will continue to require a dedicated network card.
The following minor modifications have been made in order to maintain conformance to the UNIX95 standard:
The dd command was modified to accept and ignore a double dash (--) as an end of options indicator. Note that dd has no options that begin with a dash (-), so "--" can only appear as the leading argument and consequently has no real purpose.
The sort command has been modified to remove its previous (mistaken) UNIX95 behavior.
Previously, when using sort -c with the POSIX2 environment
variable set, sort only indicated whether the input was sorted through its exit value.
Now, sort -c will always return a diagnostic if the input is out of order (regardless of whether
POSIX2 is set or not).
Previously, the two supported Korn shells (/bin/ksh and /u95/bin/sh) did not recognize an integer literal with a leading 0 as being octal, nor a leading 0x or 0X as hexadecimal in arithmetic constructs. This does not match the intent of the POSIX.2 and Open Group shell specification. So, for example, the following output was seen in previous versions of the Korn shell:
$ echo $((10+1)) 11 $ echo $((010+1)) 11 $ echo $((0x10+1)) /u95/bin/sh: 0x10+1: arithmetic syntax error
A change has been made to accept octal and hexadecimal specifiers as explained above when the
POSIX2 environment variable is set:
$ export POSIX2=on $ echo $((10+1)) 11 $ echo $((010+1)) 9 $ echo $((0x10+1)) 17
Note that because integer constants like 010 have a silent change in behavior,
this change requires POSIX2 to be set in the environment.
Minor namespace changes were made to the following header files:
arpa/inet.h netdb.h netinet/in.h netinet/in6_f.h netinet/in_f.h fmtmsg.h grp.h libgen.h pwd.h stdarg.h strings.h unistd.h utmp.h utmpx.h wchar.h sys/fcntl.h sys/stat.h sys/statvfs.h sys/convsa.h sys/stropts.h sys/mman.h sys/socket.h sys/un.h sys/regset.h sys/siginfo.h sys/ucontext.h sys/fp.h
© Copyright 2003 The SCO Group, Inc. All rights reserved.