Youtube summary using AI

 

To get youtube summary, its wholetranscript, relevant mindmap, relevant AI chat.

https://notegpt.io/youtube-video-summarizer

 

 

Enable/Disable wayland

==

// To check whether wayland / X11 

$ echo $XDG_SESSION_TYPE

x11

==
// To update wayland / x11

$ sudo gvim /etc/gdm3/custom.conf 

  // edit the line 

// this means x11

WaylandEnable=false

// and this means wayland

WaylandEnable=true

==

// To check after update - after reboot 

$ echo $XDG_SESSION_TYPE

==

syslog vs dmesg

Understanding /var/log/syslog and its Relation to dmesg

Both /var/log/syslog and dmesg play crucial roles in logging system activity on Linux-based systems, but they have distinct purposes and relationships. Here's a breakdown:

What is /var/log/syslog?

• This file acts as a central repository for various system logs originating from diverse sources like:
  • Users & applications
  • Background services (daemons)
  • System startup and shutdown processes
  • Kernel messages (after the system is fully booted)
• Syslog offers flexibility by allowing different log messages to be directed to specific log files within the /var/log directory based on predefined rules.
• This categorization facilitates targeted troubleshooting for specific areas of the system.

What is dmesg?

• Dmesg is a command-line tool that displays the contents of the kernel's ring buffer, a temporary storage for early boot messages and kernel-related activity.
• This buffer is volatile and resets upon system reboot, meaning dmesg only shows currently ongoing kernel activity.
• Dmesg isn't a file; it's a real-time snapshot of the kernel ring buffer.

Relationship between /var/log/syslog and dmesg:

• While syslog captures various system logs, dmesg focuses specifically on kernel messages.
• Early boot messages, before syslog starts, are only accessible through dmesg.
• Once syslog is operational, kernel messages are also directed to /var/log/syslog by default.
• So, dmesg offers a real-time glimpse of kernel activity, while /var/log/syslog provides a more comprehensive historical record of various system events, including kernel messages.

Key differences:

Feature	/var/log/syslog	dmesg
Scope	Diverse system logs	Kernel messages
Persistence	Persistent across reboots	Volatile, resets on reboot
Real-time view	Not directly	Yes
Specific file	Yes (individual files for categories)	No (command-line tool)

Note: I got the above from google gemini while looking about syslog and dmesg.

To setup default kernel in Linux(Fedora)

 

To setup default kernel in Linux(Fedora):

$ sudo grubby --info=ALL | grep -E "^kernel|^index"
index=0
kernel="/boot/vmlinuz-6.5.5-200.fc38.x86_64"
index=1
kernel="/boot/vmlinuz-6.2.15-100.fc36.x86_64"
index=2
kernel="/boot/vmlinuz-5.17.12-100.fc34.x86_64"
index=3
kernel="/boot/vmlinuz-0-rescue-eeca1c676989405b94bedc847e363048"
index=4
kernel="/boot/memtest86+x64.bin"

$ sudo grubby --default-kernel
// this displays the default kernel in your system.

==

$ sudo grubby --set-default-index=2
The default is /boot/loader/entries/eeca1c676989405b94bedc847e363048-5.17.12-100.fc34.x86_64.conf with index 2 and kernel /boot/vmlinuz-5.17.12-100.fc34.x86_64

$ sudo grubby --default-title
Fedora (5.17.12-100.fc34.x86_64) 34 (Workstation Edition)
 

 

 

Software version and end-of-life info.

Software version information

"End-of-life (EOL) and support information is often hard to track, or very badly presented. endoflife.date documents EOL dates and support lifecycles for various products."

https://endoflife.date/

For eg, kubernetes related info. here :

https://endoflife.date/kubernetes