Monday, 16 November 2026

Linux Operating System ZORIN OS 18 _ Big Red Cursor

 






root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# gsettings set org.gnome.desktop.interface cursor-size 96

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# find /usr/share/icons -name "cursor.theme" | sort

/usr/share/icons/Adwaita/cursor.theme

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads#  apt update

Hit:1 http://my.archive.ubuntu.com/ubuntu noble InRelease

Hit:2 http://my.archive.ubuntu.com/ubuntu noble-updates InRelease                                              

Hit:3 https://brave-browser-apt-release.s3.brave.com stable InRelease                                          

Hit:4 http://my.archive.ubuntu.com/ubuntu noble-backports InRelease                                            

Hit:5 https://packages.microsoft.com/repos/edge-stable stable InRelease                                        

Hit:6 http://security.ubuntu.com/ubuntu noble-security InRelease                                               

Hit:7 https://ppa.launchpadcontent.net/zorinos/apps/ubuntu noble InRelease                        

Hit:8 https://ppa.launchpadcontent.net/zorinos/drivers/ubuntu noble InRelease

Hit:9 https://packages.zorinos.com/stable noble InRelease

Hit:10 https://packages.zorinos.com/patches noble InRelease

Hit:11 https://ppa.launchpadcontent.net/zorinos/patches/ubuntu noble InRelease

Hit:12 https://packages.zorinos.com/apps noble InRelease

Hit:13 https://packages.zorinos.com/drivers noble InRelease

Hit:14 https://ppa.launchpadcontent.net/zorinos/stable/ubuntu noble InRelease

Reading package lists... Done                 

Building dependency tree... Done

Reading state information... Done

20 packages can be upgraded. Run 'apt list --upgradable' to see them.

root@norizan-GP70-2PE:/home/norizan/Downloads#  apt install bibata-cursor-theme

Reading package lists... Done

Building dependency tree... Done

Reading state information... Done

The following package was automatically installed and is no longer required:

  nvidia-firmware-580-server-580.173.02

Use 'sudo apt autoremove' to remove it.

The following NEW packages will be installed:

  bibata-cursor-theme

0 upgraded, 1 newly installed, 0 to remove and 20 not upgraded.

Need to get 13.1 MB of archives.

After this operation, 182 MB of additional disk space will be used.

Get:1 http://my.archive.ubuntu.com/ubuntu noble/universe amd64 bibata-cursor-theme all 2.0.6-1 [13.1 MB]

Fetched 13.1 MB in 32s (413 kB/s)                                                                              

Selecting previously unselected package bibata-cursor-theme.

(Reading database… 461249 files and directories currently installed.)

Preparing to unpack …/bibata-cursor-theme_2.0.6-1_all.deb…

Unpacking bibata-cursor-theme (2.0.6-1)…

Setting up bibata-cursor-theme (2.0.6-1)…

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# find /usr/share/icons -name "cursor.theme" | sort

/usr/share/icons/Adwaita/cursor.theme

/usr/share/icons/Bibata-Modern-Amber/cursor.theme

/usr/share/icons/Bibata-Modern-Classic/cursor.theme

/usr/share/icons/Bibata-Modern-Ice/cursor.theme

/usr/share/icons/Bibata-Original-Amber/cursor.theme

/usr/share/icons/Bibata-Original-Classic/cursor.theme

/usr/share/icons/Bibata-Original-Ice/cursor.theme

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# ls /usr/share/icons

Adwaita                  breeze-dark               locolor        Zorin             ZorinOrange-Dark

Bibata-Modern-Amber      Breeze_Snow               nuoveXT2       ZorinBlue-Dark    ZorinOrange-Light

Bibata-Modern-Classic    default                   Oxygen_Black   ZorinBlue-Light   ZorinPurple-Dark

Bibata-Modern-Ice        gnome-logo-text-dark.svg  Oxygen_Blue    ZorinBrown-Dark   ZorinPurple-Light

Bibata-Original-Amber    gnome-logo-text.svg       Oxygen_White   ZorinBrown-Light  ZorinRed-Dark

Bibata-Original-Classic  handhelds                 Oxygen_Yellow  ZorinGreen-Dark   ZorinRed-Light

