Nvidia new hotplug feature on Linux

 If you use nvidia driver for your GPU, you probably wonder why in some config, you can't hotplug your second monitor. You need to reboot to be able to use it. I found out recently with the help of chatgpt that I have been using old feature of nvidia driver all this time. The key settings are in /etc/environment.

 My previous settings:

  __NV_PRIME_RENDER_OFFLOAD=1
__GLX_VENDOR_LIBRARY_NAME=nvidia
LIBVA_DRIVER_NAME=nvidia
GTK_USE_PORTAL=1

KWIN_DRM_USE_EGL_STREAMS=1

If you can see above, I am using KWIN_DRM_USE_EGL_STREAMS=1 which means KDE is using NVIDIA’s old EGLStreams backend, which is notoriously bad at detecting new monitors in Wayland sessions. I should remove it and replace it with    GBM_BACKEND=nvidia-drm which is the modern buffer management backend for NVIDIA + Wayland that supports hotplugging of monitors.

 So i replaced it with this settings:

  
__NV_PRIME_RENDER_OFFLOAD=1
__GLX_VENDOR_LIBRARY_NAME=nvidia
LIBVA_DRIVER_NAME=nvidia
GTK_USE_PORTAL=1  
GBM_BACKEND=nvidia-drm

 I need to reboot once and testing it by unplugging and plugging it back. It works!

 That's all there is to it. Have fun! 

Renew letsencrypt ssl certificate for zimbra 8.8.15

 Letsencrypt certs usually consists of these files:

1. cert.pem

2. chain.pem

3. fullchain.pem

4. privkey.pem

I am not going to discuss about how you get those files from letsencrypt. This is for how to renew ssl cert for zimbra specifically version 8.8.15 GA 4717 that i am using. It may or may not work for previous or later version. YMMV

Put the folder containing the certs in /opt/zimbra. Let's say directory named letsencrypt. Make sure it owns by zimbra. 

Step 1:

Download letsencrypt root cert here to the same folder as those letsencrypt certs above. The file name is isrgrootx1.pem.

Step 2:

run this: cat isrgrootx1.pem >> chain.pem

Step 3:

Verify the certs using zmcrtmgr. Run the command as user zimbra. The output as following:

zmcertmgr verifycrt comm privkey.pem cert.pem chain.pem  
** Verifying 'cert.pem' against 'privkey.pem'
Certificate 'cert.pem' and private key 'privkey.pem' match.
** Verifying 'cert.pem' against 'chain.pem'
Valid certificate chain: cert.pem: OK

Step 4: 

If step 3 above is ok. Deploy the certs (asa user zimbra)

zmcertmgr deploycrt comm  cert.pem chain.pem

Step 5: 

If step above is successful. Restart the services (as user zimbra):

zmcontrol restart

If there's no error. Your zimbra's ssl is renewed successfully.

Workaround: insync icon doesn't show up in KDE's tray in Wayland session

 This is a workaround for insync icon doesn't show up in KDE's tray in Wayland session

1. Go to System Settings

2. Click on Startup and Shutdown menu on the left

3. Clik on + Add... button to add insync and then select + Add Application...

4. Select insync in the dialog and click OK

5. insync should be listed in the Autostart 

6. Click on the insync's Properties button

7. Go o Application tab and add QT_QPA_PLATFORM=xcb in the Command section as below and then click OK button to save the settings:

8. Reboot your computer. The insync's tray icon should show up in the tray.

That's all there is to it.

Wireguard on Linux : A basic approach using Ubuntu 20.04 LTS server and client

 We begin with a fresh installation of Ubuntu server 20.04 LTS

Server

