Tux Machines
Posted by Roy Schestowitz on Jan 28, 2023
=> /n/2023/01/28/Android_Leftovers.3.gmi Android Leftovers
=> /n/2023/01/28/Open_Hardware_Modding_Stories.gmi Open Hardware/Modding Stories
=> https://www.matuzo.at/blog/2023/100daysof-day90/ ↺ Day 90: scoped styles in container queries
Rules within a container query only apply to descendants of that container.
If you write a media query and you put rules in the media block, the rules apply to the entire document.
=> https://www.matuzo.at/blog/2023/100daysof-day89/ ↺ Day 89: higher-order custom properties
Caution: If you’re a fan of Tailwind or similar utility frameworks, you might find this post offensive because it suggests using fewer classes instead of more.
=> https://utcc.utoronto.ca/~cks/space/blog/linux/ZFSOnLinuxTrimNotes ↺ Some notes on using using TRIM on SSDs with ZFS on Linux
ZFS on Linux has two ways to periodically TRIM your pool(s), the automatic way and the manual way. The automatic way is to set 'autotrim=on' for selected pools; this comes with various cautions that are mostly covered in zpoolprops(7). The manual way is to periodically run 'zpool trim' with suitable arguments. One significant advantage of explicitly running 'zpool trim' is that you have a lot more control over the process, and in particular manual trims let you restrict trimming to a single device, instead of having trimming happen on all of them at once. If you trim your pools for only one device at a time (or only one device per vdev) and then scrub your pool afterward, you're pretty well protected against something going wrong in the TRIM process and the wrong disk blocks getting erased.
=> https://utcc.utoronto.ca/~cks/space/blog/sysadmin/ZFSTrimUsefullnessQuestion ↺ Some thoughts on whether and when TRIM'ing ZFS pools is useful
Now that I've worked out how to safely discard (TRIM) unused disk blocks in ZFS pools, I can think about if and when it's useful or important to actually do this. In theory, explicitly discarding disk blocks on SSDs speeds up their write performance because it gives the SSD more unused flash storage space it can pre-erase so the space is ready to be written into. So the first observation is that how much TRIM'ing a pool matters depends on how much you're writing to it (well, to filesystems and perhaps zvols in it). If you're writing almost nothing to the pool, you have almost no need of fresh chunks of flash storage.
=> https://www.linuxtechi.com/install-fedora-server-step-by-step/ ↺ How to Install Fedora Server 37 Step-by-Step
In this post, we will cover how to install Fedora Server 37 step-by-step with screenshots.
=> https://unixcop.com/increase-load-stress-command-linux/ ↺ How to increase load with stress command on Linux
Many times we want to experience how good is our processor when the workload is very high. Occasionally, we can’t do it but thanks to a tool it is easy to do it. Today, you will learn how to increase load with stress command on Linux.
=> https://tecadmin.net/resolved-npm-error-eacces-permission-denied/ ↺ Error: EACCES: permission denied, scandir (Resolved) - TecAdmin
The “Error: EACCES: permission denied, scandir” error can also occur when using NPM (Node Package Manager) and trying to install a package. This is because NPM needs to access certain directories on your system, such as log files under the home directory or the global node_modules directory, and the error occurs when it doesn’t have the proper permissions to do so.