F04118F

joined 2 years ago
[–] F04118F@feddit.nl 10 points 1 week ago* (last edited 1 week ago) (2 children)

keep it on cache since I do a lot of code compilation, but I will usually switch it to frequency for gaming and stuff.

Isn't gaming the most cache-heavy CPU workload there is? The X3D CPUs have consistently topped gaming benchmarks, even outperforming much more modern CPUs that lack 3D cache.

I'd sooner do it the other way around: frequency for compiling, rendering, transcoding, etc. Cache for gaming!

[–] F04118F@feddit.nl 26 points 1 week ago

@Smorty@lemmy.blahaj.zone this feeling you describe, is exactly how I feel every time I see one of your posts on Lemmy.

Thank you for the good vibes!

[–] F04118F@feddit.nl 9 points 2 weeks ago (2 children)

It's not something to be proud of, that's obvious.

But Rutte was not made secretary-general because of his personal pride. I wasn't happy to have him as prime minister, at all, for all those years, but he is very good at one thing: getting everyone in the room to agree and making everyone in the room feel heard.

This is how you get Trump to be enthusiastic about your project. He is using Trump's ego to get him om board with NATO. This is top-tier manipulation, and it's working!

Rutte is the perfect man for this job, and this is exactly why. No pride, no ego, just doing whatever it takes to keep the unity in NATO and to ensure we are strong enough to deter Russia.

[–] F04118F@feddit.nl 5 points 2 weeks ago* (last edited 2 weeks ago)

Nothing is too big a task for the armed for the armed forces that flew the MiG-21 for 61 years and turned it into a precision bomber.

Real picture of a Romanian MiG-21 LanceR with Litening TGP on the belly station

[–] F04118F@feddit.nl 7 points 2 weeks ago (1 children)

LXQt runs on it

[–] F04118F@feddit.nl 3 points 2 weeks ago (1 children)

No but OPs frame of it might be

[–] F04118F@feddit.nl 5 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

And now each and every country is supposed to spend more on tanks and guns and drones only

Nope, 3.5%.

The other 1.5% is infrastructure and stuff that has both peacetime and wartime benefits, such as roads and rail that can be used for military transport in case of war, cybersecurity, I'd even argue that energy independence can be shared under this.

[–] F04118F@feddit.nl 14 points 2 weeks ago (5 children)

What is this community's policy on Russian propaganda?

[–] F04118F@feddit.nl 28 points 2 weeks ago

Yep, and then there's probably a good number of people who have no idea of threat modelling who just copy those actions to say they have "good privacy".

Tbh, I'm closer to the latter.

[–] F04118F@feddit.nl 2 points 2 weeks ago

The problem with non-PLP drives is that Rook-Ceph will insist that its writes get done in a way that is safe wrt power loss.

For regular consumer drives, that means it has to wait for the cache to be flushed, which takes aaaages (milliseconds!!) and that can cause all kinds of issues. PLP drives have a cache that is safe in the event of power loss, and thus Rook-Ceph is happy to write to cache and consider the operation done.

Again, 1Gb network is not a big deal, not using PLP drives could cause issues.

If you don't need volsync and don't need ReadWriteMany, just use Longhorn with its builtin backup system and call it a day.

[–] F04118F@feddit.nl 3 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

I tried Longhorn, and ended up concluding that it would not work reliably with Volsync. Volsync (for automatic volume restore on cluster rebuild) is a must for me.

I plan on installing Rook-Ceph. I'm also on 1Gb/s network, so it won't be fast, but many fellow K8s home opsers are confident it will work.

Rook-ceph does need SSDs with Power Loss Protection (PLP), or it will get extremelly slow (latency). Bandwidth is not as much of an issue. Find some used Samsung PM or SM models, they aren't expensive.

Longhorn isn't fussy about consumer SSDs and has its own built-in backup system. It's not good at ReadWriteMany volumes, but it sounds like you won't need ReadWriteMany. I suggest you don't bother with Rook-Ceph yet, as it's very complex.

Also, join the Home Operations community if you have a Discord account, it's full of k8s homelabbers.

[–] F04118F@feddit.nl 5 points 2 weeks ago* (last edited 2 weeks ago)