1. Install wireguard
• sudo apt install wireguard
2. Generate server and client keys
• umask 077
• wg genkey | tee server_private_key | wg pubkey > server_public_key
• wg genkey | tee client_private_key | wg pubkey > client_public_key
3. Create server config
• Create a file wg0.conf in /etc/wireguard/
• [Interface] Address = 10.199.0.1/24 SaveConfig = true PrivateKey = <insert server_private_key> ListenPort = 51820 [Peer] PublicKey = <insert client_public_key> AllowedIPs = 10.199.0.2/24 <-- it means 254 IPs allowed to connect
• Note: If you only want 1 IP to connect,change /24 to /3You can change filename from wg0.conf to vpn.conf or whatever name you want
4. Running the wireguard's service
• sudo systemctl enable wg-quick@wg0 <-- need to run for the first time only
• sudo systemctl start wg-quick@wg0
5. Enable IP forwarding (Applicable for internet-enabled vpn connection. See client's note below)
• echo 1 > /proc/sys/net/ipv4/ip_forward
• sudo sysctl -p <-- to make the above change effective without reboot

Client

1. Install wireguard package
• sudo apt install wireguard
2. Create a file in /etc/wireguard called wg0.conf
• [Interface] Address = 10.199.0.2/24 PrivateKey = <insert client_private_key> DNS = 1.1.1.1 [Peer] PublicKey = <insert server_public_key> Endpoint = <insert vpn_server_address>:51820 AllowedIPs = 10.199.0.0/24 PersistentKeepalive = 60
• Note: Address parameter is the IP address for the client
• you can also change the name of the file wg0.conf to something else
• EndPoint is the wireguard server's IP address above.You can use IP or domain name
• DNS is the IP of DNS server for the client.
• *IF* the AllowedIPs is 0.0.0.0/0, it means all the traffic from the client
• will go through vpn server and if you want the client to be able to go to
• the internet, you must add this rule in the server:
• iptables -t nat -A POSTROUTING -s 10.199.0.0/24 -o eth0 -j MASQUERADE or
• You can put the iptables command above in server's wireguard config as below under [Interface]:
• PostUp = iptables -t nat -A POSTROUTING -s 10.199.0.0/24 -o eth0 -j MASQUERADE 
3. Connect the client
• sudo systemctl enable wg-quick@wg0 <-- run only this time
• sudo systemctl start wg-quick@wg0
• Test the connection: ping 10.199.0.1

That'sall there is to it. Hope it is working for you.

Cheers!

PS: Check this out! Easy setup for wireguard : https://github.com/burghardt/easy-wg-quick

            

How to install oci8 instant client for Ubuntu Linux

• First prerequirements are a working apache2 and php7.2 (Ubunti 18.04) environment.
• Download the basic (like instantclient-basic-linux.x64-12.2.0.1.0.zip) and the sdk (instantclient-sdk-linux.x64-12.2.0.1.0.zip) package from the Oracle Website http://www.oracle.com/technetwork/database/database-technologies/instant-client/downloads/index.html
• Upload both files to your webserver, you can use WinSCP (windows) or rsync/scp (linux) for it
• Unzip both files on server, in my case, you will get a new folder named "instantclient_12_2"
• Create destination folder : mkdir /opt/oracle
• Move and rename the instantclient folder: mv instantclient_12_2 /opt/oracle/instantclient
• Change rights on folder: chown -R root:www-data /opt/oracle 
• Check if you have the required packages for installing OCI8: apt install php7.2-dev php-pear build-essential libaio1 
• Create necessary soft links: ln -s /opt/oracle/instantclient/libclntsh.so.12.1 /opt/oracle/instantclient/libclntsh.so; ln -s /opt/oracle/instantclient/libocci.so.12.1 /opt/oracle/instantclient/libocci.so
• Add instant client to ld config files : echo /opt/oracle/instantclient > /etc/ld.so.conf.d/oracle-instantclient.conf
• Update Dynamic Linker Run-Time Bindings : ldconfig
• Now install OCI8 by pecl: pecl install oci8 
• The OCI8 installation is asking you for the right folder: instantclient,/opt/oracle/instantclient
• Add oci lib to the cli php config (console php): echo "extension = oci8.so" >>/etc/php/7.2/cli/php.ini
• Add oci lib to the apache php config: echo "extension = oci8.so" >> /etc/php/7.2/apache2/php.ini
• Set environment variables for the cli version (you will need to reboot the server after): echo "LD_LIBRARY_PATH=\"/opt/oracle/instantclient\"" >> /etc/environment echo "ORACLE_HOME=\"/opt/oracle/instantclient\"" >> /etc/environment
• Set environement variables for the apache version: echo "export LD_LIBRARY_PATH=\"/opt/oracle/instantclient\"" >> /etc/apache2/envvars; echo "export ORACLE_HOME=\"/opt/oracle/instantclient\"" >> /etc/apache2/envvars 
• Restart Apache: service apache2 restart or systemctl restart apache2 
• You're done, now you can test your connection to the Oracle database

Update: If you're using Ubuntu 22.04 LTS with php 8.1, then then pecl install oci8-3.2.1

Original source: https://serverfault.com/questions/911475/howto-install-oracle-oci8-instantclient-on-ubuntu-18-04

Setup SSL for Jira

How to do it...

Perform the following steps to import an SSL certificate:

1. Open up a command window and go to the directory where the certificate file
resides.

2. Generate a Java KeyStore (JKS) for JIRA by running the

keytool -genkey -alias jira -keyalg RSA -keystore /opt/jks/jira.jks

3. Import the certificate into KeyStore repository
keytool -import -alias jira -keystore JIRA_INSTALL/jira.jks -file file.crt

where file.crt is the certificate file.

4. Open the server.xml file located in the /opt/atlassian/jira/conf directory in a text editor.

5. Locate and uncomment the following XML configuration snippet:

maxThreads="150"
minSpareThreads="25" maxSpareThreads="75"
enableLookups="false"
disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
clientAuth="false"
sslProtocol="TLS" useBodyEncodingForURI="true"
keystoreFile="/opt/jks/jira.jks"
keystorePass="mypassword"
keyAlias="jira"
keystoreType="JKS"/>




Letsencrypt

Install certbot ppa:

sudo add-apt-repository ppa:certbot/certbot

then install certbot:
sudo apt install certbot


 run certbot for manual installation of letsencrypt using challenge via DNS:

sudo certbot certonly --manual --preferred-challenges dns

openssl pkcs12 -export -in fullchain1.pem -inkey privkey1.pem -out cert_and_key.p12 -name tomcat -CAfile chain1.pem -caname root

keytool -importkeystore -srcstorepass ppz2017 -deststorepass ppz2017 

-destkeypass ppz2017 -srckeystore jira.siza.my/cert_and_key.p12 

-srcstoretype PKCS12 -alias tomcat 

-keystore jira.jks

TO see what contains in the keystore:

keytool -list -keystore /opt/jks/jira.jks

6. Restart JIRA to apply the changes.
sudo systemctl stop jira
sudo systemctl start jira

Navigate through bash history with page up/down key

Linux bash history with Page up / Page down

In linux you can configure the pgup/pgdown keys to navigate through commands you typed that begin with the string you just typed. Type "mysql" and then hit "Page up", and you will see nothing but mysql-related commands.

Unfortunately this has to be configured anew on every machine or server/vm I work on, and I always forget where this is configured (and it takes a while to find it in google), so I thought I should write it down.

In /etc/inputrc, uncomment:

# alternate mappings for "page up" and "page down" to search the history
"\e[5~": history-search-backward
"\e[6~": history-search-forward

Restart your shell or use Ctrl+X, Ctrl+R to tell it to re-read.
(thanks stackoverflow)

Yep, it's not ".bashrc" but "inputrc". Not sure why this one is not hidden, but so it is. You could try ~/.inputrc for a local, user-specific configuration.

Tried this in Ubuntu, and it works.

And I tried it in kde-neon and it works.

Credit goes to Andreas Hennings aka "donquixote". Visit his page about this here

Error mounting NFS volume

If you got error to mount NFS volume in CentOS like below:

#mount -t nfs  10.12.1.23:/volume1/test  /mnt/test                                             
mount: wrong fs type, bad option, bad superblock on 10.12.1.230:/volume1/test,
       missing codepage or helper program, or other error
       (for several filesystems (e.g. nfs, cifs) you might
       need a /sbin/mount. helper program)

       In some cases useful info is found in syslog - try
       dmesg | tail or so.




To solve this problem, you need to install nfs-utils package:

#yum install nfs-utils

In debian-based distros, you can try install nfs-common package:

#apt install nfs-common


That's all there is to it!

Have fun :)

