Testing Mobile Safari on device using linux with ios-safari-remote-debug-kit

One thing that has been frustrating to me is how hard it is to test iOS devices when you no longer have a MacOS device and Safari to test on.

I stumbled upon ios-safari-remote-debug-kit which uses ios-webkit-debug-proxy to allow the inspector in Chromium. This ended up being straightforward despite the many dependencies listed on the latter. Mainly because I already had them with Slackware!

The only caveat is that I needed to allow Chromium write access to its files again. I removed write access to specific files in ~/.config/chromium for privacy, which Chromium complains about, but it still...

https://nokoto.org/node/583

## First steps towards Raspberry Pi5 support

### Stuart Winter's latest announcement on 05 Oct on the official Linux ARM port:

Using the new SAIR (Slackware AArch64 Installer Respin) tool, I created a variant of the Slackware AArch64 Installer that uses the Raspberry Pi Kernel fork instead of the upstream Linus Torvalds kernel. To test it, I installed Slackware onto a Raspberry Pi 4, and it worked — a big milestone! 🎉 Why the Pi 4? Because I don’t yet have an RPi5, but this gives me a way to get the core pieces working now so that we’ll be ready to integrate full support for the Raspberry Pi 5 as soon as I can test on real hardware. This is just the beginning, but it’s an exciting step forward. Thanks so much for your support.

If you're interested in a fully supported rolling distro for your production rPi home or office network you can track development following the Changelog HERE

Installation guides and video tutorials for rPi4 installation (including a rather comprehensive hardware guide) are located HERE and complete instructions for installation on other popular product lines such as Pine64 as well can be found HERE.

Stuart and Brent work hard at bringing the very leading edge of computing to the ARM architecture and #Slackware_Linux rides the cusp of that endeavor with their dedication and commitment to the single board computer market.

For your next #Raspberry_Pi project, consider the simple yet sleek and performant stability that Slackware Linux has been famous for since it was first distributed around campus at Moorehead State University on floppy disks over 30 years ago, predating Debian, Redhat, and every other Linux distribution in the marketplace.

As for me? Well, it says so in most of my profiles: "Slackware, OpenBSD, and a bit of a Debiantard." And that about sums it up for now!

### A bit on source based and rolling Linux distributions:

- Slackware -current, like Debian testing, Gentoo, and Arch Linux, is a fully rolling Linux distribution. A single command provides complete system updates to the very latest in versioning of packages and ongoing, active development.
- Unlike most other package based distributions, Slackware linux 'can be' a completely sourced based Linux distro, albeit a mostly inconvenient and rather redundant effort, since a single command can fetch and reinstall every single component of the base system (once initial installation of the machine has been completed), due to Slackware's uniquely historical, and simplistic methodology.
- Almost all additional packages not already in the official Slackware installation, with exception of a few very large and intensive applications, are #source_based installs, also capable of being fetched, downloaded from the upstream developer source repos, compiled, packaged, and installed locally (including dependencies) - with a single command. Some packages such as Firefox, LibreOffice, etc., are so huge that trusted package repos are maintained so they can be downloaded, and then installed in seconds with a single command.
- Once you have installed applications, you can share those packages with others freely so they can merely take those packages and install them in a few seconds with a single command. It is however, preferred by most to use the SlackBuilds.org repository for #Slackbuild scripts to compile and install from source (it's a trust issue).
- Slackware Linux is the oldest, extant Linux distro, and has maintained an aggressive, continuous development cycle since its initial public announcement on Usenet in 1993. The Slackware Team has also traditionally provided the longest running support for release versions over that of all Linux distributions (over a decade before EOL in many cases).

I hope that helps, enjoy!

#tallship @mozes #Slackware #FOSS #UNIX #ARM

I tried to update greetd package, which needs a bunch of new crates and versions. But it looks like static.crates.io has blocked me already.

Ugh, I really do not like working with cargo and rust. It’s so annoying. I much prefer working with a dependency system that relies on libraries that I can package as well, but that’s not practical with rust as everything depends a bajillion packages (may not actually be true).

Guess I have to wait a while to update a package.

In retrospect, I should have worked out the bash loop around the greetd.download file first.

My basic work flow is

There seem like a lot of changes to the build instructions for obs-studio in the recent major version release. 

A list of changes that I needed to make in the SBO current SlackBuild: