shrugs

u/shrugs@lemmy.world
0 posts · 284 comments

Recent posts

No posts.

Recent comments

Not self hosted but at work: after an update to both our firewall cluster nodes they both acted wonky, restarted 5 min after booting, ssh connection wasn't working half the time, dropped packages... the problem persisted through multiple reboots, support had no idea.

the fix was to pull the plug entirely, wait 10 seconds then power them on again. on both nodes we had this behavior and both worked again after losing power for a few seconds.

seems that even for business appliances "have you tried to turn it off and on again" is a viable solution.

on hmmm · c/hmmm · 5 pts · 16d

Are you sure, you wanne eat that?

Same for the second problem.

pretty sneaky way to mask your mistake. if your explanation is correct, then the second problem has 450 solutions (450,0|449,1|448,2...), which obviously is a stupid question then...

it's been said that reverse-engineering takes three times as long as writing it on your own. Yet everyone prefers reverse-engineering stupid ai answers instead of thinking for themselves. Make it make sense

These are the kinds of problems I like the most: I once squirted some ketchup on my new shoes while we were out drinking. Ignored it, the next day when it was dry I could pull it off without even a discoloration. If I had used a towel to wipe it off, the shoes would have been ruined.

Less work, more results, that's what I like

The script gets called as either

nvidia-sleep.sh suspend

On suspend and resume as

nvidia-sleep.sh resume

The important part is this:

echo "$1" > /proc/driver/nvidia/suspend

where $1 is either suspend or resume. /proc is a kernel interface that, I guess in this case, tells the kernel to suspend or resume the GPU. It just puts the corresponding string into /proc/driver/nvidia/suspend which causes the kernel to act accordingly.

chvt and fgconsole are commands you should look into, as they are called after the echo to proc and might be important.

In your case, since the driver doesn't come back but the system is usable, ssh into the system from another one and you can check with "sudo journalctl -f" and "sudo dmesg -w" what's happening.

Tbh, I don't see anything systemd-specific.

Hope that helps. Ask away if it doesn't.

I'm not really sure what you mean. If you have a live usb stick and boot a system of it, like fedora or mint, there is usally an installer to install the system onto the pc. this does not alter your usb stick though. you can install as often as you like.

I don't get the download part either. the live usb stick is the installer. no need to download additional files.

Remember the live usb environment is not persistant. after every boot from it, all files you have created inside the live environment will be gone.

Connections
Puzzle #1101
🟩🟩🟩🟩
🟦🟦🟦🟦
🟨🟨🟨🟨
πŸŸͺπŸŸͺπŸŸͺπŸŸͺ

you sound like a beginner. trust me, don't take nix. Nix is great but nix has a learning curve you cant climb as a beginner.

linux is great as in, you can just copy a hard drive to another disk and boot it, after fixing fstab...

If you are using docker to run your services you can copy your docker compose directories and the volumes to a new host and start them, So all in all, install the services on you laptop or inside a vm / as docker container and when you get dedicated hardware you can just migrate the services.

And guys really, recommending nix to someone that doesn't know how to migrate a service and asks about it. that's a load of bullocks!

Im the same. I hate cooking, I feel it's way too time intensive. Most of the time I'll order something or eat on the go.

I almost never think about food, aside of actually being hungry and thinking about how to change that with the least work.