[-] ulterno@programming.dev 3 points 1 hour ago* (last edited 1 hour ago)

gut push --force does not work.

But I added "force"!

sudo gut push --force still not working.
Of course I don't try to understand the error output. I just see that it is not working.

[-] ulterno@programming.dev 0 points 1 hour ago

I do that when I want it running with root privileges.
In case of user privileges though, the autostart is a better idea.

[-] ulterno@programming.dev 3 points 23 hours ago

Also, if you use an NTFS USB drive to move the .git folder, you will be in trouble.
Thankfully, moving those things to pen drives is very slow, making most users tar it first, anyway, hence sidestepping the problem.

[-] ulterno@programming.dev 1 points 4 days ago

As long as you are fine with corruption.

[-] ulterno@programming.dev 8 points 1 month ago* (last edited 1 month ago)

For LibreOffice, I'd go with, worse and better at the same time.

  • I have just noticed, overtime, that it has some problems in some cases, where MS Office does better, while there are certain cases where it does better.

There are 2 major pain points though:

  1. Calc UI stutters when using the scrollbar with mouse click and drag.
  2. Adding images to files makes the whole thing way slower than acceptable.

I haven't used it for a few months though, so something might have changed. But the second issue specifically is a long time one.

On the other hand, the formula usages are much better in Calc. Also, the documents don't get wonky between versions as much as MS Office

[-] ulterno@programming.dev 8 points 1 month ago

You can have OSS without the F

[-] ulterno@programming.dev 14 points 1 month ago

Google: Sure, we'll sell it to anyone who pays off our Russian Govt fine.

[-] ulterno@programming.dev 11 points 1 month ago

And that would make it reusable due to the non-destructive nature towards the seal.
Just need to replenish the high explosive.

[-] ulterno@programming.dev 20 points 1 month ago

And they wonder why we walk with a pegleg…

Because they took an arm and a leg and didn't leave us with enough to get high quality prosthetics.

30
submitted 1 month ago* (last edited 1 month ago) by ulterno@programming.dev to c/linux@programming.dev

I have a multiboot system. One of the installed OS's does not use the NVMe SSD installed on the motherboard at all.
At the time of taking the screenshot, all the SSD partitions are unmounted, so apart from detection, the SSD is mostly unused.

  • I would like the temps to drop down to SYSTIN (≈35°C) levels.
  • I know, it's right next to my GPU, but I am not doing anything GPU intensive, the GPU temps are ~37°C ^[apart from GPU memory, which is 48°C due to the awful AMD 7th gen Zero RPM, which has no workarounds on Linux]

For the unmounted and unused HDDs, I just use hdparm -Y, but there seems to be nothing in terms of that for the SSD. And even though I appreciate the additional heat in winters, this is going to be too expensive for me. I'd rather burn some cheap Nichrome than my data storage device.

I checked out a Debian forum thread and from that, I checked the following:

❯ sudo nvme get-feature /dev/nvme0 -f 2 -H
get-feature:0x02 (Power Management), Current value:0x00000004
        Workload Hint (WH): 0 - No Workload
        Power State   (PS): 4

Showing it is already in the lowest power state.

I have no active cooling setup for the SSD from my side. This becomes relevant soon.

  • Checking the SSD temps (using the same widget as in the image), the temperature on Sensor 2 starts out at ~40°C (after a normal reboot) and slowly increases to >50°C as shown at the start of the graph. Power State (PS) is still 4.

  • Running KDE partitionmanager, which probably does some reading to check the partition information, at 50°C stage, causes a temperature drop, as shown in the image.

  • Running KDE partitionmanager right after reboot, when the temperature is increasing very sloowly, seems to do nothing significant.


  • Turns out that after a few minutes of System Standby, the SSD doesn't return to PS: 4, so I have the culprit.
  • Running partitionmanager after that causes it to go back to PS: 4

So we have a solution! All I need to do is run partitionmanager on wake. nlol jk


Motherboard: MSI MAG X570S TORPEDO MAX (MS-7D54)
SSD: Samsung 980 512GB (correct firmware, bought long before the fakes started coming out)

[-] ulterno@programming.dev 17 points 1 month ago

It's not trying to say either of them.

It's just guessing what word to say next, given the previous words in the context.

[-] ulterno@programming.dev 9 points 1 month ago* (last edited 1 month ago)

Except for that most of it was not.
A lot of the noise on the screen (and speaker) was affected by radiation from nearby stuff.

I'd think that nowadays, it would be even more so, with way more WiFi and mobile phone signals everywhere. Now sure, different frequencies mean they would affect less, but the cumulative effect would still be more than the CMBR.

Also, I have a flat-screen CRT at home.

[-] ulterno@programming.dev 14 points 1 month ago

In those cases, I just use amend.

It's a new website afterall, nobody is pulling that.

270
submitted 1 month ago* (last edited 1 month ago) by ulterno@programming.dev to c/programmer_humor@programming.dev

Until he actually had to use it.

Took 2 hours of reading through examples just to deploy the site.
Turns out, it is hard to do even just the bash stuff when you can't see the container.

view more: next ›

ulterno

joined 1 month ago