I can't find the place to configure a local update directory ?
I have the updates on a server for 9.3 -10.1.
In SL10.1 I don't find the correct place to configure the patch directory :(.
Is there a FAQ to include a nfs directory for updates ?
mit freundlichen Grüßen / best Regards,
Günther J. Niederwimmer
What changed in factory? I looked at my rsync logs, and found a strange
thing. No package was deleted, no version change, but all of them are
reloaded from stage. There is nothing in ChangeLog. Any clues? Bye,
I just found a new feature in 'factory' called 'Update Configuration'.
Should I already report bugs about it, or it's not yet feature complete...
Here are just a few:
- 'Details' does not show any details, just the commands generating
- starting a browser on a machine with 256M of RAM takes a lot of time
and heavy swapping
- it seems to have a color palette problem, colors look ugly depending
on the position of the mouse pointer
- What does "By registering your product you will gain access to online
updates." on the web page means? YOU won't work without registration?
There won't be any more mirrors for updates?
- 'Please close this window' should be detailed, as there is no 'x'
button on the window. A 'Please use File & Quit' would be better'.
- I got an error at the end: "An error occurred while connecting to the
server." When I clicked details, I got a misleading error message: "this
service type requires a network connection, but none is present" An
ifconfig shows, that I have a properly configured network connection, I
could use that for ssh using names, so DNS is properly configured as well.
I have the problem that KsCD don't work anymore, beginning with SL10 or
change the motherboards to ICH5-8 KsCD is not working ?
I tested the cable and all i found by Google, all Player are working, but KsCD
The Problem are my friends ;), all like KsCD, and are not willing to change !
mit freundlichen Grüßen / best Regards,
Günther J. Niederwimmer
DVD drive fails to mount disc with automount/kde.
KDE detects when I insert a dvd disc, but in console I have running
udevmonitor --env, and it do'nt detect nothing.
If I accept the message from kde to open in new window, I got "An unknown
I have installed the update from the last saturday, (I mean beta 8).
I just installed from factory FTP for the first time. I see Deja Vu
fonts installed, but not Bitstream Vera. I think if that's to be the
default installation configuration then /etc/fonts/fonts.conf should be
setting an alias for the various Bitstream Vera Fonts to their DejaVu
counterparts so that the much smaller default (Nimbus Sans L) sans-serif
doesn't get substituted on web pages using Vera Sans as a Verdana fallback.
"Blessed are they whose ways are blameless, who walk according
to the law of the Lord." Psalm 119:11 NIV
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://mrmazda.no-ip.com/
SUSE/Novell has announced that non-GPL kernel modules will no longer be
part of future Novell products.
Since SUSE Linux 6.3, AVM has been providing pre-compiled drivers for SUSE
Linux. Since the release of SUSE 8.1 in September 2002, AVM drivers have
been integrated into SUSE Linux distributions. Each time a new SUSE Linux
Version beta cycle starts, AVM provides the latest drivers and Karsten Keil
does an excellent job integrating those drivers. Therefore, a new SUSE
Linux release goes hand in hand with the latest AVM driver development. At
present, nearly the entire AVM product portfolio comes up with SUSE
pre-compiled modules for ISDN and DSL devices and as such is part of the
AVM ISDN-Controller FRITZ!Card Classic
AVM ISDN-Controller A1
AVM ISDN-Controller FRITZ!Card PnP
AVM ISDN-Controller FRITZ!Card PCI / PCI v2.x
AVM ISDN-Controller FRITZ!Card PCMCIA
AVM ISDN-Controller A1 PCMCIA
AVM ISDN-Controller FRITZ!Card USB
AVM ISDN-Controller FRITZ!Card USB v2.x
AVM DSL/ISDN-Controller FRITZ!Card DSL
AVM DSL/ISDN-Controller FRITZ!Card DSL v2.0
AVM DSL/ISDN-Controller FRITZ!Card DSL USB
AVM DSL/ISDN-Controller FRITZ!Card DSL USB v2.0
AVM DSL-Controller FRITZ!Card DSL USB analog
AVM DSL-Controller FRITZ!Card DSL SL
AVM DSL-Controller FRITZ!Card DSL SL USB
AVM ISDN-Controller B1 v1.4/v2.0/v3.0 (ISA)
AVM ISDN-Controller B1 PCI / B1 PCI v4.0
AVM ISDN-Controller B1 PCMCIA
AVM ISDN-Controller C2
AVM ISDN-Controller C4
AVM ISDN-Controller T1
AVM ISDN-Controller T1-B
AVM FRITZ!X USB/ v2.0/ v3.0
AVM FRITZ!X ISDN
(AVM WLAN-Controller FRITZ!WLAN USB Stick)
In the past, the customer bought a fully functional distribution with the
release of the brand new SUSE Linux. He could use ISDN fax G3, analog modem
emulations or simply surf the internet via DSL/ISDN right away out of the
box. For most users, that is the most important point in the distribution
decision process. "Easy to use and right away surf the internet", that is
the feedback we receive from our customers, when they visit AVM at fairs.
The market share SUSE gained over past years is also based on SUSE's
user-friendly policy of AVM driver integration. For six years now this
strategic partnership with SUSE/Novell payed off for all parties. With
Novell's decision to have non-GPL drivers no longer integrated, AVMs
drivers will not be included on the distribution media anymore. The
customer then needs to have an internet connection to download AVM's
drivers or other packages. But without drivers the customer cannot download
anything from the internet.
This process will lead to our no longer being able to provide driver
packages to the end user with a new SUSE/Novell box release. Our driver
build and QS process will be subsequent to the box release instead of
parallel to the beta cycle. The process is extended. Moreover, if the
Novell decision is implemented as stated, the unique selling proposition of
the SUSE Linux Distribution is diminished. And ultimately this decision
will generate more support for both of us.
This mail is not intended to provoke a discussion of open vs. closed
The only intention of this mail is to make you aware of the consequences of
such a decision.
AVM Audiovisuelles Marketing und Computersysteme GmbH
Alt-Moabit 95, D-10559 Berlin
09.02.2006 17:14 opensuse-announce(a)opensuse.org
[opensuse-announce] SUSE Linux
I'd like to give you an update on our beta process with the following
list of topics:
* Deliverable of Beta4 and further schedule
* non-GPL kernel modules
* Kernel Changes km_ packages
* Major bug in Beta3: Fontconfig
* Package manager major changes
Deliverable of Beta4 and Further Schedule
Beta4 did not pass our internal tests, we have to delay it by one
The FACTORY distribution has been updated with our current packages
that everybody can use, but doing a complete installation from the
current FACTORY tree is NOT recommended. You should just update
single packages as needed.
We have decided to release Beta 4 on 2006-02-16 and Beta 5 on
2006-02-23. We'll finalize the schedule after testing and evaluating
these two betas.
non-GPL kernel modules:
Most developers of the kernel community consider non-GPL kernel
modules to be infringing on their copyright. Novell does respect this
position, and will no longer distribute non-GPL kernel modules as part of
future products. Novell is working with vendors to find alternative
ways to provide the functionality that was previously only available
with non-GPL kernel modules.
Kernel Changes / km_, kmp, and kernel-flavor-nongpl packages:
We added support to cleanly handle packages that contain kernel
modules by representing the dependencies of mouldes on the kernel ABI
as rpm dependencies. This allows third party modules to be provided
and integrated cleanly.
Modules that were previously included in our kernel packages using the
km_ package mechanism  have been converted to the new package
format ; the km_ mechanism is no longer supported. Packages that
contain additional kernel modules are now named name-kmp-kernelflavor
(e.g., wlan-kmp-default. lirc-kmp-smp).
The kmp mechanism  supports creating and using additional Kernel Module
Packages easily and reliably.
The kernel-kernelflavor-nongpl packages which contained modules that
had non-GPL licenses have been removed.
 The km_ package mechanism is described at
 Kernel Module Packages Manual for CODE10,
