[ARMedslack] armedslack hang on emqbit

Vitaly V. Ch vitaly.v.ch at gmail.com
Thu Feb 4 08:12:53 UTC 2010


At now I'm find root of troubles: incompatibility my patched kernels and
glibc from armedslack.

PS: I'm last maintainer of BCSLinux and maintainer of iZumLinux. Both
Slackware based.

\\wbr Vitaly Chernookiy

On Wed, Feb 3, 2010 at 11:28 PM, Vitaly V. Ch <vitaly.v.ch at gmail.com> wrote:

>
>
> On Wed, Feb 3, 2010 at 1:40 PM, Stuart Winter <m-lists at biscuit.org.uk>wrote:
>
>>
>> On Tue, 2 Feb 2010, Vitaly V. Ch wrote:
>>
>> > rootfs is created in way like tinstall.sh. also i'm notice then rootfs
>> > armedslack-devtools/armel/rootfs/armel-root-fs.tar.bz2 is also
>> unbootable,
>>
>> Oh this is ancient stuff - it's not Slackware - just a collection of
>> stuff I was using when creating the eabi port.
>>
>
> I found this stuff pretty :)
>
>>
>> I don't have a rootfs for ARMedslack available yet; but if there's demand
>> then I could write a script to create one!
>>
>
> I'm wrong. I can successfully boot only when I use debian 4.0 root fs from
> Your repositoriy at armedslack-devtools/armel/rootfs/armel-root-fs.tar.bz2.
>
> Any other rootfs fail to boot.
>
> \\wbr Vitaly Chernookiy
>
>>
>> --
>>
>> Stuart Winter
>> Slackware ARM: www.armedslack.org
>> _______________________________________________
>> ARMedslack mailing list
>> ARMedslack at lists.armedslack.org
>> http://lists.armedslack.org/mailman/listinfo/armedslack
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.armedslack.org/pipermail/armedslack/attachments/20100204/1902d57b/attachment.htm>


More information about the ARMedslack mailing list