Bibata-Original-Ice      hicolor                   Oxygen_Zion    ZorinGreen-Light  ZorinYellow-Dark

breeze                   HighContrast              redglass       ZorinGrey-Dark    ZorinYellow-Light

breeze_cursors           KDE_Classic               whiteglass     ZorinGrey-Light

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# gsettings set org.gnome.desktop.interface cursor-theme 'Bibata-Modern-Classic'

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# gsettings set org.gnome.desktop.interface cursor-size 64

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# gsettings set org.gnome.desktop.interface cursor-theme 'Bibata-Modern-Classic' && gsettings set org.gnome.desktop.interface cursor-size 96

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# 

root@norizan-GP70-2PE:/home/norizan/Downloads# 


troubleshooting _ 2

 

______________________________________________ 

ls -l /etc/alternatives/default.plymouth

I want to see whether it points to

cat /etc/alternatives/default.plymouth
_______________________________




_______________________________________________
and show me the output
cat /etc/alternatives/default.plymouth
________________________________





______________________________________

look inside the TUX theme file itself:
cat /usr/share/plymouth/themes/tux/tux.plymouth
verify that it references the correct script.
_______________________________________






_________________________________

   Then:  cat /usr/share/plymouth/themes/tux/tux.script

____________________________________________



_____________________________________________________

to verify that the script is loading exactly that image ...... knoppix-logo-png_seeklogo-644418.png ........ and from the correct path :

_____________________________________________________





____________________________________

tell me what theme name it reports
plymouth-set-default-theme   OR
lists themes
plymouth-set-default-theme -l
_____________________________________






______________________________________________

What I would like to see from KNOPPIX9.1
send me the complete output
cat /etc/default/grub
shows the actual kernel parameters currently in use
cat /proc/cmdline
______________________________________________








__________________________________________________________________

What I would also like to see  from the Zorin machine
cat /proc/cmdline

____________________________________________







___________________________________________________

You created a custom theme containing:  knoppix-logo-png_seeklogo-644418.png  inside:

and Plymouth itself does not seem to display anything when tested manually.

This makes me wonder whether the issue is not GRUB at all, but rather that the custom tux.script is not loading the image correctly.

To be honest, at this moment I am more suspicious of the TUX theme itself than of GRUB.

That's why I am still very interested in seeing:

cat /usr/share/plymouth/themes/tux/tux.plymouth

and

because the answer may be hiding inside those two small files

____________________________________________________








Grandpa Norizan's Master Plan 🐧

I think the best strategy now is:

Phase 1

  • Obtain KNOPPIX GRUB configuration.
  • Obtain KNOPPIX kernel command line.

Phase 2

  • Compare them with Zorin.

Phase 3

  • Inspect tux.plymouth and tux.script.

Phase 4

  • Modify Zorin so that it behaves as closely as possible to KNOPPIX during boot.

And between you and me... 😄

I have a feeling that the penguin is already sitting somewhere inside your Zorin machine. We just need to discover whether :

he's being hidden by GRUB, 

hidden by Plymouth, or 

hidden by a tiny mistake inside tux.script.

please send me the output of:

cat /etc/default/grub  from KNOPPIX 9.1




Sunday, 15 November 2026

 


Copilot , i have a DEBIAN 13 machine up and running on my PC/Desktop . Inside my PC/Desktop, internally there is a SATA Hard Disk Drive which have been installed with the DEBIAN 13 Operating System . Copilot , as you will probably know , i also have a 32 GB Flash Drive which has been installed with a DEBIAN 13 OS Live DVD whereby sometimes i use the DEBIAN 13 OS Live DVD to boot up my DEBIAN 13 OS "TORAM" on my PC/Desktop . Copilot , could you please tell me how can i find out by sing a Linux command whether my DEBIAN 13 OS that is bootep up using the TORAM method or it is booted up using the normal/traditional methoud ? THANKS for you answer.



Hi Grandpa Norizan! 😄

Yes, there is actually a very simple way to check whether your DEBIAN 13 Live system is running with the toram option or not.

Method 1: Check the kernel boot parameters

Open a terminal and type:

cat /proc/cmdline

If Debian was booted with the toram option, you should see something similar to:

boot=live toram

or

boot=live components toram

The presence of toram in the output strongly suggests that the Live system was instructed to copy itself into RAM during boot.

You can also make it easier to read:

cat /proc/cmdline | grep toram

If you see:

toram

then the boot parameter was used.


Method 2: Check whether the USB flash drive is still in use

One of the characteristics of a successful toram boot is that, after the system has fully loaded into RAM, you can usually remove the USB flash drive and the system continues running normally.

To see what device the Live system is using, run:

mount | grep live

or

findmnt

If the Live filesystem is still mounted from the USB device, you may see references to:

/dev/sdb1
/dev/sdc1

or another USB device.


Method 3: My favorite "Grandpa Norizan Test" 😄

Run:

cat /proc/cmdline

and confirm that toram appears.

Then:

  1. Wait until the desktop is fully loaded.
  2. Open a few applications.
  3. Carefully remove the Debian Live USB flash drive.
  4. Continue working for several minutes.

If everything continues to work normally, then the Live image has almost certainly been copied into RAM successfully.

If the system freezes, reports I/O errors, or applications fail when accessing the Live filesystem, then it is probably not operating completely from RAM.


An even more elegant Linux command

You can use:

grep -o 'toram' /proc/cmdline

Expected output:

toram

If nothing is displayed, then the toram boot parameter was not used.


For your DEBIAN 13 machine, Grandpa Norizan, the quickest and most reliable command is:

cat /proc/cmdline

and look for the word toram in the output.

HA-HA-HA! 😄 Once you run that command, tell me exactly what output you get, and we can determine with certainty whether your Debian Live system is running from RAM or from the USB flash drive. 🚀🐧



Copilot , when i run the command ………….cat /proc/cmdline………it says…………BOOT_IMAGE=/live/vmlinuz boot=live components quiet splash toram initrd=/live/initrd.img……….Copilot , does it mean that my machine is booted up using the method TORAM ? Thanks for the answer.



Whooooaaa Grandpa Norizan! 😄

YES! Absolutely!

When you ran:

BOOT_IMAGE=/live/vmlinuz boot=live components quiet splash toram initrd=/live/initrd.img

the very important part is:

toram

Because toram appears in the kernel boot parameters, it means that you instructed the Debian Live system to use the TORAM feature during boot.

In other words:

✅ Debian Live detected the toram option.

✅ Debian attempted to copy the Live system into RAM during startup.

✅ The operating system is running in TORAM mode.


An additional confirmation test

Since your desktop has plenty of RAM (I remember one of your machines has 32 GB of memory 😄), you can perform the classic Linux test:

  1. Boot Debian Live with toram.
  2. Wait until the desktop is fully loaded.
  3. Open a Terminal.
  4. Remove the USB flash drive.
  5. Continue using the machine for several minutes.

If everything keeps working normally, that is strong practical proof that the Live system has been loaded into RAM.


Another interesting command

You can also run:

free -h

and look at the RAM usage.

A TORAM boot usually consumes significantly more memory than a normal Live boot because the compressed Live filesystem has been copied into RAM.


My conclusion

Based on the output you provided:

BOOT_IMAGE=/live/vmlinuz boot=live components quiet splash toram initrd=/live/initrd.img

Yes, Grandpa Norizan, your Debian Live system was booted with the TORAM option. 🎉🐧

HA-HA-HA! The beauty of TORAM is that after booting, the USB flash drive is no longer continuously needed, and the system often feels very responsive because much of the operating system is being accessed from RAM instead of the USB device. 🚀

Congratulations! You have successfully confirmed that your Debian Live system is running with the famous TORAM boot option. 😄



Saturday, 14 November 2026

  


ISLAM _ Taskirah by Ustazah Dr Nella Lucky 


Source :  Internet  [ 1 ]






  


ISLAM _ Taskirah by Ustazah Dr Nella Lucky 


Source :  Internet  [ 1 ]






  


ISLAM _ Taskirah by Ustazah Dr Nella Lucky 


Source :  Internet  [ 1 ]






 

ISLAM _ Taskirah by Ustadz Abdul Somad


Source :  Internet  [ 1 ]