SUSE Linux 10.1 Beta5

Most of Beta4's rough edges have been smoothed but this beta is still not production ready

• 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:
  • 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)".
  • 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.
  • After installation, if you go into the YaST packager, all installed packages are listed twice.
  • Adding a new installation source does not work.
  • 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.
  • An upgrade from a previous installation might fail, even one from 10.1 Beta3 Bug 153142
• During an update from a previous release, packages that are not available anymore get deleted - once at the start of CD1 and then again at the end of CD1. Pressing Ignore a couple of times allows to continue. Bug 153135
• The partitioner is broken in some cases Bug 151947. which might result in:
  • mixed up filesystem types - for example one chooses ext2 and the partition is getting formatted with reiserfs
  • creates double or totally obscure entries within the fstab of the system
  • makes inproper proposals for a standard partitioning

• Download of Release Notes will fail.
• The online test with download of Updates will fail.
• The second part of the installation is done in text mode Bug 153066, but afterwards the graphical login manager is started.
• X11 configuration during installation is totally broken in Beta5 due to a bug in package manager. Instead of the native X11 driver fbdev or even vesa driver will be configured. In order to create a valid X11 configuration stop xdm ("rcxdm stop") and use SaX2 for configuration ("sax2 -r"). ATI users should update the radeon driver first before executing SaX2. Otherwise the result will likely be a blank screen. Driver RPMs for i386/x86_64 are attached to Bug 153367 and are also on the ftp server in the fixed rpm directory.