Christoph Thiel wrote:

On Sat, 18 Feb 2006, Eberhard Moenkeberg wrote:

Beta4 is really for the adventureous experts and not for anybody without a good Linux experience:

* The CD 1 needs to remain in the cd drive after installing from it. Do not remove it during the reboot and wait for YaST to request CD 2.

Otherwise the installation of packages from CD 2-5 will fail afterwards.

* Due to the integration of the new package manager which is not complete, note the following non working pieces:

 o Only a fresh installation is supported. Update from a previous
   installation is not working!

 o ncurses installation is not supported right now

 o Some statistics do not work, e.g. you see "Size of packages to
install: 0" - or "Number of packages to install: 0", or "Software: Default system (0)".

 o The graphical package manager frontend has only a limited list of
"views", currently you get a list of all the packages and can only search in them.

 o Only adding of selections works. If you want to remove a
selection, remove all packages in that selection and run the resolver manually with the "Check" button.

 o Language dependend packages are not handled correctly. This
results in the installation of one package-$lang package but not necessarily the one for the languages asked for.

 o It is not possible to abort installation while installing
   packages.

 o Network Installations: smb/cifs does not work, http, nfs and ftp
   should work.

* The partitioning proposal looks broken in some cases.

* There are no Release Notes shown - and the download of them fails.

Summing up: The installer is in a rather bad shape, only INSTALLATION is supported. The rest of the system should be stable.

For those of you who don't want to do a fresh installation, just use y2pmsh to upgrade ot the latests beta. It (still) uses the (old) YaST2 package manager backend and therefore is very stable and useable for an upgrade. (I'v used it successfully for the last 3 betas ;))

Here is a short guide on "how to upgrade with y2pmsh":

1.) Get the latests y2pmsh and yast2-packagemanager from Factory and install them using "rpm -Uvh y2pmsh*.rpm yast2-packagemanager*". Run SuSEconfig.

2.) Fire of y2pmsh by calling "y2pmsh".

   # y2pmsh
   Welcome to the YaST2 Package Manager!
   This tool is meant for debugging purpose only.

   initializing installation sources ...
   refreshing [... bla bla bla]
   initializing target ...
   reading RPM database .............ok
[some more info]

   type help for help, ^D to exit

==> make sure you don't have any source active, if there are some, call
   "source -R <numberofsource>" to remove them:

   [0] y2pm > source -ls
   Known sources:
   [0] y2pm > source --add <url to factory mirror>
   refreshing SUSE LINUX Version 10.0.42... ok (already up to date)
   [0] y2pm > upgrade

==> ... lot's of info

   ===[sum]============================================
   Packages checked     1119

   totalToInstall       1115
   totalToDelete        0
   totalToKeep          3
   --------------------------
   sum                  1118
   ====================================================
   ====================================================

==> looks OK!

  [0] y2pm > solve

==> hopefully you don't get to many conflicts... ;)
   this is just an example how to resolve a conflict

   Name: evolution-sharp
   Edition: 0.10.2-7
   From-Input-List: yes
   Unresolvable: evolution-sharp-0.10.2-7 requires libedataserver-1.2.so.4


   Packages with errors: 2
   Packages to install:  1117
   Packages to keep:     3
   Packages to delete:   1
   Download size:        1.27 GB
   Needed Space:         -5.2 MB
   [1] y2pm > remove evolution-sharp
   [1] y2pm > solve
[...]
   Packages with errors: 0
   Packages to install:  1116
   Packages to keep:     3
   Packages to delete:   2
   Download size:        1.27 GB
   Needed Space:         -5.8 MB
   [0] y2pm > commit

==> get yourself a cup of coffee and relax ;)

   [0] y2pm > quit

   # SuSEconfig
   # insserv -r novell-zmd # ;)

==> You might want to check with
   # rpm -qa --last | tail -200

if there are some packages that haven't been updated (the virtual gpgkey packages are fine), but others might need some manuall interaction. This is e.g. the case if packages have been dropped. Just remove those packages with

  # rpm -e <packagename>

  # reboot


Regards
        Christoph

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


There are so many things not working in the Betas, I want to install on a x86_64 box, I installed beta 3. I'am just going to wait for the final release, will it be called 10.1 or 10.2 .

Jim

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to