perl: warning: Setting locale failed.

If you have error like the following:

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = "en_US:en",
        LC_ALL = (unset),
        LC_MONETARY = "ms_MY.UTF-8",
        LC_ADDRESS = "ms_MY.UTF-8",
        LC_TELEPHONE = "ms_MY.UTF-8",
        LC_NAME = "ms_MY.UTF-8",
        LC_MEASUREMENT = "ms_MY.UTF-8",
        LC_IDENTIFICATION = "ms_MY.UTF-8",
        LC_NUMERIC = "ms_MY.UTF-8",
        LC_PAPER = "ms_MY.UTF-8",
        LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = "en_US:en",
        LC_ALL = (unset),
        LC_MONETARY = "ms_MY.UTF-8",
        LC_ADDRESS = "ms_MY.UTF-8",
        LC_TELEPHONE = "ms_MY.UTF-8",
        LC_NAME = "ms_MY.UTF-8",
        LC_MEASUREMENT = "ms_MY.UTF-8",
        LC_IDENTIFICATION = "ms_MY.UTF-8",
        LC_NUMERIC = "ms_MY.UTF-8",
        LC_PAPER = "ms_MY.UTF-8",
        LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").


The solution is to run this command:


sudo locale-gen en_US en_US.UTF-8 ms_MY ms_MY.UTF-8


