You have to search for Slackware to find references to it running on the Raspberry Pi - I had to ask here - which is not what most users will do. Let us petition/harrass/work on adding ArmedSlack and Slackware to the list of "supported" or "blessed" distros running on the Raspberry Pi.

http://www.raspberrypi.org/downloads

The "blessed" list already includes Arch so they are not entirely avoiding distros with a somewhat steep learning curve, and I would argue that Slackware is far easier to install and use than Arch.

Personally I thing that the miniroot install method is by far the quickest ... and Slackware ARM is on of the few that give you miniroot images naturally you need a little knowledge (but not that much) to go from a miniroot to wherever you want to go.

To my understanding on the RPF download section they have ready-made images and apart from my emergency miniroot install method the community has moved towards targeting the Pi via a normal install. The problem is that the only image that would be maintained as slackware evolves is the miniroot that that is a bit too minimal to be a ready to use image to give to RPF.
Supposing we made such an image who would maintain it ?
There needs be someone that maintains at least the list of packages that go in the image and keep updating the kernel with whatever is shipped with rasbian (or eventually one day, if the patches get pushed mainsteam, with a vanilla kernel configured for the Pi).

If we can find such a volunteer I thinks the rest could be arranged. Any volunteers ?

Someone already tried to get Slackware on to the list of distributions there but couldn't for some reason -- I forget what the problem was now.

Given that we have FatDog's detailed installation instructions, I don't see any reason why we couldn't have Slackware on that list: unless there are some other criteria that are not laid out.
Does anybody know of any reason why we couldn't?

By the way I am not against the idea of a 'fat root' where there are X packages and window managers etc. The only issue is that I cannot test those. The testing of the miniroots is limited to 'ls' 'find' and a few other bits of activity that happen to fire in my brain at the time when the script drops to the chroot (since I maintain the entire distribution, I tend to remember what dependencies have been added, so they get added to the mini root build script ahead of time). That really is the limit of the unit test for that one (seems to work well so far though apart from one fix I needed to make in several years). Adding X and window managers means I'd have to have an actual set of test procedures. At that point it's better to just install the packages you need using the installer, since if you install them all then it's been tested reasonably well already. I cannot test X inside a chroot from a serial console.

Don't worry Stuart: all my Slackware ARM installations are done starting off with one of your miniroots ... so if something brakes I'll tell you. And thanks again for giving us such a powerful and flexible thing.

Because I've received no response from repeated forum posts and direct emails asking the same question, I get the impression the RPi Foundation just aren't interested in supporting Slackware ARM. The problem was no reply, response, comment in my particular case.

It's odd that a no profit foundation is ignoring community self supported efforts for their hardware ... or maybe they're just not listening where we are asking.

This is from their contact us section on their site:
Are they really reading everything ?

Penthux: Not sure if this stuff has already made it way into the fat dog's image ... this is just in case it has not.
I recently compiled newest available kernel for rpi (3.10.29) from sources ... and updated to the newest boot firmware and my pi now boot much more reliably then it was doing before with 3.6.11 kernel and the older boot firmware (where it was common that I'd haveto power up and down a few time before successfully booting).

Just browsing here: http://elinux.org/RPi_Distributions and I've noticed there is absolutely no mention of SlackwareARM except as a footnote to SlaXBMCRPi...

Has anyone talked to the folks at elinux about Slackware?

But Salckware ARM is amongst the supported OS on the pi's wikipedia page:
http://en.wikipedia.org/wiki/Raspber...rating_systems

I know. Just pointing out that http://elinux.org/RPi_Hub aggregates a huge amount of information on using, developing, hacking the RaspberryPI, yet there is no mention of Slackware anyware... Perhaps we could help.

Personally, I found Fatdog's guide so detailed, so well done and so usefull that, along with Stanley's and Dave's work, it should be among the recommended guides.

Perhaps we should help out and add it! After all, eLinux is a Wiki, unlike the RPI foundation whose responsiveness, or more likely lack of it is mentioned earlier.

How about somebody creates an account there and adds Slackware ARM to it? There are links and thanks to the elinux.org site on rpi.fatdog.eu so it makes sense.