Exactly. All modern CPUs are so standardized that there is little reason to store all the data in ASCII text. It's so much faster and less complicated to just keep the raw binary on disk.
FuckBigTech347
NVK doesn't support older cards though last time I checked. Pretty funny how I ended up with a stack of paperweights because NVidia dropped support and Nouveau/NVK can't get their shit together and instead of focusing on existing hardware they rather keep chasing the "latest and greatest".
AI? Look, I helped a friend fix a new install. It wasn’t Linux fault, it was a setting in the bios that needed to be changed. But the AI had them trying all sorts of things that were unrelated, and was never going to help. Use with a grain of salt.
I have the same experience but sometimes it was even worse; Sometimes the AI would confidently recommend doing things that might lead to breakage. Personally I recommend against using AI to learn Linux. It's just not worth it and will only give new users a false impression of how things work on Linux. People are much better off reading documentation (actual documentation, not SEO slop on random websites) or asking for help in forums.
It has a green lock icon with the word "Private" next to it so it's fine bro.
arch-meson
is a small wrapper script for meson
:
$ cat /usr/bin/arch-meson
#!/bin/bash -ex
# Highly opinionated wrapper for Arch Linux packaging
exec meson setup \
--prefix /usr \
--libexecdir lib \
--sbindir bin \
--buildtype plain \
--auto-features enabled \
--wrap-mode nodownload \
-D b_pie=true \
-D python.bytecompile=1 \
"$@"
That's only been my experience with software that depends on many different libraries. And it's extra painful when you find out that it needs hyper specific versions of libraries that are older than the ones you have already installed. Rust is only painless because it just downloads all the right dependencies.
Some old software does use 8-Bit ASCII for special/locale specific characters. Also there is this Unicode hack where the last bit is used to determine if the byte is part of a multi-byte sequence.
This reads like it was written by some LLM.
Enable journaling only if needed:
tune2fs -O has_journal /dev/sdX
Don't ever disable journaling if you value your data.
Disk Scheduler Optimization
Change the I/O scheduler for SSDs:
echo noop > /sys/block/sda/queue/scheduler
For HDDs:
echo cfq > /sys/block/sda/queue/scheduler
Neither of these schedulers exist anymore unless you're running a really ancient Kernel. The "modern" equivalents are none
and bfq
. Also this doesn't even touch on the many tunables that bfq
brings.
Also changing them like they suggest isn't permanent. You're supposed to set them via udev rules or some init script.
SSD Optimization Enable TRIM:
fstrim -v /
Optimize mount settings:
mount -o discard,defaults /dev/sdX /mnt
None of this changes any settings like they imply.
Optimized PostgreSQL shared_buffers and work_mem.
Switched to SSDs, improving query times by 60%.
No shit. Who would've thought that throwing more/better hardware at stuff will make things faster.
EDIT: More bullshit that I noticed:
Use ulimit to prevent resource exhaustion:
ulimit -n 100000
Again this doesn't permanently change the maximum number of open files. This only raises the limit for the user who runs that command. What you're actually supposed to do is edit /etc/security/limits.conf
and then relog the affected user(s) (or reboot) to apply the new limits.
Use compressed swap with zswap or zram:
modprobe zram echo 1 > /sys/block/zram0/reset
This doesn't even make any sense.
What a load of bloat. NetBSD has a whole guide on diskless booting various machines, none of this shit is new.
Imagine defending this guy. I will never understand people who like influencers.
I don't use Gentoo but I still frequent the Gentoo Wiki and pick apart packages because it's such a great resource for OpenRC.