From zck580 at yahoo.com Wed Aug 1 14:23:52 2012 From: zck580 at yahoo.com (Zack S) Date: Wed, 1 Aug 2012 07:23:52 -0700 (PDT) Subject: [ARMedslack] running in a simulator Message-ID: <1343831032.78067.YahooMailClassic@web121506.mail.ne1.yahoo.com> Hi folks, Has anyone yet tried running Slackware ARM on any if the ARM emulators, like ArcEm, SkyEye or Simit? If so I'm curious to learn roughly how many instructions per second are being reported. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From vapier at gentoo.org Wed Aug 1 18:19:08 2012 From: vapier at gentoo.org (Mike Frysinger) Date: Wed, 1 Aug 2012 14:19:08 -0400 Subject: [ARMedslack] running in a simulator In-Reply-To: <1343831032.78067.YahooMailClassic@web121506.mail.ne1.yahoo.com> References: <1343831032.78067.YahooMailClassic@web121506.mail.ne1.yahoo.com> Message-ID: <201208011419.10144.vapier@gentoo.org> On Wednesday 01 August 2012 10:23:52 Zack S wrote: > Has anyone yet tried running Slackware ARM on any if the > ARM emulators, like ArcEm, SkyEye or Simit? > If so I'm curious to learn roughly how many instructions > per second are being reported. use QEMU -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. URL: From louigi600 at yahoo.it Thu Aug 2 06:10:58 2012 From: louigi600 at yahoo.it (Davide) Date: Thu, 2 Aug 2012 07:10:58 +0100 (BST) Subject: [ARMedslack] running in a simulator In-Reply-To: <201208011419.10144.vapier@gentoo.org> References: <1343831032.78067.YahooMailClassic@web121506.mail.ne1.yahoo.com> <201208011419.10144.vapier@gentoo.org> Message-ID: <1343887858.37905.YahooMailNeo@web29701.mail.ird.yahoo.com> >> Has anyone yet tried running Slackware ARM on any if the >> ARM emulators, like ArcEm, SkyEye or Simit? >> If so I'm curious to learn roughly how many instructions >> per second are being reported. >use QEMU >-mike Yeah there is some documentation on how to get going pretty fast with qemu on the armedslack site and versatile is one of the officially supported platforms which is one ov the things that qemu emulates. Ciao David -------------- next part -------------- An HTML attachment was scrubbed... URL: From galen.dp at gmail.com Wed Aug 22 19:55:19 2012 From: galen.dp at gmail.com (Doug Peterson) Date: Wed, 22 Aug 2012 13:55:19 -0600 Subject: [ARMedslack] Slackware Documentation Project Message-ID: Hi all, In case you didn't see it, the Slackware Documentation Project has been started. It is at http://docs.slackware.com/start. As ArmedSlack is the official port of Slackware to ARM platforms, would there be any problems if I added mention of the website and mailing list to the SDP? -Doug From pr0f3ss0r1492 at yahoo.com Wed Aug 22 20:22:18 2012 From: pr0f3ss0r1492 at yahoo.com (Ottavio Caruso) Date: Wed, 22 Aug 2012 21:22:18 +0100 Subject: [ARMedslack] Slackware Documentation Project In-Reply-To: References: Message-ID: On 22 August 2012 20:55, Doug Peterson wrote: > As ArmedSlack is the official port of Slackware to ARM platforms, > would there be any problems if I added mention of the website and > mailing list to the SDP? As Armedslack is the official port of Slackware for ARM I don't see why not. From galen.dp at gmail.com Wed Aug 22 23:23:30 2012 From: galen.dp at gmail.com (Doug Peterson) Date: Wed, 22 Aug 2012 17:23:30 -0600 Subject: [ARMedslack] Slackware Documentation Project In-Reply-To: References: Message-ID: On Wed, Aug 22, 2012 at 2:22 PM, Ottavio Caruso wrote: > On 22 August 2012 20:55, Doug Peterson wrote: >> As ArmedSlack is the official port of Slackware to ARM platforms, >> would there be any problems if I added mention of the website and >> mailing list to the SDP? > > As Armedslack is the official port of Slackware for ARM I don't see why not. Ok. -Doug From m-lists at biscuit.org.uk Thu Aug 23 09:33:46 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Thu, 23 Aug 2012 10:33:46 +0100 (BST) Subject: [ARMedslack] Slackware Documentation Project In-Reply-To: References: Message-ID: > > As ArmedSlack is the official port of Slackware to ARM platforms, > > would there be any problems if I added mention of the website and > > mailing list to the SDP? > > As Armedslack is the official port of Slackware for ARM I don't see why not. Yes that's be brilliant, thanks. From m-lists at biscuit.org.uk Sat Aug 25 09:19:09 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 25 Aug 2012 10:19:09 +0100 (BST) Subject: [ARMedslack] Slackware ARM "current" directory name is being changed - Mon 27th August Message-ID: Hi In an effort to standardise on the name "Slackware ARM" and move away from the old "ARMedslack" name, I'll be renaming on the FTP site: armedslack-current to slackwarearm-current The Slackware ARM 14.0 release will have name "slackwarearm-14.0", and going forward all new releases will be named in this way. The previous releases will continue to have the existing names. There won't be any updates to -current until the name change is complete. -- Stuart Winter Slackware ARM: www.armedslack.org From m-lists at biscuit.org.uk Sat Aug 25 22:30:25 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sat, 25 Aug 2012 23:30:25 +0100 (BST) Subject: [ARMedslack] Slackware ARM "current" directory name is being changed - Mon 27th August In-Reply-To: References: Message-ID: In addition, the root directory on the FTP site & the rsync module name will also change as below: FTP: ftp.armedslack.org/armedslack becomes ftp.armedslack.org/slackwarearm rsync: ftp.armedslack.org::armedslack becomes ftp.armedslack.org::slackwarearm Cheers s. From louigi600 at yahoo.it Sun Aug 26 10:36:51 2012 From: louigi600 at yahoo.it (Davide) Date: Sun, 26 Aug 2012 11:36:51 +0100 (BST) Subject: [ARMedslack] Slackware ARM "current" directory name is being changed - Mon 27th August In-Reply-To: References: Message-ID: <1345977411.72438.YahooMailNeo@web29703.mail.ird.yahoo.com> Don't forget to update the mirror list in slackpkg for the upcoming current packages ;) Regards David ________________________________ Da: Stuart Winter A: Slackware ARM port Inviato: Sabato 25 Agosto 2012 23:30 Oggetto: Re: [ARMedslack] Slackware ARM "current" directory name is being changed - Mon 27th August In addition, the root directory on the FTP site & the rsync module name will also change as below: FTP:? ftp.armedslack.org/armedslack? becomes ftp.armedslack.org/slackwarearm rsync: ftp.armedslack.org::armedslack becomes ftp.armedslack.org::slackwarearm Cheers s. _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From rclark at clavi.net Mon Aug 27 19:26:08 2012 From: rclark at clavi.net (Rob Clark) Date: Mon, 27 Aug 2012 14:26:08 -0500 Subject: [ARMedslack] A perplexing Raspberry Pi problem and my workaround. Comments? Message-ID: <503BC9D0.1090808@clavi.net> First, let me thank Stuart Winter and the other contributors for Slackware ARM on the Raspberry Pi. My problem: I am fortunate to have two RPi boards of nearly sequential serial numbers to play with. I had absolutely no trouble booting and installing Slackware ARM on _one_ of them, but they other hangs on boot, either with the rainbow screen, or no video output at all. Debian-wheezy and Arch Linux from the raspberrypi.org site both work on both boards. The problem is the same booting from either the installation image raspi-slack-installer-01Aug12.img.xz or on a fully installed Slackware ARM made on the working RPi. It boots on one device, but not the other. I tried different SDHC cards, power supplies, keyboards, etc. to no avail. Switch everything to the other RPi, and it works fine. My workaround: Based on something I read on the Raspberry Pi troubleshooting forum, I copied the start.elf and loader.bin from debian-wheezy to the first partition of the raspi-slack-installer-01Aug12. Now I am able to boot on the balky RPi. This is dumb luck because I charged ahead without understanding the boot process on ARM. So I offer this information, for whatever it's worth :) From sorin at spit-ct.ro Mon Aug 27 19:50:06 2012 From: sorin at spit-ct.ro (Sorin Mitrica) Date: Mon, 27 Aug 2012 22:50:06 +0300 Subject: [ARMedslack] A perplexing Raspberry Pi problem and my workaround. Comments? In-Reply-To: <503BC9D0.1090808@clavi.net> References: <503BC9D0.1090808@clavi.net> Message-ID: <503BCF6E.7010506@spit-ct.ro> Install the latest firmware and kernel from https://github.com/raspberrypi/firmware The boot partition must contain: root at kernel:/boot# ls LICENCE.broadcom* arm128_start.elf* arm224_start.elf* bootcode.bin* config.txt* kernel.img.old* kernel_emergency.img* start.elf* README* arm192_start.elf* arm240_start.elf* cmdline.txt* kernel.img* kernel_cutdown.img* loader.bin* Important is bootcode.bin , kernel.img , start.elf , cmdline.txt , loader.bin Also copy the modules in /lib/modules Or maybe you have a damaged Pi. On 27.08.2012 22:26, Rob Clark wrote: > First, let me thank Stuart Winter and the other contributors for > Slackware ARM on the Raspberry Pi. > > My problem: > I am fortunate to have two RPi boards of nearly sequential serial > numbers to play with. I had absolutely no trouble booting and > installing Slackware ARM on _one_ of them, but they other hangs on boot, > either with the rainbow screen, or no video output at all. > > Debian-wheezy and Arch Linux from the raspberrypi.org site both work on > both boards. > > The problem is the same booting from either the installation image > raspi-slack-installer-01Aug12.img.xz or on a fully installed Slackware > ARM made on the working RPi. It boots on one device, but not the other. > > I tried different SDHC cards, power supplies, keyboards, etc. to no > avail. Switch everything to the other RPi, and it works fine. > > My workaround: > Based on something I read on the Raspberry Pi troubleshooting forum, I > copied the start.elf and loader.bin from debian-wheezy to the first > partition of the raspi-slack-installer-01Aug12. Now I am able to boot > on the balky RPi. > > This is dumb luck because I charged ahead without understanding the boot > process on ARM. So I offer this information, for whatever it's worth :) > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > From pirkster at gmail.com Mon Aug 27 19:46:48 2012 From: pirkster at gmail.com (Steve Pirk) Date: Mon, 27 Aug 2012 12:46:48 -0700 Subject: [ARMedslack] A perplexing Raspberry Pi problem and my workaround. Comments? In-Reply-To: <503BC9D0.1090808@clavi.net> References: <503BC9D0.1090808@clavi.net> Message-ID: I have 3 RPi devices, and have only fired up one so far using the Raspian image. Let me try all 3 with a Slackware arm build and see if I can duplicate your error on any of them. If I get one that hangs, I can try your workaround to see if it is consistent. -- steve On Mon, Aug 27, 2012 at 12:26 PM, Rob Clark wrote: > First, let me thank Stuart Winter and the other contributors for > Slackware ARM on the Raspberry Pi. > > My problem: > I am fortunate to have two RPi boards of nearly sequential serial > numbers to play with. I had absolutely no trouble booting and > installing Slackware ARM on _one_ of them, but they other hangs on boot, > either with the rainbow screen, or no video output at all. > > Debian-wheezy and Arch Linux from the raspberrypi.org site both work on > both boards. > > The problem is the same booting from either the installation image > raspi-slack-installer-01Aug12.img.xz or on a fully installed Slackware > ARM made on the working RPi. It boots on one device, but not the other. > > I tried different SDHC cards, power supplies, keyboards, etc. to no > avail. Switch everything to the other RPi, and it works fine. > > My workaround: > Based on something I read on the Raspberry Pi troubleshooting forum, I > copied the start.elf and loader.bin from debian-wheezy to the first > partition of the raspi-slack-installer-01Aug12. Now I am able to boot > on the balky RPi. > > This is dumb luck because I charged ahead without understanding the boot > process on ARM. So I offer this information, for whatever it's worth :) > _______________________________________________ > 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 Mon Aug 27 21:15:38 2012 From: stanley at stanleygarvey.com (stanley garvey) Date: Mon, 27 Aug 2012 22:15:38 +0100 Subject: [ARMedslack] Slackware ARM "current" directory name is being changed - Mon 27th August References: Message-ID: <20120827211538.B664B3B2ABC94@bmail04.one.com> On Aug 27, 2012 22:15 "stanley garvey" wrote: > On Aug 25, 2012 23:30 "Stuart Winter" wrote: > > > In addition, the root directory on the FTP site & the rsync module > > name > > will also change as below: > > > > FTP: ftp.armedslack.org/armedslack becomes > > ftp.armedslack.org/slackwarearm > > rsync: ftp.armedslack.org::armedslack becomes > > ftp.armedslack.org::slackwarearm > > > > Cheers > > s. > > _____ > > So I need to change : > > > > # For: Slackware-13.37. Should work on all previous versions > > # Descr: Upgrades to patched/fixed/upgraded packages via rync mirror > > # URL: http://www.stanleygarvey.com/ > > # Needs: slackware public key: http://www.slackware.com/gpg-key > > # Changelog: > > mirror="rsync.slackware.org.uk" > > cd /root > > system=`cut -d" " -f2 /etc/slackware-version | cut -d. -f1-2` > > echo "Found Slackware-$system, getting upgraded packages from > > $mirror" > > #from : > > rsync -avz --delete > > $mirror::armedslack/slackware-$system/patches/packages/ > > packages-$system > > #to : > > #rsync -avz --delete > > $mirror::slackwarearm/slackware-$system/patches/packages/ > > packages-$system > > cd packages-$system > > for f in *.t*z > > do > > echo "Verifying $f" > > gpg -q --verify $f.asc $f > > if [ $? == 0 ]; then > > echo "Passed" > > upgradepkg $f > > else > > echo "failed" > > fi > > done > > ____________________________________ > > ARMedslack mailing list > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hammack at GotSlack.org Mon Aug 27 21:24:23 2012 From: hammack at GotSlack.org (Jim Hammack) Date: Mon, 27 Aug 2012 16:24:23 -0500 Subject: [ARMedslack] A perplexing Raspberry Pi problem and my workaround. Comments? In-Reply-To: <503BC9D0.1090808@clavi.net> References: <503BC9D0.1090808@clavi.net> Message-ID: <503BE587.40703@GotSlack.org> An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Tue Aug 28 21:11:41 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 28 Aug 2012 22:11:41 +0100 (BST) Subject: [ARMedslack] Slackware ARM "current" directory name is being changed - Mon 27th August In-Reply-To: <20120827211538.B664B3B2ABC94@bmail04.one.com> References: <20120827211538.B664B3B2ABC94@bmail04.one.com> Message-ID: > > > #from : > > > rsync -avz --delete > > > $mirror::armedslack/slackware-$system/patches/packages/ > > > packages-$system > > > #to : > > > #rsync -avz --delete > > > $mirror::slackwarearm/slackware-$system/patches/packages/ No because this never worked ;-) For all existing releases, the dirs are named "armedslack-$version" not "slackware-$version", so your original rsync line wouldn't have worked. The directory names for -current and -14.0 are "slackwarearm-$version". From stanley at stanleygarvey.com Wed Aug 29 19:14:08 2012 From: stanley at stanleygarvey.com (stanley garvey) Date: Wed, 29 Aug 2012 20:14:08 +0100 Subject: [ARMedslack] Slackware ARM "current" directory name is being changed - Mon 27th August In-Reply-To: References: <20120827211538.B664B3B2ABC94@bmail04.one.com> Message-ID: <20120829191408.C93E0F73805F2@bmail03.one.com> On Aug 28, 2012 22:11 "Stuart Winter" wrote: > > > > #from : > > > > rsync -avz --delete > > > > $mirror::armedslack/slackware-$system/patches/packages/ > > > > packages-$system > > > > #to : > > > > #rsync -avz --delete > > > > $mirror::slackwarearm/slackware-$system/patches/packages/ > > No because this never worked ;-) > > For all existing releases, the dirs are named "armedslack-$version" > not "slackware-$version", so your original rsync line wouldn't have > worked. > > The directory names for -current and -14.0 are > "slackwarearm-$version". > > Heh, Yes, the script is simple, as is the author. Its from an x86 box. > I plan to use it on Slackware arm. Perhaps it will need to be more > elaborate. > > _______________________________________________ > ARMedslack mailing list > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mozes at slackware.com Fri Aug 31 14:09:33 2012 From: mozes at slackware.com (Stuart Winter) Date: Fri, 31 Aug 2012 07:09:33 -0700 (PDT) Subject: [ARMedslack] QEMU support - does anybody care about it? Message-ID: Hi I am thinking about removing the QEMU packages from -current. I only added these years ago because my real ARM hardware died and I needed a stop gap. The thing is that QEMU is *so slow* that I cannot imagine it being useful at all, apart from a 10 minute novelty for x86 users. It takes time to test whether the installation works, and takes time to build the Versatile kernel. Is anybody going to miss it if I drop the packages and install docs? -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: www.armedslack.org From thenktor at gmail.com Fri Aug 31 14:29:09 2012 From: thenktor at gmail.com (=?ISO-8859-1?Q?Thorsten_M=FChlfelder?=) Date: Fri, 31 Aug 2012 16:29:09 +0200 Subject: [ARMedslack] QEMU support - does anybody care about it? In-Reply-To: References: Message-ID: I've never used QEMU and I think nowadays ARM hardware is really cheap to get. So even for a first try beginners may rather buy an ARM board than using QEMU. 2012/8/31 Stuart Winter : > > Hi > > I am thinking about removing the QEMU packages from -current. > I only added these years ago because my real ARM hardware died and I > needed a stop gap. > > The thing is that QEMU is *so slow* that I cannot imagine it being useful > at all, apart from a 10 minute novelty for x86 users. > It takes time to test whether the installation works, and takes time to > build the Versatile kernel. > > Is anybody going to miss it if I drop the packages and install docs? > > -- > Stuart Winter > www.slackware.com/~mozes > Slackware for ARM: www.armedslack.org > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack From robby at rlworkman.net Fri Aug 31 14:37:31 2012 From: robby at rlworkman.net (Robby Workman) Date: Fri, 31 Aug 2012 09:37:31 -0500 Subject: [ARMedslack] QEMU support - does anybody care about it? In-Reply-To: References: Message-ID: <20120831093731.292d14dd@liberty.rlwhome.lan> On Fri, 31 Aug 2012 07:09:33 -0700 (PDT) Stuart Winter wrote: > > Hi > > I am thinking about removing the QEMU packages from -current. > I only added these years ago because my real ARM hardware died and I > needed a stop gap. > > The thing is that QEMU is *so slow* that I cannot imagine it being > useful at all, apart from a 10 minute novelty for x86 users. > It takes time to test whether the installation works, and takes time > to build the Versatile kernel. > > Is anybody going to miss it if I drop the packages and install docs? Well... I would, since I often build packages in a qemu VM (I'm usually in no hurry, so time isn't a problem). However, I can adjust :-) -RW From louigi600 at yahoo.it Fri Aug 31 15:05:26 2012 From: louigi600 at yahoo.it (Davide) Date: Fri, 31 Aug 2012 16:05:26 +0100 (BST) Subject: [ARMedslack] QEMU support - does anybody care about it? In-Reply-To: References: Message-ID: <1346425526.28090.YahooMailNeo@web29705.mail.ird.yahoo.com> I still find qemu useful when I want to test something out amd that qould be emulating ARM from x86 hardware. I know arm hardware is cheap nowadays ... but qemu is cheaper and no need to wait for shipping ;) ________________________________ Da: Stuart Winter A: Slackware ARM mailing list Inviato: Venerd? 31 Agosto 2012 16:09 Oggetto: [ARMedslack] QEMU support - does anybody care about it? Hi I am thinking about removing the QEMU packages from -current. I only added these years ago because my real ARM hardware died and I needed a stop gap. The thing is that QEMU is *so slow* that I cannot imagine it being useful at all, apart from a 10 minute novelty for x86 users. It takes time to test whether the installation works, and takes time to build the Versatile kernel. Is anybody going to miss it if I drop the packages and install docs? -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: www.armedslack.org _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From pr0f3ss0r1492 at yahoo.com Fri Aug 31 15:11:45 2012 From: pr0f3ss0r1492 at yahoo.com (Ottavio Caruso) Date: Fri, 31 Aug 2012 16:11:45 +0100 Subject: [ARMedslack] QEMU support - does anybody care about it? In-Reply-To: References: Message-ID: On 31 August 2012 15:09, Stuart Winter wrote: > > I am thinking about removing the QEMU packages from -current. > I only added these years ago because my real ARM hardware died and I > needed a stop gap. I don't understand what you mean by qemu packages. Do you mean the /slackwarearm/slackwarearm-devtools/qemu/ ? I have actually never used those to install inside qemu. I only used the mini-root and the volatile kernel. From m-lists at biscuit.org.uk Fri Aug 31 15:22:23 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 31 Aug 2012 16:22:23 +0100 (BST) Subject: [ARMedslack] QEMU support - does anybody care about it? In-Reply-To: References: Message-ID: > I don't understand what you mean by qemu packages. Do you mean the > /slackwarearm/slackwarearm-devtools/qemu/ ? The 'versatile' kernel packages. -- Stuart Winter Slackware ARM: www.armedslack.org From pr0f3ss0r1492 at yahoo.com Fri Aug 31 15:24:39 2012 From: pr0f3ss0r1492 at yahoo.com (Ottavio Caruso) Date: Fri, 31 Aug 2012 16:24:39 +0100 Subject: [ARMedslack] QEMU support - does anybody care about it? In-Reply-To: References: Message-ID: On 31 August 2012 16:22, Stuart Winter wrote: > >> I don't understand what you mean by qemu packages. Do you mean the >> /slackwarearm/slackwarearm-devtools/qemu/ ? > > The 'versatile' kernel packages. Then in this case, yes, I'd still like to play with them if possible. From unixjohn1969 at gmail.com Fri Aug 31 15:13:55 2012 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Fri, 31 Aug 2012 11:13:55 -0400 Subject: [ARMedslack] QEMU support - does anybody care about it? In-Reply-To: <1346425526.28090.YahooMailNeo@web29705.mail.ird.yahoo.com> References: <1346425526.28090.YahooMailNeo@web29705.mail.ird.yahoo.com> Message-ID: <5040D4B3.50905@gmail.com> On 08/31/2012 11:05 AM, Davide wrote: > I still find qemu useful when I want to test something out amd that qould be > emulating ARM from x86 hardware. > I know arm hardware is cheap nowadays ... but qemu is cheaper and no need to > wait for shipping ;) and you can add gobs of RAM SWAP support in qeum that isnt available to the real hardware. -- === 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 From m-lists at biscuit.org.uk Fri Aug 31 16:15:26 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 31 Aug 2012 17:15:26 +0100 (BST) Subject: [ARMedslack] QEMU support - does anybody care about it? In-Reply-To: <5040D4B3.50905@gmail.com> References: <1346425526.28090.YahooMailNeo@web29705.mail.ird.yahoo.com> <5040D4B3.50905@gmail.com> Message-ID: > and you can add gobs of RAM SWAP support in qeum that isnt available to the > real hardware. The machine type I provide packages for is the VersatilePB which only supports 256MB RAM, and you certainly would not want it paging. -- Stuart Winter Slackware ARM: www.armedslack.org From niels.horn at gmail.com Fri Aug 31 17:02:33 2012 From: niels.horn at gmail.com (Niels Horn) Date: Fri, 31 Aug 2012 14:02:33 -0300 Subject: [ARMedslack] QEMU support - does anybody care about it? In-Reply-To: <20120831093731.292d14dd@liberty.rlwhome.lan> References: <20120831093731.292d14dd@liberty.rlwhome.lan> Message-ID: On Fri, Aug 31, 2012 at 11:37 AM, Robby Workman wrote: > On Fri, 31 Aug 2012 07:09:33 -0700 (PDT) > Stuart Winter wrote: > >> >> Hi >> >> I am thinking about removing the QEMU packages from -current. >> I only added these years ago because my real ARM hardware died and I >> needed a stop gap. >> >> The thing is that QEMU is *so slow* that I cannot imagine it being >> useful at all, apart from a 10 minute novelty for x86 users. >> It takes time to test whether the installation works, and takes time >> to build the Versatile kernel. >> >> Is anybody going to miss it if I drop the packages and install docs? > > > Well... I would, since I often build packages in a qemu VM (I'm > usually in no hurry, so time isn't a problem). However, I can > adjust :-) > > -RW Yeah, I'd miss it too... I still use qemu with its snapshot feature to build packages on a "clean" installation. My real ARM hardware has too many packages installed to consider it a clean installation. -- Niels Horn