Updating suse dating services in phila
devices=/dev/disk/by-id/ata-VBOX_CD-ROM_VB2-01700376,/dev/sr0 2 | repo-debug | open SUSE-13.1-Debug | No | Yes | 3 | repo-debug-update | open SUSE-13.1-Update-Debug | No | Yes | 4 | repo-debug-update-non-oss | open SUSE-13.1-Update-Debug-Non-Oss | No | Yes | 5 | repo-non-oss | open SUSE-13.1-Non-Oss | Yes | Yes | 6 | repo-oss | open SUSE-13.1-Oss | Yes | Yes | 7 | repo-source | open SUSE-13.1-Source | No | Yes | 8 | repo-update | open SUSE-13.1-Update | Yes | Yes | 9 | repo-update-non-oss | open SUSE-13.1-Update-Non-Oss | Yes | Yes | It will take a while depending upon your Internet connection speed. After updating the system, reboot it to apply the new changes.As I mentioned already, disable any third party or OBS repositories before proceed to upgrade.So make sure that have an uninterrupted power supply and stable Internet connection. To find the current running open SUSE version, enter the following command: NAME=open SUSE VERSION="13.1 (Bottle)" VERSION_ID="13.1" PRETTY_NAME="open SUSE 13.1 (Bottle) (x86_64)" ID=opensuse ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:opensuse:13.1" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://opensuse.org/" ID_LIKE="suse" Well, let us begin to upgrade from open SUSE 13.1 to 13.2.
For more details, read the open SUSE 13.2 release announcement and new features of 13.2 here.
If you have already added a channel from a local repository path, you will not be able to change its URL to point to a different path afterwards Up-to-date data is now available on your SUSE Manager server and is ready for updating client systems.
According to your maintenance windows or update schedule refresh the data on the storage medium with SMT. On your SUSE Manager server, unmount the storage medium and connect it to your SMT. On your SMT system, continue with Step 4 as referenced in "SMT: Fetching Repository Data from SUSE Customer Center" above.
The next procedure will show you how to update your server from the SMT media. Mount the storage medium on your SUMA server in the SAME directory each time it is updated and referenced (for example, at /media/disk). Specify the local path on the SUSE Manager server (one time) in /etc/rhn/rhn.conf: The disk must always be available at the same mount point.
To avoid data corruption, do not trigger a sync, if the storage medium is not mounted.