Ditto.

It seems to me the big fuss is not being able to achieve something and blaming someone/something else as the reason why, or why not. Fair dinkum mate. Biggest pile of horse hockey I've seen this year!

I've already advised the OP that he's wasting his time compiling the mainstream kernel for the RPi, unless he's doing it for education purposes, etc. It's a LOT of work compared to using the Raspberry Pi GitHub kernel which is pre-configured for the device(s). Therefore, it makes good sense to use it, and learn all about it, before trying to get to grips with the mainstream kernel. You have to be able to walk before trying to run.

Compiling a kernel is a little more involved than running a makefile or SlackBuild script. I get the impression the OP would like it to be as effortless and simple. That's never going to happen.

I spent quite a lot of time building mainstream kernels for the RPis until I realised it didn't make a damned difference whether the mainstream kernel or the RPi flavoured kernel was running with Slackware ARM. The only benefit being; my personal satisfaction of knowing the kernel that I'd built hadn't been fiddled with, only by me. Although, my personal failures far outnumber my successes. To this day that still holds true. As you know, it's often a case of finding out what doesn't work many, many times over until you find out what does work.

je vous en prie

1 members found this post helpful.

A way while back I did some project management for a very switched on entrepreneur up in the Territory. People often sought his advice. I once remarked to him that he was a real expert to which he replied that he was the sum total of all his mistakes and that one only needs to know a couple more things than the rest to be the expert in the room.

Are there SlackBuild's for the sarpi.fatdog.eu's system packages (incl. kernel) available? I was surprised I could not find any.

No. The SARPi build scripts are not available.

I'd hate to see a multitude of modified/thrown-together/botched SARPi versions out there. And, in that reality, just _who_ do you think would get the blame for someone else's voodoo-Slacking?

However, when the SARPi Project first began we used a highly modified version of Dave Spencer's [Daves Collective] build scripts for creating the installer and packages on the RPi [1], and continue to do so to this day. We make changes and do updates as required but it's basically the same set of scripts we started out with in 2012. For the RPi 2 and 3 we wrote our own build scripts based on Dave's work. Probably not as efficient in the code but they have the same end result.

If you are interested in building your own Slackware ARM installer(s) for the RPis then Dave's Collective is THE best place to start!

1 members found this post helpful.

First, thanks for setting up the project and the pointer to Dave Spencer's repo :+1:

This may be less of a problem than you perceive. We are operating in an open-source environment where people would expect to come across modified versions. After all, how is the situation any different from Slackware's?

You're welcome. Back in early-mid 2012 there was a gaping void between Slackware ARM and the Raspberry Pi and thats why the project came into being. We were planning to write our own build scripts from scratch but when we found Dave's Collective it just made more sense to use his work and save some time.

I don't need to perceive how serious a problem is, or insignificant. Especially when the problem doesn't exist.

1 members found this post helpful.

Unfortunately this is a problem for me, and I'll have to find an alternative. One of the reasons I use Slackware is it is mostly Open Source, however this essentially makes core components closed.

Closed source, like the Raspberry Pi firmware you mean? Sure. I get your point.

However, SARPi is nothing but a method to install Slackware ARM on a Raspberry Pi 1,2, or 3. It's Slackware ARM that's installed not SARPi. SARPi is not an operating system or anything which encroaches on Slackware ARM, other than facilitating the installation of the OS. Which core components are you referring to? Are you suggesting that Slackware ARM is diminished in some way because the build scripts for SARPi installers are not available to download or view?

SARPi takes MoZes' minirootfs and the closed source firmware from RPi GitHub and mashes it together in a union that obviously works, but shouldn't really be allowed. I never used to have a problem with the RPi firmware being closed source but, as I have grown over time in knowledge and experience, I now see disparity between the openness and transparency of Slackware ARM and the BS surrounding the Raspberry Pi in certain areas. Closed source firmware being one of those areas.

My closing questions are; Why do you want the SARPi installer code to be made publicly available? Are you interested in taking the project on yourself, hence saving fatdog.nl the time/trouble/effort of managing, maintaining, and hosting it? Was your visit to the Mecca of Slackware ARM on a Raspberry Pi [i.e. Dave's Collective] not as inspriational and productive as you'd imagined or hoped?

So you can kick back and post threads like this?

2 members found this post helpful.

One can re-build the ARM packages from the ARM source tree by following the instructions, but many of the ARM port's tools are not open and never will be, for a variety of reasons.

I think he just doesn't want to share it :-)

1 members found this post helpful.

"SARPi takes MoZes' minirootfs and the closed source firmware from RPi GitHub and mashes it together in a union that obviously works, but shouldn't really be allowed. I never used to have a problem with the RPi firmware being closed source but, as I have grown over time in knowledge and experience, I now see disparity between the openness and transparency of Slackware ARM and the BS surrounding the Raspberry Pi in certain areas. Closed source firmware being one of those areas."

Agreed, this is annoying.

"My closing questions are; Why do you want the SARPi installer code to be made publicly available? Are you interested in taking the project on yourself, hence saving fatdog.nl the time/trouble/effort of managing, maintaining, and hosting it? Was your visit to the Mecca of Slackware ARM on a Raspberry Pi [i.e. Dave's Collective] not as inspriational and productive as you'd imagined or hoped?"

My "thank you" earlier was not insincere. Its mainly the System Packages, i.e. Kernel + modules. The website setup and instructions are great.

No. Yes. Perhaps. It's certainly worth considering but, hmmm, I'm not 100% sure. What kind of question is this anyway? It doesn't even hint or allude towards any Jaffa cakes what-so-ever!

The integrity and reputation of Slackware must be respected in any SARPi work we decide to publicly release. We control that aspect because we're maintaining the build scripts, creation process(es), testing, released software, etc. If we made those build scripts available to the public, who knows what personal additions and modifications people would carry out in order to "make it better"? SARPi doesn't need to be messed about with. It works as intended and pretty damned flawlessly, just like Slackware [ARM]. There's no way I would risk polluting what we do for the Slackware ARM community, however great or small that risk may be, by allowing others to DIY their own SARPi shizzle using our means, methods, and scripts/tools/Jaffa cakes to achieve it.

I understand how many of Slackware ARM port's tools are not open and never will be, for a variety of reasons. One of those reasons must be because you don't want me to see that your bash scripting is a lot messier than mine!

PS - I was joking about the Jaffa cakes. Obviously!

Not biting.

OK. I'm going to assume here that you're looking for an effortless way to build a kernel and modules and put them in neat little Slackware.txz packages for you. By all means correct me if I am misunderstanding and/or have misread your intentions.

Building the Linux kernal/modules, and putting them in packages is quite a big topic, depending on your current knowledge and experience in this area of Slackware Linux. It's not necessarily an easy process but certainly not too difficult. However, what you may gain from such a venture is potentially HUGE and I'm all for Slackers getting their hands dirty and doing some real interesting educational work. Let me know where you're at or what you're looking for and I will try to point you in the right direction.