Why do I get the following error message every time I do a SOSUPD? I get the message whether or not I do the update as root:

06-Dec-10 12:37:23 Checking for SOSLIB updates...
06-Dec-10 12:37:24 Adding ini.vue: cur: , -1 bytes; new: 2008-01-15 14:14:2, 182 bytes
06-Dec-10 12:37:25 Backing up ini.vue to ini.001
06-Dec-10 12:37:25 Unable to copy ini.vue to ini.001 (error -2)
06-Dec-10 12:37:25 Aborting

The message does not indicate the location of the ini.vue file that has the problem. (PS: I was trying to do a SOSUPD, because my Linux SOSLIB has no copy of ATHTTP in it.)
.

That appears to have been a bug in SOSUPD. It was confusing the return status when looking up to see if the file existed, such that it was trying to back up a file that didn't exist. I've posted an improved sosupd.run 2.1(116) which you can download manually here and then run it.

Aside from probably dodging the error, it should also report the ppn that the files are in and the operating system error message that goes with the error.

The new SOSUPD fixes the problem (thank you), but it still does not report the ppn of the problem file (INI.VUE):

06-Dec-10 16:22:08 Updating xtra5.bp: cur: 2010-01-25 16:7:34, 39546 bytes; new: 2010-12-05 17:47:58, 40121 bytes
06-Dec-10 16:22:09 Backing up xtra5.bp (39546 bytes) to xtra5.001 [908021]
06-Dec-10 16:22:09 Hostex: unzip -o sosupd.zip >tskaac.tmp 2>&1
06-Dec-10 16:22:09 Archive: sosupd.zip
06-Dec-10 16:22:09 inflating: xtra5.bp
06-Dec-10 16:22:09 Adding ini.vue: cur: , -1 bytes; new: 2008-01-15 14:14:2, 182 bytes
06-Dec-10 16:22:10 Error downloading ini.vue
06-Dec-10 16:22:29 Updating xtra13.bp: cur: 2010-01-25 16:7:34, 13668 bytes; new: 2010-11-02 8:31:17, 14750 bytes

I added the ppn to "Backing up..." message (e.g. [980021] in the example above). I guess it could be added to some other messages as well (like the "Adding..." message).

It's probably ini.vue[907,9] which somehow slipped into to the library.

I guess it was time for a few updates to the SOSUPD program's UNIX update mode. I posted a newer version here: SOSUPD.RUN 1.2(117)

Among other improvements, this one will update itself before updating any other files (although that will only kick in after you've either run a complete update with an earlier version, or manually download the later version with the link above).

Another improvement is that if both the current and potentially updated files have A-Shell versions, that will determine whether the update is needed. Only if one or both is missing the version, or if the versions are the same, does it rely on the size and date information (much less reliable as to which is really a newer version). The Windows version has done this for some time, because it uses the UpdateCenter. But the UNIX mode was never (until now) updated to use the version info added some time ago to the UpdateCenter.

Lovely! The newest SOSUPD works very well and the mysterious INI.VUE was added to [907,9]. Thank you for fixing this.

06-Dec-10 22:01:03 Checking for SOSLIB updates...
06-Dec-10 22:01:06 Updating ateupd.run[901,2]: cur: 2010-12-4 12:7:23, 10254 b
06-Dec-10 22:01:06 Backing up ateupd.run (10254 bytes) to ateupd.001 [901002]
06-Dec-10 22:01:06 Hostex: unzip -o sosupd.zip >tskaac.tmp 2>&1
06-Dec-10 22:01:06 Archive: sosupd.zip
06-Dec-10 22:01:06 inflating: ateupd.run
06-Dec-10 22:01:06 Adding ini.vue[907,9]: cur: , -1 bytes, ver ; new: 2008-01-
06-Dec-10 22:01:07 Hostex: unzip -o sosupd.zip >tskaac.tmp 2>&1
06-Dec-10 22:01:07 Archive: sosupd.zip
06-Dec-10 22:01:07 inflating: ini.vue