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)

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.

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.

Steam, wine and dosbox with them, you can effectively play any game worth playing. Beyond that I never needed to know.

!datahoarder@lemmy.ml

Is the best place to ask

Well my husband’s work place does audit the code they deploy but they have a big problem with contractors just downloading random shit and putting it on production systems without following proper review and in violation of policy.

The phrase fucking Deloitte is a daily occurrence.

Not every version of chmod supports that and you really don’t want your media files to be executable

Well sudo find ${path} -type d exec chmod 750 {}; to fix the folders first Then sudo find ${path} -type f exec chmod 640 {}; to fix the files

After that sudo chown -Rv my user:media ${path} and everything should be sorted

Unfortunately the XSettings freedesktop spec is trash and hasn’t been released let alone revised since 2001