schmonz.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
https://www.linux-magazine.com/Online/News/Akamai-Will-Host-kernel.org
Great to see! Akamai has supported Slackware for > a decade with the web site on the Content Delivery Network, and now with some infra on Linode.com. #slackware #linux #floss
For those #Linux users who use the #Sway window manager, have you tried Jay?
Jay just released 1.10.0.
https://github.com/mahkoh/jay/releases/tag/v1.10.0
Same vibes as Sway, but in Rust but without an attempt to maintain compatibility. For example, the config file is in TOML.
Wie Europas Open-Source-Versagen in die US-Abhängigkeit geführt hat
#OpenSource #Linux #Abhängigkeit #Microsoft #Google #Amazon #Versagen #DigitaleSouveränität #Verwaltung #openDesk
DId you know that some BSDs would return 0 if called recvmsg() for non-blocking UDP socket with all iov_len totalling to 0? No-one says this is incorrect return value, but Linux does return -1 EAGAIN in this case. It's a subtle difference but it can cause trouble if your code assumes certain behaviour.
netbsd kernel code responsible for returning 0 in this case: https://github.com/NetBSD/src/blob/68fd9ef50c0ab993c10e4f19cfa2a1f4dbb10802/sys/kern/uipc_socket.c#L578
Ubuntu 25.04 “Plucky Puffin” Takes Flight https://techstrong.it/featured/ubuntu-25-04-plucky-puffin-takes-flight/ by @sjvn via @techstronggroup
The latest #Ubuntu #Linux is looking pretty good as it takes off.
Why will the Year of the #Linux Desktop always be next year?
Because we're still trying to decide on the perfect window manager 🙄
Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟱/𝟬𝟰/𝟮𝟭 (Valuable News - 2025/04/21) available.
https://vermaden.wordpress.com/2025/04/21/valuable-news-2025-04-21/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
Latest 𝗩𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗡𝗲𝘄𝘀 - 𝟮𝟬𝟮𝟱/𝟬𝟰/𝟮𝟭 (Valuable News - 2025/04/21) available.
https://vermaden.wordpress.com/2025/04/21/valuable-news-2025-04-21/
Past releases: https://vermaden.wordpress.com/news/
#verblog #vernews #news #bsd #freebsd #openbsd #netbsd #linux #unix #zfs #opnsense #ghostbsd #solaris #vermadenday
On continue la tentative de migration de VM sous #Proxmox, c'est tout de suite sur https://twitch.tv/ahp_nils ! #sysadmin #devops #twitchfr #twitchstreamer #TwitchStreamers #linux
LXQt 2.2.0 released with enhanced Wayland support, power profiles in LXQt Power Management, PCManFM-Qt improvements, QTerminal text rendering fixes
https://lxqt-project.org/release/2025/04/17/release-lxqt-2-2-0/
#lxqt #qt6 #linuxdesktop #linux #opensource #freesoftware #wayland
3/3
Details warum das so ist, ob man das wirklich braucht (nein?!) und was man dafür oder dagegen machen kann sind in folgenden Link nachzulesen:
#verschlimmbessert #ctf #cybersecurity #linux #broken #permissions #chmod #sysctl
2/3
Im Detail lag die Datei in einem Verzeichnis mit Mode 1777 (sticky Bit am Verzeichnis gesetzt), die zu schreibende Datei gehörte nicht dem der Schreiben wollte/sollte - ein Prozess unter einer anderen UserID. Die Datei war mit Absicht Mode 666 (rw-rw-rw-) eben damit geschrieben werden kann, Standard unter Unix seit zigzig Jahren.
Stellt sich am Ende raus: das ist Linux-only und abhängig von einem sysctl.
#ctf #cybersecurity #linux #broken #permissions #chmod #sysctl
1/3
Ich konnte neulich nichts an eine fremde Datei anhängen die Mode 666 (rw-rw-rw-) war. Linux (natürlich), Fehlermeldung grad nicht zur Hand:
echo bla >> /tmp/logfile
Was war geschehen?
#ctf #cybersecurity #linux #broken #permissions #chmod #sysctl
💾 Quick HomeLab Update 💾
As a follow up to this morning's iGPU 512M GART debugging (re: drm-61-kmod memory leak on amdgpu.ko), here are some pics. Reluctantly, the "ok fine" method for testing the memory leak allocation aspects involves using a non-integrated GPU which requires the same driver, for which this low-TDP single-slot AMD W7500 was acquired. Sometime tomorrow it will be installed in my workstation, which is the third chassis from the bottom (4U) situated above the two 5U chassis (HCI private cloud for GPU compute VMs).
More to follow...
Dive into topics like PulseAudioDB, OpenBSD routers, shell history improvements, and more.
It's a solid edition with a gem: “Get your own home bin”, something we probably all do already in our own special ways.
→ https://utcc.utoronto.ca/~cks/space/blog/sysadmin/MyPersonalProgramsSetup
→ Full issue: https://newsletter.nixers.net/entries.php#286
#Unix #Linux #OpenBSD #Shell #Dotfiles #Newsletter #Nixers
Ubuntu 25.04 "Plucky Puffin" released with GNOME 48, Linux Kernel 6.14, enhanced installer and boot experience, new ARM64 desktop ISO
https://canonical.com/blog/canonical-releases-ubuntu-25-04-plucky-puffin
#ubuntu #ubuntu2504 #linux #linuxdesktop #gnome #gnome48 #canonical
When you want to run a middleweight Linux distribution and you already love & know Debian but don't want to run on super stable Server level since you are running a workstation *not* a server MX Linux is a very good choice as a distribution for you
You've got the power of Debian you'll get the stability of Debian yet you are bleeding edge and don't have applications which are rock stable but for a workstation a tad old
If you don't have a recent MX Linux installation you can download the new ISO version 23.6
If you have v23.5 there's no need to execute a fresh installation. The updated executables will roll out to you automatically.
https://mxlinux.org/blog/mx-23-6-now-available/
.🖋️ #bash #MX #mxLinux #sh #zsh #ksh #csh #tksh #fish #distro #Linux #POSIX #fresh #programming
There's one thing I had not done in a long time which is install a distribution of my choice with a full KDE desktop manager. I haven't done that in more than 2 decades. KDE has been wonderful at it's infancy and KDE is still wonderful now.
Since MX Linux is my distribution of choice, it's logical that I installed the KDE version of that distribution even if it's just for a test drive.
I've allocated just 20 gigs for KDE which means it's tight with space but it's still usable for a test run.
One tool I immediately missed was gparted the powerful gnome UI, which puts the precision of partition manipulation at your fingertips, without the chances of making costly mistakes if you don't pay enough attention or are not affluent enough with the commands in your favorite shell.
I missed that tool during the installation of mxKDE because I needed to add partitiond before the installation could proceed I just left Blank Space on an SSD.
Apart from that I can tell you from the initial view that KDE has not just matured, advanced and elevated itself. KDE has become so lightweight in resource usage that it can complete with very Light Desktop managers.
You can still edit your widgets up to & icons almost the pixel. The things that I love about KDE from decades ago are still there and are even more powerful.
Since I started to use KDE when GPU usage on the desktop was not even a thing, you can imagine how fast the DE is now and a period where GPU usage is normal for everything.
Out of the box KDE is already fantastic. Go and see what KDE can be for you, by installing it yourself
.🖋️ #bash #MX #mxLinux #sh #zsh #ksh #csh #tksh #fish #distro #KDE #Gnome #Linux #POSIX #fresh #programming
My next step was something unexpected.
In XFce4 my desktops all have different backgrounds per IPS Led Panel. Its a matter of context_menu_key (on my keyboard I have one) select background, then move the program to the next display beside it and repeat, then move it to the next desktop, display besides AD Infinitum
KDE says HELL NO to that ease.
I did some reasearch and saw that it was easy peasy in KDE 4.5.x then got replaced with activities in KDE Plasma 5.x
The simple command is now either kwin scripts or a lot of keystrokes and time.
Instead of getting pissed I went further and found that what the programmers replaced with activities (which are POWERFULL and versatile) and also usuable for wallpapers per VTop (Virtual desktop) was eased back (in 2022) with VallPaper
Source is here
https://cadence.moe/blog/2022-12-03-implementing-different-wallpapers-on-kde-virtual-desktops
.🖋️ #bash #MX #mxLinux #sh #zsh #ksh #csh #tksh #fish #distro #KDE #Gnome #Linux #POSIX #fresh #programming #backgrounds #wallpaper
I'm giving my thanks to the programmer of Vallpaper because it is a Gift from Thor IMHO. Without Vallpaper I would not be able to seamlessly change my wallpapers on all the desktops I have. Thank you for creating this wonderful program
Vallpaper can be found here https://store.kde.org/p/1197828
.🖋️ #bash #MX #mxLinux #sh #zsh #ksh #csh #tksh #fish #distro #KDE #Gnome #Linux #POSIX #fresh #programming #backgrounds #wallpaper #Vallpaper
I also encountered another problem; I can immediately tell you that it's not a KDE specific problem but it popped up in konsole.
The subject is fonts and the section is point size. The monitors I use are not of a small resolution. In fact an ideal IPS LED panel layout for me would be an 8K panel two 4K panels flanking it and two 1080p ultra ultra wide panels at a left and right of those.
With such a setup I can monitor different machines at the glance and control them with ease.
Even on my 1080p Ultra Ultra wide panel the default Point sizes for fonts are too small. On a scratch KDE based MX Linux installation, the following problem was repeated twice in Konsole.
The first time I changed font point sizes, closed konsole. When I reopened konsole the fixed with font, was replaced with one that appended spaces behind every couple of letters.
This rendered konsole unusable for work.
Changing the fonts Point sizes to the defaults again did not fix the problem.
Sinds that installation was Vanilla and didn't have enough space for home and root on one partition to actually Play with KDE, I wiped it and started again.
This time I deliberately did not change the point sizes even though it was hard to read. I then copied over some configuration directories from my other installation to this One, none of them related to anything KDE wise or any fonts directory. When I rebooted that installation The problem occurred for the second Time.
As with the wallpaper issue, I immediately converted that energy of irritation to something positive. I troubleshooted the font problem for a short while and when I couldn't isolate it I did a simple thing. I created a couple of other accounts on the same KDE installation to see if I could repeat the error.
That reproduction step is vital before a bug report is created. The other accounts were also residing on my other xFace MX Linux installations, which means I could simply copy them over to the other home partition where KDE was looking at.
In the other accounts I could not repeat the error.
That means a bug report is worthless because repeatability is crucial. Since the usage of a terminal in the K Desktop Environment is important, I changed my strategy and simply installed the xFace Four terminal in KDE. In the end that was a nice move since I know all the keyboard shortcuts of the terminal by hand they are in muscle memory and they have been there for years.
As a bonus I also installed other good shells in MX KDE the hashtags tell you which.
Right now I have a KDE installation in which I can actually work based upon the MX Linux KDE variant
I shall link a couple of photographs in a few minutes
.🖋️ #bash #MX #mxLinux #sh #zsh #ksh #csh #tksh #fish #distro #KDE #Gnome #Linux #POSIX #fresh #programming #backgrounds #wallpaper #Vallpaper
The next step was to config KDE connect in this KDE. Luckily I know that I need gufw to migrate my profile, from the xFce MX linux to this KDE MX linux.
It was a matter of installing gufw, which is not default in KDE distro, since it has its own nice interface. For me sticking with what I know is the easiest since I want to drive KDE on desktop again after so many decades, even though XFce is still going to be used most, due to shortcut muscle memory
.🖋️ #bash #MX #mxLinux #sh #zsh #ksh #csh #tksh #fish #distro #KDE #Gnome #Linux #POSIX #fresh #programming #backgrounds #wallpaper #Vallpaper
Next #swad improvement: Make sure to #wipe #passwords from RAM directly after used. That's more of a #security precaution, because there *should* be no way how an attacker can access a running process' memory, but you never know which bugs surface 🙈.
Unexpectedly, that posed #portability issues. #C11 has #memset_s ... a pretty weird function, but suitable for wiping. It's there on #FreeBSD and on #OpenBSD. Not on #NetBSD though. But NetBSD offers the much saner #C23 function #memset_explicit. Looking at #Linux, there's neither. But there is the (non-standard!) #explicit_bzero 🤯 .. and with glibc, it requires _DEFAULT_SOURCE to be defined as soon as you compile with a C standard version given to the compiler. This function exists on some other systems as well, but there's confusion whether it should be declared in string.h or strings.h. 🤪
Here's the full set of compile-tests I'm now doing, only to find the best way to really erase memory:
https://github.com/Zirias/swad/blob/master/src/bin/swad/swad.mk#L6
And if none of these functions is found, swad uses the "hacky" way that most likely works as well: Access the normal memset function via a volatile pointer.
Canonical Releases Ubuntu 25.04 Plucky Puffin https://canonical.com/blog/canonical-releases-ubuntu-25-04-plucky-puffin
Today, I implemented the #async / #await pattern (as known from #csharp and meanwhile quite some other languages) ...
... in good old #C! 😎
Well, at least sort of.
* It requires some standard library support, namely #POSIX user context switching with #getcontext and friends, which was deprecated in POSIX-1.2008. But it's still available on many systems, including #FreeBSD, #NetBSD, #Linux (with #glibc). It's NOT available e.g. on #OpenBSD, or Linux with some alternative libc.
* I can't do anything about the basic language syntax, so some boilerplate comes with using it.
* It has some overhead (room for extra stacks, even extra syscalls as getcontext unfortunately also always saves/restores the signal mask)
But then ... async/await in C! 🥳
Here are the docs:
https://zirias.github.io/poser/api/latest/class_p_s_c___async_task.html
I finally eliminated the need for a dedicated #thread controlling the pam helper #process in #swad. 🥳
The building block that was still missing from #poser was a way to await some async I/O task performed on the main thread from a worker thread. So I added a class to allow exactly that. The naive implementation just signals the main thread to carry out the requested task and then waits on a #semaphore for completion, which of course blocks the worker thread.
Turns out we can actually do better, reaching similar functionality like e.g. #async / #await in C#: Release the worker thread while waiting to do other jobs. The key to this is user context switching support like offered by #POSIX-1.2001 #getcontext and friends. Unfortunately it was deprecated in POSIX-1.2008 without an obvious replacement (the docs basically say "use threads", which doesn't work for my scenario), but still lots of systems provide it, e.g. #FreeBSD, #NetBSD, #Linux (with #glibc) ...
The posercore lib now offers both implementations, prefering to use user context switching if available. It comes at a price: Every thread job now needs its private stack space (I allocated 64kiB there for now), and of course the switching takes some time as well, but that's very likely better than leaving a task idle waiting. And there's a restriction, resuming must still happen on the same thread that called the "await", so if this thread is currently busy, we have to wait a little bit longer. I still think it's a very nice solution. 😎
In any case, the code for the PAM credential checker module looks much cleaner now (the await "magic" happens on line 174):
https://github.com/Zirias/swad/blob/57eefe93cdad0df55ebede4bd877d22e7be1a7f8/src/bin/swad/cred/pamchecker.c
Certain models of Lenovo laptops now ship with Fedora and Ubuntu Linux. This is done to keep costs low and cater to developers or IT professionals who heavily rely on Linux. Another reason could be the increased unpopularity of Windows 11 in recent times due unwanted features like "AI" or "Recall", but that is just my own wild guess ;) LOL. Would you buy it?