Felicitations fellow Slackers...

There are some notable changes to be aware of on the SARPi Project website. Expect more changes to come. Some may be announced, others may not.

http://sarpi.fatdog.eu

NB: A Slackware ARM kernel source package is now available for each individual build [i.e. sarpi2, sarpi3, 14.2/current, etc.] so the sarpi*-kernel-source*.txz that's available on the <sarpi version here> downloads page is the same Linux kernel source data that built the image and kernel/modules packages. This can be verified through its git revision - which is available to view within the sarpi*.BuildLog.txt file on the same <sarpi version here> downloads page. As with the kernel source package, the build log is relevant to that SARPi build only. The build log is just for reference purposes until I find the time [and motivation] to deploy something more appropriate and Slackwaresque.

NB: Take this announcement as confirmation that Slackware ARM 14.2 is no longer being developed by the SARPi Project. This decision has been made because it takes as much time [and longer] to build and test for the 14.2 [soft float] port as it does for the current [hard float] port. Considering the bandwidth usage that SARPi incurs every month, there's more accrued by the [Slackware ARM 14.2] downloads for the RPi(1) alone, than the RPi2 and RPi3 combined, and that accounts for less than 10% of overall demand. So, it's not really worth the time and effort it requires when considering the 14.2 port will become EOL on the release of Slackware ARM 15.0 - which I hope and pray will not be long in arriving.

NB: The above does NOT mean that the SARPi Project intends to drop the support and distribution of Slackware ARM 14.2 related media. The file archives and packages will remain in place - sine die - even if/when Slackware ARM 14.2 is designated as EOL.

NB: There's been a double-overhaul of the build process(es) involved and, although there should be no impact what-so-ever on the end-user, I'd very much appreciate being apprised of any issues you may encounter while installing Slackware ARM using the [Linux kernel +5.4.x] SARPi installer(s). Likewise, if you upgrade your kernel and firmware using SARPi packages please make me aware of any issue(s).

NB: The Slackware ARM 14.2/current i2c-tools package that SARPi has supported and made available for many years has now ended. MoZes ships this package with Slackware ARM and has done for some time. So, you can now get this package from the Slackware ARM repositories and mirrors via direct download or 'slackpkg'. The SARPi i2c-tools packages will still be available to download via the RTC guide [http://sarpi.fatdog.eu/index.php?p=chronodot-rtc] but not from the main downloads page.

Thanks for your interest.

That’s a lot of updates at once. You’ve been busy! Thanks for the notification.

1 members found this post helpful.

I'd love to see some of your build processes/scripts published, they might help others when porting to other platforms.

It's not so much the build scripts themselves, as much as the process(es) involved as every task or function they perform can be very easily be carried out on command line. So they're nothing special in that sense. As with all software, the correct files in the right place means processes run like clockwork and that's pretty much the way SARPi works too. Yet, I take no credit for this!

The credit must go to Dave Spencer for his 'raspi-SlackBuild' work [https://github.com/idlemoor/raspi-slackbuild], which I fondly refer to as the "Mecca" of Slackware ARM on a Raspberry Pi, and these scripts are what the SARPi Project initially used as a template back in 2012. If you have the time to dedicate and are interested in porting Slackware ARM to other platforms then I would highly recommend diving headlong into these scripts and fathoming their depths. For me, this is how and where it all began, when me and Aal (fatdog.nl owner) rolled our sleeves up, downloaded 'raspi-SlackBuild', and got our hands dirty with some good old fashioned hard work.

The 'raspi-SlackBuild' scripts can be modified to build Slackware ARM images and packages for other platforms than the RPi, but it will take some time/effort to achieve it. I used them for reference when I ported Slackware ARM to the Hummingboard for the [now] discontinued humbo.fatdog.eu website.

If your Slackware adventure leads you on a similar path then I'd love to see you 'getting your hands dirty'. I'd love to see a lot more Slackers doing just that!

2 members found this post helpful.

Thanks.

[EDIT] All aliases and forwards to https://sarpi.fatdog.eu should be OK now.

The 'sarpi.co.uk' domain which was a forwarder to the SARPi Project website] has been dropped. Any links to the domain on the Internet will no longer take you to the sarpi.fatdog.eu website and should be ignored. Please use sarpi.fatdog.eu instead.

Thanks.