The output :

Generating locales (this might take a while)...
  en_US.ISO-8859-1... done
  en_US.UTF-8... done
  ms_MY.ISO-8859-1... done
  ms_MY.UTF-8... done
Generation complete.



Run the command that produce the error. The error should not appear again.


That's all there is to it. Have fun!

KDE desktop with no taskbar

Depending on the cause of this issue in your case, you may be able to fix it by editing your plasma-org.kde.plasma.desktop-appletsrc file and then performing

kquitapp plasmashell && kstart plasmashell

One cause I've run into is the buggy multimonitor functionality sometimes "losing" the taskbar from my laptop screen after I've connected to an external monitor and later disconnected (this was in plasma 5.5 or 5.6, I think). In this scenario, I've found the problem to be the lastScreen setting in the taskbar configuration. To fix this, find the section of text in plasma-org.kde.plasma.desktop-appletsrc that looks like:

[Containments][1]
activityId=
formfactor=2
immutability=1
lastScreen=1
location=4
plugin=org.kde.panel
wallpaperplugin=org.kde.image

(Some of these lines may vary in your configuration. In mine, this section was only a dozen lines down in the file, but I have no idea how much that may vary.)

Setting lastscreen=0 fixed the problem for me. I assume that 0 represents my laptop screen, and 1 is the external monitor.

If in doubt, you can always perform the procedure in jozxyqk's answer, and compare the newly generated plasma-org.kde.plasma.desktop-appletsrc with your saved plasma-org.kde.plasma.desktop-appletsrc.bak before restoring an edited version of your saved copy.

Using bluetooth headset on Linux

I bought a bluetooth headset recently. I got to make it work with my Linux laptop. There are 2 tools that I found useful in my experience in making it works such as:

1. rfkill - let you know whether particular feature is blocked or not

Example: rfkill list

0: phy0: Wireless LAN

        Soft blocked: no

        Hard blocked: no

1: asus-wlan: Wireless LAN

        Soft blocked: no

        Hard blocked: no

2: asus-bluetooth: Bluetooth

        Soft blocked: yes

        Hard blocked: no

As you can see, the bluetooth is soft blocked. It means, you have to turn it on using software. Usually you can enable it using a GUI tool in your KDE or GNOME desktop. If it is hard blocked, it means you have to turn it on by pressing a combination of or a key on your keyboard or a switch. 

2. pavucontrol

Taken verbatim from here:

Pulseaudio volume control (pavucontrol) is a simple gtk+ based volume control tool (mixer) for the pulseaudio sound server. in contrast to classic mixer tools this one allows you to control both the volume of hardware devices and of each playback stream separately. it also allows you to redirect a playback stream to another output device without interrupting playback.

It is a powerful tool to control your input and output devices. If you want to use your bluetooth headset, you can change it here (see picture above).

That's all there is to it. Have fun!

Introducing Pipelight

Hi there!

I was trying to access a page with silverlight on it but I couldnt view the page correctly because I was using Mozilla and Linux. I need to instll silverlight plugin. I could've installed Project Mono but it has been discontinued the project and won't support it in the future. In Ubuntu forum, someone mentioned about Pipelight. The concept of Pipelight is running the plugin using wine (it will run in the background). It solved my problem. I can now access the page and view it correctly. Try it.

Have fun! :D

How to disable ctl+alt+backspace key from killing your X server in KDE?

I recently accidentally pressed ctrl+alt+backspace key combination. It killed my X server. To prevent it from happening again and to protect your unsaved works, you have to disable this key combination. For KDE 4.x users, below are the steps:

Open the settings page:
Menu --> Applications --> Settings --> System Settings

Open the Input Devices:

Clik on Keyboard and the Advanced tab and click on the Configure keyboard options checkbox:

Find Key sequence to kill the X server from the list and untick the check box for Ctrl + Alt + Backspace

And then click the Apply button to save the settings.

That is all there is to it. Have fun!

Enable or disable a service from autostarting on ubuntu and derivatives

To make a upsmon service to autostart during bootup:

sudo update-rc.d upsmon enable

The output looks like this:

update-rc.d: warning: /etc/init.d/upsmon missing LSB information
update-rc.d: see
 Disabling system startup links for /etc/init.d/upsmon ...
 Removing any system startup links for /etc/init.d/upsmon ...
   /etc/rc0.d/K06upsmon
   /etc/rc1.d/K06upsmon
   /etc/rc2.d/S61upsmon
   /etc/rc3.d/S61upsmon
   /etc/rc5.d/S61upsmon
   /etc/rc6.d/K06upsmon
 Adding system startup for /etc/init.d/upsmon ...
   /etc/rc0.d/K06upsmon -> ../init.d/upsmon
   /etc/rc1.d/K06upsmon -> ../init.d/upsmon
   /etc/rc6.d/K06upsmon -> ../init.d/upsmon
   /etc/rc2.d/K39upsmon -> ../init.d/upsmon
   /etc/rc3.d/K39upsmon -> ../init.d/upsmon
   /etc/rc5.d/K39upsmon -> ../init.d/upsmon

To disable autostart:

sudo update-rc.d upsmon disable


The output:

update-rc.d: warning: /etc/init.d/upsmon missing LSB information
update-rc.d: see
 Enabling system startup links for /etc/init.d/upsmon ...
 Removing any system startup links for /etc/init.d/upsmon ...
   /etc/rc0.d/K06upsmon                                                                          
   /etc/rc1.d/K06upsmon                                                                          
   /etc/rc2.d/K39upsmon                                                                          
   /etc/rc3.d/K39upsmon                                                                          
   /etc/rc5.d/K39upsmon                                                                          
   /etc/rc6.d/K06upsmon
 Adding system startup for /etc/init.d/upsmon ...
   /etc/rc0.d/K06upsmon -> ../init.d/upsmon
   /etc/rc1.d/K06upsmon -> ../init.d/upsmon
   /etc/rc6.d/K06upsmon -> ../init.d/upsmon
   /etc/rc2.d/S61upsmon -> ../init.d/upsmon
   /etc/rc3.d/S61upsmon -> ../init.d/upsmon
   /etc/rc5.d/S61upsmon -> ../init.d/upsmon
















To see available services:




service --status-all

Changing display manager on Linux Mint using command

If you used to login to Linux using GUI, it means you were using X display manager. There are many display managers. Among popular ones are gdm, kdm, mdm and lightdm. You can change display manager using gui tools but you can also use command for that purpose. On Linux Mint (and i think on other debian-based distros), you can use this command (say you are using gdm):

dpkg-reconfigure gdm

A dialog will ask you whether you want to change to other installed display managers or not. You can replace mdm with other installed display manager.

That's all there is to it folk. Have fun! :D

Proxmox KVM usb passthrough

Open KVM monitor for your KVM machine in Proxmox GUI or in the command line with the following command:

# qm monitor 168
Entering Qemu Monitor for VM 168 - type 'help' for help
qm> 

Show the usb devices info from your host machine:

qm> info usbhost
  Bus 4, Addr 2, Port 1, Speed 12 Mb/s
    Class 00: USB device 046b:ff10, Virtual Keyboard and Mouse
  Bus 6, Addr 2, Port 2, Speed 1.5 Mb/s
    Class 00: USB device 0624:0294, Dell 03R874
  Bus 2, Addr 3, Port 1, Speed 480 Mb/s
    Class 00: USB device 0930:6533, DataTraveler 2.0
  Auto filters:
    Bus *, Addr *, Port *, ID 0930:6533

According to device “USB device 0930:6533” in the example, add the device to guest machine:

qm> device_add usb-host,id=myusb,vendorid=0x0930,productid=0x6533

Verify that the new usb device is added in your guest:

qm> info usb
  Device 0.1, Port 1, Speed 12 Mb/s, Product QEMU USB Tablet
  Device 0.3, Port 2, Speed 12 Mb/s, Product QEMU USB Hub
  Device 0.4, Port 2.1, Speed 480 Mb/s, Product DataTraveler 2.0

After using it, remove usb device from your guest:

qm> device_del myusb

If you run the command again, you will see the usb device is gone from your guest:

qm> info usb
  Device 0.1, Port 1, Speed 12 Mb/s, Product QEMU USB Tablet
  Device 0.3, Port 2, Speed 12 Mb/s, Product QEMU USB Hub

This has been tested in Proxmox 3.0/957f0862

Source

Book review: Implementing SAMBA 4

Samba is a Windows implementation of sharing files and folders in Linux world. It is a favorite way of sharing your files on Linux with Windows users. But its use is much more than that. It can also act as servers of various roles.

Implementing SAMBA 4 is a book worth reading for Linux admins, system engineers or anybody who plan to use and master SAMBA configurations. In this version, a new feature, Active Directory Domain Controller (AD DC) is the most sought after by admins. This will let you configure SAMBA 4 as an AD DC. Using Debian 7 as the OS, I found no problem with it although many admins out there are using Fedora/Red Hat/CentOS as the main distros of choice.

Looking at the table of contents, I can say this book is not for beginners. So you have been warned. :)

Reading the sample chapter provided (Chapter 3), this book is an interesting to read. Steps are shown in pictures and clearly explained. Although I have little knowledge of AD DC, this book will make it easier for you to understand the steps needed by lots of screenshots.

Other topics mentioned that I found important and interesting are:

• Understand the migration steps from Samba 3 to Samba 4
• Integrate GNU/Linux operating system authentication into the AD
• Understand the tasks and attention points when replacing a Microsoft Windows AD

If you are looking for a reading to better understand on how to configure SAMBA 4 for your AD DC, I recommend this kind of book.

ralink firmware

In Mageia, not all packages from non-free repo are installed by default. One of them is ralink-firmware. In Mageia 2, various ralink wireless firmwares are separated in many packages like rt61-, rt2860-, rt2870-, rt3090-, rt73-. Now they are bundled in one package.

If you connect external wireless hardware that uses those rt chipsets family, you have to install this package. Please examine your syslog for the error in loading the driver such as this:

Dec 24 18:54:00 localhost kernel: ieee80211 phy1: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
Dec 24 18:54:00 localhost kernel: ieee80211 phy1: rt2x00lib_request_firmware: Error - Failed to request Firmware

Install the firmware by issuing :

urpmi ralink-firmware

or you can use rpmdrake GUI for that.

Cheers.

Mandriva Linux 2009 released

Mandriva has released its latest desktop edition which comes in 4 edition: One, Free, PowerPack and Mandriva Flash.

Mandriva One comes in CD and suitable for those who want to start using Mandriva Linux in no time. You can boot in to live CD and start working. It has the option to install to hard disk. This edition comes with proprietary softwares.

Mandriva Free is the free edition. It doesn't contain proprietary softwares. You can add those later though if you add the relevant repositories.

Mandriva Powerpack is a commercial pack containing proprietary packages such as flash plugin, nvidia, nvidia, ati, mp3 codec etc.

Mandriva Flash is a USB disk version of Mandriva. It now uses 8GB USB drive instead of 4GB in previous version. You have to order it from Mandriva Store.

More info on this release

I have been using Mandriva Linux for almost 7 years now and in my opinion it is one of the best distributions out there.

On a quest to get a 3D desktop

I'm very excited with 3D desktop after watching AIGLX and XGL in action with beryl or compiz window manager. I haven't been able to get it run on my computer with my video card since it is not supported composite extension and DRI simultaneously. The ATI's proprietary driver (fglrx) I use, doesn't support dri and composite extension simultaneously. I downloaded kororaa live CD to try it out and I was amazed.

At one point, I downloaded xorg, compiz and Mesa from cvs and I managed to get Xorg compiled with Xgl enabled but I couldn't get compiz to run because there was no composite extension.

Picture above is a screenshot of my desktop running dropline GNOME on Slackware and Xgl running in a window with KDE as the window manager. It's like running X in X or nested X.

However, I'm still trying... :)

Other links:
Xgl,compiz and Mesa - http://www.freedesktop.org/wiki/Software_2fXgl
Dropline GNOME - http://www.droplinegnome.org/