Thanks, Carlos E. R., for kindly taking the time to write to me. Gratefully my problem of failing to obtain updates to software installed in an openSUSE-11.4, Linux operating system has been solved. But I’m not certain precisely why it has been solved or what the exact problem was; nevertheless I am happy that it has been solved. Basically I started another session using my computer in my friend’s mobile home with a fresh connection of an ethernet cable from an ethernet card to her modem, a fresh start of openSUSE 11.4, etc. And this time gratfully I could obtain the openSUSE-11.4 updates. Earlier yesterday or today when I was having the failure I wish I had tried some simple things like trying to visit a Web page in a browser, checking an ethernet cable connection, and looking for the Network Manager panel icon. But early I think I did a poor job in not checking and/or paying attention to those simple things; sorry about that.
In answer to some questions and comments of yours below is the output corresponding to the command “zypper lr --details” obtained while online in my installation of the openSUSE-11.4, Linux operating system.
linux-iy6k:~ # zypper lr --details
# | Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
1 | Updates for openSUSE 11.3 11.3-1.82 | Updates for openSUSE 11.3 11.3-1.82 | No | Yes | 99 | rpm-md | http://download.opensuse.org/update/11.3/ |
2 | http://download.videolan.org/pub/videolan/vlc/SuSE/11.4/ | http://download.videolan.org/pub/videolan/vlc/SuSE/11.4/ | No | Yes | 99 | rpm-md | http://download.videolan.org/pub/videolan/vlc/SuSE/11.4/ |
3 | openSUSE-11.3 11.3-1.82 | openSUSE-11.3 11.3-1.82 | No | No | 99 | yast2 | cd:///?devices=/dev/sr0,/dev/sr1 |
4 | repo-11.4-non-oss | openSUSE-11.4 Non-OSS | Yes | No | 99 | yast2 | http://download.opensuse.org/distribution/11.4/repo/non-oss |
5 | repo-11.4-oss | openSUSE-11.4 OSS | Yes | No | 99 | yast2 | http://download.opensuse.org/distribution/11.4/repo/oss |
6 | repo-11.4-update | openSUSE-11.4 Updates | Yes | No | 99 | rpm-md | http://download.opensuse.org/update/11.4 |
7 | repo-debug | openSUSE-11.3-Debug | No | Yes | 99 | NONE | http://download.opensuse.org/debug/distribution/11.3/repo/oss/ |
8 | repo-non-oss | openSUSE-11.3-Non-Oss | No | Yes | 99 | yast2 | http://download.opensuse.org/distribution/11.3/repo/non-oss/ |
9 | repo-oss | openSUSE-11.3-Oss | No | Yes | 99 | yast2 | http://download.opensuse.org/distribution/11.3/repo/oss/ |
10 | repo-source | openSUSE-11.3-Source | No | Yes | 99 | NONE | http://download.opensuse.org/source/distribution/11.3/repo/oss/ |
Sorry, I did not include the explanation of YaST2 in my previous posting here, namely Yet another Setup Tool 2. I think one reason I may have referred to Windows gigabytes as GiB could be because I may have read quite some time ago that Windows used GiB, of course in the case of hard-disk drives that have at least a GiB of capacity. But sorry, I realize that referring to Windows gigabytes as GiB is wrong or could lead to a mixup. I was aware that a GiB is a number of bytes which is some power of two resulting in 2**(that power) or 2^(that power) close, but not exactly equal to one billion (I saw from the Internet that that power of two is 30. And I see that 230=1,073,741,824). The new thing I learned from you is that GiB stands for gibibytes. So thanks for teaching me that. Also I see that openSUSE-11.3 also referred to a size in GiB. So I think it is better for me to refer to a GiB as 2^30 or 230 binary bytes, or else a gibibyte.
I found my notes written while making the online upgrade of openSUSE from version 11.3 to 11.4 during April 27-28, 2011. The steps I followed had a great overlap with the steps outlined at http://en.wikipedia.org/Upgrade on the Internet. I set up one third-party repository for downloading, namely Index of /pub/videolan/vlc/SuSE/11.4/ after changing 11.3 to 11.4 in that URL (Uniform Resource Locator). And I used this URL for the both the “Name” and “URL” fields for this repository. However, I think one of the zypper commands I used might have resulted in overruling that third-party repository with an openSUSE repository for VideoLAN software, which, if so, is okay with me, as long as that works.
During the downloading and/or installing of the upgrade software an early problem was that I had error number 30987, which I suppose was likely a result of my RedHat Package Manager (RPM) database being corrupt, based on someone else’s similar experience posted at Crash during update. Will not update. on the Internet. From that Internet reference I learned that I could enter the command “rpmdb --rebuilddb” to probably rebuild my openSUSE rpm database. Evidently and fortunately that gratefully worked for me to afterward avoid the error number 30987.
To reduce the risk of a possible non-working or partially non-working or so-called “broken” installation of openSUSE during an openSUSE upgrading process, other people could perform an online upgrade in an ideal way and in a way somewhat different than the way I did; but due to limited free disk space on the root partition of a hard-disk drive this way I am about to discuss may not be practical for everyone. I recommend that an openSUSE online upgrader (person): 1) backup his hard-disk drive. 2) Perform the online upgrade somewhere where he can have access to an Internet connection for many preferably, but I guess not essentially, non-stop hours, unless his Internet connection speed is extremely high. That could be in someone’s home, perhaps the upgrader’s own home. 2) Somehow find out how many GiB of downloading his upgrading is going to require. For me the answer was at least 2.35 GiB. I am not certain if it is possible to know the size of the download an upgrader will need before starting the downloading for his upgrade. But if that is possible, then an upgrader could perhaps prepare enough free space on his openSUSE root partition for the big download before he starts the downloading. If it is not possible to know that number of GiB before the downloading starts, then at least by shortly after the time an upgrader finishes typing “zypper ref” and “zypper dup,” he should be informed of the number of GiB of downloading an upgrade will require for him, at least for an openSUSE-11.3-to-11.4 upgrade. Then I would expect that the upgrader should be able to very quickly interrupt the downloading by briefly and simultaneously holding his computer keyboard’s “ctrl” and “C” keys to interrupt the downloading. Anyhow, before doing much, if any downloading I recommend that the upgrader prepare enough GiB of free space on his old version of openSUSE’s root partition for the entire download needed to make the upgrade of openSUSE. 3) With enough free space on the root partition of the hard-disk drive, instead of typing ‘zypper dup’, I recommend that the upgrader type 'zypper dup --download “in-advance” ’ using the double, but not the single quotation marks. I have not done that and have no experience with it. But I think the purpose of such a command is to first download all of the required software to make the openSUSE upgrade. Then after that the new software for the newer version of openSUSE is to be installed on the computer.
The advantage of using the 'zypper dup --download “in-advance” ’ command is that if there is a power failure, an Internet connection is lost, or for any reason the downloading has to be interrupted or the computer is or has to be powered off, he will still have a working openSUSE operating system, the lower version of it, of course not the newer version of it yet. Then after that I presume that the time to install the upgrade version of openSUSE would take less time than the downloading of the new software. If there is a problem of some kind during the installation of the new version of the openSUSE operating system, then the upgrader could restore his hard-disk drive’s software using his hard-disk drive backup that he hopefully made prior to starting the upgrade process and then try the upgrade procedure again.
However, in my case I used the “zypper dup” command which I think downloaded a software package, installed it, downloaded another package, installed it, etc. Doing things that way did not require a large volume of free disk space on my openSUSE-11.3 root partition. I probably could have arranged such free space using the program GParted (Gnu Not Unix) GNU Partition Editor]; but you could say I took the easy route of typing the command “zypper dup,” which included the risk of having a “broken” operating system, if something were to have gone badly wrong during the downloading and upgrading process. But I am grateful that fortunately after I completed the online upgrade using the “zypper dup” command, I was able to use a program I used quite often in the new, openSUSE-11.4 operating system. But as I think about things now, making the hard-drive backup and using “zypper dup” command may not be a bad way to do things, relying on the hard-disk-drive backup to, if necessary, restore the old, openSUSE operating system before the new one is in place and ready to use. Then in that case regarding the importance of making the hard-disk drive backup the saying, “Don’t throw away your old shoes until you get your new ones” seems appropriate here where the old shoes would be analogous to the old version of openSUSE and the new shoes would be analogous to the new version of openSUSE in the upgrade process.