Major Bug in Beta3: Fontconfig
It might be that X11 apps just crash or are really slow (installation
of some packages took rather long), which was due to a bug in
fontconfig. A first fix is in fontconfig packages in the Beta3
fixed-rpm directory on ftp.opensuse.org .
Beta4 will fix most known bugs. Current packages are available at:
If you use them, update to both fontconfig and fonts-config. The
packages in there are newer than what is currently in the FACTORY
tree. If you find bugs in the m17n packages, please report them in
bugzilla stating the exact version you're using.
Package Manager Major Changes
We're replacing our package manager resolver library with a new version
libzypp is the integration of SUSE's yast2 Package manager and
Ximian's libredcarpet. At Novell we used two solutions so far - Red
Carpet and YaST package manager - and decided to merge both in a best
of breed approach.
The advantages for SUSE Linux are:
* A better resolver than before
* More information about why a package is installed or no solution is
* A better integration of all those feature that were added over the
years to our package manager.
* A command line interface ("rug")
* A common handling of packages *and* patches
* Dependency handling for update packages
* A better way to handle selections (we call them now "patterns")
* Remote management (not yet in SUSE Linux 10.1)
* Additional repositories during installation (no GUI in SUSE Linux 10.1)
* More flexibility in handling of different repositories, e.g. it is
possible to have additional patterns for each repository.
The new library handles yum metadata, YaST sources (both also remote
via ftp, http, nfs and smb) and additionally Zenworks, Opencarpet and
RCE (Red Carpet Enterprise) servers as installation sources. The
alternatives smart and apt-get will also work as they did on SUSE
Together with libzypp, we get the zmd daemon, the rug command line
interface, the zen-updater, zen-remover, zen-installer packages.
In addition to the existing packages, we're adding these new packages:
* zmd: system daemon used by rug, zen-*
* rug: Command line client
* web-updater: Updater with more features than zen-updater
* zen-updater: Simple updater
* zen-remover: Tool to remove packages
* zen-installer: Tool to add packages
We're still working on the integration of "libzypp" into our tree, the
package manager in our FACTORY tree is not yet fully functional.
Xgl is an Xserver that uses OpenGL for its drawing operations. Xgl
engineer David Reveman has posted enhancements to Xgl and a new
compositor, 'Compiz' with a request that it be added to the
freedesktop.org CVS repository. Some operations like antialiased font
rendering is noticeably faster with this technology, and future
graphics hardware might only have support for 3D operations and no 2D
core any more.
These additional packages have now been added to the SUSE Linux
FACTORY tree. Note that compiz has a couple of build problems that
need to be fixed before it will go out.
For details on XGL, please check http://www.opensuse.org/Xgl .
Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj/
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
[Anhang "att3brm9.dat" gelöscht von Sven Schmidt/AVM]
There are a couple of non-documented shortcomings in this package I
would like you all inform about:
1. NetworkManager at its present state cannot deal with WLAN card using
the prism54 chip. The corresponding bug 148210 has been marked FIXED
without submitting or communicating a fix. Workaround: Either do not use
NetworkManager (the traditional method supports prism54 with no
problems) or install ndiswrapper from the factory tree (not included in
the beta isos!) and use the corresponding MS driver with ndiswrapper.
Then NetworkManager can deal with it. Sort of a Trojan horse to get MS
drivers into Linux.
2. NetworkManager relies on DCHP in a very rigid manner: DHCP must
provide not only the IP address but also the name server address. As
many DHCP servers sit in DSL routers and similar devices they are often
limited in functionality. E.g. they cannot provided a fixed MAC-IP
address relation. Naturally these routers work as the name servers. So
in case you want to put your DHCP server on to another node this server
needs to address the issue of having a different name server (the one in
the router). All this because there is currently no way to specify a
fixed name server address NetworkManager will use (bug 159524).
FYI: (GhostScript Bug #685335)
------- Forwarded message follows -------
Dear Ulrich Windl,
Thank you for the sample file.
I confirm that released versions of Ghostscript generate PDF files
that convert to text with wrong encoding. This problem is fixed in the
current development version since rev. 6178. The development version of
Ghostscript can be obtained from the Subversion repository as
svn checkout http://svn.ghostscript.com:8080/ghostscript/trunk/gs/
------- End of forwarded message -------