>
> Hi
>
>
> Since Slackware 14.1 is coming together, could all of you who
> plan on preparing and distributing support for Slackware ARM
> 14.1 for the RaspberryPi please reply to this message (on-list) with the
> following information. I will collate it and put it into the
> /INSTALL_RASPBERRYPI.TXT document within the release.
>
> Note that this is *only* for those of you who are supplying
> images/installers that contain the _official_ Slackware ARM packages which
> will be taken from ftp.arm.slackware.com/slackwarearm/slackwarearm-14.1.
>
> 1. The URL of the web site containing information about your
> distribution.
>
> 2. Installation method: regular installer / pre-supplied image(s)
>
> If it's a pre-supplied image, what categories of software are
> included:
>
> Don't list every package, but a high level brief description such as:
>
> dev tools ('d')
>
> - Compilers and toolchain tools
> - Python, Perl
>
> X11 ('x')
>
> - X packages relevant to the Rpi
>
> KDE ('kde')
> - All of KDE
> - Base components of KDE
>
>
> 3. RPi boards / versions of boards that your distribution has been
> tested with and confirmed operational.
>
> 4. The particular reason for choosing yours over another. Some of the
> reasons that some people have created their own image is because Dave
> Spencer's work stopped at 13.37, or theirs addressed particular
> problems on certain boards.
>
> Please note that this shouldn't be a reason for the 14.1 release -
> you should treat this as new rather than a patch to someone else's
> work (even
> if that's what it started out as).
>
>
> Deadline:
> ---------
>
> I'll stop taking submissions at the release of RC1 of Slackware 14.1 x86.
>
> Any questions - please ask!
>
> Cheers
> Stuart.
>
>
> --
> Stuart Winter
> www.slackware.com/~mozes
> Slackware for ARM: http://arm.slackware.com
> _______________________________________________
> ARMedslack mailing list
> ARMedslack@lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
>
Hi Stuart
I would be happy to provide both an installer and some pre-installed
images for 14.1 for the Raspberry Pi.
Installer:
1) stanleygarvey.com/Slackberry/index.php
2)regular installer, after install drop to shell and execute
raspberrypi/finalise.sh (a simple bash script to remove non rpi kernels,
source and stuff).
3) Version 14.0 tested on model B boards revision A 256MB and B 512MB and
confirmed operational, however the file '70-persistent-net.rules' may
require tweeking to bring eth0 up.
4) No particular reason for choosing my installer over another. It is a
modified version of your versatile-initrd placed on David Spenser's
partition scheme.
Pre-supplied images:
1) stanleygarvey.com/Slackberry/index.php
2)full install of all packages excluding KDE KDEI and kernel source.
3) Version 14.0 tested on model B boards revision A 256MB and B 512MB and
confirmed operational, however the file '70-persistent-net.rules' may
require tweeking to bring eth0 up.
4) No particular reason for choosing my pre-installed images over another.
Kernels are now built using a modified slackwarearm build script and do
not occupy the kernel.bin namespace.
Also a plea for help. Since 14.0 eth0 is renamed to eth1 on first boot
(but not always), I did not see this in version 13.37 and attributed this
to an error on my part then to rc.wireless. since It also occurs when
using the installer I think it may be a race condition some were. If
anyone can help with this please drop a line to me on the list.
_______________________________________________
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
