I realized it works in most programs, however it doesn’t in xwayland

And it’s precisely those xwayland programs (IntelliJ and Android Studio) that I would use this key most times

Sure, someone helped me setting up a script to share the wl socket between namespaces so I can run GUI programs in isolated namespaces, and if you look at this post you can check the namespaced-openvpn; also check vole’s answer if you want to run GUI programs

Thank you for summarizing it up

I’ve been using network namespaces in Linux where each one also use a different user; this way you can have multiple profiles of apps separated not only by permissions but also by the VPN connection that is the only route out

So you can have a connection that will supply your favorite iso sharer, a VPN connection to work, all unaware of each ot

I still haven’t figured how to make GUI media applications work on them though

It seems that a namespace only has access to process that originates inside itself

systemctl --user list-units 
Failed to connect to bus: No medium found             

as we can see, the same user doesn’t have access to other processes so we would need to duplicate every process above the namespace until we could acess the media

would duplicate of everything - pulsewire, dbus, etc - even work ?

Relevant

you install program A, it needs and installs libpotato then later you install program B that depends on libfries, and libfries depends on libpotato, however since you already have libpotato installed, only program B and libfries are installed The intelligence behind this is called a package manager

In windows when you install something, it usually installs itself as a standalone thing and complains/reaks when dependencies are not met - e.g having to install Visual C++ 2005-202x for games, JRE for java programs etc

instead of making you install everything that you need to run something complex, the package manager does this for you and keep tracks of where files are

and each package manager/distribution has an idea of where some files be stored

You can freely manipulate NTFS in Linux. Just make sure your distribution has, after kernel >=5.15, enabled it, otherwise you may need to install the ntfs-eg driver. Other than that, Ach Wiki has info that may help you on any distro:

https://wiki.archlinux.org/title/NTFS

I have done something similar to what you want to do, just needed the ntfs-3g driver installed and “Disks” (gnome disks) application would mount/read/write the disks as usual

You can configure this behavior for CLI, and by proxy could run GUI programs that require elevation through the CLI:

https://wiki.archlinux.org/title/Sudo#Using_visudo

Defaults passwd_timeout=0(avoids long running process/updates to timeout waiting for sudo password)

Defaults timestamp_type=global (This makes password typing and it’s expiry valid for ALL terminals, so you don’t need to type sudo’s password for everything you open after)

Defaults timestamp_timeout=10(change to any amount of minutes you wish)

The last one may be the difference between having to type the password every 5 minutes versus 1-2 times a day. Make sure you take security implications into account.

Timeshift, make sure to “include hidden files” to recover any configuration for desktop environments

After a few mess ups, you may find yourself not needing to backup everything, only the file(s) that messed up, and that’s still a good thing to have Timeshift for

IP is like an address to a big skyscraper where a company operates. You are the delivery man and must go to 201.154.76.19 and deliver something. When you get at the reception, you tell them you have a package to deliver to Mrs HTTPS, at room (port) 443. Since Mrs HTTPS is well known and has cleared your entry before, you’re allowed to enter this room and only this room.

If you were to get at the same address and try to access other rooms you would either get refused because they are closed, or if open, someone would specifically need to be in the room so you can deliver something

Malicious actors that wanted access to the building could try to disguise their deliveries and enter the building, that’s why the default policy of most firewalls is “reject” and you specifically need to open a port and have a program listening to it if you want incoming connections.

Used to be messing with kernel arguments and installing/tweaking boot parameters. That was until Grub broke, I learned systemd-boot and chrooting into the system via live USB

Now if I break anything it’s just a matter of “sigh, let me get the USB and type a few commands”

Mind sharing whhich situations would a timecard be useful ? Probably something that requires enhanced time precision, I just can’t figure it out

Depends on config, ArchWiki recommends optmizing some sysctl values to take advantage of it

it generally starts kicking in after >60% RAM usage even with this config

These updates land on testing quickly, however due to the several packages updated at once, they all need to be tested by volunteers, and only when all of them are signed it’s pushed out of testing

That’d be over 1TB with zram on

Considering it’s almost always 30°C+ 60%+ RH at least half of the year where I live, yes

Refrigerating them increases their shelf life significantly in these conditions

It’s probably less effective in other cooler and drier climates

For those who use Wayland and autostart, don’t forget to edit

/etc/sddm.conf.d/kde_settings.conf

from KDE5: Session=plasmawayland

to Plasma6: Session=plasma

to confirm the exact name, check what is available under /usr/share/wayland-sessions/

if you’re stuck, try pacman -Q | grep -i kde and pacman -Q | grep -i plasma and remove everything related, then fresh install plasma-meta or plasma group and it should work

For those who use Wayland, don’t forget to edit

/etc/sddm.conf.d/kde_settings.conf

from KDE5: Session=plasmawayland

to Plasma6: Session=plasma

to confirm the exact name, check what is available under /usr/share/wayland-sessions/

if you’re stuck, try pacman -Q | grep -i kde and pacman -Q | grep -i plasma and remove everything related + remove orphans , then fresh install plasma-meta or plasma group and it should work

Happened once around two years ago, s botched update from mainstream or something like that. Made me learn systemd boot which is simple and never EVER use grub again

Already switched to AMD to enjoy it