ClemaX

It all makes sense when you think about the way it will be parsed. I prefer to use newlines instead of semicolons to show the blocks more clearly.

for file in *.txt
do
    cat "$file"
done

The do and done serve as the loop block delimiters. Such as { and } in many other languages. The shell parser couldn't know where stuff starts/ends.

Edit: I agree that the then/fi, do/done case/esac are very inconsistent.

Also to fail early and raise errors on uninitialized variables, I recommend to add this to the beginning of your bash scripts:

set -euo pipefail

Or only this for regular sh scripts:

set -eu

-e: Exit on error

-u: Error on access to undefined variable

-o pipefail: Abort pipeline early if any part of it fails.

There is also -x that can be very useful for debugging as it shows a trace of every command and result as it is executed.

Rust is special regarding references but Kotlin reads similarly.

What are you missing on Firebase?

The quieter you become, the more you are able to hear – Rumi

This + node_exporter.

Ah least they would need to know it first.

I don't think that browsers do that. There is HSTS but I think that it only checks if the connection is using TLS.

I think you may want to use for device in /dev/disk/by-uuid/*

That doesn't explain why you aren't seeing messages. I see there is a shebang at the start of the script. Can you confirm that the script has the executable bit set for the root user?

It works with USB interfaces using passthrough. But yeah doesn't make a lot of sense.

In French, oursin (urchin) seems to be the diminutive of ours, which means bear. So oursin means something like "little bear".

You wouldn't download a car‽