From mozes at slackware.com Thu Nov 7 22:22:18 2013 From: mozes at slackware.com (Stuart Winter) Date: Thu, 7 Nov 2013 14:22:18 -0800 (PST) Subject: [ARMedslack] Slackware 14.1 is released Message-ID: Hi! Slackware x86, x86_64 and ARM v14.1 is released today. Thanks to everyone here who has helped with testing, feedback and improvements. The next thing I plan on looking at is the Chromebook suport. Happy release day and have a good weekend upgrading. Stuart -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: http://arm.slackware.com From openpandora at free.fr Sat Nov 16 17:31:29 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Sat, 16 Nov 2013 18:31:29 +0100 (CET) Subject: [ARMedslack] Creating a rootfs from a x86 host: unknown machine 40 In-Reply-To: <1627388158.9363373.1384622716699.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: <729018631.9369354.1384623089982.JavaMail.root@zimbra53-e8.priv.proxad.net> Hi ! After my upgrade from x86_64 14.0 to 14.1, my pandora rootfs doesn't work anymore. Can't find init. My creation logs show this: Executing install script for glibc-solibs-2.17-arm-14.tgz. install/doinst.sh: line 38: sbin/ldconfig: cannot execute binary file /sbin/ldconfig: ld-2.17.so is for unknown machine 40. /sbin/ldconfig: No link created since soname could not be found for ld-2.17.so /sbin/ldconfig: libBrokenLocale-2.17.so is for unknown machine 40. /sbin/ldconfig: No link created since soname could not be found for libBrokenLocale-2.17.so /sbin/ldconfig: libanl-2.17.so is for unknown machine 40. ...And a lot more According to this guy: http://buildroot-busybox.2317881.n4.nabble.com/ldconfig-unknown-machine-40-td47588.html "'These are _not_ just warnings; ldconfig ignores the library content, so "output/target/etc/ld.so.cache" is left unpopulated, meaning that the target device will not boot successfully due to missing libraries (the libraries are on the file-system, just the ld.so.cache does not list them).'" I would like to ask for your knowledge about this. From openpandora at free.fr Sat Nov 16 17:39:27 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Sat, 16 Nov 2013 18:39:27 +0100 (CET) Subject: [ARMedslack] Slackware 14.1 is released In-Reply-To: Message-ID: <981361051.9379439.1384623567716.JavaMail.root@zimbra53-e8.priv.proxad.net> Great :D Thanks for the hard work, i feel at home with Slackware on any device ^^. LS ----- Mail original ----- De: "Stuart Winter" ?: "Slackware ARM mailing list" Envoy?: Jeudi 7 Novembre 2013 23:22:18 Objet: [ARMedslack] Slackware 14.1 is released Hi! Slackware x86, x86_64 and ARM v14.1 is released today. Thanks to everyone here who has helped with testing, feedback and improvements. The next thing I plan on looking at is the Chromebook suport. Happy release day and have a good weekend upgrading. Stuart -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: http://arm.slackware.com _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From m-lists at biscuit.org.uk Sat Nov 16 23:00:26 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 16 Nov 2013 23:00:26 +0000 (GMT) Subject: [ARMedslack] Creating a rootfs from a x86 host: unknown machine 40 In-Reply-To: <729018631.9369354.1384623089982.JavaMail.root@zimbra53-e8.priv.proxad.net> References: <729018631.9369354.1384623089982.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: > "'These are _not_ just warnings; ldconfig ignores the library content, so > "output/target/etc/ld.so.cache" is left unpopulated, meaning that the > target device will not boot successfully due to missing libraries (the > libraries are on the file-system, just the ld.so.cache does not list them).'" He's right - it's broken. There's a patch that's in Gentoo and Red Hat, but it doesn't fix this problem. There's also this one which I haven't tried: http://patchwork.ozlabs.org/patch/255486/ You're going to have to either try the patch in the last URL and rebuild glibc with it, or take the ldconfig from Slackware 14.0 -- works for me: cd slackware64-14.0/slackware64/l mkdir Q ; cd Q tar xf ../glibc-2.15-x86_64-7.txz cp sbin/ldconfig /sbin/ldconfig-2.15 Go into a dir of ARM shared objects: prisere [p3] # readelf lib/ld-2.17.so -h|grep Machin Machine: ARM prisere [p3] # uname -m x86_64 prisere [p3] # /sbin/ldconfig-2.15 -r . prisere [p3] # strings etc/ld.so.cache |head -n5 ld.so-1.7.0 glibc-ld.so.cache1.1G libz.so.1 /lib/libz.so.1 libuuid.so.1 prisere [p3] # From openpandora at free.fr Sun Nov 17 02:04:15 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Sun, 17 Nov 2013 03:04:15 +0100 (CET) Subject: [ARMedslack] Creating a rootfs from a x86 host: unknown machine 40 In-Reply-To: Message-ID: <718652181.9651824.1384653855819.JavaMail.root@zimbra53-e8.priv.proxad.net> Thanks ! I appreciate. ----- Mail original ----- De: "Stuart Winter" ?: "Slackware ARM port" Envoy?: Dimanche 17 Novembre 2013 00:00:26 Objet: Re: [ARMedslack] Creating a rootfs from a x86 host: unknown machine 40 > "'These are _not_ just warnings; ldconfig ignores the library content, so > "output/target/etc/ld.so.cache" is left unpopulated, meaning that the > target device will not boot successfully due to missing libraries (the > libraries are on the file-system, just the ld.so.cache does not list them).'" He's right - it's broken. There's a patch that's in Gentoo and Red Hat, but it doesn't fix this problem. There's also this one which I haven't tried: http://patchwork.ozlabs.org/patch/255486/ You're going to have to either try the patch in the last URL and rebuild glibc with it, or take the ldconfig from Slackware 14.0 -- works for me: cd slackware64-14.0/slackware64/l mkdir Q ; cd Q tar xf ../glibc-2.15-x86_64-7.txz cp sbin/ldconfig /sbin/ldconfig-2.15 Go into a dir of ARM shared objects: prisere [p3] # readelf lib/ld-2.17.so -h|grep Machin Machine: ARM prisere [p3] # uname -m x86_64 prisere [p3] # /sbin/ldconfig-2.15 -r . prisere [p3] # strings etc/ld.so.cache |head -n5 ld.so-1.7.0 glibc-ld.so.cache1.1G libz.so.1 /lib/libz.so.1 libuuid.so.1 prisere [p3] # _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From m-lists at biscuit.org.uk Sun Nov 17 15:59:10 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 17 Nov 2013 15:59:10 +0000 (GMT) Subject: [ARMedslack] Linux 3.12.0 on Kirkwood? Message-ID: Hi I built it but it fails. I'm not sure whether it has something to do with flattened device tree - which the u-Boot on my OpenRD client does not nor probably never will have. Has anybody got Linux 3.12.0 working on their Sheevaplug? Uncompressing Linux... done, booting the kernel. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.12.0-kirkwood (root at pepa) (gcc version 4.8.2 (GCC) ) #2 Sun Nov 17 11:01:31 GMT 2013 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] Machine: Marvell OpenRD Client Board [ 0.000000] bootconsole [earlycon0] enabled [ 0.000000] Memory policy: ECC disabled, Data cache writeback [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 [ 0.000000] Kernel command line: earlyprintk console=ttyS0,115200 nic=auto:eth0:dhcp kbd=uk root=/dev/ram rw [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] Memory: 496800K/524288K available (3328K kernel code, 239K rwdata, 1132K rodata, 179K init, 512K bss, 27488K reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) [ 0.000000] vmalloc : 0xe0800000 - 0xff000000 ( 488 MB) [ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) [ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB) [ 0.000000] .text : 0xc0008000 - 0xc04635ec (4462 kB) [ 0.000000] .init : 0xc0464000 - 0xc0490f3c ( 180 kB) [ 0.000000] .data : 0xc0492000 - 0xc04cdd30 ( 240 kB) [ 0.000000] .bss : 0xc04cdd30 - 0xc054e04c ( 513 kB) [ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [ 0.000000] NR_IRQS:114 [ 0.000000] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms [ 0.000000] Console: colour dummy device 80x30 [ 6.455145] Calibrating delay loop... [ 6.460464] Unable to handle kernel NULL pointer dereference at virtual address 00000000 [ 6.468858] pgd = c0004000 [ 6.471630] [00000000] *pgd=00000000 [ 6.475284] Internal error: Oops: 80000005 [#1] ARM [ 6.480219] Modules linked in: [ 6.483352] CPU: 0 PID: 0 Comm: swapper Not tainted 3.12.0-kirkwood #2 [ 6.489934] task: c049d260 ti: c0492000 task.ti: c0492000 [ 6.495393] PC is at 0x0 [ 6.498001] LR is at __irq_svc+0x40/0x4c [ 6.501987] pc : [<00000000>] lr : [] psr: 200000d3 [ 6.501987] sp : c0493f18 ip : 000008f8 fp : 00000000 [ 6.513578] r10: 0048ad70 r9 : 56251311 r8 : 00000000 [ 6.518859] r7 : c0493f4c r6 : ffffffff r5 : 60000053 r4 : c0008f70 [ 6.525434] r3 : c0008f64 r2 : c0493f60 r1 : c049e090 r0 : c0493f18 [ 6.532009] Flags: nzCv IRQs off FIQs off Mode SVC_32 ISA ARM Segment kernel [ 6.539543] Control: 0005397f Table: 00004000 DAC: 00000017 [ 6.545340] Process swapper (pid: 0, stack limit = 0xc04921c0) [ 6.551224] Stack: (0xc0493f18 to 0xc0494000) [ 6.555640] 3f00: 0000001a 00000000 [ 6.563862] 3f20: ffff8ad0 ffff8ad0 c049ac70 00000000 c04cdd94 c04a3998 00000000 56251311 [ 6.572087] 3f40: 0048ad70 00000000 000008f8 c0493f60 c0008f64 c0008f70 60000053 ffffffff [ 6.580312] 3f60: 00000004 60000053 c095a100 00000024 00000004 c00a15e4 c049eab8 c04d0960 [ 6.588537] 3f80: 00000060 000003d8 c04b8f8c c04ca3b0 00000000 c09523d8 c09523d8 00000001 [ 6.596763] 3fa0: c05429e0 c049ac70 00000000 c048c050 c09500c0 00004000 56251311 0048ad70 [ 6.604988] 3fc0: 00000000 c04649ac ffffffff ffffffff c04644e4 00000000 00000000 c048c050 [ 6.613213] 3fe0: 00000000 00053975 c049a044 c048c04c c049e088 00008040 00000000 00000000 [ 6.621452] [] (__irq_svc+0x40/0x4c) from [] (calibrate_delay+0x31c/0x4ac) [ 6.630119] [] (calibrate_delay+0x31c/0x4ac) from [] (start_kernel+0x2a8/0x358) [ 6.639212] [] (start_kernel+0x2a8/0x358) from [<00008040>] (0x8040) [ 6.646482] Code: bad PC value [ 6.649636] ---[ end trace da227214a82491b7 ]--- [ 6.654319] Kernel panic - not syncing: Attempted to kill the idle task! [ 6.661077] Unable to handle kernel NULL pointer dereference at virtual address 00000000 [ 6.669210] pgd = c0004000 [ 6.671984] [00000000] *pgd=00000000 [ 6.675636] Internal error: Oops: 80000005 [#2] ARM [ 6.680571] Modules linked in: [ 6.683705] CPU: 0 PID: 0 Comm: swapper Tainted: G D 3.12.0-kirkwood #2 [ 6.691237] task: c049d260 ti: c0492000 task.ti: c0492000 [ 6.696695] PC is at 0x0 [ 6.699301] LR is at __irq_svc+0x40/0x4c [ 6.703290] pc : [<00000000>] lr : [] psr: 200000d3 [ 6.703290] sp : c0493c48 ip : 000008f8 fp : c0493d27 [ 6.714882] r10: 00000000 r9 : c04b2490 r8 : c0492008 [ 6.720162] r7 : c0493c7c r6 : ffffffff r5 : 60000053 r4 : c031c55c [ 6.726737] r3 : c0041574 r2 : c0493c90 r1 : c049e090 r0 : c0493c48 [ 6.733312] Flags: nzCv IRQs off FIQs off Mode SVC_32 ISA ARM Segment kernel [ 6.740837] Control: 0005397f Table: 00004000 DAC: 00000017 [ 6.746634] Process swapper (pid: 0, stack limit = 0xc04921c0) [ 6.752518] Stack: (0xc0493c48 to 0xc0494000) [ 6.756938] 3c40: 0000003a 00000000 0000003a 60000053 00000000 0000000b [ 6.765165] 3c60: c04ce408 00000000 c0492008 c04b2490 00000000 c0493d27 000008f8 c0493c90 [ 6.773390] 3c80: c0041574 c031c55c 60000053 ffffffff c03dd581 c0493cbc c049d260 0000000b [ 6.781615] 3ca0: c0493d27 c04cdec4 c0492008 00000000 00000000 c0017130 c03dd581 00000000 [ 6.789840] 3cc0: 00000000 c0492000 00000000 00000000 c0493d27 c031c9bc c03dd4ee c0493cf4 [ 6.798066] 3ce0: a82491b7 0000000b fffffff8 c0493d27 c04cdec4 00000017 00000000 00000000 [ 6.806291] 3d00: c0493d27 c000c1f8 c04921c0 0000000b c04d1246 0000000e 00000008 600000d3 [ 6.814516] 3d20: 00000000 62000000 50206461 61762043 0065756c 00000000 c0493ed0 00000000 [ 6.822742] 3d40: 80000005 00000000 c0493ed0 00000000 00000000 80000005 00000000 271ae11c [ 6.830967] 3d60: c0408957 00000000 80000005 00000000 c0493ed0 00000000 00000000 80000005 [ 6.839193] 3d80: 00000000 c031c330 c049d260 c03231d8 600000d3 c04ca400 c04d0e1f 00000001 [ 6.847417] 3da0: 00000006 c019f638 00000000 c04ca3b0 0006f1e9 00000000 00000000 00000000 [ 6.855643] 3dc0: 00000000 00000000 c0542a5c c04acb00 34350003 34353531 00000001 c04ca448 [ 6.863869] 3de0: 00000041 c04ca3b0 400000d3 00030004 c0542a5c 00000000 c04ca3b0 c0493ed0 [ 6.872093] 3e00: 80000005 00000000 c0493ed0 00000000 56251311 0048ad70 00000000 c0323264 [ 6.880319] 3e20: 00000005 c049edd4 00000000 c000843c 271ae11c c04d0e25 c0493ea0 c019ff40 [ 6.888543] 3e40: 00000001 0000000a 00000006 ffffffff 00000000 00000002 6c0a0100 ffff0006 [ 6.896769] 3e60: 00004000 c04d1246 00000001 c04d0930 600000d3 c04a5a3c 00000000 c04d0930 [ 6.904995] 3e80: c000f2c4 c049eab8 00000029 c0040a50 c04d1246 00000029 0000001a c0041574 [ 6.913220] 3ea0: 271ae11c c04d0e25 c004ef84 c04d0930 0000001a 00000000 c04d1246 00000000 [ 6.921446] 3ec0: 200000d3 ffffffff c0493f04 c0321b98 c0493f18 c049e090 c0493f60 c0008f64 [ 6.929670] 3ee0: c0008f70 60000053 ffffffff c0493f4c 00000000 56251311 0048ad70 00000000 [ 6.937895] 3f00: 000008f8 c0493f18 c0321ae0 00000000 200000d3 ffffffff 0000001a 00000000 [ 6.946121] 3f20: ffff8ad0 ffff8ad0 c049ac70 00000000 c04cdd94 c04a3998 00000000 56251311 [ 6.954346] 3f40: 0048ad70 00000000 000008f8 c0493f60 c0008f64 c0008f70 60000053 ffffffff [ 6.962572] 3f60: 00000004 60000053 c095a100 00000024 00000004 c00a15e4 c049eab8 c04d0960 [ 6.970797] 3f80: 00000060 000003d8 c04b8f8c c04ca3b0 00000000 c09523d8 c09523d8 00000001 [ 6.979022] 3fa0: c05429e0 c049ac70 00000000 c048c050 c09500c0 00004000 56251311 0048ad70 [ 6.987247] 3fc0: 00000000 c04649ac ffffffff ffffffff c04644e4 00000000 00000000 c048c050 [ 6.995472] 3fe0: 00000000 00053975 c049a044 c048c04c c049e088 00008040 00000000 00000000 [ 7.003707] [] (__irq_svc+0x40/0x4c) from [] (panic+0x154/0x1bc) [ 7.011509] [] (panic+0x154/0x1bc) from [] (do_exit+0x80/0x844) [ 7.019222] [] (do_exit+0x80/0x844) from [] (die+0x290/0x368) [ 7.026761] [] (die+0x290/0x368) from [] (__do_kernel_fault.part.10+0x54/0x74) [ 7.035768] [] (__do_kernel_fault.part.10+0x54/0x74) from [] (do_page_fault.part.11+0x2f8/0x358) [ 7.046333] [] (do_page_fault.part.11+0x2f8/0x358) from [] (do_page_fault+0x2c/0x68) [ 7.055860] [] (do_page_fault+0x2c/0x68) from [] (do_PrefetchAbort+0x34/0x98) [ 7.064776] [] (do_PrefetchAbort+0x34/0x98) from [] (__pabt_svc+0x38/0x80) [ 7.073425] Exception stack(0xc0493ed0 to 0xc0493f18) [ 7.078535] 3ec0: c0493f18 c049e090 c0493f60 c0008f64 and goes on for quite some time before finishing up crashing. -- Stuart Winter Slackware ARM: http://arm.slackware.com From m-lists at biscuit.org.uk Sun Nov 17 22:19:14 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 17 Nov 2013 22:19:14 +0000 (GMT) Subject: [ARMedslack] Linux 3.12.0 on Kirkwood? In-Reply-To: References: Message-ID: On Sun, 17 Nov 2013, Stuart Winter wrote: > > I built it but it fails. I'm not sure whether it has something to do with > flattened device tree - which the u-Boot on my OpenRD client does not nor > probably never will have. Yes it was flattened device tree. Remove that and it's fine. From louigi600 at yahoo.it Mon Nov 18 08:49:19 2013 From: louigi600 at yahoo.it (Davide) Date: Mon, 18 Nov 2013 08:49:19 +0000 (GMT) Subject: [ARMedslack] Linux 3.12.0 on Kirkwood? In-Reply-To: References: Message-ID: <1384764559.64522.YahooMailNeo@web173102.mail.ir2.yahoo.com> Things start going wrong right after the "calibrating delay loop": [? ? 6.455145] Calibrating delay loop... [? ? 6.460464] Unable to handle kernel NULL pointer dereference at virtual address 00000000 I think that's the root cause ...? I'm not sure on this but I suppose the kernel aint looking at the device tree yet so it may not be something to do with the flattened device tree. going on further down you can see the panic: [? ? 6.646482] Code: bad PC value [? ? 6.649636] ---[ end trace da227214a82491b7 ]--- [? ? 6.654319] Kernel panic - not syncing: Attempted to kill the idle task! I don't have 3.12 on any of my devices so I can't help you any more then this :( Good luck David Il Domenica 17 Novembre 2013 23:19, Stuart Winter ha scritto: On Sun, 17 Nov 2013, Stuart Winter wrote: > > I built it but it fails.? I'm not sure whether it has something to do with > flattened device tree - which the u-Boot on my OpenRD client does not nor > probably never will have. Yes it was flattened device tree.? Remove that and it's fine. _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Mon Nov 18 08:54:04 2013 From: louigi600 at yahoo.it (Davide) Date: Mon, 18 Nov 2013 08:54:04 +0000 (GMT) Subject: [ARMedslack] Creating a rootfs from a x86 host: unknown machine 40 In-Reply-To: <718652181.9651824.1384653855819.JavaMail.root@zimbra53-e8.priv.proxad.net> References: <718652181.9651824.1384653855819.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: <1384764844.38068.YahooMailNeo@web173103.mail.ir2.yahoo.com> Does your 64 bit system have multybit capabilites ? (ie can you run 32 bit stuff along with the 64 bit stuff ?) If you did that the update may have broken some of the 32 bit stuff and it could lead you to a similar error. ATB David Il Domenica 17 Novembre 2013 3:04, "openpandora at free.fr" ha scritto: Thanks ! I appreciate. ----- Mail original ----- De: "Stuart Winter" ?: "Slackware ARM port" Envoy?: Dimanche 17 Novembre 2013 00:00:26 Objet: Re: [ARMedslack] Creating a rootfs from a x86 host: unknown machine 40 > "'These are _not_ just warnings; ldconfig ignores the library content, so > "output/target/etc/ld.so.cache" is left unpopulated, meaning that the > target device will not boot successfully due to missing libraries (the > libraries are on the file-system, just the ld.so.cache does not list them).'" He's right - it's broken.? There's a patch that's in Gentoo and Red Hat, but it doesn't fix this problem. There's also this one which I haven't tried: http://patchwork.ozlabs.org/patch/255486/ You're going to have to either try the patch in the last URL and rebuild glibc with it, or take the ldconfig from Slackware 14.0 -- works for me: cd slackware64-14.0/slackware64/l mkdir Q ; cd Q tar xf ../glibc-2.15-x86_64-7.txz cp sbin/ldconfig /sbin/ldconfig-2.15 Go into a dir of ARM shared objects: prisere [p3] # readelf lib/ld-2.17.so -h|grep Machin ? Machine:? ? ? ? ? ? ? ? ? ? ? ? ? ARM prisere [p3] # uname -m x86_64 prisere [p3] # /sbin/ldconfig-2.15 -r . prisere [p3] # strings etc/ld.so.cache |head -n5 ld.so-1.7.0 glibc-ld.so.cache1.1G libz.so.1 /lib/libz.so.1 libuuid.so.1 prisere [p3] # _______________________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Mon Nov 18 09:55:17 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 18 Nov 2013 09:55:17 +0000 (GMT) Subject: [ARMedslack] Linux 3.12.0 on Kirkwood? In-Reply-To: <1384764559.64522.YahooMailNeo@web173102.mail.ir2.yahoo.com> References: <1384764559.64522.YahooMailNeo@web173102.mail.ir2.yahoo.com> Message-ID: > Things start going wrong right after the "calibrating delay loop": > [? ? 6.455145] Calibrating delay loop... > [? ? 6.460464] Unable to handle kernel NULL pointer dereference at virtual > address 00000000 > > I think that's the root cause ...? > I'm not sure on this but I suppose the kernel aint looking at the device tree yet so it may not be something to do with the flattened device tree. The issue seems to be that they've migrated all of the Sheevaplug support in to Flattened Device Tree - which is fine because there's a newer u-Boot available that supports it. However, if I use a kernel with FTD support compiled in, it crashes on the OpenRD client. I'm seeing if there's any combination of options that will make it work on both before mailing the kernel list. I suspect nobody has tested it since 3.12 is new. I'm also thinking about how best to proceed with ARMv7 since to support a multitude of devices using the current method, we'd end up with massive initrd's and installers (Although the installer is probably less of a concern or interest if you can't boot it anyway ;-) ). Debian have 'flash-kernel' which determines the type of device and (I assume, from the name) flashes the kernel to NAND if possible, and creates an appropriate initrd for that device. The other option is if Eric has time to complete and work on his port, apart from the Trimslice I'll leave the ARMv7 support alone and let Slackware ARM focus on the soft float devices. Hmm. Time will tell. From m-lists at biscuit.org.uk Mon Nov 18 10:17:58 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 18 Nov 2013 10:17:58 +0000 (GMT) Subject: [ARMedslack] Creating a rootfs from a x86 host: unknown machine 40 In-Reply-To: <1384764844.38068.YahooMailNeo@web173103.mail.ir2.yahoo.com> References: <718652181.9651824.1384653855819.JavaMail.root@zimbra53-e8.priv.proxad.net> <1384764844.38068.YahooMailNeo@web173103.mail.ir2.yahoo.com> Message-ID: No - it's pure 64bit. On Mon, 18 Nov 2013, Davide wrote: > Does your 64 bit system have multybit capabilites ? (ie can you run 32 bit stuff along with the 64 bit stuff ?) > If you did that the update may have broken some of the 32 bit stuff and it could lead you to a similar error. > > ATB > David > > > > > Il Domenica 17 Novembre 2013 3:04, "openpandora at free.fr" ha scritto: > > Thanks ! > I appreciate. > > ----- Mail original ----- > De: "Stuart Winter" > ?: "Slackware ARM port" > Envoy?: Dimanche 17 Novembre 2013 00:00:26 > Objet: Re: [ARMedslack] Creating a rootfs from a x86 host: unknown machine 40 > > > > "'These are _not_ just warnings; ldconfig ignores the library content, so > > "output/target/etc/ld.so.cache" is left unpopulated, meaning that the > > target device will not boot successfully due to missing libraries (the > > libraries are on the file-system, just the ld.so.cache does not list them).'" > > He's right - it's broken.? There's a patch that's in Gentoo and Red Hat, > but it doesn't fix this problem. > > There's also this one which I haven't tried: > http://patchwork.ozlabs.org/patch/255486/ > > You're going to have to either try the patch in the last URL and rebuild > glibc with it, or take the ldconfig from Slackware 14.0 -- works for me: > > cd slackware64-14.0/slackware64/l > mkdir Q ; cd Q > tar xf ../glibc-2.15-x86_64-7.txz > cp sbin/ldconfig /sbin/ldconfig-2.15 > > Go into a dir of ARM shared objects: > > prisere [p3] # readelf lib/ld-2.17.so -h|grep Machin > ? Machine:? ? ? ? ? ? ? ? ? ? ? ? ? ARM > prisere [p3] # uname -m > x86_64 > prisere [p3] # /sbin/ldconfig-2.15 -r . > prisere [p3] # strings etc/ld.so.cache |head -n5 > ld.so-1.7.0 > glibc-ld.so.cache1.1G > libz.so.1 > /lib/libz.so.1 > libuuid.so.1 > prisere [p3] # > > _______________________________________________ > 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: http://arm.slackware.com From openpandora at free.fr Mon Nov 18 16:03:48 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Mon, 18 Nov 2013 17:03:48 +0100 (CET) Subject: [ARMedslack] Creating a rootfs from a x86 host: unknown machine 40 In-Reply-To: Message-ID: <1788642935.12350338.1384790628805.JavaMail.root@zimbra53-e8.priv.proxad.net> 64 here too. I also went multilib, same problem. As recommended, going to 14.0 ldconfig works like a charm. ----- Mail original ----- De: "Stuart Winter" ?: "Slackware ARM port" Envoy?: Lundi 18 Novembre 2013 11:17:58 Objet: Re: [ARMedslack] Creating a rootfs from a x86 host: unknown machine 40 No - it's pure 64bit. On Mon, 18 Nov 2013, Davide wrote: > Does your 64 bit system have multybit capabilites ? (ie can you run 32 bit stuff along with the 64 bit stuff ?) > If you did that the update may have broken some of the 32 bit stuff and it could lead you to a similar error. > > ATB > David > > > > > Il Domenica 17 Novembre 2013 3:04, "openpandora at free.fr" ha scritto: > > Thanks ! > I appreciate. > > ----- Mail original ----- > De: "Stuart Winter" > ?: "Slackware ARM port" > Envoy?: Dimanche 17 Novembre 2013 00:00:26 > Objet: Re: [ARMedslack] Creating a rootfs from a x86 host: unknown machine 40 > > > > "'These are _not_ just warnings; ldconfig ignores the library content, so > > "output/target/etc/ld.so.cache" is left unpopulated, meaning that the > > target device will not boot successfully due to missing libraries (the > > libraries are on the file-system, just the ld.so.cache does not list them).'" > > He's right - it's broken.? There's a patch that's in Gentoo and Red Hat, > but it doesn't fix this problem. > > There's also this one which I haven't tried: > http://patchwork.ozlabs.org/patch/255486/ > > You're going to have to either try the patch in the last URL and rebuild > glibc with it, or take the ldconfig from Slackware 14.0 -- works for me: > > cd slackware64-14.0/slackware64/l > mkdir Q ; cd Q > tar xf ../glibc-2.15-x86_64-7.txz > cp sbin/ldconfig /sbin/ldconfig-2.15 > > Go into a dir of ARM shared objects: > > prisere [p3] # readelf lib/ld-2.17.so -h|grep Machin > ? Machine:? ? ? ? ? ? ? ? ? ? ? ? ? ARM > prisere [p3] # uname -m > x86_64 > prisere [p3] # /sbin/ldconfig-2.15 -r . > prisere [p3] # strings etc/ld.so.cache |head -n5 > ld.so-1.7.0 > glibc-ld.so.cache1.1G > libz.so.1 > /lib/libz.so.1 > libuuid.so.1 > prisere [p3] # > > _______________________________________________ > 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: http://arm.slackware.com _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From m-lists at biscuit.org.uk Thu Nov 21 15:32:44 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 21 Nov 2013 15:32:44 +0000 (GMT) Subject: [ARMedslack] Slackware ARM 14.1 community supported devices - update installation guides and availability Message-ID: Hello If you provide 'community support' for a device and have updated it for 14.1, please update the table here: http://docs.slackware.com/howtos:hardware:arm:start ( you will need an account on docs.slackware.com to update this table - if you don't have one, join - docs.slackware.com will/should contain the ARM documentation, or at least be a portal/jump point to 3rd party hosted content if you don't fancy keeping your docs on the wiki). Thanks s. -- Stuart Winter Slackware ARM: http://arm.slackware.com From m-lists at biscuit.org.uk Thu Nov 21 15:35:31 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 21 Nov 2013 15:35:31 +0000 (GMT) Subject: [ARMedslack] Thinking of decomissioning this mailing list in favour of a sub forum on LinuxQuestions.org Message-ID: Hello As the subject says - I am thinking of asking for a sub forum on LQ and using that for ARM related stuff. LQ is the official Slackware questions forum for x86, so it makes sense from that perspective. In addition it also raises the profile of the ARM port - since the communication won't be squirreled away in an archive mbox. I am personally not a fan of web forums as I don't like having to click everywhere - it's easier to use PINE and the keyboard controls; however the two points above really should outweigh my personal preferences ;-) Any thoughts? -- Stuart Winter Slackware ARM: http://arm.slackware.com From gregg.drwho8 at gmail.com Thu Nov 21 15:45:41 2013 From: gregg.drwho8 at gmail.com (Gregg Levine) Date: Thu, 21 Nov 2013 10:45:41 -0500 Subject: [ARMedslack] Thinking of decomissioning this mailing list in favour of a sub forum on LinuxQuestions.org In-Reply-To: References: Message-ID: Hello! I don't like them either. So far each of my three devices, the Raspberry Pi, two Netduinos, and several Arduinos all use them. And unless the message contains tags that are set appropriately, the boards do not remind me when I have a response waiting. Isn't this list searchable via Google? That is the search engine is aware of the archival site for the list? ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again." On Thu, Nov 21, 2013 at 10:35 AM, Stuart Winter wrote: > > Hello > > As the subject says - I am thinking of asking for a sub forum on LQ and > using that for ARM related stuff. LQ is the official Slackware questions > forum for x86, so it makes sense from that perspective. In addition it > also raises the profile of the ARM port - since the communication won't be > squirreled away in an archive mbox. > > I am personally not a fan of web forums as I don't like having to click > everywhere - it's easier to use PINE and the keyboard controls; however > the two points above really should outweigh my personal preferences ;-) > > Any thoughts? > > -- > Stuart Winter > Slackware ARM: http://arm.slackware.com > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack From m-lists at biscuit.org.uk Thu Nov 21 15:53:20 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 21 Nov 2013 15:53:20 +0000 (GMT) Subject: [ARMedslack] Thinking of decomissioning this mailing list in favour of a sub forum on LinuxQuestions.org In-Reply-To: References: Message-ID: The LQ forum has the tick box option at the bottom (which is on by default, IIRC) so that you receive email responses when the thread is updated. The mailing list is searchable by google, yes and some list aggregators also have subscribed to the list, so you can view the list within a UI. The other good point of the forum is that the user can join (if they are a Slackware user, the chances are that they'll already have an account) and reply to a thread that was previously created, where as with the mailing list this isn't the case unless they go to a lot of effort to import an mbox into their MUA of choice. I've almost convinced myself about this, apart from I am now reminded of how annoing it is to trim forum posts and include textual/code/console output within forum tags. hmm. On Thu, 21 Nov 2013, Gregg Levine wrote: > Hello! > I don't like them either. So far each of my three devices, the > Raspberry Pi, two Netduinos, and several Arduinos all use them. And > unless the message contains tags that are set appropriately, the > boards do not remind me when I have a response waiting. > > Isn't this list searchable via Google? That is the search engine is > aware of the archival site for the list? > ----- > Gregg C Levine gregg.drwho8 at gmail.com > "This signature fought the Time Wars, time and again." > > > On Thu, Nov 21, 2013 at 10:35 AM, Stuart Winter wrote: > > > > Hello > > > > As the subject says - I am thinking of asking for a sub forum on LQ and > > using that for ARM related stuff. LQ is the official Slackware questions > > forum for x86, so it makes sense from that perspective. In addition it > > also raises the profile of the ARM port - since the communication won't be > > squirreled away in an archive mbox. > > > > I am personally not a fan of web forums as I don't like having to click > > everywhere - it's easier to use PINE and the keyboard controls; however > > the two points above really should outweigh my personal preferences ;-) > > > > Any thoughts? > > > > -- > > Stuart Winter > > Slackware ARM: http://arm.slackware.com > > _______________________________________________ > > 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: http://arm.slackware.com From dhm at mersenne.com Thu Nov 21 16:38:17 2013 From: dhm at mersenne.com (David Madden) Date: Thu, 21 Nov 2013 08:38:17 -0800 Subject: [ARMedslack] Thinking of decomissioning this mailing list in favour of a sub forum on LinuxQuestions.org In-Reply-To: References: Message-ID: <528E36F9.2010505@mersenne.com> On 11/21/13, 7:35 AM, Stuart Winter wrote: > I am personally not a fan of web forums I don't like 'em either -- the main problem is, there are so many of them, and each one a security disaster waiting to happen. (Yes, I use different usernames and passwords everywhere, but that's a hassle for me to keep track of.) If I want to "subscribe to someone's newsletter," send it to my email where I can drop it in a folder on my own disk. -- Mersenne Law LLC ? www.mersenne.com ? +1-503-679-1671 - Small Business, Startup and Intellectual Property Law - 9600 S.W. Oak Street ? Suite 500 ? Tigard, Oregon 97223 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4003 bytes Desc: S/MIME Cryptographic Signature URL: From exaga at fatdog.eu Thu Nov 21 18:19:40 2013 From: exaga at fatdog.eu (Exaga) Date: Thu, 21 Nov 2013 18:19:40 -0000 Subject: [ARMedslack] Thinking of decomissioning this mailing list in favour of a sub forum on LinuxQuestions.org In-Reply-To: References: Message-ID: <000901cee6e6$40f94e70$c2ebeb50$@fatdog.eu> Hi, I can't agree with your personal opinion on forums, Stuart, sorry. :P However, I do agree that a LQ sub-forum would be a great idea in order to further raise the profile and individualise Slackware ARM, if for no other reasons than to make for easier viewing and referral for people like me. It's also easier to get involved and post/reply specifically. :) I'm an avid Slackware acolyte with a strong interest in promoting it on the RPi. The Raspberry Pi Foundation seems to have little or no interest in supporting Slackware ARM (or even recognising that it exists) which seems counter-productive towards their goal of bringing the 'real' fundamentals of computing back to the masses. So, in my opinion, somebody else has to do it. The more ways in which Slackware ARM can be promoted and supported the better, in my view. Cheers, Exaga ==== __ KEEP THE DOG ALIVE!!! ()'`; / /\|` W00f W00f W00f www.fatdog.eu -----Original Message----- From: ARMedslack [mailto:armedslack-bounces at lists.armedslack.org] On Behalf Of Stuart Winter Sent: 21 November 2013 15:36 To: armedslack at lists.armedslack.org Subject: [ARMedslack] Thinking of decomissioning this mailing list in favour of a sub forum on LinuxQuestions.org Hello As the subject says - I am thinking of asking for a sub forum on LQ and using that for ARM related stuff. LQ is the official Slackware questions forum for x86, so it makes sense from that perspective. In addition it also raises the profile of the ARM port - since the communication won't be squirreled away in an archive mbox. I am personally not a fan of web forums as I don't like having to click everywhere - it's easier to use PINE and the keyboard controls; however the two points above really should outweigh my personal preferences ;-) Any thoughts? -- Stuart Winter Slackware ARM: http://arm.slackware.com _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack From m-lists at biscuit.org.uk Thu Nov 21 21:46:00 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 21 Nov 2013 21:46:00 +0000 (GMT) Subject: [ARMedslack] Thinking of decomissioning this mailing list in favour of a sub forum on LinuxQuestions.org In-Reply-To: <000901cee6e6$40f94e70$c2ebeb50$@fatdog.eu> References: <000901cee6e6$40f94e70$c2ebeb50$@fatdog.eu> Message-ID: > I can't agree with your personal opinion on forums, Stuart, sorry. :P I'm still not a fan of forums but the great thing about them in this instance is that the rest of the Slackware discussions are going on, so I'd rather link the ARM port to the rest of it rather than having it as an outlier. > However, I do agree that a LQ sub-forum would be a great idea in order to > further raise the profile and individualise Slackware ARM, if for no other > reasons than to make for easier viewing and referral for people like me. > It's also easier to get involved and post/reply specifically. :) > > I'm an avid Slackware acolyte with a strong interest in promoting it on the > RPi. The Raspberry Pi Foundation seems to have little or no interest in > supporting Slackware ARM (or even recognising that it exists) which seems > counter-productive towards their goal of bringing the 'real' fundamentals of > computing back to the masses. I don't know why that is - whether it's because it's a soft float port or because the people behind the RPi favour Ubuntu or whatever. Whatever the reason, there are a lot of RPi owners running Slackware on it due to a combination of the community that built itself around that device. From mozes at slackware.com Thu Nov 21 22:05:22 2013 From: mozes at slackware.com (Stuart Winter) Date: Thu, 21 Nov 2013 14:05:22 -0800 (PST) Subject: [ARMedslack] Slackware ARM/old ARMedslack mailing list is now retired Message-ID: Hello I have made the decision (and I think it's the right one) to retire this list. I will prevent new posts from being sent to it tomorrow (Fri 22nd Nov 2013), which gives you a number of hours to air your discontentment with the decision and have it stored forever more in the mailing list archive ;-) The new forum is a sub forum of the 'Slackware' parent on LinuxQuestions.org, and it may be found here: http://www.linuxquestions.org/questions/slackware-arm-108 Thanks to Jeremy @ LQ for setting it up, and to Robby Workman for hosting the mailman list for a *long* time! Cheers, s. From niels.horn at gmail.com Thu Nov 21 22:23:22 2013 From: niels.horn at gmail.com (Niels Horn) Date: Thu, 21 Nov 2013 20:23:22 -0200 Subject: [ARMedslack] Thinking of decomissioning this mailing list in favour of a sub forum on LinuxQuestions.org In-Reply-To: References: <000901cee6e6$40f94e70$c2ebeb50$@fatdog.eu> Message-ID: I haven't been very active with Slackware ARM lately for lack of time, but I vote for migrating the list to a sub-forum on LinuxQuestions.org. I receive tons of e-mail per day and end up not reading everything. The idea of having both Slackware-x86 and Slackware-ARM discussions on the same site sound good to me. -- Niels Horn On Thu, Nov 21, 2013 at 7:46 PM, Stuart Winter wrote: > > > > I can't agree with your personal opinion on forums, Stuart, sorry. :P > > I'm still not a fan of forums but the great thing about them in this > instance is that the rest of the Slackware discussions are going on, so > I'd rather link the ARM port to the rest of it rather than having it as > an outlier. > > > However, I do agree that a LQ sub-forum would be a great idea in order to > > further raise the profile and individualise Slackware ARM, if for no > other > > reasons than to make for easier viewing and referral for people like me. > > It's also easier to get involved and post/reply specifically. :) > > > > I'm an avid Slackware acolyte with a strong interest in promoting it on > the > > RPi. The Raspberry Pi Foundation seems to have little or no interest in > > supporting Slackware ARM (or even recognising that it exists) which seems > > counter-productive towards their goal of bringing the 'real' > fundamentals of > > computing back to the masses. > > I don't know why that is - whether it's because it's a soft float port or > because the people behind the RPi favour Ubuntu or whatever. > Whatever the reason, there are a lot of RPi owners running Slackware on it > due to a combination of the community that built itself around that > device. > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Fri Nov 22 00:20:17 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Fri, 22 Nov 2013 00:20:17 +0000 Subject: [ARMedslack] Slackware ARM/old ARMedslack mailing list is now retired In-Reply-To: References: Message-ID: <20131122002017.221B96C6C843@bmail-n01.one.com> I will miss the list, but I think it was for the best. I've just registered with LQ. I find it somewhat confusing, I am sure with time that will pass... The adverts for 'mature dating' are a bit of a worry, perhaps I should have fudged my date of birth! Kind regards Stanley. > > _______________________________________________ > ARMedslack mailing list > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From exaga at fatdog.eu Fri Nov 22 00:37:22 2013 From: exaga at fatdog.eu (Exaga) Date: Fri, 22 Nov 2013 00:37:22 -0000 Subject: [ARMedslack] Slackware ARM/old ARMedslack mailing list is now retired In-Reply-To: <20131122002017.221B96C6C843@bmail-n01.one.com> References: <20131122002017.221B96C6C843@bmail-n01.one.com> Message-ID: <000601cee71b$03ab3c10$0b01b430$@fatdog.eu> Then welcome to LQ, Stanley. I hope the initial disorientation subsides quickly. :) I'm more concerned with the fact that I only joined the mailing list last Sunday and already Stuart is axing it! Was it something I said, or did? Do I need to shower perhaps? Maybe I should have fudged my identity! :P Exaga ==== __ KEEP THE DOG ALIVE!!! ()'`; / /\|` W00f W00f W00f www.fatdog.eu From: ARMedslack [mailto:armedslack-bounces at lists.armedslack.org] On Behalf Of stanley garvey Sent: 22 November 2013 00:20 To: Slackware ARM mailing list; Slackware ARM port Subject: Re: [ARMedslack] Slackware ARM/old ARMedslack mailing list is now retired I will miss the list, but I think it was for the best. I've just registered with LQ. I find it somewhat confusing, I am sure with time that will pass... The adverts for 'mature dating' are a bit of a worry, perhaps I should have fudged my date of birth! Kind regards Stanley. _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Fri Nov 22 00:53:04 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Fri, 22 Nov 2013 00:53:04 +0000 Subject: [ARMedslack] Slackware ARM/old ARMedslack mailing list is now retired In-Reply-To: <000601cee71b$03ab3c10$0b01b430$@fatdog.eu> References: <20131122002017.221B96C6C843@bmail-n01.one.com> <000601cee71b$03ab3c10$0b01b430$@fatdog.eu> Message-ID: <20131122005304.8473880BDC2A3@bmail06.one.com> On Nov 22, 2013 00:37 "Exaga" wrote: > > Then welcome to LQ, Stanley. I hope the initial disorientation > subsides quickly. :) > > > > I?m more concerned with the fact that I only joined the mailing list > last Sunday and already Stuart is axing it! Was it something I said, > or did? Do I need to shower perhaps? Maybe I should have fudged my > identity! :P > > > > Exaga > > ==== > __ KEEP THE DOG ALIVE!!! > ()'`; / > /\|` W00f W00f W00f > > > > > Hey It's been going for some time now. I've been watching armslack.org > for a good few years now, but until the advent of the Raspberry Pi I > had nothing to run it on except Qemu. > > SlackwareARM is a very important work, Raspberrypi.org can't support > every distro, and settled upon Debian, shame, I would have thought > Slackware was the obivious choice for education being one up from LFS. > > Regards, > > Stanley. > > _______________________________________________ > ARMedslack mailing list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: