To use tmux for a persistent Midnight Commander session that survives SSH disconnections:
- SSH into your server and start tmux:
ssh your-server tmux new -s mc
For a single-drive pool, both ZFS and ext4 are viable options, but they serve different purposes:
ZFS advantages on a single disk:
ext4 advantages:
To find and remove files by extension in a directory and its subdirectories on Linux, you can use the command: find /path/to/dir -name "*.extension" -type f -delete, replacing /path/to/dir with your directory path and *.extension with the specific file extension you want to delete. For example, to remove all .txt files, use find /path/to/dir -name "*.txt" -type f -delete.
The error you're seeing is related to extended attributes (ext2/ext3/ext4 filesystem attributes) that can't be transferred over Samba to your destination. This is a common issue when syncing between Linux systems via Samba shares.
To resolve this, you have a few options:
In your sync/backup tool:
In smb.conf on the server: Add or modify these settings in your share configuration:
The message "ACPI: OSL: Resource conflict; ACPI support missing from driver?" indicates a conflict between system resources claimed by the ACPI (Advanced Configuration and Power Interface) subsystem and those accessed by a legacy driver, such as hardware monitoring drivers like nct6775 or it87 This typically occurs when an ACPI OperationRegion (OpRegion) and a driver's I/O port range overlap, leading to potential instability or erratic system behavior
The root cause is often a misconfiguration or outdated firmware, particularly in the BIOS, where ACPI settings may not properly coordinate with hardware drivers While the warning suggests that the driver may lack ACPI support, the issue is frequently resolved by adjusting kernel parameters rather than modifying the driver itself
A common solution is to use the kernel parameter acpi_enforce_resources=no, which disables ACPI's enforcement of resource reservations, allowing legacy drivers to access conflict
To schedule a task to run automatically at system boot using cron, use the @reboot directive in the crontab file. This directive ensures the specified command or script executes once immediately after the system restarts To configure it, open the crontab editor with crontab -e, then add a line using the syntax @reboot [full path to command or script] For example, to run a script located at /root/backup.sh, add @reboot /root/backup.sh to the crontab It is essential to use the full path to the command or script, as the cron environment may not include standard paths like /usr/sbin
The @reboot directive can also be used with commands that require a delay after boot, such as @reboot sleep 300 && date >> ~/date.txt, which waits 300 seconds before executing the date command This is useful for ensuring system services are fully initialized before running dependent tasks. The cron daemon automatically detects changes to the crontab file after saving, so no manual restart
To create a 7z archive in the Linux terminal, you can use the following command:
7z a archive.7z files_to_archiveReplace archive.7z with the desired name for your archive, and files_to_archive with the files you want to include in the archive.
If you want to specify additional options, such as compression level or password protection, you can use the following format:
7z a -t7z -m0=lzma -mx=9 -mfb=64 -md=32m -ms=on archive.7z files_to_archiveYou can use the date command to include the current date and time in your echo statements. Here are a few common examples:
echo "Converted: $filename → $output at $(date)"echo "Converted: $filename → $output at $(date +'%Y-%m-%d %H:%M:%S')"The "no matching swap device is available" warning during update-initramfs indicates that the system's initramfs configuration references a swap partition UUID that is no longer present or valid, often due to changes like partition resizing, disk replacement, or switching from a swap partition to a swap file This typically occurs when the RESUME variable in /etc/initramfs-tools/conf.d/resume points to a UUID that no longer corresponds to an active swap device
To resolve this issue, first identify the current UUID of the active swap device using the blkid command and locate the line containing TYPE="swap" Then, update the /etc/initramfs-tools/conf.d/resume file to reflect the correct UUID If the swap configuration has changed significantly—such as switching from a partition to a file or using encrypted swap—it may be necessary to set RESUME=none instead of a UUID, especially if hibernation is not used Alternatively, if the RESUME va