UPGRADE to version 1.1.2 1) Upgrading from 1.1.1 If you are upgrading from version 1.1.1, there are only two changes that should be done regarding configuration. - Change the home directory for the user root from '/' to '/root' in the file /etc/passwd.. - In the file pslave.conf, ports configured as protocol "telnet" or "socket_server" must have their parameter "socket_port" configured with a valid value. If the socket_port parameter is not configured, then 23 will be used. This new version brings the following new features: - Userauto : default user name for a port (profile TS only). - Two new parameters for Data Buffering in order to: . Write Data buffering into a NFS file . Disable DB menu presentation. - Changing in the portslave authentication process. For more information about these new features, please read the up-to-date Cyclades-TS documentation. 2) Upgrading from 1.1.0 If you are upgrading from version 1.1.0 make sure that there is no parameter initchat for ports configured as socket_server or socket_ssh. Also, Change the home directory for root as described in the previous section. This new version brings two new features: - Boot parameters configuration: using the program bootconf the user can configure all boot parameters including the Fast Ethernet operation mode (100bt Half/full, 10bt half/full, or auto negotiable) - Port access restriction: a new parameter s.users was created in order to define a group (set) of users that can or not can access a serial port. 3) Upgrading from version 1.0.x Many of the packages of TS version 1.0.1 were updated. So, If the user has a TS running a 1.0.x version, special care should be taken regarding configuration. In this document we assume that the TS is already running the new Linux Kernel Image (1.1.2) and that it will be the version used from now on. For those who are new to Linux/Unix, we recommend to read appendix A from the Cyclades TS Manual. The user can choose to start the configuration from scratch by simply doing: echo 0 > /proc/flash/script reboot Or the user must perform the steps listed below: 1 - The Openssh needs a new configuration file: /etc/ssh/sshd_config. The user must copy /etc/ssh/sshd_config.save over /etc/ssh/sshd_config and and redo his own changes, if any, in /etc/ssh/sshd_config. 2 - The portslave configuration file /etc/portslave/pslave.conf has many parameters created, changed or deleted. The user can just copy the file /etc/portslave/pslave.save over /etc/portslave/pslave.conf and redo his own configuration or perform the steps 2.1 to 2.5. PS. The prefix means "all", "s1", "s2", ... and so on. 2.1 The ppp option "uselib", that is into the parameters .autoppp and .optppp, must be changed to "plugin". 2.2 A new parameter .utmpfrom was created. Its default value is "%p:%P.%3.%4". This is the information that portslave will write in the "/var/run/utmp" file, where: %p - Port number %P - Protocol %3 - Third byte of remote ip %4 - Fourth byte of remote ip 2.3 The new portslave has only one modem string parameter ".initchat". The user should get a sample of this parameter in the new portslave configuration file /etc/portslave/pslave.save. 2.4 The following parameters should be deleted from the file: .waitfor .answer .aa .checkchat .checktime .stripname. 2.5 The parameters ".stopbit" and ".servername" must be respectively replaced with ".stopbits" and "serverfarm". 3 - The user must copy /etc/config_files.save over /etc/config_files and make his own changes again, if any, in /etc/config_files. 4 - The new TS version 1.1.2 has a ntpclient that can be activated by the script "/bin/ex_ntpclient". 5 - Before continue, make the changes that are stated in the sections Upgrading from versions 1.1.0 and 1.1.1 6 - If the user did not make any changes in the files /etc/inittab and /etc/rc.sysinit he must skip this step. If he had changed /etc/inittab, he must copy /etc/inittab.save over /etc/inittab and make his own changes again. If he had changed /etc/rc.sysinit he must copy /etc/rc.sysinit.save over /etc/rc.sysinit and make his own changes again. After saving the configuration (by running saveconf) and rebooting the TS, the upgrade is done. 7 - To run the new configuration and save it into flash the user must execute the commands: signal_ras hup saveconf