![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/4271bdc6-5114-4749-a5a9-afbc82a99c78.png)
Youtube tip everyone needs to now: remove the si
query parameter, it’s not necessary and used for tracking
From
https://youtu.be/LKCVKw9CzFo?si=06X6O91R9pX_8UbX
Into
https://youtu.be/LKCVKw9CzFo
Youtube tip everyone needs to now: remove the si
query parameter, it’s not necessary and used for tracking
From
https://youtu.be/LKCVKw9CzFo?si=06X6O91R9pX_8UbX
Into
https://youtu.be/LKCVKw9CzFo
people’s configs on github?
That citrussy had Cloud acting most unwise.
It goes like this:
normal: command not found
It is with zfs, but I not with regular mount
I think (at least not by default). It might depend on the filesystem though.
You can also do the following to prevent unwanted writes when something is not mounted at /mnt/thatdrive
:
# make sure it is not mounted, fails if not mounted which is fine
umount /mnt/thatdrive
# make sure the mountpoint exists
mkdir -p /mnt/thatdrive
# make the directory immutable, which disallows writing to it (i.e. creating files inside it)
chattr +i /mnt/thatdrive
# test write to unmounted dir (should fail)
touch /mnt/thatdrive/myfile
# remount the drive (assumes it’s already listed in fstab)
mount /mnt/thatdrive
# test write to mounted dir (should succeed)
touch /mnt/thatdrive/myfile
# cleanup
rm /mnt/thatdrive/myfile
From man 1 chattr
:
A file with the ‘i’ attribute cannot be modified: it cannot be deleted or renamed, no link can be created to this file, most of the file’s metadata can not be modified, and the file can not be opened in write mode.
Only the superuser or a process possessing the CAP_LINUX_IMMUTABLE capability can set or clear this attribute.
I do this to prevent exactly the situation you’ve encountered. Hope this helps!
Then you might like this tech blog: https://theluddite.org/#!post/ai-hype
More memory and cores will help you with compiling and running your code.
Have you even read my comment?
It’s probably best to limit yourself to a used laptop.
Reading and writing code is nothing more than reading and writing text, and for that you don’t need a fancy gpu or screen.
What I would recommend you look for in a laptop is
More memory and cores will help you with compiling and running your code.
And make sure you take regular backups! You never know when your disk will fail.
Also make sure to check linux compatibility before you buy. Laptops used to be a pain (10+ years ago), and it’s gotten a lot better, but it’s not always perfect. Just search for “[brand] [model] linux” or try to find the model on the archlinux wiki.
And those 8 really rich guys definitely work less than 5 days a week already
because bash isn’t always in /usr/bin/bash
.
On macOS the version on /usr/bin/bash
is very old (bash 3 I think?), so many users install a newer version with homebrew which ends up in PATH, which /usr/bin/env
looks at.
Protip: I start every bash script with the following two lines:
#!/usr/bin/env bash
set -euo pipefail
set -e makes the script exit if any command (that’s not part of things like if-statements) exits with a non-zero exit code
set -u makes the script exit when it tries to use undefined variables
set -o pipefail will make the exit code of the pipeline have the rightmost non-zero exit status of the pipeline, instead of always the rightmost command.
Thank you, was wondering what happened there.