Recommended update for release-notes
(Last modified: 17AUG2005)
solutions Recommended update for release-notes SuSE Linux Maintenance Web (67b65b8c057f9a70185f29fe26fb6dda)
Product(s): SUSE CORE 9 for IBM S/390 31bit
SUSE CORE 9 for IBM zSeries 64bit
- Add download locations to Emulex firmware section Two minor spelling fixes in vacation tool and PCI driver autoloading.
- Update entry about required firmware level for Emulex adapters: LP10000, LP10000DC, LP10000ExDC 1.90a4 LP982, LP9802 1.81x1
- Adding entry about changed partition types in YaST (#94918)
- Adding entry about PCI driver autoloading via coldplug (#96878)
- Update installation server howto for SP2. Use rescue file from SP instead of GA. (#95413 , #63327)
Release Notes for SUSE LINUX Enterprise Server 9 for IBM(R) S390(R)
SP2 Release Notes
A comprehensive list of what Service Pack 2 includes
(Features, driver updates)
can be found in the file
Noteson the CD.
These release notes are structured as follows:
- Issues applying for SP2 exclusively.
- Original release notes as shipped with SLES9 GA.
- General: Information that everybody should read.
- Update: Explains changes that are not mentioned in the Admin Guide, Chapter 2.
- Installation: Additional pertinent information for the installation.
- Updates and Features: This sections contains a number of technical changes and enhancements for the experienced user.
- Providing Feedback
SP2 Release Notes
Installing with SP2
SP2 is just another install CD. It is important to ensure that you either boot of it directly or copy the file "driverupdate" to the installation server.
SPident Reports the Service Pack Level
SPident is a tool to identify the Service Pack level of the current installation.
SPident may report that the system has not reached the level of Service Pack 2. This happens, when so-called "optional" updates, which will not be automatically installed by YOU, are not manually selected during update. If you use or need any of these packages which have optional updates you should select these in order to reach SP2 level.
Included support for Oracle Cluster Filesystem 2 (ocfs2) for limited use
At the time of this release notes support is limited to the following conditions:
- x86, AMD64 & Intel EM64T, IPF hardware platform (not: IBM POWER, IBM S/390 & zSeries)
- valid support agreement with Novell and Oracle
- use as a home for Oracle RAC (no general purpose use)
One of the three methods offered for updating an existing SLES 9 system might fail under the circumstances below. If you boot the installation system from Service Pack 2 and choose the option "Update system on hard disk", the installation of the new kernel may not succeed. This was seen to fail on S/390 and zSeries.
However, being as there are two other possibilities for updating an existing SLES 9 ("System update" and "Install Patch CD") those should be preferred.
Unicast ping works but Broadcast and Multicast ping doesn't work
The kernel is configured not to answer Broadcast and Multicast pings. This is done for security reasons as this can be used for a Denial of Service attack. If this feature is needed please enable it by issuing the following command:
echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
To permanently change this behaviour change the line:
net.ipv4.icmp_echo_ignore_broadcasts = 1
in the file /etc/sysctl.conf to
net.ipv4.icmp_echo_ignore_broadcasts = 0
Restriction when using cpint/hcp
When using the cpint/hcp interface the guest should not have more then 2 GByte of storage. If the geust has more storage, the command may fail.
This restriction applies to the 64-Bit system only.
Microsoft Windows(R) or Samba Server as Installation Server
If you use a Microsoft Windows system or a Samba server to share the SLES 9 SP 2 installation source, it might happen that the download fails after several packages. In this case ignore the error message and restart the download and the install process. Then the remaining packages are downloaded and installed.
Unconfiguring a VLAN-device
If a VLAN-Device should be unconfigured, it is important to remove the VLAN-device correct. So the following command sequence should be used to correctly unconfigure a VLAN-Device.
Add network Device
echo 0.0.f300,0.0.f301,0.0.f302 > /sys/bus/ccwgroup/drivers/qeth/group echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.f300/layer2 echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.f300/onlineConfigure network device
ifconfig eth1 hw ether 00:02:55:09:30:26 ifconfig eth1 10.35.30.26 netmask 255.255.0.0 broadcast 10.35.255.255 upAdd VLAN device over existing dev
vconfig add eth1 35Configure VLAN device
ifconfig eth1.35 10.135.30.26 netmask 255.255.0.0 broadcast 10.135.255.255 upShutdown the VLAN dev
ifconfig eth1.35 downUnconfigure the VLAN-Device
vconfig rem eth1.35Shutdown the the network dev
ifconfig eth1 downRemove network device
echo 0 > /sys/bus/ccwgroup/drivers/qeth/0.0.f300/online echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.f300/ungroup
Systems with PERC3 or PERC4 RAID controllers
To update a GA version to SP2 you need to boot with the SP2 CD1. The 'Patch CD update' will not work on these systems.
An update from SP1 to SP2 can be made with any of the documented update methods.
Using SCSI or hotplug devices may lead to boot failure or mount
On reboot, SCSI or hotplug devices may be assigned to different device file names than before. If the root filesystem moved to a different device name, the kernel will not find it and fail booting.
For a root filesystem use
mount by volume label, see below.
For all other filesystems configure
mount by UUIDusing YaST2:
- In YaST2 go to the Partitioner
- For every SCSI device partition
/dev/sd?with a mount point, go to
Fstab Optionsand select
Mount in /etc/fstab by UUID.
mount by volume labelfor root filesystem:
- Assign a volume label to the root filesystem and activate
mount by volume labelGo to the YaST2 Partitioner. Select the root filesystem (
Mount on /) and go to
Fstab Options. Check
Mount in /etc/fstab by Volume label. Enter a label in the field
Volume Label, e.g.
rootvollabel. Be sure to use a volume label that is not used by any other volume in the system. Commit changes (press
- Set up the
root=kernel parameter in the bootloader configuration Go to the YaST2 Boot Loader Setup. Press
Edit Configuration Files. In the line that starts with
append =, add
root=LABEL=rootvollabelto the kernel command line.
rootvollabelis the Label you assigned to the root filesystem above. Commit changes (press
The rescue system contains device nodes for a limited number of devices. If your system has more devices, use the command
on the command line. This creates the missing device nodes in
/devfor all devices that are listed in
Apache Modules util_ldap and mod_auth_ldap
The apache modules
mod_auth_ldaphave been updated from 2.0.49 to 2.0.52 level, because of the number of bugs fixed in these modules. They are still declared experimental by the authors. The update causes a minor binary incompatibility in the API exposed by the
util_ldapmodule. Only third-party software built directly on top of
util_ldapis affected by this incompatibility. There is *no* incompatible change in the functionality provided by the two modules or in their configuration.
GA Release Notes
These release notes cover the following areas:
- General: Information that everybody should read.
- Update: Explains changes that are not mentioned in the Admin Guide, chapter 2.
- Installation: Additional pertinent information for the Installation.
- Updates and Features: These sections contains a number of technical changes and enhancements for the experienced user.
- Providing Feedback
Updated SLES 9 manuals and translations of YaST messages
You will find the SLES 9 manuals in pdf format on CD1 in the directory "docu". They contain a vast collection of valuable information. Please read them as they may answer many questions for you. Translations for YaST are also included. Feedback on documentation and translations should be mailed to
Polish language support
If Polish language support is needed, please make sure to install the packages
yast2-trans-pl. You have to select them manually from the selection list.
Globus Toolkit 2.0
The Globus Toolkit 2.0 was part of SUSE Linux Enterprise Server 8. Because of major changes in the Globus TK API and of binaries we have decided to not include Globus Toolkit 2.x or 3.x into SUSE Linux Enterprise Server 9. Support for the Globus Toolkit is available through a consulting agreement. Please contact http://www.suse.com/contact for available offerings.
The Common Internet File System (CIFS) which is shipped together with the Kernel is currently not supported. The current implementation is not stable enough to work in a production environment.
Network Device Setup
The network device setup has been changed. Previously the configuration of a non-existing interface triggered initialisation of the hardware. Now, new hardware is searched for and initialised first, which then triggers the setup of the new network interface.
Additionally new names are introduced for the configuration files. Since the name of a network interface is created dynamically and the usage of hotplug devices increases more and more, a name like ethX is not usable anymore for configuration purposes. Therefore we now use unique descriptions like the MAC-address or the PCI slot for naming of interface configurations.
Note: You can use interface names once they are present. ifup eth0 / ifdown eth0 still works.
The configuration for devices is found in /etc/sysconfig/hardware. The interfaces these devices provide is found as usual (only with different names) in
An extended README is available under /usr/share/doc/packages/sysconfig/README.
If the DHCP daemon is set to start at boot time and the system is updated from SLES8 to SLES9, this setting will be lost during the update process due to a packaging bug. To re-enable starting of the DHCP server at boot time, use the command
chkconfig -a dhcpdor, alternatively, the YaST2 runlevel editor.
Non UTF-8 filenames
Files on filesystems created by 9.0 and older distributions (when not set otherwise) use non-UTF-8 encoding. If these file names contain non ASCII characters, they will be garbled on SLES 9 and later versions. One fix is to use the convmv script which changes the encoding of the files to UTF-8.
XML Stylesheets and DTDs
The FHS now requires XML resources (DTDs, stylesheets, etc.) to be installed in
/usr/share/xml. Therefore, some directories are no longer available in
/usr/share/sgml. If you encounter problems, modify your scripts or makefiles or use the official catalogs (especially
Codepage with mounting VFAT partitions
When mounting VFAT partitions the parameter formerly called
code=must be changed to
codepage=. If mounting a VFAT partition causes problems, check if the file
/etc/fstabcontains the old name for the parameter.
Apache 1.3 has been replaced by Apache 2
The apache web server (version 1.3) has been replaced by apache2 (version 2.0.49). A system update on a machine with a HTTP server installation will remove the apache package, install apache2 after which will need to adapt your setup manually, because there is no automated facility available.
Configuration files that were under
/etc/httpdare now in
/etc/apache2. Apache2 requires either package
apache2-prefork(recommended for stability) or
During update there may be some conflicts requiring manual attention
- horde requires either apache2-mod_php4 or apache-mod_php4 In this case either deinstall horde (if you do not need it), or select the mod_php4 package belonging to the Apache version you want to use.
- dprobes conflicts with oprofile (over libbfd) In this case please chose deinstallation of dprobes. dprobes is not provided with SLES 9.
If you used Samba on SLES 8 with SAMBA_SAM set to "ldap" in /etc/sysconfig/samba you need to migrate your Samba LDAP configuration to the new Samba 3 LDAP schema as included in SLES 9.
There have been significant changes in the implementation of raw devices. For more details, see
/usr/share/doc/packages/util-linux/README.rawwhich is provided in the
DASD load order in SLES9
When specifying DASDs in the DASD-configuration menu which are not numerically ascending (e.g. dasda = 0.0.1090, dasdb = 0.0.0150) the system reloads the driver and the DASDs are now in numerically ascending order. To avoid this behaviour do the following:
Before you hit the next button in the DASD-configuration screen, open a ssh-session to the system you install and issue the following command:
echo "exit 0" > /sbin/dasd_reload
Now the DASDs will stay in the sequence specified.
WARNING: If there are any holes in the sequence of the DASDs (e.g. the first DASD is dasdb and dasda does not exist at all) the installation/update will fail.
Installing with an FTP-Server
If you use an FTP-Server to provide the CDs for installation, there is a restriction for the path you specify during the installation. Currently, you may only specify relative paths. That means that every path specified starts at the login directory of the ftp server. There is no difference whether you use a personal or anonymous login.
Same CD requested twice
Depending on the selection you chose it is possible that some CDs have to be inserted twice during the installation process. This is a known issue, but due to dependencies it cannot always be avoided. A workaround is to install via network or harddisk instead of CDs.
Setting up an installation server for network installations
If you have a SLES9 already installed, use the YaST installation-server module to create a network install source. It can be found below
Misc - Installation Serverin the YaST main screen.
Note: the SLES9 GA version of the YaST installation-server module can not integrate SLES9 service pack iso images. This bug was fixed in SLES9 SP1. Either upgrade the server to SP1 or newer, or just update the yast2-instserver.rpm:
rpm -Uvh /SP1-CD1/suse/noarch/yast2-instserver-2.9.22-0.2.noarch.rpmRestart YaST after the yast2-instserver package update.
Every new service pack CD provides an updated rescue system on CD1/boot/rescue. To use this new rescue system on a YaST generated installation source, remove the 'boot' symlink in the toplevel directory.
rm boot mkdir boot cp SUSE-SLES-Version-9/CD1/boot/root ./boot/root cp SUSE-SLES-9-Service-Pack-Version-2/boot/rescue ./boot/rescue
To manually set up an installation Server for installations via NFS/FTP/HTTP the CDs have to be copied into a special directory structure.
Go to a directory of your choice and execute the following commands:
mkdir -p installroot/sles9/CD1
# now copy the contents of SLES CD1 into this directory
mkdir -p installroot/core9/CD1
# now copy the contents of SLES CD2 into this directory
mkdir -p installroot/core9/CD2
# now copy the contents of SLES CD3 into this directory
mkdir -p installroot/core9/CD3
# now copy the contents of SLES CD4 into this directory
mkdir -p installroot/core9/CD4
# now copy the contents of SLES CD5 into this directory
mkdir -p installroot/core9/CD5
# now copy the contents of SLES CD6 into this directory
mkdir -p installroot/sp2/CD1
# now copy the contents of SLES SP2 CD1 into this directory
mkdir -p installroot/sp2/CD2
# now copy the contents of SLES SP2 CD2 into this directory
mkdir -p installroot/sp2/CD3
# now copy the contents of SLES SP2 CD3 into this directory
ln -s ../sles9/CD1/boot/root boot/root
ln -s ../sp2/CD1/boot/rescue boot/rescue
ln -s sp2/CD1/driverupdate driverupdate
ln -s sp2/CD1/linux linux
ln -s sles9/CD1/content content
ln -s sles9/CD1/control.xml control.xml
ln -s sles9/CD1/media.1 media.1
echo "/sp2/CD1 /sp2/CD1" > yast/instorder
echo "/sles9/CD1 /sles9/CD1" >> yast/instorder
echo "/core9/CD1 /core9/CD1" >> yast/instorder
echo "/sp2/CD1 /sp2/CD1" > yast/order
echo "/sles9/CD1 /sles9/CD1" >> yast/order
echo "/core9/CD1 /core9/CD1" >> yast/order
If you are now asked for the installation directory just specify
If you want to set up an MS windows system as an install server go to the directory dosutils/install. There is a script
install.batthat will create the structure and asks you for the CDs. There are also the files
orderthat have to be copied to the directory
\suseinstall\yast. Before you copy the
orderfile please replace the Variables UserAccount, PASSword and IP-Number with the respective values of your MS windows machine. During the installation process you only need to specify the share suseinstall.
If you use a SAMBA-Server as installation server, simply use the commands mentioned above to create the appropriate structure. Use the
dosutils/installand replace the Variables UserAccount, PASSword and IP-Number with the respective values. The following shares need to be exported:
installroot(the directory installroot)
sles9-CD1(the directory installroot/sles9/CD1)
core9-CD1(the directory installroot/core9/CD1)
core9-CD2(the directory installroot/core9/CD2)
core9-CD3(the directory installroot/core9/CD3)
core9-CD4(the directory installroot/core9/CD4)
core9-CD5(the directory installroot/core9/CD5)
sp2-CD1(the directory installroot/sp2/CD1)
sp2-CD2(the directory installroot/sp2/CD2)
sp2-CD3(the directory installroot/sp2/CD3)
Problems with "xhost +" to display remote X sessions on your local
This is only relevant if you control an installation over a network and want to display your remote X or YaST session on your local display. On some Linux/Unix-Systems it is no longer sufficient to enter the command "xhost +" to grant access to the local X-Server. For security reasons the X-Server no longer listens on port 6000. To verify whether the X-Server still listens on port 6000 enter the command:
netstat -an | grep 6000
If the line
tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN
does not show up, the server is not listening. In this case you can either enable port 6000 or use the command
ssh -X "Address of the system be installed"
which will always work.
Adding storage drivers after initial installation needs manual
During installation, all block-device drivers for storage controllers are added to an "initial ramdisk". This ensures accessibility for attached storage at all times.
Adding such a controller (with attached storage) at a later point in time will initially work as expected (as a side-effect of the new hot/coldplug capabilities), but later (e.g. after creating a LV on those disks) it may not function.
To ensure system integrity at all times, we recommend to follow YaST2 standards and add the appropriate module to INITRD_MODULES in /etc/sysconfig/kernel, and then rerun /sbin/mkinitrd.
Migrating Multipath Devices from SLES8 to SLES9 on zSeries
The way multipath devices are handled has changed in SLES9
For further on how to access, use, and configure zFCP devices on zSeries please refer to the IBM Red Book: Linux for zSeries: Fibre Channel Protocol Implementation Guide http://www.redbooks.ibm.com/redpieces/abstracts/sg246344.html.
Chapter 6 in this book provides a very good description of how to configure SLES9 for zFCP as well as how to configure and add zFCP devices.
Chapter 9 in this book describes how to access, configure, and use multipath devices on SLES9.
Devices that had been configured with MD or LVM1 in SLES8 can be used in SLES9. Some tips follow for migrating your existing multipath configure devices.
Migrating Multipath Devices that were configured using MD
To migrate MD multipath configured devices from SLES8 to SLES9 start the system with the kernel parameter
barrier=off. Using this parameter will allow YaST to access MD configured devices during the update. This does not apply to MD multipathing volumes that were not originally configured using EVMS. If RAID Tools were originally used to configure the devices, the configuration must be converted to a device mapper configuration.
Migrating Multipath Devices that were configured with LVM1
During the update the multipath devices that had been configured using LVM1 on SLES8 will be recognised as standard LVM volumes. After the update has completed you should use EVMS to manage these devices. EVMS will recognize devices that been configured for multipath using LVM1.
Creating CA Certificate during Phase II Installation
if in a new installed system the hostname of the new System cannot be resolved with DNS, the creation of the CA Certificate during Phase II Installation may fail. To avoid this you have to connect via
ssh -Xto the system you are installing and create an entry into the file
/etc/hostswith the name and the IP-number of the system you are installing.
Some disk drives need boot option to prevent hangs
Some hard drives do not support barrier mode correctly and cause the system to hang in some situations, for example during mounting and formatting. In these cases the system must be booted with the boot option "
Updates and Features
Updated core system with latest versions/features of all packages,
- kernel 2.6.5 - SUSE Linux Kernel version
- glibc 2.3.3 - main C library
- GCC 3.3.3 - GNU compiler collection
- XFree 4.3.99 - Xfree X11 graphical user interface
- KDE 3.2.1 - K Desktop Environment
- GNOME 2.4.2 - GNOME Desktop Environment
- Samba 3.0.4 - file & print & more services
- Apache 2.0.49 - apache webserver version 2.x
- Bind 9.2.3 - domain name server
- new YaST license (GPL)
- improved/new installation methods (NFS, HTTP, FTP, VNC, ssh, SLP)
- many config modules have been added or improved: DNS - domain name server configuration front end DHCP - dynamic host configuration protocol front end NIS - network information service config front end LDAP - LDAP server configuration front end CA - certificate authority setup front end VPN - virtual private network setup front end Mail - mail server configuration front end TFTP - tiny ftp server configuration front end Install-server - configure SLES as an installation server YOU-server - provide updates to other SLES servers Boot-server - boot-and-deploy-other-systems setup CD creation - CD image creation support UML install - UserMode Linux installation front end
- LDAP enablement (for users/groups + DHCP, DNS and Mail config)
- Systems management enablement through CIM (providers + CIMOM)
- improved HT and NUMA support
- better support of big SMP systems
- fine granular locking which boosts parallel execution
- many kernel tuning parameters (like I/O scheduler)
- support more than 64 CPUs
- support thousands of devices/disks (64bit major/minor)
- new greatly improved block I/O layer
- improved network stack with IPv6, IPSEC and Mobile IPv6
- hotplug support (SCSI, USB, Firewire, PCI, CPU)
- persistent device names, unified device handling through sysfs
- new record breaking memory management (objrmap, anon VMA)
- class based kernel resource management (CKRM)
- ACPI improvements (xapic on big machines, suspend to disk/RAM)
- RAS enhancements (netconsole, crash dump, dprobes, event log)
- Infiniband support
By default umount.cifs isn't installed setuid root. If you would like to allow users a umount of CIFS filesystems please adjust the permissions by adding:
/sbin/umount.cifs root:root 4755
to /etc/permissions.local and run SuSEconfig afterwards.
Improved HA support
- heartbeat, drbd and multipath working with 2.6 kernel
- cluster volume manager (EVMS)
- cluster IP alias
Ready for the Asian market including translations and commercial fonts
Inclusion of Red Carpet Enterprise daemon
SLES 9 includes the Red Carpet Daemon. To install the Red Carpet Daemon please execute the following command:
OpenSSH Updated to Version 3.8p1
gssapisupport has been replaced with the
gssapi-with-micto fix possible MITM (man-in-the-middle attacks) attacks. These two versions are not compatible. This means that you cannot authenticate from older distributions by kerberos tickets because different methods for authentication are used.
libiodbc has been Dropped
People using FreeRADIUS now have to link against unixODBC as libiodbc has been dropped.
Change in Resolver Library
Incompatible change: the resolver library treats the
.localtop level domain as link-local domain and sends multicast DNS requests to the multicast address 126.96.36.199 port 5353 instead of normal DNS requests. If you already use the
.localdomain in your nameserver configuration you will have to switch to another domain name. See http://www.multicastdns.org for more information on multicast DNS.
Update of IBM Java SDK 1.4.2 for SLES9
Testing on SuSE SLES 9 has revealed new defects. To correct these defects an updated version of SDK 1.4.2 for this platform has been made available from the SuSE maintenance website.
Future Service Refresh releases of IBM Java SDK 1.4.2 will also be made available from the SuSE maintenance website as they become available.
SSH and Terminal Applications
When using remote access (notably SSH, telnet and RSH) between SUSE LINUX 9.1 / SLES 9(in its default configuration with UTF-8 enabled) and older systems (9.0 and lower, where UTF-8 is not enabled by default or not supported), terminal applications might display garbled characters.
This is because OpenSSH does not forward locale settings so that system-defaults are used which might not match the remote terminal settings. This affects text mode YaST and applications run remotely as non-root user. The applications run as root are only affected when the users changes the default locales for root (only LC_CTYPE is set by default).
POSIX compliant, high performance threads support (NPTL)
SUSE LINUX 9.1 / SLES 9 features a new pthread implementation called NPTL, which is faster and better than the old implementation called linuxthreads.
If your program is incompatible with this new threading implementation, we also provide the old one. To switch to the old version, set the environment variable LD_ASSUME_KERNEL to 2.4.21 by using (e.g.)
export LD_ASSUME_KERNEL=2.4.21in bash.
Applications using ncurses
If problems occur with ncurses based applications running on the text console then simply issuing
unicode_stop(reverting keyboard and console from unicode mode) should usually provide a fix.
SuSEplugger now supports drive notifications and therefore does not poll the devices. Drives that fail to support notification might not react. A workaround is to enable polling to get back the old behavior.
For information about the changes with printing see http://portal.suse.com/sdb/en/2004/03/jsmeix_print-einrichten-91.html
Memory requirements for running the System
For running SLES 9 a minimum of 256 Mbyte of memory is required.
Using unformatted DASD for the installation
During the initial installation work flow you will be guided to a panel where the DASD are set online/offline.
If unformatted DASD are used during installation, they should be formated at this point in time.
System Administration: Adding Disks to System after the installation
If disks are added to system after the installation mkinitrd and zipl have to be run to ensure that the disks are configured correctly during the boot of the system.
This has also to be done, if the disk was added using YaST.
modules.conf / modprobe.conf
Parameters for loadable modules have now to be placed in modprobe.conf.
The current version of vacation is neither 32/64 bit nor endian-safe.
If you use this tool in mixed environments please run vacation on the mail delivering server, which is normally the NFS server, or retry with the added option -f to force the creation of ~/.vacation.db
YaST partitioner will fail to assign the correct partition type during
The yast2 partitioner can fail to assign the correct partition type when you
repartition. On a partition that was deleted and then recreated, if you change
the type on the partition YaST will assign the original partition type. This
may lead to a non-booting system if the partition is part of a software RAID or
For example, the default partition scheme sets sda1 to type PReP on ppc. If
delete and then recreate sda1 and then change the type to DOS, YaST will still
set it as PReP.
To change the partition type, boot into the rescue system. Run
(or whatever the disk device node is in your setup) and change the type using
the 't' command.
Providing Feedback to our products
On the top level of the first CD you will find a very detailed ChangeLog. Please also read the READMEs on the CD.
In case of encountering a bug you may file a report via http://www.suse.com/feedback.
Your SUSE LINUX Enterprise Team
Mon Aug 15 10:33:33 UTC 2005
rpm -Fvh release-notes.rpm
Download Source Packages
Download the source code of the patches for maintained products.
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.