When I attempt to proceed from terminal with zypper, I get:
947 packages to upgrade, 3 to downgrade, 150 new, 51 to remove, 1 to change
vendor, 13 to change arch.
Overall download size: 701.1 MiB. After the operation, additional 262.0 MiB
will be used.
Continue? [y/n/?] (y): y
Do you agree with the terms of the license? [yes/no] (no):
Aborting installation due to user disagreement with openSUSE product license.
linux-xmay:/home/randall #
What happened there is, after I typed y for yes to continue, the license agreement appeared; I scrolled to the end and typed q and hit enter. Then the curser goes straight to the next prompt not giving me the option to agree to the terms of the license. It is as though zypper inserts the “(no)” on its own accord – never mind me.
linux-xmay:/home/randall # zypper ref
Repository ‘openSUSE-11.2-Non-Oss’ is up to date.
Repository ‘openSUSE-11.2-Oss’ is up to date.
Repository ‘openSUSE-11.2-Update’ is up to date.
All repositories have been refreshed.
linux-xmay:/home/randall # zypper in zypper libzypp
Loading repository data…
Reading installed packages…
‘zypper’ is already installed.
‘libzypp’ is already installed.
Resolving package dependencies…
The following package is going to change vendor:
openSUSE-release openSUSE Build Service -> openSUSE
947 packages to upgrade, 3 to downgrade, 150 new, 51 to remove, 1 to change
vendor, 13 to change arch.
Overall download size: 701.1 MiB. After the operation, additional 262.0 MiB
will be used.
Continue? [y/n/?] (y): y
Do you agree with the terms of the license? [yes/no] (no):
Aborting installation due to user disagreement with openSUSE product license.
linux-xmay:/home/randall #
It did it again. (I left out the bulk of the output).
Further, I had to get to wagon in the first place via terminal. Alt-F2 produces an error message: ERROR Could not open location ‘file: ///home/randall/yast’ Error stating file ‘/home/randall/yast.’ No such file or directory.
dup is proceeding as desired. Thank you very much.
Only since you advised me thus, does it seem as if I might have previously seen that (or something to that effect) in zypper help. It’s safe to say that just as I didn’t remember it, I wouldn’t have remembered.
Install of 11.2 from 11.2 media is the desired. ‘dup’ might not work.
There is an official page for upgrade that seems to proceed differently: Upgrade/Supported - openSUSE
how do I make sure " . . . that the relevant partition holding /var/ does have enough free space
/var
would normally be on /
so unless you have made a separate partition? /var will be defined by /
In that other post in applications, the reason you are asked about space is because it asks you to download all the packages first, which could be be well over 1 GB. It’s just in case your internet were to go down during the upgrade process. Then the upgrade is run from the downloaded packages rather than streaming direct.
We got 11.1 gnome installed, updated, and upgraded to 11.2 last night. I restarted and it wouldn’t boot. I fiddled around with the 11.1 live DVD repair for several hours – no go. It would never boot. And to add insult to injury, I couldn’t boot PCLinuxOS.
So I reinstalled 11.1 gnome . . . upgraded to 11.2, and the same all over again. I am amazed at how long it all takes. The first time I successfully accomplished an 11.2 upgrade, I fell asleep and restarted the next morning, so I didn’t know that it’s a four and a half hour deal. Finally, it sank into my gourd that an 11.2 gnome isn’t going to happen – not here, for me.
So with no more PCLOS, I went ahead with an 11.1 KDE reinstall and upgrade to 11.2. Just finished. To tell you the truth, I’m surprised.
So, now, I don’t know whether to go on to things to do after an upgrade, finish Thanksgiving dinner *, or just go to sleep.
No; wait. My thread in the Applications forum, posted 24 November 2009, 00:21.
"Desktop won’t boot, instead I get a command line.
In red letters a couple inches up, it says /var filesystem inaccessible; and near the prompt, it tells me to manually repair filesystem. I don’t know what happened, nor how the fix it. Any suggestions? Any will be much appreciated."
As far as I can tell, I didn’t do anything to make that one self-destruct. What can I do now to circumvent another occurrence of that?
I do recall putting / and home in separate partitions before; but not selecting that option this time. Would this make any difference? What will?