You’re right, apparently amongst other things there are some hooks that are ran during the package’s lifecycle in something that is called the control archive.

Actually it’s just an archive. It can be easily extracted using dpkg -x *.deb ~/.local for example.

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.

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

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‽

This book was left blank…

I’m not buying anything, as I do not need anything.

Pepper itself is overrated. At least the black one.

From Archwiki > xrandr:

Tip: Both GDM and SDDM have startup scripts that are executed when X is initiated. For GDM, these are in /etc/gdm/, while for SDDM this is done at /usr/share/sddm/scripts/Xsetup. This method requires root access and mucking around in system configuration files, but will take effect earlier in the startup process than using xprofile.

Try disabling hardware acceleration

Mount the drive with the user or group as plex. See mount options uid and gid. You can also set precise permissions on the mount point (using options at mount time) to let plex access a subdirectory.

We growing wiser, or are we just growing tall?

• Damian Marley

• Gnorv

Try this:

for file in ./*
do
    echo "$file"
done

To do some substitution operation om the filename you can use Bash Parameter Expansion.

Rumors say there are some platforms selling grow-kits including everything needed to get started. In Europe, people recommend some platform starting with Zam and ending with nesia, which supposedly provide a variety of kits.

You can also find plenty of resources online to start from scratch. The easiest seems to be the uncle bens method.

I think it helps to cool the drink and inot only satisfactory.

Phosphorescent light-rods.