ARMedslack Slackware ARM port ()

headers Giovanni | 21 Apr 2011 13:24 · /slackware/

_______________________________________________
ARMedslack mailing list
ARMedslack <at> lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

On Thu, 21 Apr 2011 13:24:12 +0200
Giovanni <pino.otto <at> gmail.com> wrote:

> Do you know whether it is possible to install and run Slackware ARM
> on this small computer?
> 
> http://www.dealextreme.com/p/standalone-bittorrent-bt-client-usb-nas-ftp-samba-printer-upnp-sharing-network-lan-server-26320
> 
> This is the hardware:
> 
> CPU clock at 250MHz, CPU: FA526id(wb)(ARMv4) Memory: 32MB = 32MB
> total PCI clock at 33M

I don't know, but I don't think you'll be happy with it regardless.
The transfer speeds are going to be terribly slow - bottlenecking
due to the usb2 speeds *and* the general wimpiness of the hardware.

-RW

> I don't know, but I don't think you'll be happy with it regardless.
> The transfer speeds are going to be terribly slow - bottlenecking
> due to the usb2 speeds *and* the general wimpiness of the hardware.

Yeah having built the distribution on 287MHZ RiscPCs for a couple of years
with 256MB RAM... I don't know how I kept going.  I guess because there
wasn't any better or faster supported arm hardware at the time, so I
didn't have anything to wish I could have 