I don't have experience with any of the models you're considering. I used a Corsair for years (don't!) and am currently quite happy with an old Filco Majestouch 2 TKL that I added some white and pink keycaps to.

The Filco was bought used, is built like a tank and only cost about €80.

The one thing I miss in it is QMK/VIA support.

As I understand it, a keyboard with QMK or another firmware with VIA support essentially allows you to program your keyboard however you want. And then bring that programming ("layout") with you to another board.

My Filco has 4 dip switches on the back that allow very limited programming: for example, switching Esc and `, or switching Caps Lock and Ctrl.

But I can't make it such that Caps Lock works as Caps Lock when long-pressed alone, but as Ctrl when struck in a chord with another key. QMK/VIA would make this possible.

Even if you don't want to do this now, having the option to play with combination keys and smart layouts like that is very interesting when you want to downsize from TKL to a smaller board.

Also, consider the used market.

 

cross-posted from: https://feddit.nl/post/24216224

Problem: new kernels not showing up in boot menu

I can install new kernels, and I see them in /boot/efi/{PARITION_UUID}, but they don't show up in the systemd-boot menu.

Data

Normally, Fedora shows the 3 latest kernels (plus a recovery kernel) in the boot menu. I only see up to 6.11.6 in the systemd-boot menu. On the /boot partition, I see much newer kernel versions (both labeled fc40 and fc41)

➜  ~ sudo ls /boot/efi/808f2c9ae4464f1ab2f0a7d367da1b30 -l
total 20
drwx------. 2 root root 4096 Jul  4 19:25 0-rescue
drwx------. 2 root root 4096 Nov  8 12:42 6.11.6-200.fc40.x86_64
drwx------. 2 root root 4096 Nov 18 17:57 6.11.7-200.fc40.x86_64
drwx------. 2 root root 4096 Nov 12 16:47 6.11.7-300.fc41.x86_64
drwx------. 2 root root 4096 Nov 20 10:10 6.11.8-300.fc41.x86_64
➜  ~ sudo ls /boot/efi/808f2c9ae4464f1ab2f0a7d367da1b30/6.11.8-300.fc41.x86_64 -l 
total 72484
-rwx------. 1 root root 57917440 Nov 20 10:10 initrd
-rwx------. 1 root root 16304488 Nov 20 10:10 linux

Systemd-boot

I started with other distros on this disk before I settled on Fedora. Since I was happy with systemd-boot and its automatic discovery of boot entries, I chose to use systemd-boot when I installed Fedora. I know that Grub is the default bootloader and manager for Fedora, but I have systemd-boot. It's an option in the installer.

Major OS upgrades and rolling back the rollback

Last weekend I upgraded from Fedora 40 KDE Spin to Fedora 41. On the next Monday morning, screensharing in Edge Browser had stopped working, so I rolled back to a Fedora 40 snapshot with BTRFS Assistant. This turned out to be an issue in the latest Edge version, not in the underlying OS, so I rolled back the rollback and went to the Monday evening snapshot, then upgraded my packages.

Ever since, I'm not seeing new Kernels in the systemd-boot menu. Any idea how I can fix this, short of a fresh install of Fedora 41 KDE?

 

Problem: new kernels not showing up in boot menu

I can install new kernels, and I see them in /boot/efi/{PARITION_UUID}, but they don't show up in the systemd-boot menu.

Data

Normally, Fedora shows the 3 latest kernels (plus a recovery kernel) in the boot menu. I only see up to 6.11.6 in the systemd-boot menu. On the /boot partition, I see much newer kernel versions (both labeled fc40 and fc41)

➜  ~ sudo ls /boot/efi/808f2c9ae4464f1ab2f0a7d367da1b30 -l
total 20
drwx------. 2 root root 4096 Jul  4 19:25 0-rescue
drwx------. 2 root root 4096 Nov  8 12:42 6.11.6-200.fc40.x86_64
drwx------. 2 root root 4096 Nov 18 17:57 6.11.7-200.fc40.x86_64
drwx------. 2 root root 4096 Nov 12 16:47 6.11.7-300.fc41.x86_64
drwx------. 2 root root 4096 Nov 20 10:10 6.11.8-300.fc41.x86_64
➜  ~ sudo ls /boot/efi/808f2c9ae4464f1ab2f0a7d367da1b30/6.11.8-300.fc41.x86_64 -l 
total 72484
-rwx------. 1 root root 57917440 Nov 20 10:10 initrd
-rwx------. 1 root root 16304488 Nov 20 10:10 linux

Systemd-boot

I started with other distros on this disk before I settled on Fedora. Since I was happy with systemd-boot and its automatic discovery of boot entries, I chose to use systemd-boot when I installed Fedora. I know that Grub is the default bootloader and manager for Fedora, but I have systemd-boot. It's an option in the installer.

Major OS upgrades and rolling back the rollback

Last weekend I upgraded from Fedora 40 KDE Spin to Fedora 41. On the next Monday morning, screensharing in Edge Browser had stopped working, so I rolled back to a Fedora 40 snapshot with BTRFS Assistant. This turned out to be an issue in the latest Edge version, not in the underlying OS, so I rolled back the rollback and went to the Monday evening snapshot, then upgraded my packages.

Ever since, I'm not seeing new Kernels in the systemd-boot menu. Any idea how I can fix this, short of a fresh install of Fedora 41 KDE?

 

cross-posted from: https://feddit.nl/post/21143429

0
Troonrede 2045 (www.youtube.com)
 

cross-posted from: https://feddit.nl/post/21143429

1
Troonrede 2045 (www.youtube.com)
 

Context: in the UK, climate activists got 4-5 years in jail for planning a non-violent protest. The law that made this possible was literally written by the oil lobby: https://www.opendemocracy.net/en/dark-money-investigations/rishi-sunak-right-wing-think-tank-anti-protest-laws-policy-exchange/?ref=publicsquare.uk

 

cross-posted from: https://feddit.org/post/492288

ich🌭iel

251
submitted 1 year ago* (last edited 1 year ago) by F04118F@feddit.nl to c/linuxmemes@lemmy.world
 

https://www.gamingonlinux.com/steam-tracker/

Thanks to the @teawrecks@sopulk.xyz in !linux_gaming@lemmy.ml for the inspiration!

 

cross-posted from: https://feddit.nl/post/14562342

Small 1:72 F4U Corsair model built in a weekend

Full album can be found at: https://www.scalemates.com/profiles/mate.php?id=118436&p=albums&album=111437&view=thumbs

 

I noticed this immediately because I use kanshi (highly recommended for laptops running sway!). I don't know the how or why (maybe it's the wlroots bump), but when I upgraded Sway to 1.9 today, the Hex ID form one of my external monitors changed. So I had to update it in the config for kanshi to work again.

Just a heads up for other kanshi users, and people whose scripts may be influenced by this.

view more: ‹ prev next ›