If you use external USB drives and storage devices, you can safely disconnect and disconnect them in the graphical desktop environment of your Linux system with a few clicks. Devices issued in this way will no longer be accessible, as the associated block device names will be lost and the hardware will be de-energized. By default, we can only re-use hardware by physically reconnecting it, which requires human intervention. There may be a need to still have access to our software-disconnected, turned-off storage device without having to physically unplug it and then reconnect it. If for any reason you want to be able to access your logically disconnected and unplugged USB storage device, this tutorial will look at how to restart and make available your external HDD, flash drive, or card reader without having to physically reconnect it.

When you connect an external USB drive or flash drive to your machine, the Linux system will automatically mount its file system for the appropriate user. However, this automatic mount may fail for some reason and you will get a small window with an "Not authorized to perform operation" error message.

If our locales are not set correctly or are set up after installing or updating a program, Perl-based programs will report an error. In this short guide, we will look at the solution to this error.

ISPConfig uses a variety of protection systems to keep it secure, including IDS (Intrusion Detection System) technology. However, this setting may be too sensitive and disable us from the control panel as well. In this little troubleshooter, we'll see what we can do if our ISPConfig control panel doesn't allow us, but instead gets a "Possible attack detected. This action has been logged." error message.

If you are using custom PHP versions on your Debian server that are updated via the Sury.org repository, you have previously configured this repository, which was still working before, and APT upgraded the packages without any problems. However, an update may cause an error in the package manager and you may not be able to access the latest packages. We will remedy this problem in this short troubleshooter.

PHP sessions are global variables that transmit data stored during web visits across multiple pages, i.e., they are not lost when moving from one page to another. PHP accomplishes this by assigning unique IDs to visits (sessions) and creating files in the server-side file structure associated with those IDs in which it stores the data required for the session. The system places these files in a specific directory, usually tmp, which is normally deleted by the garbage collector after a specified time. However, the situation is sometimes not so obvious. This is because if the PHP environment on the server changes, the garbage collector may not be able to delete these obsolete, unnecessary session files. In this description, we will look at how we can use our own solution to ensure that these session files are deleted when the default cleaning system cannot remove them.

There have been several base system updates for Drupal 9 CMS in recent weeks, so it's worth reviewing its update mechanism as before for the Drupal 8 update. In this description, I'm going to update the Drupal 10 website installed on the Debian 9 (Buster) perfect server from 9.1.2 to 9.1.4, so here we now jump to several versions at once. There are two ways to do this: first with a composer, and then look at the manual update.

On January 2021, 8, Linux Mint announced the release of 20.1, codenamed "Ulyssa," which was made available in a variety of desktop environments. In this description, we will install the version packaged with Cinnamon. We’ve dealt with a Linux Mint 20 (ulyana) based installation before, now let’s look at the latest version of the Linux Mint Linux distribution with the Cinnamon desktop in its original form. This installation is performed on a machine with a 64-bit BIOS system, where the 64-bit system is mounted on a single partition on a hard disk created with an MBR partition scheme.