I wouldn't bother with it. Some devices use lower speed ARM CPUs but their
usage (and software) is tuned to the device to match the usage with the
device's specs.  Slackware ARM is a generic distribution built to run
on the widest range of products possible, at the expense of speed in some
areas (which IMO can easily be re-gained by recompiling glibc and some
other critical libraries; but that's another topic :) ).

_______________________________________________
ARMedslack mailing list
ARMedslack <at> lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

You would have to install it either manually using a script, or try and
use the mini root filesystem (probably the easiest route).
You could not install using the slackware installer because the installer
wouldn't even fit into RAM!

It may work though but as usual you'd have get a kernel, figure out the
boot loader etc..

On Thu, 21 Apr 2011, Giovanni wrote:

> Do you mean that I can install and run Slackware ARM on the NS-K330?
>
> best regards
> giovanni
>
>
> On Thu, Apr 21, 2011 at 5:49 PM, Stuart Winter <m-lists <at> biscuit.org.uk>wrote:
>
> >
> > > I don't know, but I don't think you'll be happy with it regardless.
> > > The transfer speeds are going to be terribly slow - bottlenecking
> > > due to the usb2 speeds *and* the general wimpiness of the hardware.
> >
> > Yeah having built the distribution on 287MHZ RiscPCs for a couple of years
> > with 256MB RAM... I don't know how I kept going.  I guess because there
> > wasn't any better or faster supported arm hardware at the time, so I
> > didn't have anything to wish I could have 
> >
> > I wouldn't bother with it. Some devices use lower speed ARM CPUs but their
> > usage (and software) is tuned to the device to match the usage with the
> > device's specs.  Slackware ARM is a generic distribution built to run
> > on the widest range of products possible, at the expense of speed in some
> > areas (which IMO can easily be re-gained by recompiling glibc and some
> > other critical libraries; but that's another topic :) ).
> >
> >
> > _______________________________________________
> > ARMedslack mailing list
> > ARMedslack <at> lists.armedslack.org
> > http://lists.armedslack.org/mailman/listinfo/armedslack
> >
>

--

-- 
Stuart Winter
Slackware ARM: www.armedslack.org

_______________________________________________
ARMedslack mailing list
ARMedslack <at> lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

I'm interested in the recompiling glibc thing to regain speed on specific hardware: has this been
discussed in the ML previously ?

--- Gio 21/4/11, Stuart Winter <m-lists <at> biscuit.org.uk> ha scritto:

> Da: Stuart Winter <m-lists <at> biscuit.org.uk>
> Oggetto: Re: [ARMedslack] Slackware ARM on Small NAS (NS-K330)
> A: "Slackware ARM port" <armedslack <at> lists.armedslack.org>
> Data: Giovedì 21 Aprile 2011, 17:49
> 
> > I don't know, but I don't think you'll be happy with
> it regardless.
> > The transfer speeds are going to be terribly slow -
> bottlenecking
> > due to the usb2 speeds *and* the general wimpiness of
> the hardware.
> 
> Yeah having built the distribution on 287MHZ RiscPCs for a
> couple of years
> with 256MB RAM... I don't know how I kept going.  I
> guess because there
> wasn't any better or faster supported arm hardware at the
> time, so I
> didn't have anything to wish I could have 
> 
> I wouldn't bother with it. Some devices use lower speed ARM
> CPUs but their
> usage (and software) is tuned to the device to match the
> usage with the
> device's specs.  Slackware ARM is a generic
> distribution built to run
> on the widest range of products possible, at the expense of
> speed in some
> areas (which IMO can easily be re-gained by recompiling
> glibc and some
> other critical libraries; but that's another topic :) ).
> 
> 
> _______________________________________________
> ARMedslack mailing list
> ARMedslack <at> lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
> 

I think it has but I don't recall anybody having done it.

What hardware?

I'm quite interested in it because I'm still thinking about building
armedslack for armv5te (it's armv4 at the moment).
We need some valid test cases.

On Sat, 30 Apr 2011, Davide wrote:

> I'm interested in the recompiling glibc thing to regain speed on specific hardware: has this been
discussed in the ML previously ?
>
> --- Gio 21/4/11, Stuart Winter <m-lists <at> biscuit.org.uk> ha scritto:
>
> > Da: Stuart Winter <m-lists <at> biscuit.org.uk>
> > Oggetto: Re: [ARMedslack] Slackware ARM on Small NAS (NS-K330)
> > A: "Slackware ARM port" <armedslack <at> lists.armedslack.org>
> > Data: Giovedì 21 Aprile 2011, 17:49
> >
> > > I don't know, but I don't think you'll be happy with
> > it regardless.
> > > The transfer speeds are going to be terribly slow -
> > bottlenecking
> > > due to the usb2 speeds *and* the general wimpiness of
> > the hardware.
> >
> > Yeah having built the distribution on 287MHZ RiscPCs for a
> > couple of years
> > with 256MB RAM... I don't know how I kept going.  I
> > guess because there
> > wasn't any better or faster supported arm hardware at the
> > time, so I
> > didn't have anything to wish I could have 
> >
> > I wouldn't bother with it. Some devices use lower speed ARM
> > CPUs but their
> > usage (and software) is tuned to the device to match the
> > usage with the
> > device's specs.  Slackware ARM is a generic
> > distribution built to run
> > on the widest range of products possible, at the expense of
> > speed in some
> > areas (which IMO can easily be re-gained by recompiling
> > glibc and some
> > other critical libraries; but that's another topic :) ).
> >
> >
> > _______________________________________________
> > ARMedslack mailing list
> > ARMedslack <at> lists.armedslack.org
> > http://lists.armedslack.org/mailman/listinfo/armedslack
> >
> _______________________________________________
> ARMedslack mailing list
> ARMedslack <at> lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
>

--

-- 
Stuart Winter
Slackware ARM: www.armedslack.org
_______________________________________________
ARMedslack mailing list
ARMedslack <at> lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

I wanted to get all I can out of my dockstar if it works well I might even do that on my zauruses (C 760/860/1000).
The zauri should all be ARMv5 as husky boxer are PXA255 and Akita is PXA270.
While the dockstar I'm not sure but I think it's ARMv5 too.

It would be the first time I look into rebuilding glibc in order to get better performance and actually I
don't recall ever doing it at all so if I did I just followed the build scripts to build it. Any help is
appreciated for this task.

Regards
David

> I think it has but I don't recall anybody having done it.
> 
> What hardware?
> 
> I'm quite interested in it because I'm still thinking about
> building
> armedslack for armv5te (it's armv4 at the moment).
> We need some valid test cases.
> 
> On Sat, 30 Apr 2011, Davide wrote:
> 
> > I'm interested in the recompiling glibc thing to
> regain speed on specific hardware: has this been discussed
> in the ML previously ?
> >
> > --- Gio 21/4/11, Stuart Winter <m-lists <at> biscuit.org.uk>
> ha scritto:
> >
> > > Da: Stuart Winter <m-lists <at> biscuit.org.uk>
> > > Oggetto: Re: [ARMedslack] Slackware ARM on Small
> NAS (NS-K330)
> > > A: "Slackware ARM port" <armedslack <at> lists.armedslack.org>
> > > Data: Giovedì 21 Aprile 2011, 17:49
> > >
> > > > I don't know, but I don't think you'll be
> happy with
> > > it regardless.
> > > > The transfer speeds are going to be terribly
> slow -
> > > bottlenecking
> > > > due to the usb2 speeds *and* the general
> wimpiness of
> > > the hardware.
> > >
> > > Yeah having built the distribution on 287MHZ
> RiscPCs for a
> > > couple of years
> > > with 256MB RAM... I don't know how I kept
> going.  I
> > > guess because there
> > > wasn't any better or faster supported arm
> hardware at the
> > > time, so I
> > > didn't have anything to wish I could have 
> > >
> > > I wouldn't bother with it. Some devices use lower
> speed ARM
> > > CPUs but their
> > > usage (and software) is tuned to the device to
> match the
> > > usage with the
> > > device's specs.  Slackware ARM is a generic
> > > distribution built to run
> > > on the widest range of products possible, at the
> expense of
> > > speed in some
> > > areas (which IMO can easily be re-gained by
> recompiling
> > > glibc and some
> > > other critical libraries; but that's another
> topic :) ).
> > >
> > >
> > > _______________________________________________
> > > ARMedslack mailing list
> > > ARMedslack <at> lists.armedslack.org
> > > http://lists.armedslack.org/mailman/listinfo/armedslack
> > >
> > _______________________________________________
> > ARMedslack mailing list
> > ARMedslack <at> lists.armedslack.org
> > http://lists.armedslack.org/mailman/listinfo/armedslack
> >
> 
> -- 
> Stuart Winter
> Slackware ARM: www.armedslack.org
> -----Segue allegato-----
> 
> _______________________________________________
> ARMedslack mailing list
> ARMedslack <at> lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
> 

ftp://ftp.armedslack.org/armedslack/armedslack-current/source/README_SOURCE.txt
Read that and download the slackware64-current tree (including sources)

cd armedslack-current/source/l/glibc
sed -i 's?armv4t?armv5te?g' glibc.SlackBuild

Change the BUILD number in the arm/build script to whatever - increase it
or make it your own stamp - eg 4_davide

Start the build (under screen would be better incase your host machine
dies!)

On a sheevaplug the build takes about a day to build natively:

./arm/build

Then your packages will appear in the armedslack-current/slackware/{a,l}
directories.

> I wanted to get all I can out of my dockstar if it works well I might even do that on my zauruses (C 760/860/1000).
> The zauri should all be ARMv5 as husky boxer are PXA255 and Akita is PXA270.
> While the dockstar I'm not sure but I think it's ARMv5 too.
>
> It would be the first time I look into rebuilding glibc in order to get better performance and actually I
don't recall ever doing it at all so if I did I just followed the build scripts to build it. Any help is
appreciated for this task.
>
> Regards
> David
>
> > I think it has but I don't recall anybody having done it.
> >
> > What hardware?
> >
> > I'm quite interested in it because I'm still thinking about
> > building
> > armedslack for armv5te (it's armv4 at the moment).
> > We need some valid test cases.
> >
> > On Sat, 30 Apr 2011, Davide wrote:
> >
> > > I'm interested in the recompiling glibc thing to
> > regain speed on specific hardware: has this been discussed
> > in the ML previously ?
> > >
> > > --- Gio 21/4/11, Stuart Winter <m-lists <at> biscuit.org.uk>
> > ha scritto:
> > >
> > > > Da: Stuart Winter <m-lists <at> biscuit.org.uk>
> > > > Oggetto: Re: [ARMedslack] Slackware ARM on Small
> > NAS (NS-K330)
> > > > A: "Slackware ARM port" <armedslack <at> lists.armedslack.org>
> > > > Data: Giovedì 21 Aprile 2011, 17:49
> > > >
> > > > > I don't know, but I don't think you'll be
> > happy with
> > > > it regardless.
> > > > > The transfer speeds are going to be terribly
> > slow -
> > > > bottlenecking
> > > > > due to the usb2 speeds *and* the general
> > wimpiness of
> > > > the hardware.
> > > >
> > > > Yeah having built the distribution on 287MHZ
> > RiscPCs for a
> > > > couple of years
> > > > with 256MB RAM... I don't know how I kept
> > going.  I
> > > > guess because there
> > > > wasn't any better or faster supported arm
> > hardware at the
> > > > time, so I
> > > > didn't have anything to wish I could have 
> > > >
> > > > I wouldn't bother with it. Some devices use lower
> > speed ARM
> > > > CPUs but their
> > > > usage (and software) is tuned to the device to
> > match the
> > > > usage with the
> > > > device's specs.  Slackware ARM is a generic
> > > > distribution built to run
> > > > on the widest range of products possible, at the
> > expense of
> > > > speed in some
> > > > areas (which IMO can easily be re-gained by
> > recompiling
> > > > glibc and some
> > > > other critical libraries; but that's another
> > topic :) ).
> > > >
> > > >
> > > > _______________________________________________
> > > > ARMedslack mailing list
> > > > ARMedslack <at> lists.armedslack.org
> > > > http://lists.armedslack.org/mailman/listinfo/armedslack
> > > >
> > > _______________________________________________
> > > ARMedslack mailing list
> > > ARMedslack <at> lists.armedslack.org
> > > http://lists.armedslack.org/mailman/listinfo/armedslack
> > >
> >
> > --
> > Stuart Winter
> > Slackware ARM: www.armedslack.org
> > -----Segue allegato-----
> >
> > _______________________________________________
> > ARMedslack mailing list
> > ARMedslack <at> lists.armedslack.org
> > http://lists.armedslack.org/mailman/listinfo/armedslack
> >
> _______________________________________________
> ARMedslack mailing list
> ARMedslack <at> lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
>

--

-- 
Stuart Winter
Slackware ARM: www.armedslack.org
_______________________________________________
ARMedslack mailing list
ARMedslack <at> lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

On 05/01/2011 02:19 AM, Stuart Winter wrote:
>
> ftp://ftp.armedslack.org/armedslack/armedslack-current/source/README_SOURCE.txt
> Read that and download the slackware64-current tree (including sources)
>
> cd armedslack-current/source/l/glibc
> sed -i 's?armv4t?armv5te?g' glibc.SlackBuild

I have been actively doing this with alot of the libs and currently gcc and 
adding PKGARCH to scripts that dont have it and building armv5te packages.

Once I get to re-build the libs and gcc with armv5te binaries (another day or 
so) I will tackle the rest of the basics, then run some benchmarks.  Not sure if 
anything will jump out or if it will be the same...

But I'm bored 

And I have 4 plugs chugging away at this.  I love distcc!

I'll let you know what comes of it.

John

--

-- 
=== Never ask a geek why, just nod your head and slowly back away.===
+================================+==================================+
|  John O'Donnell                |                                  |
|  (Sr. Systems Engineer,        |    http://juanisan.homeip.net    |
|  Net Admin, Programmer, etc.)  |  E-Mail: unixjohn1969 <at> gmail.com  |
+================================+==================================+
No man is useless who has a friend, and if we are loved we are
indispensable.  -- Robert Louis Stevenson

> ftp://ftp.armedslack.org/armedslack/armedslack-current/source/README_SOURCE.txt
> Read that and download the slackware64-current tree
> (including sources)

What's the difference between 
ftp://ftp.slackware.com/pub/slackware/slackware64-current/source
and
ftp://ftp.slackware.org.uk/armedslack/armedslack-current/source/ 

Is it "Slackware ARM only includes the sources in situations when .... " ?

At the time I worked on something I liked to call slackurus I had a different approach: I used to fix the
slackbuild scripts so that I could use them for building binaries for zaurus by cross compilation and I had
my own overlall build script that looked for packages to build and built them.
But at that time either armedslack was not around or I did not know about it ... way back in 2004 ... well also
many other things might have changed 

> cd armedslack-current/source/l/glibc
> sed -i 's?armv4t?armv5te?g' glibc.SlackBuild

Ok that will change just one thing in that buildscript:
-march=armv4t to -march=armv5te

> Change the BUILD number in the arm/build script to whatever
> - increase it
> or make it your own stamp - eg 4_davide
> 
> Start the build (under screen would be better incase your
> host machine
> dies!)
> 
> On a sheevaplug the build takes about a day to build
> natively:
> 
> ./arm/build
> 
> Then your packages will appear in the
> armedslack-current/slackware/{a,l}
> directories.

Will this build everiting ?
Can I just rebuild glibc or is it necessary to rebuild every binary that links the new glibc ?
I was hoping that since version will not be changing maybe I could do with just slipping in the new armv5 tuned
glibc: am I wrong in hoping this ?

> > I wanted to get all I can out of my dockstar if it
> works well I might even do that on my zauruses (C
> 760/860/1000).
> > The zauri should all be ARMv5 as husky boxer are
> PXA255 and Akita is PXA270.
> > While the dockstar I'm not sure but I think it's ARMv5
> too.
> >
> > It would be the first time I look into rebuilding
> glibc in order to get better performance and actually I
> don't recall ever doing it at all so if I did I just
> followed the build scripts to build it. Any help is
> appreciated for this task.
> >
> > Regards
> > David
> >
> > > I think it has but I don't recall anybody having
> done it.
> > >
> > > What hardware?
> > >
> > > I'm quite interested in it because I'm still
> thinking about
> > > building
> > > armedslack for armv5te (it's armv4 at the
> moment).
> > > We need some valid test cases.
> > >
> > > On Sat, 30 Apr 2011, Davide wrote:
> > >
> > > > I'm interested in the recompiling glibc
> thing to
> > > regain speed on specific hardware: has this been
> discussed
> > > in the ML previously ?
> > > >
> > > > --- Gio 21/4/11, Stuart Winter <m-lists <at> biscuit.org.uk>
> > > ha scritto:
> > > >
> > > > > Da: Stuart Winter <m-lists <at> biscuit.org.uk>
> > > > > Oggetto: Re: [ARMedslack] Slackware ARM
> on Small
> > > NAS (NS-K330)
> > > > > A: "Slackware ARM port" <armedslack <at> lists.armedslack.org>
> > > > > Data: Giovedì 21 Aprile 2011, 17:49
> > > > >
> > > > > > I don't know, but I don't think
> you'll be
> > > happy with
> > > > > it regardless.
> > > > > > The transfer speeds are going to
> be terribly
> > > slow -
> > > > > bottlenecking
> > > > > > due to the usb2 speeds *and* the
> general
> > > wimpiness of
> > > > > the hardware.
> > > > >
> > > > > Yeah having built the distribution on
> 287MHZ
> > > RiscPCs for a
> > > > > couple of years
> > > > > with 256MB RAM... I don't know how I
> kept
> > > going.  I
> > > > > guess because there
> > > > > wasn't any better or faster supported
> arm
> > > hardware at the
> > > > > time, so I
> > > > > didn't have anything to wish I could
> have 
> > > > >
> > > > > I wouldn't bother with it. Some devices
> use lower
> > > speed ARM
> > > > > CPUs but their
> > > > > usage (and software) is tuned to the
> device to
> > > match the
> > > > > usage with the
> > > > > device's specs.  Slackware ARM is a
> generic
> > > > > distribution built to run
> > > > > on the widest range of products
> possible, at the
> > > expense of
> > > > > speed in some
> > > > > areas (which IMO can easily be
> re-gained by
> > > recompiling
> > > > > glibc and some
> > > > > other critical libraries; but that's
> another
> > > topic :) ).
> > > > >
> > > > >
> > > > >
> _______________________________________________
> > > > > ARMedslack mailing list
> > > > > ARMedslack <at> lists.armedslack.org
> > > > > http://lists.armedslack.org/mailman/listinfo/armedslack
> > > > >
> > > >
> _______________________________________________
> > > > ARMedslack mailing list
> > > > ARMedslack <at> lists.armedslack.org
> > > > http://lists.armedslack.org/mailman/listinfo/armedslack
> > > >
> > >
> > > --
> > > Stuart Winter
> > > Slackware ARM: www.armedslack.org
> > > -----Segue allegato-----
> > >
> > > _______________________________________________
> > > ARMedslack mailing list
> > > ARMedslack <at> lists.armedslack.org
> > > http://lists.armedslack.org/mailman/listinfo/armedslack
> > >
> > _______________________________________________
> > ARMedslack mailing list
> > ARMedslack <at> lists.armedslack.org
> > http://lists.armedslack.org/mailman/listinfo/armedslack
> >
> 
> -- 
> Stuart Winter
> Slackware ARM: www.armedslack.org
> -----Segue allegato-----
> 
> _______________________________________________
> ARMedslack mailing list
> ARMedslack <at> lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
> 
Regards
David

> What's the difference between
> ftp://ftp.slackware.com/pub/slackware/slackware64-current/source
> and
> ftp://ftp.slackware.org.uk/armedslack/armedslack-current/source/
>
> Is it "Slackware ARM only includes the sources in situations when .... " ?

Yes.
[mozes <at> bourbon armedslack-13.37] $ du -sh source/
513M    source/
[mozes <at> bourbon armedslack-13.37] $ du -sh ../slackware64-current/source/
2.5G    ../slackware64-current/source/
[mozes <at> bourbon armedslack-13.37] $

Most of the MBs in armedslack's sources are firefox, seamonkey and
kernels.

> At the time I worked on something I liked to call slackurus I had a
> different approach: I used to fix the slackbuild scripts so that I could
> use them for building binaries for zaurus by cross compilation and I had
> my own overlall build script that looked for packages to build and built
> them. But at that time either armedslack was not around or I did not
> know about it ... way back in 2004 ... well also many other things might
> have changed 

The way I did it was based on trial, error and doing my best to do as
little as possible to update the packages in order to build them.
There are other bits that aren't in the public tree which are used to show
the differences in the x86 tree how it is now, and how it was when I last
built the package.
Updating the source files means two things:
 - You have to keep copying them - could be scripted, but then what about
   new patches? what about the old ones? some bits would be scriptable but
   it's just easier not to.
 - You then need to spend ages uploading the sources.

The way I have done it has worked with minimal effort since 2002 

> > armedslack-current/slackware/{a,l}
> > directories.
>
> Will this build everiting ? Can I just rebuild glibc or is it necessary
> to rebuild every binary that links the new glibc ? I was hoping that
> since version will not be changing maybe I could do with just slipping
> in the new armv5 tuned glibc: am I wrong in hoping this ?

It'll build glibc - the glibc packages (solibs & zoneinfo) that are in the
a/ series, and the main glibc packages (including the header files) in l/
Look in the slackware directories or just read the build script - it's
easy to figure it out.

You don't need to rebuild everything that links against glibc (ie
everything in the entire distribution). You're rebuilding glibc with
optimisations - you're not changing the ABI or anything like that!
You might want to rebuild bash too.  I've got a feeling you should also
rebuild zlib.

--

-- 
Stuart Winter
Slackware ARM: www.armedslack.org

> > What's the difference between
> > ftp://ftp.slackware.com/pub/slackware/slackware64-current/source
> > and
> > ftp://ftp.slackware.org.uk/armedslack/armedslack-current/source/
> >
> > Is it "Slackware ARM only includes the sources in
> situations when .... " ?
> 
> Yes.
> [mozes <at> bourbon armedslack-13.37] $ du -sh source/
> 513M    source/
> [mozes <at> bourbon armedslack-13.37] $ du -sh
> ../slackware64-current/source/
> 2.5G    ../slackware64-current/source/
> [mozes <at> bourbon armedslack-13.37] $
> 
> Most of the MBs in armedslack's sources are firefox,
> seamonkey and
> kernels.
> 
> > At the time I worked on something I liked to call
> slackurus I had a
> > different approach: I used to fix the slackbuild
> scripts so that I could
> > use them for building binaries for zaurus by cross
> compilation and I had
> > my own overlall build script that looked for packages
> to build and built
> > them. But at that time either armedslack was not
> around or I did not
> > know about it ... way back in 2004 ... well also many
> other things might
> > have changed 
> 
> The way I did it was based on trial, error and doing my
> best to do as
> little as possible to update the packages in order to build
> them.
> There are other bits that aren't in the public tree which
> are used to show
> the differences in the x86 tree how it is now, and how it
> was when I last
> built the package.
> Updating the source files means two things:
>  - You have to keep copying them - could be scripted, but
> then what about
>    new patches? what about the old ones?
> some bits would be scriptable but
>    it's just easier not to.
>  - You then need to spend ages uploading the sources.
> 
> The way I have done it has worked with minimal effort since
> 2002 

Don't get me wrong ... I don't want to change how you do things I was just telling how I went about it.
But if armedslack was around since 2002 I wasted a lot of time with the slackurus thing I played with and never
actually finished. I know that you can't fit armedslack in a the zaurus internal flash .... but I was
already using SD as storage for root filesystem and in amy case I could have borrowed tons of packages. 
Actually if I can get a satisfactory kernel I might dig up again my C1000 and use it around the place instead of
my netbook 

> 
> > > armedslack-current/slackware/{a,l}
> > > directories.
> >
> > Will this build everiting ? Can I just rebuild glibc
> or is it necessary
> > to rebuild every binary that links the new glibc ? I
> was hoping that
> > since version will not be changing maybe I could do
> with just slipping
> > in the new armv5 tuned glibc: am I wrong in hoping
> this ?
> 
> 
> It'll build glibc - the glibc packages (solibs &
> zoneinfo) that are in the
> a/ series, and the main glibc packages (including the
> header files) in l/
> Look in the slackware directories or just read the build
> script - it's
> easy to figure it out.
> 
> You don't need to rebuild everything that links against
> glibc (ie
> everything in the entire distribution). You're rebuilding
> glibc with
> optimisations - you're not changing the ABI or anything
> like that!
> You might want to rebuild bash too.  I've got a
> feeling you should also
> rebuild zlib.

Maybe I should let John run ahead to see if he gets some good kick out of it .... for the moment I've enough of my
spare time going into the busybox micro system (wife is already complaining that I'm not helping enough
with the kid).

> 
> -- 
> Stuart Winter
> Slackware ARM: www.armedslack.org
> _______________________________________________
> ARMedslack mailing list
> ARMedslack <at> lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
> 

> > The way I have done it has worked with minimal effort since
> > 2002 
>
> Don't get me wrong ... I don't want to change how you do things I was
> just telling how I went about it.

Me too! 

> But if armedslack was around since
> 2002 I wasted a lot of time with the slackurus thing I played with and
> never actually finished.

Heh. It's a lot of effort isn't it and a *lot* of time.
I have no idea how much time I've spent on this since 2002. I was even
working on it when I was backpacking in Australia - although I don't think
I'd released anything then -- it looks like 11.0 in 2007 was the first
time I'd released although it'd been publically in -current form since
2004: that's probably why you didn't find anything when you looked.

> I know that you can't fit armedslack in a the
> zaurus internal flash ....

You just reminded me that I didn't update the minirootfs for 13.37!
/me updates the release instruction docs!

The miniroot for -current expands to 213MB-- the SD Card is smaller?

> > rebuild zlib.
>
> Maybe I should let John run ahead to see if he gets some good kick out
> of it .... for the moment I've enough of my spare time going into the
> busybox micro system (wife is already complaining that I'm not helping
> enough with the kid).

Can do -- I can also do it. -current for x86 won't be started for a while
yet, so my SPs have nothing to do.  I've got to upgrade my ancient systems
from 13.something to .37 tomorrow, rebuild the x-toolchains and then I'll
start a build of glibc going and I'll upload it somewhere.

Can anybody suggest any valid benchmark tests though?
I'm going to have a look at lmbench now

--

-- 
Stuart Winter
Slackware ARM: www.armedslack.org

> > But if armedslack was around since
> > 2002 I wasted a lot of time with the slackurus thing I
> played with and
> > never actually finished.
> 
> Heh. It's a lot of effort isn't it and a *lot* of time.
> I have no idea how much time I've spent on this since 2002.
> I was even
> working on it when I was backpacking in Australia -
> although I don't think
> I'd released anything then -- it looks like 11.0 in 2007
> was the first
> time I'd released although it'd been publically in -current
> form since
> 2004: that's probably why you didn't find anything when you
> looked.

That cheers me up because I was blaming myself for not looking hard enough.
I know what you mean ... I spent tons of time and I never even got trough it! You've been at it for many releases
... thanks a million for the effort you put in.

> > I know that you can't fit armedslack in a the
> > zaurus internal flash ....
> 
> You just reminded me that I didn't update the minirootfs
> for 13.37!
> /me updates the release instruction docs!
> 
> The miniroot for -current expands to 213MB-- the SD Card is
> smaller?

No and the internal flash is 265Mb but the bare miniroot is too leen to be used on a netbook replacement ... but
it's a cool starting point.

Has anyone managed to build tinyx from recent xorg sources ?
I'd like to try that and fluxbox or icevm as window manager on my Z.

> 
> > > rebuild zlib.
> >
> > Maybe I should let John run ahead to see if he gets
> some good kick out
> > of it .... for the moment I've enough of my spare time
> going into the
> > busybox micro system (wife is already complaining that
> I'm not helping
> > enough with the kid).
> 
> Can do -- I can also do it. -current for x86 won't be
> started for a while
> yet, so my SPs have nothing to do.  I've got to
> upgrade my ancient systems
> from 13.something to .37 tomorrow, rebuild the x-toolchains
> and then I'll
> start a build of glibc going and I'll upload it somewhere.

That would be really nice of you ... I'd be happy to do some benchmarking for you.

> Can anybody suggest any valid benchmark tests though?
> I'm going to have a look at lmbench now

Maybe should pick some benchmark tool and just flunk the mass storage info, as everyone has different
storage arrangements, and gust look closely at how cpu is performing ?

Would it be any good to time how long it takes to compile the armedslack-current kernel ? But to eliminate io
related differences everyone paticipating should then compile twice (once with old glibc and once with
new glibc).

Regards
David

Forgot to mention another thing: I've put up a qemu environment on a machine running dual core centrino  <at> 
1.83Ghz with 1Gb of ram.
I know there's a lot better around but that's what I get at work and my own PC has not been upgraded since 2002
and mu netbook is no better then that too. 
Would it make sense to compile with a virtual machine under qemu (let's say I can give it some 750Mb of ram) or
would it be better to comple directly on the dockstar ?

I know there are better ways to do this but for the moment these are my best 2 choices.

Regards
David

> ftp://ftp.armedslack.org/armedslack/armedslack-current/source/README_SOURCE.txt
> Read that and download the slackware64-current tree
> (including sources)
> 
> cd armedslack-current/source/l/glibc
> sed -i 's?armv4t?armv5te?g' glibc.SlackBuild
> 
> Change the BUILD number in the arm/build script to whatever
> - increase it
> or make it your own stamp - eg 4_davide
> 
> Start the build (under screen would be better incase your
> host machine
> dies!)
> 
> On a sheevaplug the build takes about a day to build
> natively:
> 
> ./arm/build
> 
> Then your packages will appear in the
> armedslack-current/slackware/{a,l}
> directories.
> 
> > I wanted to get all I can out of my dockstar if it
> works well I might even do that on my zauruses (C
> 760/860/1000).
> > The zauri should all be ARMv5 as husky boxer are
> PXA255 and Akita is PXA270.
> > While the dockstar I'm not sure but I think it's ARMv5
> too.
> >
> > It would be the first time I look into rebuilding
> glibc in order to get better performance and actually I
> don't recall ever doing it at all so if I did I just
> followed the build scripts to build it. Any help is
> appreciated for this task.
> >
> > Regards
> > David
> >
> > > I think it has but I don't recall anybody having
> done it.
> > >
> > > What hardware?
> > >
> > > I'm quite interested in it because I'm still
> thinking about
> > > building
> > > armedslack for armv5te (it's armv4 at the
> moment).
> > > We need some valid test cases.
> > >
> > > On Sat, 30 Apr 2011, Davide wrote:
> > >
> > > > I'm interested in the recompiling glibc
> thing to
> > > regain speed on specific hardware: has this been
> discussed
> > > in the ML previously ?
> > > >
> > > > --- Gio 21/4/11, Stuart Winter <m-lists <at> biscuit.org.uk>
> > > ha scritto:
> > > >
> > > > > Da: Stuart Winter <m-lists <at> biscuit.org.uk>
> > > > > Oggetto: Re: [ARMedslack] Slackware ARM
> on Small
> > > NAS (NS-K330)
> > > > > A: "Slackware ARM port" <armedslack <at> lists.armedslack.org>
> > > > > Data: Giovedì 21 Aprile 2011, 17:49
> > > > >
> > > > > > I don't know, but I don't think
> you'll be
> > > happy with
> > > > > it regardless.
> > > > > > The transfer speeds are going to
> be terribly
> > > slow -
> > > > > bottlenecking
> > > > > > due to the usb2 speeds *and* the
> general
> > > wimpiness of
> > > > > the hardware.
> > > > >
> > > > > Yeah having built the distribution on
> 287MHZ
> > > RiscPCs for a
> > > > > couple of years
> > > > > with 256MB RAM... I don't know how I
> kept
> > > going.  I
> > > > > guess because there
> > > > > wasn't any better or faster supported
> arm
> > > hardware at the
> > > > > time, so I
> > > > > didn't have anything to wish I could
> have 
> > > > >
> > > > > I wouldn't bother with it. Some devices
> use lower
> > > speed ARM
> > > > > CPUs but their
> > > > > usage (and software) is tuned to the
> device to
> > > match the
> > > > > usage with the
> > > > > device's specs.  Slackware ARM is a
> generic
> > > > > distribution built to run
> > > > > on the widest range of products
> possible, at the
> > > expense of
> > > > > speed in some
> > > > > areas (which IMO can easily be
> re-gained by
> > > recompiling
> > > > > glibc and some
> > > > > other critical libraries; but that's
> another
> > > topic :) ).
> > > > >
> > > > >
> > > > >
> _______________________________________________
> > > > > ARMedslack mailing list
> > > > > ARMedslack <at> lists.armedslack.org
> > > > > http://lists.armedslack.org/mailman/listinfo/armedslack
> > > > >
> > > >
> _______________________________________________
> > > > ARMedslack mailing list
> > > > ARMedslack <at> lists.armedslack.org
> > > > http://lists.armedslack.org/mailman/listinfo/armedslack
> > > >
> > >
> > > --
> > > Stuart Winter
> > > Slackware ARM: www.armedslack.org
> > > -----Segue allegato-----
> > >
> > > _______________________________________________
> > > ARMedslack mailing list
> > > ARMedslack <at> lists.armedslack.org
> > > http://lists.armedslack.org/mailman/listinfo/armedslack
> > >
> > _______________________________________________
> > ARMedslack mailing list
> > ARMedslack <at> lists.armedslack.org
> > http://lists.armedslack.org/mailman/listinfo/armedslack
> >
> 
> -- 
> Stuart Winter
> Slackware ARM: www.armedslack.org
> -----Segue allegato-----
> 
> _______________________________________________
> ARMedslack mailing list
> ARMedslack <at> lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
> 

QEMU is limited to 256MB RAM for the ARM emulation, and it'll be way
slower than a dockstar.  On my 3.4GHz PentiumD, QEMU ARM isn't something
I'd want to use unless I really had to - which is why I shelled out some
more ££ and bought another sheevaplug to maintain 13.37 on!
.. and I don't like spending money (unless it's someone else's)! 

On Sun, 1 May 2011, Davide wrote:

> Forgot to mention another thing: I've put up a qemu environment on a machine running dual core centrino  <at> 
1.83Ghz with 1Gb of ram.
> I know there's a lot better around but that's what I get at work and my own PC has not been upgraded since 2002
and mu netbook is no better then that too.
> Would it make sense to compile with a virtual machine under qemu (let's say I can give it some 750Mb of ram) or
would it be better to comple directly on the dockstar ?
>
> I know there are better ways to do this but for the moment these are my best 2 choices.
>
> Regards
> David
>
> > ftp://ftp.armedslack.org/armedslack/armedslack-current/source/README_SOURCE.txt
> > Read that and download the slackware64-current tree
> > (including sources)
> >
> > cd armedslack-current/source/l/glibc
> > sed -i 's?armv4t?armv5te?g' glibc.SlackBuild
> >
> > Change the BUILD number in the arm/build script to whatever
> > - increase it
> > or make it your own stamp - eg 4_davide
> >
> > Start the build (under screen would be better incase your
> > host machine
> > dies!)
> >
> > On a sheevaplug the build takes about a day to build
> > natively:
> >
> > ./arm/build
> >
> > Then your packages will appear in the
> > armedslack-current/slackware/{a,l}
> > directories.
> >
> > > I wanted to get all I can out of my dockstar if it
> > works well I might even do that on my zauruses (C
> > 760/860/1000).
> > > The zauri should all be ARMv5 as husky boxer are
> > PXA255 and Akita is PXA270.
> > > While the dockstar I'm not sure but I think it's ARMv5
> > too.
> > >
> > > It would be the first time I look into rebuilding
> > glibc in order to get better performance and actually I
> > don't recall ever doing it at all so if I did I just
> > followed the build scripts to build it. Any help is
> > appreciated for this task.
> > >
> > > Regards
> > > David
> > >
> > > > I think it has but I don't recall anybody having
> > done it.
> > > >
> > > > What hardware?
> > > >
> > > > I'm quite interested in it because I'm still
> > thinking about
> > > > building
> > > > armedslack for armv5te (it's armv4 at the
> > moment).
> > > > We need some valid test cases.
> > > >
> > > > On Sat, 30 Apr 2011, Davide wrote:
> > > >
> > > > > I'm interested in the recompiling glibc
> > thing to
> > > > regain speed on specific hardware: has this been
> > discussed
> > > > in the ML previously ?
> > > > >
> > > > > --- Gio 21/4/11, Stuart Winter <m-lists <at> biscuit.org.uk>
> > > > ha scritto:
> > > > >
> > > > > > Da: Stuart Winter <m-lists <at> biscuit.org.uk>
> > > > > > Oggetto: Re: [ARMedslack] Slackware ARM
> > on Small
> > > > NAS (NS-K330)
> > > > > > A: "Slackware ARM port" <armedslack <at> lists.armedslack.org>
> > > > > > Data: Giovedì 21 Aprile 2011, 17:49
> > > > > >
> > > > > > > I don't know, but I don't think
> > you'll be
> > > > happy with
> > > > > > it regardless.
> > > > > > > The transfer speeds are going to
> > be terribly
> > > > slow -
> > > > > > bottlenecking
> > > > > > > due to the usb2 speeds *and* the
> > general
> > > > wimpiness of
> > > > > > the hardware.
> > > > > >
> > > > > > Yeah having built the distribution on
> > 287MHZ
> > > > RiscPCs for a
> > > > > > couple of years
> > > > > > with 256MB RAM... I don't know how I
> > kept
> > > > going.  I
> > > > > > guess because there
> > > > > > wasn't any better or faster supported
> > arm
> > > > hardware at the
> > > > > > time, so I
> > > > > > didn't have anything to wish I could
> > have 
> > > > > >
> > > > > > I wouldn't bother with it. Some devices
> > use lower
> > > > speed ARM
> > > > > > CPUs but their
> > > > > > usage (and software) is tuned to the
> > device to
> > > > match the
> > > > > > usage with the
> > > > > > device's specs.  Slackware ARM is a
> > generic
> > > > > > distribution built to run
> > > > > > on the widest range of products
> > possible, at the
> > > > expense of
> > > > > > speed in some
> > > > > > areas (which IMO can easily be
> > re-gained by
> > > > recompiling
> > > > > > glibc and some
> > > > > > other critical libraries; but that's
> > another
> > > > topic :) ).
> > > > > >
> > > > > >
> > > > > >
> > _______________________________________________
> > > > > > ARMedslack mailing list
> > > > > > ARMedslack <at> lists.armedslack.org
> > > > > > http://lists.armedslack.org/mailman/listinfo/armedslack
> > > > > >
> > > > >
> > _______________________________________________
> > > > > ARMedslack mailing list
> > > > > ARMedslack <at> lists.armedslack.org
> > > > > http://lists.armedslack.org/mailman/listinfo/armedslack
> > > > >
> > > >
> > > > --
> > > > Stuart Winter
> > > > Slackware ARM: www.armedslack.org
> > > > -----Segue allegato-----
> > > >
> > > > _______________________________________________
> > > > ARMedslack mailing list
> > > > ARMedslack <at> lists.armedslack.org
> > > > http://lists.armedslack.org/mailman/listinfo/armedslack
> > > >
> > > _______________________________________________
> > > ARMedslack mailing list
> > > ARMedslack <at> lists.armedslack.org
> > > http://lists.armedslack.org/mailman/listinfo/armedslack
> > >
> >
> > --
> > Stuart Winter
> > Slackware ARM: www.armedslack.org
> > -----Segue allegato-----
> >
> > _______________________________________________
> > ARMedslack mailing list
> > ARMedslack <at> lists.armedslack.org
> > http://lists.armedslack.org/mailman/listinfo/armedslack
> >
> _______________________________________________
> ARMedslack mailing list
> ARMedslack <at> lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
>

--

-- 
Stuart Winter
Slackware ARM: www.armedslack.org
_______________________________________________
ARMedslack mailing list
ARMedslack <at> lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

_______________________________________________
ARMedslack mailing list
ARMedslack <at> lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

Davide -- can you please reply properly to the threads?
I'm not sure what your mail client is doing here, but it's not prefixing
the Subject line with "Re:" for a start, so it looks as if you're starting
a new thread each time.

Can you check the settings on your mail client, or perhaps choose a
different reply method please.

On Fri, 22 Apr 2011, Davide wrote:

> If you considet that you can get a dockstar for 50 Euro in Italy or possibbly less it you look world wide ...
this little wimpy nas had better cost no more then 25 Euro or I'd just buy a dockstar instead. I know that it's
infuriating that the prices went up from 36 euro to 52 euro but for what you get it's still a nice price .... I
mean is the sheeva plug not 99 Euro (or USD I forget right now) ? whichever you can get a seagate GoFlexNET for
75 Euro.
> Wait I have it ... you want a gumstix and spend no less then 150 USD.
> Or is it that you want to play with an old sharp Zaurus (I've 3 of them do you want one ?) or some other hand-held
device and spend even more ?
> Or would you like a Toschiba with one of those dual core arm BASED CPU ? (the best price I saw around for that
was something like 225 Euro)
>
> Apart from all that is it really worth the effort fro such a wimpy piece of hardware ?
>
> Regards
> David
>
> --- Gio 21/4/11, Giovanni <pino.otto <at> gmail.com> ha scritto:
>
> Da: Giovanni <pino.otto <at> gmail.com>
> Oggetto: [ARMedslack] Slackware ARM on Small NAS (NS-K330)
> A: "Slackware ARM port" <armedslack <at> lists.armedslack.org>
> Data: Giovedì 21 Aprile 2011, 13:24
>
> Do you know whether it is possible to install and run Slackware ARM on this small computer?
>
> http://www.dealextreme.com/p/standalone-bittorrent-bt-client-usb-nas-ftp-samba-printer-upnp-sharing-network-lan-server-26320
>
>
> This is the hardware:
>
> CPU clock at 250MHz, CPU: FA526id(wb)(ARMv4)
> Memory: 32MB = 32MB total
> PCI clock at 33M
>
>
> and currently it supports SnakeOS:
>
> http://code.google.com/p/snake-os/
>
> Best regards,
> giovanni
>
>
>
> -----Segue allegato-----
>
> _______________________________________________
> ARMedslack mailing list
> ARMedslack <at> lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
>

--

-- 
Stuart Winter
Slackware ARM: www.armedslack.org
_______________________________________________
ARMedslack mailing list
ARMedslack <at> lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

I was told that reply made a mess by some other user.

I'll fix it manually just tell me what fields I should leave and where.
This is what my client would normaly do as a reply:
"Re: [ARMedslack] Slackware ARM on Small NAS (NS-K330)"

What's good in that and what's bad in that ?

Regards
David
--- Ven 22/4/11, Stuart Winter <m-lists <at> biscuit.org.uk> ha scritto:

> Da: Stuart Winter <m-lists <at> biscuit.org.uk>
> Oggetto: Re: [ARMedslack] Slackware ARM on Small NAS (NS-K330)
> A: "Slackware ARM port" <armedslack <at> lists.armedslack.org>
> Data: Venerdì 22 Aprile 2011, 10:14
> 
> Davide -- can you please reply properly to the threads?
> I'm not sure what your mail client is doing here, but it's
> not prefixing
> the Subject line with "Re:" for a start, so it looks as if
> you're starting
> a new thread each time.
> 
> Can you check the settings on your mail client, or perhaps
> choose a
> different reply method please.
> 
> On Fri, 22 Apr 2011, Davide wrote:
> 
> > If you considet that you can get a dockstar for 50
> Euro in Italy or possibbly less it you look world wide ...
> this little wimpy nas had better cost no more then 25 Euro
> or I'd just buy a dockstar instead. I know that it's
> infuriating that the prices went up from 36 euro to 52 euro
> but for what you get it's still a nice price .... I mean is
> the sheeva plug not 99 Euro (or USD I forget right now) ?
> whichever you can get a seagate GoFlexNET for 75 Euro.
> > Wait I have it ... you want a gumstix and spend no
> less then 150 USD.
> > Or is it that you want to play with an old sharp
> Zaurus (I've 3 of them do you want one ?) or some other
> hand-held device and spend even more ?
> > Or would you like a Toschiba with one of those dual
> core arm BASED CPU ? (the best price I saw around for that
> was something like 225 Euro)
> >
> > Apart from all that is it really worth the effort fro
> such a wimpy piece of hardware ?
> >
> > Regards
> > David
> >
> > --- Gio 21/4/11, Giovanni <pino.otto <at> gmail.com>
> ha scritto:
> >
> > Da: Giovanni <pino.otto <at> gmail.com>
> > Oggetto: [ARMedslack] Slackware ARM on Small NAS
> (NS-K330)
> > A: "Slackware ARM port" <armedslack <at> lists.armedslack.org>
> > Data: Giovedì 21 Aprile 2011, 13:24
> >
> > Do you know whether it is possible to install and run
> Slackware ARM on this small computer?
> >
> > http://www.dealextreme.com/p/standalone-bittorrent-bt-client-usb-nas-ftp-samba-printer-upnp-sharing-network-lan-server-26320
> >
> >
> > This is the hardware:
> >
> > CPU clock at 250MHz, CPU: FA526id(wb)(ARMv4)
> > Memory: 32MB = 32MB total
> > PCI clock at 33M
> >
> >
> > and currently it supports SnakeOS:
> >
> > http://code.google.com/p/snake-os/
> >
> > Best regards,
> > giovanni
> >
> >
> >
> > -----Segue allegato-----
> >
> > _______________________________________________
> > ARMedslack mailing list
> > ARMedslack <at> lists.armedslack.org
> > http://lists.armedslack.org/mailman/listinfo/armedslack
> >
> 
> -- 
> Stuart Winter
> Slackware ARM: www.armedslack.org
> -----Segue allegato-----
> 
> _______________________________________________
> ARMedslack mailing list
> ARMedslack <at> lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
> 
Am Fri, 22 Apr 2011 09:32:33 +0100 (BST)
schrieb Davide <louigi600 <at> yahoo.it>:

> 
> I was told that reply made a mess by some other user.

What I've meant was: Don't use the reply button for new threads
and change the subject only because this generates a mess in the thread
view 

> I'll fix it manually just tell me what fields I should leave and
> where. This is what my client would normaly do as a reply:
> "Re: [ARMedslack] Slackware ARM on Small NAS (NS-K330)"
> 
> What's good in that and what's bad in that ?

That's fine.

--

-- 
Thorsten Mühlfelder
Salix OS: www.salixos.org

Yep that works -- but normally your mail client should do it for you. You
can probably configure it to prefix any reply with "Re:".  It'll save wear
and tear on your fingers and keyboard! ;)

On Fri, 22 Apr 2011, Davide wrote:

>
> I was told that reply made a mess by some other user.
>
> I'll fix it manually just tell me what fields I should leave and where.
> This is what my client would normaly do as a reply:
> "Re: [ARMedslack] Slackware ARM on Small NAS (NS-K330)"
>
> What's good in that and what's bad in that ?
>
> Regards
> David
> --- Ven 22/4/11, Stuart Winter <m-lists <at> biscuit.org.uk> ha scritto:
>
> > Da: Stuart Winter <m-lists <at> biscuit.org.uk>
> > Oggetto: Re: [ARMedslack] Slackware ARM on Small NAS (NS-K330)
> > A: "Slackware ARM port" <armedslack <at> lists.armedslack.org>
> > Data: Venerdì 22 Aprile 2011, 10:14
> >
> > Davide -- can you please reply properly to the threads?
> > I'm not sure what your mail client is doing here, but it's
> > not prefixing
> > the Subject line with "Re:" for a start, so it looks as if
> > you're starting
> > a new thread each time.
> >
> > Can you check the settings on your mail client, or perhaps
> > choose a
> > different reply method please.
> >
> > On Fri, 22 Apr 2011, Davide wrote:
> >
> > > If you considet that you can get a dockstar for 50
> > Euro in Italy or possibbly less it you look world wide ...
> > this little wimpy nas had better cost no more then 25 Euro
> > or I'd just buy a dockstar instead. I know that it's
> > infuriating that the prices went up from 36 euro to 52 euro
> > but for what you get it's still a nice price .... I mean is
> > the sheeva plug not 99 Euro (or USD I forget right now) ?
> > whichever you can get a seagate GoFlexNET for 75 Euro.
> > > Wait I have it ... you want a gumstix and spend no
> > less then 150 USD.
> > > Or is it that you want to play with an old sharp
> > Zaurus (I've 3 of them do you want one ?) or some other
> > hand-held device and spend even more ?
> > > Or would you like a Toschiba with one of those dual
> > core arm BASED CPU ? (the best price I saw around for that
> > was something like 225 Euro)
> > >
> > > Apart from all that is it really worth the effort fro
> > such a wimpy piece of hardware ?
> > >
> > > Regards
> > > David
> > >
> > > --- Gio 21/4/11, Giovanni <pino.otto <at> gmail.com>
> > ha scritto:
> > >
> > > Da: Giovanni <pino.otto <at> gmail.com>
> > > Oggetto: [ARMedslack] Slackware ARM on Small NAS
> > (NS-K330)
> > > A: "Slackware ARM port" <armedslack <at> lists.armedslack.org>
> > > Data: Giovedì 21 Aprile 2011, 13:24
> > >
> > > Do you know whether it is possible to install and run
> > Slackware ARM on this small computer?
> > >
> > > http://www.dealextreme.com/p/standalone-bittorrent-bt-client-usb-nas-ftp-samba-printer-upnp-sharing-network-lan-server-26320
> > >
> > >
> > > This is the hardware:
> > >
> > > CPU clock at 250MHz, CPU: FA526id(wb)(ARMv4)
> > > Memory: 32MB = 32MB total
> > > PCI clock at 33M
> > >
> > >
> > > and currently it supports SnakeOS:
> > >
> > > http://code.google.com/p/snake-os/
> > >
> > > Best regards,
> > > giovanni
> > >
> > >
> > >
> > > -----Segue allegato-----
> > >
> > > _______________________________________________
> > > ARMedslack mailing list
> > > ARMedslack <at> lists.armedslack.org
> > > http://lists.armedslack.org/mailman/listinfo/armedslack
> > >
> >
> > --
> > Stuart Winter
> > Slackware ARM: www.armedslack.org
> > -----Segue allegato-----
> >
> > _______________________________________________
> > ARMedslack mailing list
> > ARMedslack <at> lists.armedslack.org
> > http://lists.armedslack.org/mailman/listinfo/armedslack
> >
> _______________________________________________
> ARMedslack mailing list
> ARMedslack <at> lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
>

--

-- 
Stuart Winter
Slackware ARM: www.armedslack.org
_______________________________________________
ARMedslack mailing list
ARMedslack <at> lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)

Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)

Re: Slackware ARM on Small NAS (NS-K330)