[ARMedslack] Problems with making use of existing Slackware on ARM for Raspberry PI images

Gregg Levine gregg.drwho8 at gmail.com
Mon Jan 7 20:37:54 UTC 2013


On Mon, Jan 7, 2013 at 3:31 PM, stanley garvey
<stanley at stanleygarvey.com> wrote:
> On Jan 7, 2013 20:15 "Gregg Levine" <gregg.drwho8 at gmail.com> wrote:
>
> On Mon, Jan 7, 2013 at 2:29 PM, stanley garvey
> <stanley at stanleygarvey.com> wrote:
>
> On Jan 7, 2013 15:58 "Gregg Levine" <gregg.drwho8 at gmail.com> wrote:
>
> On Mon, Jan 7, 2013 at 10:55 AM, stanley garvey
> <stanley at stanleygarvey.com> wrote:
>
> On Jan 7, 2013 15:03 "Gregg Levine" <gregg.drwho8 at gmail.com> wrote:
>
> On Mon, Jan 7, 2013 at 3:54 AM, <stanley at stanleygarvey.com> wrote:
> <Snip>
>
> Hello!
> I think from Rsync function. I'll retrieve it again and from your
> website. I'll know more later.
>
> Hi, just checked all files are identical:
> bash-4.1# md5sum SlackwareArm-14.0-8GB-20121201.zip
> 1dd852334977d734e5ff833ecacface9 SlackwareArm-14.0-8GB-20121201.zip (local
> copy)
>
> bash-4.1# md5sum SlackwareArm-14.0-8GB-20121201.zip
> 1dd852334977d734e5ff833ecacface9 SlackwareArm-14.0-8GB-20121201.zip (Danish
> server powered by windmills)
>
> Suggest you re-download the zip file and do:
> md5sum SlackwareArm-14.0-8GB-20121201.zip
> to check integrity.
> regards
> Stanley.
>
>
> Hello!
> Now it is getting baroque, I just ran the command against both a new
> file (downloaded today) and one that did cause the problems. The
> command returns the same hash codes.
>
> I'll try again momentarily.
> -----
> Gregg C Levine gregg.drwho8 at gmail.com
> "This signature fought the Time Wars, time and again."
>
> Blimey, I like baroque, somethings obviously baroque, but I cant think what
> it can be, if you live in Warwickshire I would cycle around and fix it for
> you! I Guess you don't? are you confusing a kernel panic will the annoying
> message from Pat regarding the file system being read/write? try pressing
> enter.
> With kind regards,
> Stanley.

Hello!
I see your point. I really do. This is indeed a kernel panic as the
system starts to panic when it can't find and mount the root file
system. Not the classic one regarding the file system being
read/write.

But I'll try again and see what happens next.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."


More information about the ARMedslack mailing list