======Silverblue42======

====Toolbox (toolbx)====

From: https://linuxconfig.org/getting-started-with-toolbx

The other, more flexible way to create a container based on a system of our choice, is to use --image option and provide the path of the container image we want to use. Some community-maintained images are developed on github and are hosted on the Quay.io register. Just as an example, to create a container based on the Archlinux image, we would run:

$ toolbox create --image quay.io/toolbx-images/archlinux-toolbox:latest

To retrieve the list of the toolbox container we created and the images they are based on, we can use the list sub-command:

$ toolbox list

To enter a container built on one of the supported systems, we can, again, use the corresponding arguments for the --distro and --release options. To enter the container based on RHEL 9.1, for instance, we would run:

$ toolbox enter --distro rhel --release 9.1

Finally, to enter a container based on a custom image, or more generally reference a container by its name, all we need to do is to pass the name as the last argument. We already built a container based on the “quay.io/toolbx-images/archlinux-toolbox:latest image” which is called “archlinux-toolbox-latest”. To enter it, we would run:

$ toolbox enter archlinux-toolbox-latest

===Removing containers and images===

Once we are done using a container we may want to remove it, perhaphs together with its base image. In order to do that we can use the rm and rmi commands, respectively. Sticking to previous examples, let’s suppose we want to remove the “archlinux-toolbox-latest” container. Here is the command we would run:

$ toolbox rm archlinux-toolbox-latest

The command will fail if the container we are trying to remove is still running. This may happen due to a know issue that makes containers not stopping after exiting. To be able to remove the container anyway we could either stop it directly with “podman”:

$ podman stop archlinux-toolbox-latest

Or use the --force option:

$ podman rm --force archlinux-toolbox-latest

To remove all the containers we created with toolbox at once, all we have to do is to use the --all option:

$ podman rm --force --all

To remove images instead of containers the procedure is the same as the options which can be used. The only thing that changes is the subcommand itself, which in this case is rmi. To remove the image on which the archlinux-toolbox-latest container is based on, we would run:

$ podman rmi quay.io/toolbx-images/archlinux-toolbox:latest




====Stopping and Remove Podman Container====

From: https://fedoramagazine.org/getting-started-with-podman-in-fedora/

To exit from the container use CTRL-C. You can remove the container by using the container id. Get the id and stop the container using these commands:

podman ps -a
podman stop <container_id>

You can delete the images from your machine by using the following command:

podman rmi <image_id>


====Launch Flatpak from console===

From: https://justingarrison.com/blog/2023-03-19-launch-flatpak-app/

An easier way to create a shortcut is to symlink the desired command name to the flatpak export. Create the symlink in a folder already in your PATH to avoid getting tab completions with a bunch of org and com commands.

ln -s /var/lib/flatpak/exports/bin/com.visualstudio.com $HOME/.local/bin/code

The symlink can always exist, but if the target file does not exist your shell should be smart enough to not execute or tab complete it.


====Arduino USB on Silverblue42====

from:- https://blog.christophersmart.com/2020/04/18/accessing-usb-serial-devices-in-fedora-silverblue/

While a device is correctly detected at /dev/ttyUSB0 and owned by the dialout group, adding myself to that group doesn’t work as it can’t be found. This is because under Silverblue, there are two different group files (/usr/lib/group and /etc/group) with different content.

There are some easy ways to solve this, for example we can create the matching dialout group or write a udev rule.

===On the host with groups===

If you try to add yourself to the dialout group it will fail.
sudo gpasswd -a ${USER} dialout
gpasswd: group 'dialout' does not exist in /etc/group

Trying to re-create the group will also fail as it’s already in use.
sudo groupadd dialout -r -g 18
groupadd: GID '18' already exists

So instead, we can simply grab the entry from the OS group file and add it to /etc/group ourselves:


1 grep ^dialout: /usr/lib/group |sudo tee -a /etc/group

Now we are able to add ourselves to the dialout group:

2 sudo gpasswd -a ${USER} dialout

Activate that group in our current shell:

3 newgrp dialout

And now we can talk to the arduino.