Strit

joined 2 years ago
MODERATOR OF

I've had my own for a long time. Now to judge if this new one is better. :)

[–] Strit@lemmy.linuxuserspace.show 1 points 23 hours ago (1 children)

Professional Server grade distro, would probably be either Ubuntu, Red Hat Enterprise Linux or OpenSUSE Enterprise Linux.

For my personal homelab server I run Arch Linux, but I wouldn't do it in an enterprise.

Kind of like an RSS feed reader does. It collects articles from different rss feeds and presents them to you in one place.

This is the way to do it.

Although, I can't get it to do facial recognision on my external library for some reason.

But its software freeze was a couple of months ago.

[–] Strit@lemmy.linuxuserspace.show 1 points 2 weeks ago (1 children)

This is the one where most core-utils are switched to rust based uutils, right?

Or did they roll that decision back after some not being done in time?

[–] Strit@lemmy.linuxuserspace.show 1 points 2 weeks ago (3 children)

Sure. But you have to figure that out first.

I'm just saying. It's not for everyone. I feel too limited when trying immutable stuff, so I stick with my classic. πŸ˜€

[–] Strit@lemmy.linuxuserspace.show -1 points 2 weeks ago (6 children)

But a simple thing like "install a random cli tool to run on host" is often not easy on immutable distros, so it's usually just more convinient with an oldschool distro in those cases.

[–] Strit@lemmy.linuxuserspace.show 3 points 2 weeks ago (9 children)

To be honest. Immutable distros are not for everyone. Tinkerers especially would not be suited to use them, because of all the "restrictions" in place.

Better to find another distro in that case.

I believe it also generates menu entries (.desktop files) for them.

My biggest concern with such an approach, is that companies will be more likely to choose a not completely open source licens, just to get around this. Like a code-available licens and argue that it counts as open source and should therefore be excluded.

[–] Strit@lemmy.linuxuserspace.show 3 points 2 weeks ago (1 children)

I'll do you one better. Why's Facebook?

 

Not properly released on kernel.org yet, but 7.0 has been tagged on the kernel git repository.

 

Four years since the launch of the Raspberry Pi 4, the Raspberry Pi 5 has arrived with a performance boost and house silicon that adds support for PCIe 2.0.

 

FOSDEM is a conference where thousands of open source developers meet and learn.

Location is as always in Bruxelles, Belgium, Europe, Earth.

Any of you going this year?

12
submitted 2 years ago* (last edited 2 years ago) by Strit@lemmy.linuxuserspace.show to c/kde@lemmy.kde.social
 

Hi all.

Happy KDE Plasma user for a long time and I generally love the desktop experience. But I do have one small issue.

At work, I have 2x 4K displays. connected through a Dock. But in Plasma it's only able to give me around 1080p resolution on both of them. In contrast, the display manager SDDM and TTY displays 4k on each fine.

So am I missing a trick to get the max resolution in Plasma? My install is Arch Linux, kernel 6.4.12, Plasma 5.27, Wayland session.

I did install the displaylink AUR package, as I thought it might be the dock limiting the video output, but it isn't as TTY and SDDM seems to display it correctly.

Happy to hear any thoughts and any ideas. :)

EDIT: The screens turn on and work fine with 4K resolutions in a Plasma X11 session.

 

tværpostet fra: https://lemmy.dbzer0.com/post/3076577

I posted the other day that you can clean up your object storage from CSAM using my AI-based tool. Many people expressed the wish to use it on their local file storage-based pict-rs. So I've just extended its functionality to allow exactly that.

The new lemmy_safety_local_storage.py will go through your pict-rs volume in the filesystem and scan each image for CSAM, and delete it. The requirements are

  • A linux account with read-write access to the volume files
  • A private key authentication for that account

As my main instance is using object storage, my testing is limited to my dev instance, and there it all looks OK to me. But do run it with --dry_run if you're worried. You can delete lemmy_safety.db and rerun to enforce the delete after (method to utilize the --dry_run results coming soon)

PS: if you were using the object storage cleanup, that script has been renamed to lemmy_safety_object_storage.py

view more: next β€Ί