| Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
| Notice: | Welcome to the Digital UNIX Conference |
| Moderator: | SMURF::DENHAM |
| Created: | Thu Mar 16 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 10068 |
| Total number of notes: | 35879 |
Hello folks, my customer tries an update fron V3.2c to V4.0. After loading the software-subsets the following error message is displayed an the update installation stops (instead of starting the merge): . . . 100 of 100 subset (s) installed successfully /updmnt/isl/updeng: cannot shift Customer says, there is no logfile. I recommended him to restore to V3.2c and verify the old subsets before retrying an update to V4.0. But: does anyone know what this error message means? I'm thankfull for any ideas or hints. Thank-you in advance, Corina
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 9020.1 | NETRIX::"[email protected]" | Bob Fedorchak | Tue Mar 04 1997 11:47 | 19 | |
I have taken a look at the updeng script and found where the error occurs. However, I would need to look at the /etc/fstab file in order to determine why the error occurs. My guess is that there is either an erroneous entry or a comment which contains the substring "sw". The code within the V4.0 updeng script looks for the "sw" string and then parses for the first and fourth fields on that line. If the fourth field does not exist then the script will produce an error when the shift occurs. The routine which performs the shift was removed in the V4.0B release, so V4.0B and later releases will not have a problem here. If I could look at the /etc/fstab file I could determine which lines are causing the problem. Regards, Bob Fedorchak [Posted by WWW Notes gateway] | |||||