This directory contains the images from servergate that form ptf 0013. I am told that this includes all the previous fixes ... i.e you can apply this update to a vanilla 1.3 system. The files in this directory comprise:- boot.sm.1 .......... Boot Diskette for the small kernel boot.sm.2 .......... Boot Diskette for the small kernel boot1 .............. Boot Diskette for the large kernel boot2 .............. Boot Diskette for the large kernel install ............ Install Diskette maint .............. Maintenance System Diskette netmagic ........... Network Install Diskette (????) mcc ................ lpp image for the Meteware High C compiler (included from updates 0006) set1 ............... Updates to the base system and kernel. set1.x Same as the set1 file, but as diskette images instead of one big file set2 ............... Updates to tcpip, Merge and x25 This includes the long-awaited SL/IP set2.x Same as set2, but in diskette image form set3 ............... Updates to admn, extp, man, adst, ibm-iaa, ate, gsl, tfs, rtmc(/usr/nifl) set3.x Same as set3, but in diskette image form. set4 ............... Updates to X11, Motif, x_st_mgr set4.x Same as set4, but in diskette image form snmp.1 ............. snmp lpp Diskette 1 snmp.2 ............. snmp lpp Diskette 2 snmp.3 ............. snmp lpp Diskette 3 *.install.notes .... The "Memo to Users" for each "set" in SCRIPT SOURCE format ... I did a concatenation and scripted the concatenated file on VM to read them. I have installed all of this on my machine EXCEPT for "snmp". My impression is VERY favourable. The whole system has speeded up and many bugs have been fixed. ******************************** * Instructions * ******************************** Boot diskettes ... use ONLY the LARGE boot diskettes .. the small ones do not work properly mcc and snmp should be applied using "installp" The updates in set1-4 should be applied using "updatep". After each update you will need to commit it before you can proceed to the next one. The files set1-4 are BACKUP images and their content can be reveiwed using "restore -Tvf". As you use "updatep", you will be asked to read various instructional files ... TAKE NOTE OF WHAT THEY SAY and do those things!! set1 ... changes to /etc/master and /etc/predefined. These are done to copies of the real files ... see instructions. set2 ... nothing special here set3 ... dec.ti is changed ... as with /etc/master, see the instructions. run "tic" against the changed file. set4 ... If you have the Image Adapter installed then you must rebuild the X-server ... cd /usr/lpp/X11 and rune "lpp.makeX". ******************************** * Console Colours * ******************************** Provision now exists for you to set the foreground and background colours for the console. The colours are the by numbers similar to ANSI escape sequences in DOS. The colours are:- 0 .. black 1 .. red 2 .. green 3 .. yellow 4 .. blue 5 .. magenta 6 .. cyan 7 .. white Leastways, that is what it looks like to me!! I assume that there are no others, but I have not tried any other combinations. NOTE WELL that it is possible for you to end up with a default colour setting of BLACK on BLACK ... really cool!! ... this is caused by the install script not copying "a.conf.o" to "conf.o" in directory "/usr/sys/386" ******************************** * SL/IP * ******************************** At last !! I have configured and run SL/IP successfully, BUT not without some grief. See the man page for "sliplogin", which is what is used to invoke Sl/IP. NOTE that you do not need an slattach ... sliplogin does it all. You will need to rebuild the kernel with a changed /etc/master. Look at the stanza for "slip:" and change "mandatory" from FALSE to TRUE. Also, the release notes list an entry for /etc/system which, in my case, was not inserted. I have yet to retry Sl/IP with this entry in place. I have run SL/IP successfully using a hardwired connection via a null modem to an RS6000 running AIX 3.2.3. I found that I had to configure the tty as local (not modem) and set "clocal" via stty. I had to do this both on the PS/2 and on the RS6000. I am sure that my problems are because I do not have the RS6000 tty configured properly, but I do not know at this stage what the proper settings should be. I will try and get some help from AIXSLIP forum or something. One problem that I have seen is that once a SL/IP connection is up, then if the other end dies, the PS/2 end will die also. If you now try and restart the PS/2 end, the "ifconfig" command invoked by "sliplogin" from "/etc/slip.login" fails. For example, if I start slip from "root" using:- "sliplogin -t /dev/tty0 -b 19200" and with an entry in "/etc/slip.hosts" of root 129.34.80.2 129.34.80.1 0xffffff00 1024 normal then it all works ok. If, subsequently SL/IP goes down, then the next time I issue the "sliplogin", the consequent "ifconfig" ... "ifconfig sl0 inet 129.34.80.2 129.34.80.1 netmask 0xffffff00 up" fails because it does not like the destination address. It returns:- ifconfig: ioctl(SIOCSIFDSTADDR): address not supprtd by protocol family The trick to getting it all running is first to issue:- "ifconfig sl0 inet 129.34.80.2 " and then:- "ifconfig sl0 inet 129.34.80.2 129.34.80.1 netmask 255,255,255,0 up" Don't ask why!! However it does mean that you must change "/etc/slip.login" to do these commands or to return 0 whatever happens and then you issue the commands yourself. You MUST have the right words and music in /etc/slip.hosts I had to fiddle around with tty settings, using "kermit" to check for data and correct speed etc. Once I got each end OK, I got a goodd connection and could do all the nice IP things. However, repeating what I did in a predictable way was something else. So SL/IP works!! but we need to do some research in order to get it running predictably. Of course it may all be a lot easier if you have modems and dialing and the like, because things like "RTS, CTS and DTR" are all handled properly whereas with null modems it is all a bit of a kludge.