Hello Alex!
Thanks for your reply.
The upgrade did finish completely. At the end it said that 2.0.3 was upgraded to 2.0.5! I downloaded 2.0.6. So there was a mistake in the install.dat file, I beleive, but not serious. The only error that came at the end was that sessions.def could not be accessed, permission 644.
All the defs are 644. Could it be that it needed to change but could not and also hence no change in the table?
I never understand why it creates permissions 644 that I have no access to it. This has Happened will all the installations. I run cgiwrap/cgi-sys and make it working with my user id through the browser. Then this should not happen. For every installtion trial I have to send an email to my provider to change the permissions.
I start to beleive that 30 sec. CPU power may not be sufficient to install the big tar ball. The core files needs to be installed by steps of two or three, so that if it is interrupted then atleast there is no doubt about it. For e.g. Templates could be updates in one step, program files anathor, and the last step would be help files.
In the version number it shows 2.0.6! So the install went correct. However, I used the default table instal function and hence did not notice the change in the column name. But it looks like that it did not make the change.
An important idea would be that it tells the user what it does and where it stops, if thats easy. Otherwise I would have no way to find out what its doing.
Thanks for your reply.
The upgrade did finish completely. At the end it said that 2.0.3 was upgraded to 2.0.5! I downloaded 2.0.6. So there was a mistake in the install.dat file, I beleive, but not serious. The only error that came at the end was that sessions.def could not be accessed, permission 644.
All the defs are 644. Could it be that it needed to change but could not and also hence no change in the table?
I never understand why it creates permissions 644 that I have no access to it. This has Happened will all the installations. I run cgiwrap/cgi-sys and make it working with my user id through the browser. Then this should not happen. For every installtion trial I have to send an email to my provider to change the permissions.
I start to beleive that 30 sec. CPU power may not be sufficient to install the big tar ball. The core files needs to be installed by steps of two or three, so that if it is interrupted then atleast there is no doubt about it. For e.g. Templates could be updates in one step, program files anathor, and the last step would be help files.
In the version number it shows 2.0.6! So the install went correct. However, I used the default table instal function and hence did not notice the change in the column name. But it looks like that it did not make the change.
An important idea would be that it tells the user what it does and where it stops, if thats easy. Otherwise I would have no way to find out what its doing.
