View All Attachments for Bug 127682

Attachment #53772
yast2 log	application/x-gtar	2005-10-11 20:38:52 UTC	41.52 KB	no flags	Details

Attachment cannot be viewed because its MIME type is not text/*, image/*, or application/vnd.mozilla.*. Download the attachment instead.

Attachment #53774
Screenshot 1 with unsolveble dependencies	image/jpeg	2005-10-11 20:39:56 UTC	100.75 KB	no flags	Details

Attachment #53775
Screenshot 2 with unsolveble dependencies	image/jpeg	2005-10-11 20:40:20 UTC	102.22 KB	no flags	Details

Attachment #53910
Release notes that came with 10.1 alpha 1	text/html	2005-10-13 04:31:45 UTC	14.29 KB	no flags	Details

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>SUSE Linux 10.0 Release Notes</title></head>

<body>
 <h1>SUSE Linux 10.0 Release Notes</h1>
 <p>Copyright Â© 2005 Novell, Inc.</p>

 <p>
These release notes cover the following areas:
</p>

 <ul>

  <li>
<p>General:
 Information that everybody should read.</p>
  </li>

  <li><p>Update:
 Changes that are not mentioned in the Start-Up Manual,
 Chapter 2. [still empty]</p></li>

  <li><p>Installation:
 Additional pertinent information for installation. [still empty]</p></li>

  <li><p>Technical:
 This section contains a number of technical changes
 and enhancements for the experienced user.</p></li>
 </ul>

 <p>In the Start-up Manual, find information about installation and basic
system configuration. In the Reference Guide, the system configuration is
explained in detail. Additionally, the most important
applications and the desktops in general are described.</p>
<div>
<dl>
<dt>General</dt>
<dd><ol>
<li><a href="#01">Novell AppArmor</a></li>
<li><a href="#02">Xen 3 Technology Preview</a></li>
<li><a href="#03">Adding Software Repositories for Java</a></li>
<li><a href="#04">Using Eclipse on 64-Bit Platforms (x86_64 and AMD64)</a></li>
<li><a href="#05">New GeForce Graphics Cards (6x00) and the nv Driver</a></li>
<li><a href="#06">ATI Graphics Cards and the "fglrx" Graphics Driver</a></li>
<li><a href="#07">Using Atheros WLAN Cards</a></li>
<li><a href="#08">YaST Support Module</a></li>
</ol></dd>
<dt>Update</dt>
<dd><ol><li><a href="#09">N/A</a></li></ol></dd>
<dt>Installation</dt>
<dd><ol><li><a href="#10">N/A</a></li></ol></dd>
<dt>Technical</dt>
<dd><ol>
<li><a href="#11">PCMCIA</a></li>
<li><a href="#12">Becoming Superuser Using su</a></li>
<li><a href="#13">Locale Settings in ~/.i18n</a></li>
<li><a href="#14">Setting Up D-BUS for Interprocess Communication in .xinitrc</a></li>
<li><a href="#15">NTP-Related Files Renamed</a></li>
<li><a href="#16">Hotplug Events Handled by the udev Daemon</a></li>
<li><a href="#17">Mounting Hotplugged Devices without "sync"</a></li>
<li><a href="#18">Using Parallel-Port Printers</a></li>
<li><a href="#19">File System Change Notification for GNOME Applications</a></li>
</ol></dd>
</dl>
<hr>
</div>

 <div>
  <h2>General</h2>

  
  <div>
   <h3><a name="01">Novell AppArmor</a></h3>

   <p>
This release of SUSE Linux ships with Novell AppArmor. This feature protects
your applications from software exploits. AppArmor protection can be enabled
via the AppArmor control panel, which is located in YaST under Novell
AppArmor. For detailed information about using Novell AppArmor, see
<tt>/usr/share/doc/packages/subdomain-docs/apparmor-userguide.pdf</tt>. </p>
  </div>

  

  <div>
   <h3><a name="02">Xen 3 Technology Preview</a></h3>

   <p>
Xen 3 is very new and cutting-edge technology.  Novell is proud to bring it so
early to our customers.  It is evolving quickly and some areas it covers are a
work in progress and thus not mature yet.  Xen 3 brings new features, such as
x86-64 support (working), SMP (currently disabled), PAE support (not enabled on
SUSE Linux), but we could not make all these features stable or test them
extensively.</p>

   <p>
Expect improved packages via YaST Online Update (YOU).
For current information, see
<a href="http://www.opensuse.org/Xen3_Status_and_Updates">http://www.opensuse.org/Xen3_Status_and_Updates</a>.
</p>
</div>


  <div>
   <h3><a name="03">Adding Software Repositories for Java</a></h3>

   <p>Using the YaST Installation Source module, you can add additional
software repositories to your default installation settings.  This feature is
useful if want to enhance your system with components that are not part of your
standard installation source.  For example, openSUSE is limited to open source
software, but users who need Java and packages depending on Java can
add the "inst-source-java" repository in YaST and install
those packages.  For more information, see <a href="http://www.opensuse.org/index.php/Additional_YaST_Package_Repositories">http://www.opensuse.org/index.php/Additional_YaST_Package_Repositories</a>.
   </p>

  </div>

  
  <div>
   <h3><a name="04">Using Eclipse on 64-Bit Platforms (x86_64 and AMD64)</a></h3>

   <p>
Eclipse is included only in a 32-bit version so that it works together with our
default java (java-1_4_2-sun), which is not available in a 64-bit version at
all. If you want to use Eclipse with SUN Java 1.5.0, make sure that you also
install the 32-bit version of java-1_5_0-sun and java-1_5_0-sun-devel.</p>

   <p>
To do this, open YaST, choose "Software"-&gt;"Software Management" and search
for "java-1_5_0-sun". Select the packages "java-1_5_0-sun" and
"java-1_5_0-sun-devel". For both packages, click the "Version" tab in the
RPM description pane and select the i586 version.
</p>
  </div>


  
  <div>
   <h3><a name="05">New GeForce Graphics Cards (6x00) and the nv Driver</a></h3>

   <p>
Currently, some new GeForce cards (6x00 series) can only be used without
acceleration to avoid system lockup or graphics distortions.  This issue is
under investigation by SUSE and NVIDIA.</p>

   <p>Some of these cards are configured with <tt>Option
"ShadowFB"</tt> in the <tt>/etc/X11/xorg.conf</tt> device
section. This setting disables acceleration, slowing down graphics output
considerably.  We cannot automatically detect for which graphics cards this
setting is actually necessary.  You must test it on your own by removing or
commenting the option in <tt>/etc/X11/xorg.conf</tt>. However, if
this test locks up your system, you must boot into runlevel 3 and revert the
change.</p>

   <p>
We set this option only for cards we know to be affected by this problem. Other
GeForce 6x00 based boards might be affected as well. If your system locks up
and you do not see this option in the <tt>/etc/X11/xorg.conf</tt>
device section, add it and restart the system.</p>

   <p>If you experience only graphics distortion without <tt>Option
"ShadowFB"</tt> but no system lockup, you can use both <tt>Option
"XaaNoPixmapCache"</tt> and <tt>Option
"XaaNoOffscreenPixmaps"</tt> in the
<tt>/etc/X11/xorg.conf</tt> device section instead.  This setting
does not slow down the graphics output as much as <tt>Option
"ShadowFB"</tt>.
</p>

   <p>Another solution is to install the binary-only driver from NVIDIA,
which does not seem to be affected. Use YaST Online Update (YOU) to install
this driver.
</p>

  </div>

  
  <div>
   <h3><a name="06">ATI Graphics Cards and the "fglrx" Graphics Driver</a></h3>

   <p>
For ATI graphics cards that are not supported by the open source DRI
driver, we have a download solution to enable 3D suppport using a
proprietary driver. The proprietary driver currently does not
support "suspend to disk" or "suspend to RAM."
</p>

   <p>
You can download the ATI "fglrx" graphics driver with YaST Online Update
(YOU) similarly to how the NVIDIA is handled. To install the driver,
select the patch in YOU and install the driver.  Then
configure the driver manually with SaX2. For more information, see
<tt>/usr/share/doc/packages/fglrx/README.SuSE</tt>.
</p>
  </div>


  

  <div>
   <h3><a name="07">Using Atheros WLAN Cards</a></h3>

   <p>
At the moment, the driver for Atheros WLAN cards is available under a
proprietary license only. Therefore, it is not packaged along with the normal
kernel packages.  To use the Atheros driver, install the
non-GPL kernel package matching your kernel (for example, if you use
"kernel-default", additionally install "kernel-default-nongpl").
    </p>
   <p>
Download the non-GPL kernel package from <a href="http://www.opensuse.org/Additional_YaST_Package_Repositories">http://www.opensuse.org/Additional_YaST_Package_Repositories</a>.</p>
  </div>

  <div>
   <h3><a name="08">YaST Support Module</a></h3>
   <p>
The functionality of YaST Support Module has changed.  You can use the module
to prepare a support request and collect information about your system.
Instructions for using the SUSE Linux installation support can be found at
<a href="http://www.novell.com/usersupport">http://www.novell.com/usersupport</a>.</p>
  </div>
 </div>

 <div>
  <h2>Update</h2>

  <div>
   <h3><a name="09">N/A</a></h3>
   <p>No issues known.
</p>
  </div>
 </div>

 <div>
  <h2>Installation</h2>

  <p>The installation is described in the Start-Up Guide.</p>

  <div>
   <h3><a name="10">N/A</a></h3>
   <p>No issues known.
</p>
  </div>

 </div>

 <div>
  <h2>Technical</h2>

   
   <div>
    <h3><a name="11">PCMCIA</a></h3>

    <p>
<tt>cardmgr</tt> no longer manages PC cards. Instead, as with Cardbus
cards and other subsystems, a kernel module manages them.  All necessary
actions are executed by <tt>hotplug</tt>. The
<tt>pcmcia</tt> start script has been removed and
<tt>cardctl</tt> is replaced by <tt>pccardctl</tt>. For
more information, see
<tt>/usr/share/doc/packages/pcmciautils/README.SUSE</tt>.
</p>
  </div>

  <div>
    <h3><a name="12">Becoming Superuser Using <tt>su</tt></a></h3>

    <p>By default, calling <tt>su</tt> to become
    <tt>root</tt> does not set the PATH for
    <tt>root</tt>.  Either call <tt>su -</tt> to
    start a login shell with the complete environment for
    <tt>root</tt> or set <tt>ALWAYS_SET_PATH</tt> to
    <tt>yes</tt> in <tt>/etc/default/su</tt> if you want to
    change the default behavior of <tt>su</tt>.
    </p>
   </div>

  <div>
   <h3><a name="13">Locale Settings in <tt>~/.i18n</tt></a></h3>

   <p>If you are not satisfied with locale system defaults, change the
    settings in <tt>~/.i18n</tt>.  Entries in
    <tt>~/.i18n</tt> override system defaults from
    <tt>/etc/sysconfig/language</tt>.  Use the same variable names
    but without the <tt>RC_</tt> namespace prefixes, for example, use
    <tt>LANG</tt> instead of <tt>RC_LANG</tt>.
    For information about locales in general, see "Language and
    Country-Specific Settings" in the Reference Manual.
   </p>

  </div>

  
  <div>
   <h3><a name="14">Setting Up D-BUS for Interprocess Communication in .xinitrc</a></h3>

   <p>
Many applications now rely on D-BUS for interprocess communication (IPC).
Calling <tt>dbus-launch</tt> starts
<tt>dbus-daemon</tt>. The systemwide
<tt>/etc/X11/xinit/xinitrc</tt> uses <tt>dbus-launch</tt>
to start the window manager.</p>

   <p>If you have a local <tt>~/.xinitrc</tt> file, you must
change it accordingly.  Otherwise applications like f-spot, banshee, tomboy, or
Network Manager banshee might fail.  Save your old
<tt>~/.xinitrc</tt>.  Then copy the new template file into your
home directory with:</p>

   <p><tt>cp /etc/skel/.xinitrc.template ~/.xinitrc</tt></p>

   <p>Finally, add your customizations from the saved
   <tt>.xinitrc</tt>.</p>

  </div>

  
  <div>
   <h3><a name="15">NTP-Related Files Renamed</a></h3>

   <p>
For reasons of compatibility with LSB (Linux Standard Base), most configuration files
and the init script were renamed from <tt>xntp</tt> to
<tt>ntp</tt>.  The new filenames are:</p>

<p><tt>/etc/slp.reg.d/ntp.reg</tt></p>
<p><tt>/etc/init.d/ntp</tt></p>
<p><tt>/etc/logrotate.d/ntp</tt></p>
<p><tt>/usr/sbin/rcntp</tt></p>
<p><tt>/etc/sysconfig/ntp</tt></p>
    </div>


  
  <div>
   <h3><a name="16">Hotplug Events Handled by the udev Daemon</a></h3>

   <p>
Hotplug events are now completely handled by the udev daemon
(<tt>udevd</tt>).  We do not use the event multiplexer system in
<tt>/etc/hotplug.d</tt> and <tt>/etc/dev.d</tt>
anymore. Instead <tt>udevd</tt> calls all hotplug helper tools
directly, according to its rules. Udev rules and helper tools are provided by
udev and various other packages.
</p>
  </div>

  
  <div>
   <h3><a name="17">Mounting Hotplugged Devices without "sync"</a></h3>

   <p>
If writing to USB storage devices, such as USB sticks or USB hard drives, is
rather slow or if you do not want synchronized writing to these devices,
disable the sync mount option.
</p>

<ol>
    <li>
     <p>Create a file with the name
     <tt>90-storage-nosync.fdi</tt> and the following contents:
</p>


<p><tt>&lt;?xml version="1.0" encoding="ISO-8859-1"?&gt;</tt></p>
<p><tt>&lt;deviceinfo version="0.2"&gt;</tt></p>
<p><tt>  &lt;device&gt;</tt></p>
<p><tt>    &lt;!-- disable sync for mount --&gt;</tt></p>
<p><tt>    &lt;match key="block.is_volume" bool="true"&gt;</tt></p>
<p><tt>      &lt;match key="volume.fsusage" string="filesystem"&gt;</tt></p>
<p><tt>        &lt;match key="volume.uuid" string="UUID"&gt;</tt></p>
<p><tt>          &lt;merge key="volume.policy.mount_option.sync" type="bool"&gt;false&lt;/merge&gt;</tt></p>
<p><tt>        &lt;/match&gt;</tt></p>
<p><tt>      &lt;/match&gt;</tt></p>
<p><tt>    &lt;/match&gt;</tt></p>
<p><tt>  &lt;/device&gt;</tt></p>
<p><tt>&lt;/deviceinfo&gt;</tt></p>

</li>


    <li>
     <p>Adjust the line
<tt>&lt;match key="volume.uuid" string="==UUID=="&gt;</tt>
according to your hardware.  Run <tt>lshal</tt>
to retrieve the <tt>volume.uuid</tt> and enter that ID instead of
<tt>==UUID==</tt></p>
</li>

    <li>
     <p>Copy <tt>90-storage-nosync.fdi</tt> into this directory:
</p>

     <p>cp 90-storage-nosync.fdi /usr/share/hal/fdi/policy/20thirdparty
</p>
</li>

    <li>
     <p>Restart the HAL service with <tt>rchal restart</tt>.
</p>
</li>
</ol>

  </div>


  
  <div>
   <h3><a name="18">Using Parallel-Port Printers</a></h3>

   <p>
Reboot may be required after parallel-port printer setup with YaST.  If
printing does not work when a parallel-port printer was set up with YaST, reboot
and then do not run the YaST printer setup again for testing.  Only
parallel-port printers in ECP/DMA mode are affected.
</p>


  </div>

  
  <div>
   <h3><a name="19">File System Change Notification for GNOME Applications</a></h3>

   <p>For proper functionality, GNOME applications depend on file system
   change notification support.  For local-only file systems, install the
 gamin package (preferred) or run the FAM daemon.  For remote file systems,
 run FAM on both the server and client and open the firewall for RPC calls by
 FAM. </p>

   <p>
GNOME (gnome-vfs2 and libgda) contains a wrapper that picks gamin or
fam to provide file system change notification:
</p>

   <ul>
    <li>
     <p>If the FAM daemon is not running, gamin is preferred. (Rationale:
Inotify is supported only by gamin and it is more efficient for local file
systems).  </p>
</li>

    <li>
     <p>If the FAM daemon is running, FAM is preferred
(Rationale: If FAM is running, you probably want remote notification, which
 is supported only by FAM).</p>
</li>
</ul>
</div>

 </div>



</body></html>