With the new features that Gnome and KDE (K Desktop Environment) are adding, each desktop environment is challenging the other for a larger share of the market. If Linux-like operating systems come with one desktop environment, the user has the option to add to the other. Because of the ever-increasing sophistication of the new features, some latest versions of the operating system are including packages for both desktop environments, allowing users to have the option of switching from one desktop environment to another. In this article I will briefly talk about the new features of both Gnome and KDE, and then look at some similarities and important differences between the two desktop environments.

Faceoff @ O’Reilly ONLamp.com
Original post by E@zyVG

This video shows and explains the first part of the openSUSE 10.3 installation.

This part shows the installation after the first reboot.
Original post by E@zyVG
Little late with news, but still ….. The ATI/AMD fglrx driver for x86 and x86_64 Linux is now available! . In addition to the AIGLX support, the fglrx 8.42.3 driver includes X.Org server 1.4 support, video playback improvements, more performance improvements, and Rialto AGP fixes. While this driver quite promptly supports X.Org 7.3 / X server 1.4, it does not contain Linux 2.6.23 kernel support. The new features mentioned in the release notes include support for AIGLX, X.Org 7.3, products older than the R600 now being enabled, and a new 3D user interface in the ATI Catalyst Control Center Linux Edition.
AMD Proprietary Linux Release Notes for 8.42.3. For the time being the 8.42.3 download link is here. (x86_64)
Check this article for more details: AMD 8.42 Driver Brings Fixes, AIGLX!
P.S. Expect updates to my How-Tos for ATI driver installation and running Compiz Fusion on openSUSE with AIGLX, instead of Xgl … give me few days.
Original post by E@zyVG
At intervals I get complaints that one of the printers isn’t responding from a given machine. On investigation via the CUPS frontend the error is:
/usr/lib/cups/backend/lpd failed
Restarting the printer from there works, but it is slightly irritating.
This has happened several times in the last couple of days on one particular (aging) machine, which prompted me to seek a better solution. I found this entry which explains at the bottom how to change the CUPS setup appropriately. Edit /etc/cups/printers.conf and change the ErrorPolicy for each printer from stop-printer to retry-job. So far this seems to be working fine and I shall be rolling it out across the network.
Original post by Juliet Kemp