luthis

Someone tell me if there is a better way to do this, but I don't see how.

I needed a way to see which services I have enabled that I have manually stopped.

There oddly isn't a way to do this in one command, so I had to take the output of list-unit-files 'enabled', and use that to filter for 'list-units'. The command is here:

alias sysstop='systemctl list-units --state=failed,dead,exited $( systemctl list-unit-files --state=enabled --type=service | awk "/.*\.service/ {print }" )'

So now I can remember that I need to restart mariadb and nginx at some point:

$ sysstop
  UNIT                                 LOAD   ACTIVE   SUB    DESCRIPTION                                             
  blueman-mechanism.service            loaded inactive dead   Bluetooth management mechanism
  mariadb.service                      loaded inactive dead   MariaDB 11.2.2 database server
  NetworkManager-wait-online.service   loaded active   exited Network Manager Wait Online
  nginx.service                        loaded inactive dead   A high performance web server and a reverse proxy server
  systemd-homed-activate.service       loaded active   exited Home Area Activation
  systemd-networkd-wait-online.service loaded active   exited Wait for Network to be Configured

My other aliases are here, in case anyone finds these helpful. I use them frequently myself.

alias sysdis='systemctl list-unit-files --type=service --state=disabled'
alias sysdisuser='systemctl list-unit-files --type=service --state=disabled --user'
alias sysen='systemctl list-unit-files --type=service --state=enabled'
alias sysenuser='systemctl list-unit-files --type=service --state=enabled --user'
alias sysfail='systemctl list-units --type=service --state=failed'
alias sysrun='systemctl list-units --type=service --state=running'
alias sysrunuser='systemctl list-units --type=service --state=running --user'
alias sysstatic='systemctl list-units --type=service --state=static'

Just having a play around, this turned out to be not as clear cut as expected.

so I created a file and entered some text, used xxd to get the hex values, and then opened the device /dev/sdb1 in wxhexeditor and tried to find my file, but it's not finding it. Inode is 19, so it should be right at the start of the first block group, but after several minutes, no joy. (drive is ext4.)

I thought this was going to be an easy task, just multiply the inode by the block size, open the device with wxhexeditor, and scroll to the line corresponding to the calculated byte, copy out the hex values and convert to ascii and voila, there's the 'hello world'... except no.

What am I missing here? Drive isn't encrypted, nothing silly like that.

Ok, I managed to do it with dd:

sudo dd if=/dev/sdb1 bs=8M skip=$((4660742*4096)) iflag=skip_bytes | head -c 4096

hello

but why can I not find it using wxhexeditor??

EDIT:

Duh, I didn't click that offset needed to be multiplied by the block size.

If I go to offset 4660742*4096=19090399232 in wxhexeditor, indeed I see the file contents:

Final conclusion:

After some more testing, I have concluded: you cannot easily calculate the offset using the inode. Finding files across the disk requires using the inode tables to get the offset and actual file location. So an inode does not correlate with a physical/logical sequential disk location.

I created a new file, it received inode 21, but the offset was smaller than inode 19.

Was that a good use of 3 hours of my life? Well... I still have no idea what's up with the Kardashians, so.. I guess?

From homectl:

Home directories managed by systemd-homed.service are usually in one of two states, ... when "active" they are unlocked and mounted, and thus accessible to the system and its programs; ... Activation happens automatically at login of the user

What does 'login' mean? For example, I created a user and tried to su -l test, but I got: cannot change directory to /home/test.

What is required to 'activate' a homed directory if not a login shell?

I solved this problem for myself yesterday and couldn't find the answer anywhere online (clearly stated), so here's what I did.

This also works for Plex, games, etc it's policy based routing so you can have your VPN and remote access at the same time.

This configuration is for your ssh server (ie your home PC) that has a VPN running like ProtonVPN etc and allows you to connect back to your home PC remotely either for SSH, plex, anything you're serving.

This is changing the default gateway for particular ports, so that return traffic from connection attempts doesn't go back out through the VPN.

I used this page to figure out how to do this:

http://linux-ip.net/html/tools-ip-rule.html

Add a default route to some table, arbitrarily table 10 but you can use whatever number (RTFM), also obviously needs to be your router IP

sudo ip route add default via 192.168.19.1 table 10

Add a rule for the return traffic from your ssh host

sudo ip rule add sport 22 table 10

sudo ip route flush cache

check out your fancy new rule

ip rule show

And to make this persistent across reboots, add to:

/etc/systemd/network/20-wired.network

(or whatever your file there is, add the following to the bottom. This is the same as above, just permanent)

[Route]
Gateway=192.168.19.1
Table=10

[RoutingPolicyRule]
SourcePort=22
Table=10

Will we all be fucked or is there a Linus 2?

Is anyone able to point me in the right direction to solve this issue please?

I installed the nvidia-beta drivers (Arch) and tested out Starfield. All is good. Then next time I try to startx, I get X failed to start etc.

Following the logs I get to:

` [ 1711.739] (II) NVIDIA dlloader X Driver 545.23.06 Sun Oct 15 17:26:55 UTC 2023

...

[ 1711.740] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the

[ 1711.740] (EE) NVIDIA: system's kernel log for additional error messages and

[ 1711.740] (EE) NVIDIA: consult the NVIDIA README for details.

`

Wierd. Install nvidia instead, y to remove conflicts/nvidia-utils etc, and it's all working. Try to install beta drivers again, same issue, rebooted, etc.

The beta drivers definitely did work. But now they magically aren't.

Any tips?

I did try running sudo mkinitcpio -P but no change.

Great narration, audio, music, animation...

Curl up with a blanket and a flu for 4 hours!

Just tested on Arch, installed nvidia-beta

Was using GE-Proton8-17

Got to the first open area. No missing textures, graphical glitches, nada. Seems to be running well, but didn't have FPS counter visible to see.

I have to post this on my phone

Logged out, logged in again, cannot get web pages. Can ping to ips, cannot resolve names with ping. Can resolve names with nslookup. Browsing doesn't work obviously but I can get to remote ips like repo locations.

???

REALLY seems like DNS but DNS is working with nslookup and I can change the nameserver in etc/resolv.conf and see nslookup using different nameserver but still no dice when using ping/browser

Any ideas??

Just to clarify, I'm talking about thousands of torrents across hundreds of different directories.

Just kidding, there is no closure. I could not replicate this issue again after multiple reboots.

Linked original thread: https://lemmy.nz/post/1024414

Just wanted to say thanks to everyone for their suggestions, and easier to make a post here than reply to each single comment.