Hello community, here is the log from the commit of package scpm checked in at Wed Apr 5 17:40:43 CEST 2006. -------- --- scpm/scpm.changes 2006-03-27 18:24:29.000000000 +0200 +++ scpm/scpm.changes 2006-04-05 16:36:49.000000000 +0200 @@ -1,0 +2,11 @@ +Wed Apr 5 16:30:52 CEST 2006 - jg@suse.de + +- writing boot info after update (bug 159703) + +------------------------------------------------------------------- +Wed Apr 5 13:06:35 CEST 2006 - jg@suse.de + +- added section about booting into profiles to texinfo + documentation (bug 106704) + +------------------------------------------------------------------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ scpm.spec ++++++ --- /var/tmp/diff_new_pack.7NfzJ1/_old 2006-04-05 17:40:29.000000000 +0200 +++ /var/tmp/diff_new_pack.7NfzJ1/_new 2006-04-05 17:40:29.000000000 +0200 @@ -14,7 +14,7 @@ BuildRequires: doxygen gcc-c++ graphviz libjpeg-devel libpng-devel mhash-devel Summary: System Configuration Profile Management Version: 1.1.3 -Release: 10 +Release: 11 Group: System/Base License: GPL Source: scpm-%{version}.tar.bz2 @@ -122,6 +122,11 @@ test "$RPM_BUILD_ROOT" != "/" && rm -rf $RPM_BUILD_ROOT %changelog -n scpm +* Wed Apr 05 2006 - jg@suse.de +- writing boot info after update (bug 159703) +* Wed Apr 05 2006 - jg@suse.de +- added section about booting into profiles to texinfo + documentation (bug 106704) * Mon Mar 27 2006 - jg@suse.de - updated translations * Mon Feb 20 2006 - jg@suse.de ++++++ scpm-1.1.3.tar.bz2 ++++++ diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/scpm-1.1.3/CHANGES new/scpm-1.1.3/CHANGES --- old/scpm-1.1.3/CHANGES 2006-02-20 17:22:21.000000000 +0100 +++ new/scpm-1.1.3/CHANGES 2006-04-05 12:59:16.000000000 +0200 @@ -1,4 +1,6 @@ 1.1.3 + - added section about booting into profiles to texinfo + documentation (bug 106704) - updated translations - fixed patch command (bug 150625) - ignoring missing file error on profile removal diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/scpm-1.1.3/doc/scpm.texi new/scpm-1.1.3/doc/scpm.texi --- old/scpm-1.1.3/doc/scpm.texi 2005-08-29 14:55:40.000000000 +0200 +++ new/scpm-1.1.3/doc/scpm.texi 2006-04-05 12:56:57.000000000 +0200 @@ -566,6 +566,7 @@ * Altering Profiles:: Change possibilities to existing profiles * Using Resource Sets:: Enabling, changing, and switching Resource Sets * Using Resource Groups:: Running SCPM with the Resource Set successor +* Booting into profiles:: Select your profile at the boot prompt * Switch Scripts:: SCPM can run scripts for you * Running as user:: Run SCPM as non root user * Updating SCPM:: Notes on updating SCPM and OS updates with SCPM @@ -645,7 +646,7 @@ @node Using Resource Sets, Using Resource Groups , Altering Profiles , Usage @unnumbered Using Resource Sets   -@strong{NOTE:} Resource Sets have been superseeded by Resource +@strong{NOTE} Resource Sets have been superseeded by Resource Groups. It is nothing wrong with Resource Sets, they are still supported and you can use them if you want to. @@ -672,7 +673,7 @@ the @command{/etc/scpm.conf} to @dfn{my_set} and afterwards you can initialize SCPM. -@node Using Resource Groups, Switch Scripts, Using Resource Sets, Usage +@node Using Resource Groups, Booting into profiles, Using Resource Sets, Usage Resource Groups similar to the Resource Sets should help customizing SCPM, but they are also intended to increase usabilty. @@ -695,7 +696,26 @@ intention of this is to make clear that this resource belongs to that group but is not useful to handle it by default. -@node Switch Scripts, Running as user , Using Resource Groups , Usage +@node Booting into profiles, Switch Scripts, Using Resource Groups, Usage +Besides switching profiles at runtime, you can also instruct SCPM to +set your system as configured in one of your profiles at boot time. +If you are running a SUSE Linux system and using Grub, you probably +have SCPM boot support without the need to do something special. +When in the Grub boot menu, just hit F3 and you get the list of +your installed profiles, of which you can select one to be set up +on boot + +@strong{WARNING} If you have multiple Linux installations +that make use of SCPM, and you boot them with the same Grub installation, +you might run into problems. Grub collects information about installed +profiles by reading the message file from the boot disk. That means +you typically get the profiles of the system from which you installed +the Grub bootloader, even if you want to boot another system +installation. If you need several Linux installations with SCPM support, +you can achieve that by installing a Grub into the boot partition of +each of them and use a master Grub to chainload these Grubs. + +@node Switch Scripts, Running as user , Booting into profiles , Usage @unnumbered Switch Scripts Switch scripts are normal shell scripts which are executed at certain ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Remember to have fun...