shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

285
active users

#freebsd

21 posts19 participants0 posts today
Continued thread

Ok, so check this out. I raved about how magical #FreeBSD #linuxulator is, but it gets even better! In my Ubuntu linux jail, I downloaded the source for the #mobian kernel, installed cross-compiling tools, compiled the kernel and modules, copied to an sdcard, and booted up the kernel on my #pinephonepro 🤯 So, on my amd64 FreeBSD, I used a translation layer to load up Ubuntu Linux, used it to cross-compile a Linux kernel for arm64, and booted that up on a device! How unbelievable is that?!?

Replied to Doerk

@NebulaTide @dtonlinux @mms @nixCraft

Yep, I get it. #NomadBSD is definitely a recommendation for newbies who just want to give BSD a spin.

I've been very happy with #OpenBSD on my writing machine for over a year now.

I'd like to try #FreeBSD on my home desktop again sometime. The only reason I prefer OpenBSD to it is that it tends to do S3 suspend/resume faster. Oh, and it has X11 working out of the box after install. ;)

rldane.spaceWeb 1.0 is (unironically) going great

#GoodMorning, good #tzag, and happy #Caturday! :calicat2:

Home alone this morning as A meets up with her daughter and some friends for a day out. All fed with breakfast, but still more #coffee to drink. :flan_coffee: Gonna focus on setting up that Piwigo gallery on #FreeBSD via a host provider, once I decide on which one to go with. :flan_hacker: :runbsdBg:

As for the Big Guy, here's a pic of him from yesterday before I fired up the grill. He loves being outside. :flan_cat:

Is there anybody who can tell me what to read/learn in order to create impulse response of a guitar cabinet with SciPy, please? I tried Aliki on #FreeBSD and Voxengo Deconvolver on #Windows and they all failed, so I'd like to develop a small CLI to do that. As a matter of fact, it needs to do 2 things: generate sine sweep and create IR file from sweep and capture. I know SciPy has impulse, convolve and deconvolve, but I still don't know how to use them to produce IR. Math and programming are not the problem, the problem is that I can't find explanation how it's done. Please boost for visibility! Thank you!

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:
github.com/Zirias/swad/blob/ma

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.

Simple Web Authentication Daemon. Contribute to Zirias/swad development by creating an account on GitHub.
GitHubswad/src/bin/swad/swad.mk at master · Zirias/swadSimple Web Authentication Daemon. Contribute to Zirias/swad development by creating an account on GitHub.

💡 Idea for a debugging script 💡

This might already exist for FreeBSD, and if so.. let me know!

- 1) keeps record of OS core/default settings: loader.conf, rc.conf, sysctl.conf, devfs.rules, login.conf etc
- 2) keeps record of file checksum on those OS core files (similar to the app, tripwire)
- 3) mode which shows divergence on current state vs known-default state in configs (1) and checksums (2)
-4) mode which tracks the files and their change-sets over time, similar to a zfs snapshot but at a single file-level

Continued thread

I found the problem even with ImageMagick7, which can't convert SVG to PNG. Instead it crashes with coredump.

Before April's update all programs works perfectly fine.

For now, I creating the account in the #FreeBSD bugtracker to describe this bug...

As promiced, I wrote a blog post about how to create NAM #audio files using ardour on #FreeBSD (although not FreeBSD specific). meka.rs/blog/2025/04/15/neural

Goran Mekić · Neural Amp ModelingOne of the great things that came out of AI hype is Neural Amp Modeler, or NAM for short. In essence the process is simple: take sweep sound that the AI is trained with and reamp your gear with it. Connect your preamp to your audio interface (you might need reamp box, depending on your interface’s in/out impedance and levels), record output of your preamp while it’s input is the sweep sound. To be perfectly correct it is not sweeping, but it’s term that is used in creation of Impulse Response or IR for short. I found that the easiest way to create NAM is to go to tone3000 and download “sweep signal”. Make sure your ardour session is set to 48kHz. Import the downloaded audio file (T3K-sweep-v3.wav at time of this writing) into a track that has all inputs disconnected and only one output connected: the one you use to connect your audio interface to preamp. Create one more track, disconnect all its outputs and only connect the input to the one where your preamp’s out is connected. Record the output of your preamp and align start and end of sweep and recorded clip in their tracks. Normalize the recorded clip and go to Session -> Export -> Stem Export and choose sweep and recorded tracks. Choose to export the files in 48kHz 24bit format. The reason is that no matter what I did, I couldn’t produce output wav file to be the same size or “shape” (signals were out of sync) if I export just recorded track. With stem export, both of the resulting wav files are going to be exactly the same length. Go to tone3000’s capture and upload dry (sweep) and wet (recorded) files. For better performance I suggest compiling jack from ports with SOSSO library enabled. It can dramatically reduce DSP usage in jack/ardour. Once you have your .nam file, you can use neuralrack-lv2 to load it together with some IR. I will write about IRs some other time, until then, have fun!
Replied to Michael Dexter

@dexter If any #FreeBSD folks are looking for a jails-related project, the one I’d really like someone to do is UID mapping:

For each jail, record the UID of the creator in the jail structure (we should reserve space for this in 15).

For filesystem access, do two checks, one of the creator UID against the file, the other of the jailed user UID against a field in extended attributes. If that field does not exist, do the check against the real rights for the file.

When file permissions or ownership are changed, record that change in xattrs, not in the file’s permissions.

Do not allow modification of these xattrs by jailed users.

This is most of what is required to permit jails to be created by non-root users. A jailed user’s rights are never more than those of the user, but may be less.

So, if I ever recommended @system76... disregard that shit.

I had to bury yet another battery in a bucket of sand in my yard for the same laptop. Fracking thing went all spicy pillow on me, again.

It wasn't even decent Linux centric hardware. The gorram Realtek on-board Ethernet was always dogshit slow. The wireless required me to use wifibox on #FreeBSD to get anything beyond 802.11g speeds. The speakers were tinty as hell, and the webcam was pathetic. It all worked.... barely.

I'm not paying for another battery. They took over a month the last time I needed a replacement. I'm going back to my Lenovo x230 from 2012, which is still far more reliable than anything I have wasted money on from System76.

The April 15th, 2025 Jail/Zones Production User Call is up:

youtu.be/7JzanDRuhlg

We #FreeBSD 15.0 goals, jail escape mitigations (please review!), attracting Kubernetes users, configuration file delimiters, an update on Kleene.dev, Jail names vs. IDs, and more!

"Don't forget to slam those Like and Subscribe buttons."

youtu.be- YouTubeEnjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.

Documentation in operating systems is cool. It is possible to extend and rewrite utilities as time goes on, as #freebsd proves. You can still have cool utilities, like #containers and #zfs and #hypervisors, good docs for them and a consistent base system.

I dunno where I am going with this, other than wishing I didn't have to peruse the Arch wiki and the Gentoo wiki for everything when I get stuck, and instead could just "man xyz" and get good answers, speaking as #nixos user.

Replied in thread
@ianthetechie @feld I can confirm that #Python on #FreeBSD behaves as one would expect. It consumes all RAM (with #ZFS releasing ARC as expected) and then dips into swap. As soon as Python releases memory after the ingestion routine, the swap is purged to near zero and the RAM then becomes available (and used) by the system. Far more predictable and reliable.

If you have big, vertical workloads, FreeBSD is where it is at.