12510198

joined 1 year ago
[–] 12510198@lemmy.blahaj.zone 4 points 1 week ago

Nheko is my favourite client, it uses QT and is written in C++, its lightweight and works well on my machines with low resources, it also respects my system theme

[–] 12510198@lemmy.blahaj.zone -5 points 2 weeks ago

sudo sed -i 's/libalpm.so.14/libalpm.so.15/g' /usr/bin/paru

[–] 12510198@lemmy.blahaj.zone 9 points 1 month ago (1 children)

I think it kinda looks like a lollipop

 

It took about 23 hours to get it booted under its own power using a binary kernel. And on the 4th day (today) I've managed to get a custom kernel working. Gentoo has been very fun to use and to customize, and it's very fast and responsive, even on my old hardware and with a hard disk, browsing heavy webpages with Librewolf is no problem at all. I've been sleeping on Gentoo for WAY to long.

[–] 12510198@lemmy.blahaj.zone 2 points 2 months ago

I think its just the non-exit nodes that are needed as long as the traffic stays inside the tor network, I dont think an exit node gets involved at all, but I'm not 100% sure

[–] 12510198@lemmy.blahaj.zone 5 points 2 months ago (2 children)

I think staying inside the tor network helps reduce the load on exit nodes, which helps all tor users who need to access the clearnet. I think there is even a HTTP header that can be put on the clearnet site that will put a button on the tor browser that tells users that there is a onion available.

[–] 12510198@lemmy.blahaj.zone 7 points 3 months ago

I figure that the administrators of your homeserver could see your IP address, I doubt that it would be sent to anyone you are just chatting with.

[–] 12510198@lemmy.blahaj.zone 12 points 4 months ago (2 children)

Ive only had to setup a nvidia system once, so I might be missing some packages, but I think pacman -Rns nvidia nvidia-utils lib32-nvidia-utils should get rid of all of it.

[–] 12510198@lemmy.blahaj.zone 1 points 5 months ago

WARNING: doing this will absolutely DESTROY YOUR SYSTEM, PERMANENTLY!!!

But if you wish to continue, you can erase all the EFI variables using the rm utility, I dont think you will be able to completely zero out the chip on the system from inside of Linux as its read-only.

But to delete all the EFI variables, cd into /sys/firmware/efi/efivars, if this directory is not availiable, either the efivarfs is not mounted, or you are booted in legacy BIOS mode. But once you are in this directory, run chattr -i ./* as root or sudo to remove the immutable bit on all the files, then run rm ./* as root. This WILL break your system. Only do this if you know how to restore your system using like a chip programmer.

[–] 12510198@lemmy.blahaj.zone 1 points 5 months ago (1 children)

This happened to me too. I had to grab the box that comes up and resize it like I would with a normal window, mine glitched a lot when I tried it, try resizing it as far as you can, it will try and glitch back, but just keep fighting it until it becomes a usable size, then log out of Plasma and log back in, and then you can size it back down to a normal size. Hopefully there will be an official fix for this soon

[–] 12510198@lemmy.blahaj.zone 14 points 6 months ago (1 children)

What about something like this:

for i in /media/johann/5461-000B/DCIM/100MEDIA/*.AVI; do newpath="$HOME/Public/240321/$(basename "$i" | sed 's/^IMAG/240321_/g')"; ffmpeg -i "$i" -ss 00:00:00 -t 00:00:20 "$newpath" && rm "$i"; done
[–] 12510198@lemmy.blahaj.zone 6 points 6 months ago (1 children)

If its just / owned by the mint user, you should just able to run chown root:root / as root/sudo, dont use -R. This should make root become the owner of /. Now if all files and directories in the partition are owned by the mint user, this might be a bigger problem

 

Ive been tryna figure this out all day, Ive read the manual for systemctl and I didnt see anything about switch-root after the initrd target. I did see a --force option, however it didnt do anything. Before the upgrade to version 255, I would use a script or manually mount the partition, and then I would just do like systemctl switch-root /mnt and it would just switch to the other system in an instant as if I booted it normally. But ever since this update it just prints Not in initrd, refusing switch-root operation. and does nothing.

Is there a configuration file I can edit to allow switch-root after the initrd? Or is it like hard-coded and systemd would need patching and recompiling to allow for this? If so is there a way to just trick systemd into thinking its in the initrd and just let me switch-root?

I was dissappointed when I found out I couldnt just switch-root anymore. Any help, ideas, or suggestions will be much appreciated, thank you!

EDIT: To switch root in the new versions of systemd, you will have to mount the filesystem you want to switch root into to /run/nextroot and run systemctl soft-reboot, and it will switch into the root just like before.

view more: next ›