800-1460-05 READ THIS FIRST - SOFTWARE » Notes for Sun UNIX™ Release 3.2 October 8, 1986 Introduction Release 3.2 incorporates bug fixes, System V compatibility, support for ESDI disk drives, and support for the new Sun-3/110, 260, and 280 workstations. See the Release 3.2 Manual for details. Getting help Should you have any problems while installing or using your system, call Sun Technical Support at 800-USA-4SUN (800-872-4786). From Canada, call 800-225-2615. Have your system's model and serial numbers ready to give the dispatcher. Questions also can be sent by electronic mail to sunlhotline. Your mail should include your name, company, phone number, system model number and serial number, a description of your problem, and software release number. This service is provided at no additional charge for systems under warranty or covered by a support agreement. If you have questions about Sun's support services or your shipment, call your sales representative. Notes for Release 3.2: Errors in /usr/etc/termcap. The entry for wyse-50 has a colon instead of a vertical bar. The entry for wyse-925 on the 68010 tape also has erroneous colons. Source to Sun View examples now available. The source for most of the programs in the Example Programs appendix to the release 3.2 Sun-View Programmer's Guide (800-1345) is available in /usr/src/sun/suntool/examples. The source to seln_demo, a sophisticated selection monitor from the SunView System Programmer's Guide (800-1342), is also included. This directory is installed along with source for seme of the SunView programs and demos if you select SunView and Demo Program source from setup's Optional Software form. (If you are upgrading to 3.2, answer y to install Suntools_source.) Some of the examples are slightly improved from the versions in the manual. Subwindow layout policy changed. In release 3.0, when a frame was made smaller, either by the user's stretching the frame down or from a call to window_set (), there was a bug that sometimes caused the frame border not to be drawn. In release 3.2, the window layout management software now tries to preserve the frame border by resizing subwindows when the frame's size is changed: when a frame is made smaller, subwindows that cross the frame border are resized to fit within the frame; when a frame is made larger, sub-windows that are smaller than their requested size are resized (up to their requested size) to meet the frame border. This bug fix restores the behavior of release 2.0 SunWindows. READ THIS FIRST - SOFTWARE Page 1 Lockscreen bug. The -e option to the Sun View lockscreen program is broken. This option is meant to make available the ability to exit the SunView environment from which lockscreen is running without returning to SunView. Instead, when the [Exit Desktop] button is invoked, the tools are destroyed but the suntools program is not exited. Also, when running multiple instances of suntools on different screens, invoking [Exit Desktop] crashes the kernel. Locking NFS files. There is a bug which may cause reads on NFS files locked with lockf or fcntl to crash the server. The problem occurs only if the NFS client reads starting at an offset in the file which is not a multiple of 4, and the data bytes cross a block boundary on the server's filesystem. There is another bug which may cause reads on locked NFS files to read past end-of-file. To correct this, patch your kernel as follows: Sun-2: % adb -w /vmunix rwvp+14e?w e4 # previous contents Oxlca $q % adb -w /usr/sys/OBJ/nfs_vnodeops.o rwvp+14e?w e4 # previous contents Oxlca d> « Sun-3: % adb -w /vmunix rwvp+144?w e4 # previous contents Oxlce $Q % adb -w /usr/sys/OBJ/nfs_vnodeops.o rwvp+144?w e4 # previous contents Oxlce $q New Sun-3/2x0 fonts. New fonts more suited to the Sun-3/2x0 high-resolution monitor have been added to the font library; they can be substituted for the [smaller] default font in SunView. See page 81 of the Release 3.2 Manual for details. Disk errors on Sun-3/2x0 workstations. Disk errors of the form xy ). This bug seems to result from the keyboard UART being left in an improper state and therefore will not be seen on machines using terminals rather than Sun monitors/keyboards. Installing tapeless Sun-3's. On page 123 of the Installing UNIX manual (800-1521-05), the command given for copying mini-UNIX should be From: e_interface (0,host_number, 1) mini f s if you're installing a Sun-3 and your remote host has been installed as a file server. The "1" in this case refers to public partition 1. A "1" is not needed when booting (e.g. stand/copy on page 122) because of the link under /tftpboot. VME-to-VME adapters in a Sun-3/110. When a VME-to-VME adapter (Sun Option 160A) is used to install non-Sun hardware into a Sun-3/110, the adapter must have a part number of 501-1191-01 or higher. If the adapter is Sun part number 501-1059-01 or higher (earlier version of Sun Option 160A), you may not be able to boot the system. The Sun VME SCSI Controller that is mounted in the VME-to-VME adapter must be 501-1138-01 or higher. An earlier version of the Sun VME SCSI Controller (part number 501-1149-01 or higher) used in other Sun products (Sun-2/130/160 and Sun-3/160/180) will cause the system not to boot. Formatting SMD disks. The format command now reads the defect list and is therefore recommended instead of the fix command. Installing a file server as a remote host. If you plan to use the file server you are installing as a remote host for remote installation of another workstation, you will need an additional 5 megabytes of free space in /pub. Be sure to use the correct /pub filesystem (68010 or 68020). Knowledgeable users may wish to load mini-UNIX into a filesystem other than /pub. Installing servers. Networking tools and programs must be loaded when installing a server, or it will be unable to run the Yellow Pages and diskless clients will be unable to boot. Booting from SMD disks. When booting mini-UNIX on a VME-based workstation from a Xylogics disk controller jumpered for 20-bit addressing, the kernel may panic with an "unable to mount root" error when booting for the first time. When booted a second time (without reloading mini-UNIX), it should boot without any problems. Normally pins JM on the controller are jumpered for 24-bit addressing. Setup client cards. There are no client cards in setup for Sun models 2/100, 3/110, and 3/2x0. Use the 2/120 card for the 2/100, and one of the 3/160 cards for the 3/110 and 3/2x0 series. Note that the cards for the color workstations default to a 24-megabyte swap area. Using vtlOO consoles. Using terminal type "vtlOO" during setup will result in a core dump. Use terminal type "ansi". READ THIS FIRST - SOFTWARE Page 3 Using echo -n in Bourne shell scripts. If you specify System V behavior (e.g. PATH=/usr/5bin: $PATH), shell scripts which contain lines such as echo -n args will echo "-n args" with a trailing newline. Specify a path without /usr/5bin to get the 4.2BSD behavior. GP example source. The Software Interface Manual for the Sun Graphics Processor includes example applications for the GP; they are described in Appendix A of that manual. Machine-readable code is included in /usr/src/sun/demo/GPl/VIEWPORT. There are two errors in the source files for this package: In box.c, the routine init_gp should use the gpl_d function instead of ioctl's to get the minor device number and the static block. Change GP_fd = gpl_d(pw->pw_pixrect)->ioctl_fd; if ((ioctl(GP_fd, GP1I0_GET_STATIC_BL0CK, &GP_statblk) < 0) || (ioctl(GP_fd, GP1I0_GET_TRUMIN0RDEV, &GP_mindev) < 0)) { perror(" ") ; exit(O); \ j to GP_fd = gpl_d(pw->pw_clipdata->pwcd_prmulti)->ioctl_fd; GP_mindev = gpl_d(pw->pw_clipdata->pwcd_prmulti)->minordev; if ((GP_statblk = gpl_get_static_block(GP_fd)) < 0) { fprintf(stderr,"Cannot get static block\n"); exit(0); } In gpbuf .c, the gpb pointer is accessed before it has been initialized. Move the lines gpb->gpb_gfd - gpl_d(pw->pw_clipdata->pwcd_prmulti)->ioctl_fd; gpb->gpb_mindev = gpl_d(pw->pw_clipdata->pwcd_prmulti)->minordev; if ((gpb->gpb_sbindex = gpl_get_static_block(gpb->gpb_gfd)) < 0) error("Create_VP: cannot acquire GP static block\n", 0, 0); so they appear after the statement gpb « ObjAddr(gpbobj, GPDATA); pr_close no longer in pixrect library. pr_close is