If 50 lines of text are too personal, then you either need to pick different tools or create *_local files that you don’t share.

Load goes up with the number of users. So spikes in usage are effectively a distributed denial of service attack. Be sure to support your instance.

Warzone 2100 https://wz2100.net/

The first commercial video game to be released in the GPL

So to match the fraudulent government, the USA is going to have an entirely fraudulent market and soon after an entirely fraudulent currency.

Depends on if your Window Manager supports the extension

https://www.phoronix.com/news/Wayland-Merges-Screen-Capture

But you will want to clear out the failed systemd services first to ensure that you can boot.

systemctl --failed will list what failed

After you make your /etc/fstab

systemctl daemon-reload will regenerate the units files in /run/systemd/generator but doesn’t start new automounts or stop ones removed from fstab.

systemctl start newmount.automount will start the mount. The .automount extension is required, as systemd assumes .service if not extension is specified.

systemctl stop oldmount.automount will remove a mount not longer in fstab

systemctl reset-failed will stop a previously failed removed mount from appearing in status messages

You don’t need to use the uuid for /etc/fstab (which should make it much easier)

You don’t need to reboot just set the run level via: systemctl set-default graphical.target

Ok notice the uuids, then look in your /etc/fstab file to see if they match

How about blkid?

Not grub; that is a systemd error shell due to a failed mount (probably because the value in /etc/fstab is wrong)

First

lsblk to get the list of block devices (you can use size to figure out your file system)

Then: mount -o remount,rw /dev/${name found in previous step} /

Then check for bad entries in your /etc/fstab and fix them

Then check for failed services: systemctl —failed

Then you should be able to:

systemctl set-default graphical.target to boot

A fast SSD with 2GB of swap really helps.

Any Linux distribution will work, your biggest problem is your web browser. (They are fat fucking pigs) outside of that problem less than 64MB is still usable

Well if they could get it to fit on a mini-dvd or a CD then nothing would be lost but I guess pre-UEFI systems are slowly going to be abandoned. (Guess coreboot community needs more funding)

Sounds like a rather cheap and easy way to get bad cops out of the police force

Or if a handful of paranoid people read the code for a distribution and publicly discuss everything that they find (it only would take 12 crazies in the whole world)

Only for distributions which don’t do reproducible builds and require full and complete corresponding source code under an FSF approved license.

If you choose to download binary blobs, good fucking luck.

It would be more secure if the credentials are in an in memory SQLite Database but that would require you to use something other than the shell. You would need to do a hardware key or have the user do a bootstrap password or have an API that uses a public key to authenticate the remote process passing the credentials

Well did the samba user account (used to connect to the samba share) have access to the files?

Don’t have any games that require those. So never ran into that problem. But I can imagine there are potential games/apps people would want that can’t run on Linux. Windows VMs might be a solution but I don’t know as I never had to deal with that.