I know I should be able to do an online update using cl zypper but would much prefer to use Yast’s sw manager as it’s easier to review and respond to package issues that always arise (because of packages made by me or dl’ed from obs but from repos not enabled in the repo manager)
currently running 11.2
thanks
openSUSE 11.3 is not released yet. I do not know if it’s features are allready documented somewhere. Why don’t you ask in the Pre-Release/Beta Forum?
posted here because it’s not a 11.3 specific question, more a generic upgrade question and would be as relevant going from 11.3 to 11.4
all the previous posts I’ve seen always say use cl zypper with dup
Actually, just found url for yast2 wagon and will pursue that as solution with a post in prebeta as suggested
I run 11.3 alongside 11.2 until I am happy with it, (i’m not there yet).
Very sensible imho. I did the same with 10.3 and 11.2. Same /home partition, but you can boot back and forward. Also mounting the other root partition temporary somewhere makes it easy to compare configuration files e.g. in /etc.
google01103 wrote:
> posted here because it’s not a 11.3 specific question, more a generic
> upgrade question and would be as relevant going from 11.3 to 11.4
the question will always be only applicable to pre-release software if
you are wanting to update to unreleased software…
or, do you prefer to ask the question relative to currently using 11.1
and upgrading to 11.2?
in that case the answer is found on this page:
http://en.opensuse.org/Upgrade
in which you will find the community supported way to move from 11.1
to 11.2 is by using Zypper or YaST
will that change when going from 11.2 to 11.3? i have no idea…
–
DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio
Very sensible imho. I did the same with 10.3 and 11.2. Same /home partition, but you can boot back and forward. Also mounting the other root partition temporary somewhere makes it easy to compare configuration files e.g. in /etc.
Hi, I am very interested in the best way to share /home, (or the data in home and preferably, only some chosen config files. ) on a relatively small disk with multiple linux OSes (3 off), I have read a thread you answered on this subject here
forums.opensuse.org/get-help-here/install-boot-login/439726-how-can-opensuse-ubuntu-share-home.html ( still have a few questions though )
Note that I am not ready to implement this until I am ready to move to 11.3 as my main OS, it’s easer to make the changes at a planed stage.
I’m looking forward to any replies you may have when I do ask my questions on this. thanks.
I’ve thought about it, I think probably bot that far off topic!
@dvhenry
It might be out of topic, but as long as nobody complains 
My solution may not be exactly what you are after when I read “preferably, only some chosen config files”. Starting point is having a separate partion for /home, as advised often here on the forums. Thus it is the whole of /home that is available in both systems.
I have four partition:
. Swap, to be used by both systems;
. SystemA, where the “old” openSUSE is installed (root partition);
. SystemB. where the “new” openSUSE is installed (root partition);
. Home, used by both systems mounted at /home.
Of course this is multi boot (using GRUB). When the “new” system is stable and conversion complete, the boot entry for “old” may be removed from Grub. When in a year or so we go for the “next” openSUSE, it will be installed on SystemA and we will cycle back.
When testing “new” I mount SystemA on /mnt/oldroot readonly. Readonly to protect against any changes. Now when I have a problem in e.g. my DNS configuration, I could see what is the difference between “old” and “new” with:
diff /etc/resolv.conf /mnt/oldroot/etc/resolv.conf
I hope you understand the principles here.
The end-user(s) files are the same on both systems, thus their personal FF, Amarok, KDE, etc. configurations are the same on both systems. Same of course for their documents, music, etc. But there is no choice of: yes for he FF config, but no for the Amarok ones.
There could be some negative effects. My last conversion was from 10.3 to 11.2 and that included KDE 3 to KDE 4. Now in openSUSE the two KDEs have two different sets of personal config file (in ~/.kde and ~/.kde4). I think this avoided a lot of problems when you boot intermittent into both systems. But I remember e.g. that KDE 4 connected a new icon to the Dustbin on the Desktop. Going back to 10.3/KDE3 that icon was not found and a default icon was shown. Nothing dramatic. But it is good to remind that the first time you start a new level of a program, it will find the old config file and it might convert this automaticaly to a new version. Thus when you the you the old program again (because you booted “old”) there could be a problem. Mostly these things are for- and backward compatible though.
I hope I made thhis a bit clear to you. More questions? Please feel free to ask.
@hcvv
One concern I have always had, has been the config files in /home potentially conflicting between OSes or versions, (This may be a lot less of a problem than I have anticipated) I am running openSUSE 11.2, 11,3M7 and mandriva2010. I have never attempted to use the one home for more than one OS at a time.
Yes, I understand the method you describe does not, by itself fulfil all these requirements, I noticed a suggestion in the the thread that I linked to above that I feel may be helpfull for what I am trying to achieve. And also post #18 by malcolmlewis here How to fix messed up partitions with Toshiba Laptop with Opensuse 11.1 and Windows NTF Vista - Page 2 - openSUSE Forums Is another option for me to look into.
So it seems I have some options to explore.
The possibility of a bad mix of config files in /home/<user>/ was handled by one of our members here IIRC by having not his* /home* directory shared, but only his data. Roughly it goes like this:
Mount a partition with the user data at e.g.* /mnt/userdata/*
Make symlinks in the users home directory like:
ln -s /mnt/usersdata/<user>/Documents Documents
and so forth for Music, etc.
When there is but one end-user (as is often the case with desktops/laptops) this might be feasable and not to difficult. When you have more users (acting as real end-users, where you are the sysadmin) it might be difficult to teach them not to make new files/directories in their homedir and excpectingg it to be available when booting another system.
But I have the impression that in the case you seem to have not only two openSUSEs for an upcoming upgrade, but also others distros (at least in mind) and thus are probably the only one knowing how this functions and having no other users exposed to this. which makes it easy (and in which case there is of course no need to have subdirectories for every user in* /mnt/userdata*).
But I have the impression that in the case you seem to have not only two openSUSEs for an upcoming upgrade, but also others distros (at least in mind) and thus are probably the only one knowing how this functions and having no other users exposed to this. which makes it easy (and in which case there is of course no need to have subdirectories for every user in /mnt/userdata).
Yes, I am the only user of the machine that I want to set up in this way. Yes I do still like to run my other long term favourite distro, Mandriva, I expect That I will for a while yet.
The possibility of a bad mix of config files in /home/<user>/ was handled by one of our members here IIRC by having not his /home directory shared, but only his data.
This is what I am after, I always do a fresh install, I don’t want old config files left in /home, I would prefer to reconfigure fresh, with the data on a separate partition and used by each OS and separate config files for each OS.
It looks like the previously mentioned post #18 perhaps?
Thanks.
Definitely. He is the “one of our members” (let us give him credit).
After I send of the earlier post, my mind was still meddling with it and the idea of a script making the links bubbled through. But that is rather obvious if you go for this solution and have to do the links often. After all, we are computer people and thus very lazy and refusing to do repeatative tasks. rotfl!
Thanks @hcvv and @malcolmlewis your assistance with this has been much apreciated.
I have a better understanding now of what methods are available to suit what situation, as well the best to suit this situation. Thanks again.
You are quite welcome.