Re: [ARMedslack] Slackware ARM on Small NAS (NS-K330)
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.o...@gmail.com ha scritto: Da: Giovanni pino.o...@gmail.com Oggetto: [ARMedslack] Slackware ARM on Small NAS (NS-K330) A: Slackware ARM port armedslack@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@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -- Stuart Winter Slackware ARM: www.armedslack.org___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Slackware ARM on Small NAS (NS-K330)
Am Fri, 22 Apr 2011 09:32:33 +0100 (BST) schrieb Davide louigi...@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 ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Slackware ARM on Small NAS (NS-K330)
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-li...@biscuit.org.uk ha scritto: Da: Stuart Winter m-li...@biscuit.org.uk Oggetto: Re: [ARMedslack] Slackware ARM on Small NAS (NS-K330) A: Slackware ARM port armedslack@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.o...@gmail.com ha scritto: Da: Giovanni pino.o...@gmail.com Oggetto: [ARMedslack] Slackware ARM on Small NAS (NS-K330) A: Slackware ARM port armedslack@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@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -- Stuart Winter Slackware ARM: www.armedslack.org -Segue allegato- ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -- Stuart Winter Slackware ARM: www.armedslack.org___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] micro root rescue system
Sorry for starting a new thread on something that was started elsewhere but maybe the shoot-off needs better attention with a new thread. This is a mix of a few I built myself and some gotten from current. This is what I'll be working with and should fit in a compressed jffs2 image 64Mb big. root@slackware:/usr/src/surap_packages# du -ms * | sort -n 1 busybox-1.18.4-arm-1.tgz 1 dropbear-0.53.1-arm-1.tgz 1 hostapd-0.7.3-arm-1.tgz 1 iptables-1.4.10-arm-1.tgz 1 iw-0.9.20-arm-1.tgz 1 ppp-2.4.5-arm-1.tgz 1 udev-165-arm-2.tgz 1 usb_modeswitch-1.1.6-arm-1.tgz 1 wireless-tools-29-arm-2.tgz 2 httpd-2.2.17-arm-2.tgz 2 kernel-firmware-2.6.38.3-noarch-1.tgz 5 glibc-solibs-2.13-arm-1.tgz 8 kernel_kirkwood-2.6.38.3-arm-1.tgz 10 php-5.3.5-arm-1.tgz 15 kernel-modules-kirkwood-2.6.38.3_kirkwood-arm-1.tgz root@slackware:/usr/src/surap_packages# du -ms . 43 . root@slackware:/usr/src/surap_packages# Since booting from jffs2 image does not require initrd ... and maybe one can do without documentation I'll see if I can fit that in a 32Mb image. Build a custom kernel with few modules ;) I will strip all unnecessary modules for a rescue system, remove initrd, strip documentation and carve down as much as possible ... if it won't fit I'll consider thttpd and some lighter web scripting language. Maybe web stuff is not really necessary for a rescue system anyway. Now I've a question. there are 2 ways to do this: 1) repackage the single packages and append some suffix to distinguish them from the standard packages, possibly modify the build scripts for them so that future maintenance will be easier, 2) just shove everything needed somewhere and remove all that is not needed and then build the jffs2 image. Now if this micro root system is just going to be my personal AP/3g/NAS/router/rescue the second way will take much less effort, on the other hand if you like the idea of having an armedslack micro root system that will be more then just a rescue system and possibly fit in a 32Mb compressed image; well then we should go about the first way. I say we because I'm just a user and even if I do most of the dirty work I'll need assistance from the ARMedslack team to do some of the required actions if this is of any interest to ARMedslack community. I've no reservation in sharing my work as I consider all my work GPL + it's mainly just administration so the question really is: Does armedslack want a smart micro root system ? Best regards David Rao ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
[ARMedslack] kernel setup linux-2.6.38.3
While going about recompiling kernel for micro root I noticed a few things that one can do without at least for kirkwood: Fusion MPT device support (this is a hardware RAID SCSI controller ... I doubt anyone will ever have one connected to an ARM based embedde system even if a working pcie slot. ) IEEE 1394 (FireWire) support (The kirkwood SOC does not have firewire in it so unless you have a usb2firewire adapter, which would not make much sense anyway, or a pci* slot where to place one in you wont need this. Those who have a kirkwood based system with working pcie slot and a pcie firewire card can recompile kernel ;-) ) Regards David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
