Jim, reading between the lines of Adam's post (I can do this because of my experiences with working with him! :-), I think what he was trying to say was that it should be possible to do the following to smoothly upgrade from one release of the VM SSL server to the next.....
1) Install the new release, using a different VM user id and minidisk allocation. 2) Using Leland Lucius's E2 Rexx tool, write a "simple" Rexx exec that copies the necessary Linux files from the older SSL server to the newer release. 3) start the new SSL server, make sure it boots OK, and test it. 4) After it passes it's tests, shutdown the old release, delete it from the CP directory, and either rename the new releaser's user id to the old one, or update the TCPIP configuration files to point to the new one. E2 is a library and set of Rexx interfaces that allows a CMS-based Rexx exec to read *and write* a Linux ext2fs file system. Please feel free to contact me off list for more information on this, if any one would like to learn more about it. Adam was able (way to go, Adam!) to strip out even more "unnecessary" code and applications from the Linux kernel image, hence the size of the DDR shrinking from 250 cylinders to only 200. Jim Bohnsack wrote: > Something must have gotten dropped in this append from Adam Thornton. I > know that you're not just referring to a simple DDR because the Sine > Nominee 201 disk went down from 250 cyls in the previous distribution to > 200 cyls in the current one. Can you give me a hint regarding the > "following script". > > Jim > > At 07:52 PM 11/10/2005, you wrote: > >> "If this is an upgrade, then you should link your old SSL 201 disk at >> address 1201, and the new one at 2201, and run the following script." >> >> Should work fine. Just gotta find time to do it. >> >> Adam > > > Jim Bohnsack > Cornell Univ. > (607) 255-1760 -- Dave Jones V/Soft Software, Inc. Houston 281.578.7544
