From m-lists at biscuit.org.uk Wed Sep 5 13:38:43 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Wed, 5 Sep 2012 14:38:43 +0100 (BST) Subject: [ARMedslack] QEMU support - does anybody care about it? In-Reply-To: References: <20120831093731.292d14dd@liberty.rlwhome.lan> Message-ID: > 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. I had a look and realised that to remove all the references to Versatile, and test the packages and installer would take more effort and time than to build the kernels and test it once or twice a year, so I'll leave them there. From cedric.vincent at gmail.com Thu Sep 6 08:25:52 2012 From: cedric.vincent at gmail.com (=?UTF-8?Q?C=C3=A9dric_VINCENT?=) Date: Thu, 6 Sep 2012 10:25:52 +0200 Subject: [ARMedslack] QEMU support - does anybody care about it? In-Reply-To: References: <20120831093731.292d14dd@liberty.rlwhome.lan> Message-ID: Hello, For information, QEMU user-mode doesn't require any "guest" kernel since all privileged operations are redirected to the "host" one. Moreover the user-mode is a lot faster than the system-mode since there's no device emulation at all [0]. Let me demonstrate how you can use your favorite distro with QEMU user-mode and PRoot (its companion, http://proot.me) without any setup or privilege. In the following example I assume the Slackware/ARM rootfs [1] was extracted in the "./rootfs/" directory: proot -Q qemu-arm -r ./rootfs/ At this point, you are running a shell "confined" in the Slackware/ARM rootfs and all ARM programs are "translated" by QEMU user-mode: guest$ file /bin/echo /bin/echo: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), stripped guest$ /bin/echo "hello, world." hello, world. That way, you can do whatever you would do with a "real" Slackware/ARM installation, for instance download and install new packages: guest$ wget ftp://ftp.slackware.org.uk/slackwarearm/slackwarearm-current/slackware/ap/slackpkg-2.82.0-arm-3.tgz guest$ wget ftp://ftp.slackware.org.uk/slackwarearm/slackwarearm-current/slackware/l/ncurses-5.9-arm-2.tgz guest$ installpkg slackpkg-2.82.0-arm-3.tgz guest$ installpkg ncurses-5.9-arm-2.tgz For programs that require privileges, you can use the "-0" option to fake the "root" id: guest$ slackpkg update Only root can install, upgrade, or remove packages. Please log in as root or contact your system administrator. host$ proot -Q qemu-arm -r ./rootfs/ -0 guest# slackpkg update guest# slackpkg upgrade-all guest# slackpkg install-new Feel free to ask me for support, C?dric. [0] https://github.com/cedric-vincent/PRoot/blob/master/doc/articles/extending_qemu.txt [1] ftp://ftp.slackware.org.uk/slackwarearm/slackwarearm-devtools/minirootfs/roots/slack-current-miniroot_27Aug12.tar.xz PS: A couple of words about the use of PRoot and QEMU user-mode in the industry: my team uses it to develop and optimize (GCC profile base optimizations) embedded applications on x86_64 farms. From pr0f3ss0r1492 at yahoo.com Thu Sep 6 10:04:22 2012 From: pr0f3ss0r1492 at yahoo.com (Ottavio Caruso) Date: Thu, 6 Sep 2012 11:04:22 +0100 Subject: [ARMedslack] QEMU support - does anybody care about it? In-Reply-To: References: <20120831093731.292d14dd@liberty.rlwhome.lan> Message-ID: On 6 September 2012 09:25, C?dric VINCENT wrote: > > For information, QEMU user-mode doesn't require any "guest" kernel > since all privileged operations are redirected to the "host" one. You assume that everybody uses Linux on PC as a host. If you use Windows for example you need full system emulation. From louigi600 at yahoo.it Thu Sep 6 14:10:06 2012 From: louigi600 at yahoo.it (Davide) Date: Thu, 6 Sep 2012 15:10:06 +0100 (BST) Subject: [ARMedslack] QEMU support - does anybody care about it? In-Reply-To: References: <20120831093731.292d14dd@liberty.rlwhome.lan> Message-ID: <1346940606.89366.YahooMailNeo@web29705.mail.ird.yahoo.com> >> For information, QEMU user-mode doesn't require any "guest" kernel >> since all privileged operations are redirected to the "host" one. >You assume that everybody uses Linux on PC as a host. If you use >Windows for example you need full system emulation. I just could not resist ... this is just a joke: True Windows users get an allergic rash when they use Linux, True Open Source sustainers get an allergic rash when they use non free software :-D -------------- next part -------------- An HTML attachment was scrubbed... URL: From unixjohn1969 at gmail.com Thu Sep 6 16:20:33 2012 From: unixjohn1969 at gmail.com (John O'Donnell) Date: Thu, 06 Sep 2012 12:20:33 -0400 Subject: [ARMedslack] QEMU support - does anybody care about it? In-Reply-To: References: <20120831093731.292d14dd@liberty.rlwhome.lan> Message-ID: <5048CD51.6040408@gmail.com> On 09/06/2012 06:04 AM, Ottavio Caruso wrote: > On 6 September 2012 09:25, C?dric VINCENT wrote: >> >> For information, QEMU user-mode doesn't require any "guest" kernel >> since all privileged operations are redirected to the "host" one. > > You assume that everybody uses Linux on PC as a host. If you use > Windows for example you need full system emulation. Is this a joke? -- === 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 pr0f3ss0r1492 at yahoo.com Thu Sep 6 17:58:02 2012 From: pr0f3ss0r1492 at yahoo.com (Ottavio Caruso) Date: Thu, 6 Sep 2012 18:58:02 +0100 Subject: [ARMedslack] QEMU support - does anybody care about it? In-Reply-To: <5048CD51.6040408@gmail.com> References: <20120831093731.292d14dd@liberty.rlwhome.lan> <5048CD51.6040408@gmail.com> Message-ID: On 6 September 2012 17:20, John O'Donnell wrote: > On 09/06/2012 06:04 AM, Ottavio Caruso wrote: >> >> On 6 September 2012 09:25, C?dric VINCENT >> wrote: >>> >>> >>> For information, QEMU user-mode doesn't require any "guest" kernel >>> since all privileged operations are redirected to the "host" one. >> >> >> You assume that everybody uses Linux on PC as a host. If you use >> Windows for example you need full system emulation. > > > Is this a joke? Why should it be a joke? I use qemu on Windows and I need the volatile kernel to emulate slackware on arm. From mr.chew.baka at gmail.com Thu Sep 6 22:14:16 2012 From: mr.chew.baka at gmail.com (Mr. B-o-B) Date: Thu, 6 Sep 2012 17:14:16 -0500 (CDT) Subject: [ARMedslack] F-ed up my SD card Message-ID: Hello, and a good day to you all. I am new to this list & ARMedSlack (not new to Slackware though). I recently received a Raspberry PI, and did a -current install per the instructions listed here: http://www.daves-collective.co.uk/raspi/installing.shtml All went well, but when I issued the "reboot" command it did not reboot properly. When the PI comes up now it has a solid green (OK) light, and a red light doing a quick 6 x flash. I did a little googling, and found an article on the PI site with my issue: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=10913 In a nut shell the article explains the problem is due to corrupt start.elf file. They recommended You should be able to download start.elf from here: https://github.com/raspberrypi/firmware ... aster/boot and copy it on the SD card. Does this sound about right for ARMedSlack? Any thoughts or hints about this would be greatly appreciated. Thanks! Mr. B-o-B From frmrick at aapt.net.au Fri Sep 7 03:33:19 2012 From: frmrick at aapt.net.au (Rick Miles) Date: Fri, 07 Sep 2012 13:33:19 +1000 Subject: [ARMedslack] F-ed up my SD card In-Reply-To: References: Message-ID: <1346988799.3200.13.camel@rick.miles.home> A few things to consider, there is nothing wrong with any of Dave's packages but perhaps you had a corrupt download. After your install are you sure you had the first (vfat) partition mounted as /mnt/boot and installed the raspberrypi packages as per the instructions? What is in the first partition and what is in /boot on the root files systems. The pi start.elf is nothing more than one of the numbered elf files, eg arm192_start.elf. If I thought my start.elf was bad. I'd first mount the sd card on some other machine, in the first partition I'd then delete the start elf and cp one of the numbered start.elfs to start.elf and tried a boot. On Thu, 2012-09-06 at 17:14 -0500, Mr. B-o-B wrote: > Hello, and a good day to you all. I am new to this list & ARMedSlack (not > new to Slackware though). I recently received a Raspberry PI, and did a > -current install per the instructions listed here: > > http://www.daves-collective.co.uk/raspi/installing.shtml > > All went well, but when I issued the "reboot" command it did not reboot > properly. When the PI comes up now it has a solid green (OK) light, and a > red light doing a quick 6 x flash. > > I did a little googling, and found an article on the PI site with my > issue: > > http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=10913 > > In a nut shell the article explains the problem is due to corrupt > start.elf file. They recommended You should be able to download start.elf > from here: > https://github.com/raspberrypi/firmware ... aster/boot > > and copy it on the SD card. > > Does this sound about right for ARMedSlack? > > Any thoughts or hints about this would be greatly appreciated. > > Thanks! > > Mr. B-o-B > > > > > _______________________________________________ > 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 Sep 7 19:43:25 2012 From: stanley at stanleygarvey.com (stanley garvey) Date: Fri, 07 Sep 2012 20:43:25 +0100 Subject: [ARMedslack] QEMU support - does anybody care about it? In-Reply-To: References: Message-ID: <20120907194326.24265611D770@bmail06.one.com> On Sep 5, 2012 14:38 "Stuart Winter" wrote: > > 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. > > I had a look and realised that to remove all the references to > Versatile, > and test the packages and installer would take more effort and time > than > to build the kernels and test it once or twice a year, so I'll leave > them > there. > Thank you. QEMU is a very useful tool. Without QEMU I would not have > been able to get SlackwareArm up and running on a Raspberry pi before > a proper installer existed. What would have been an impossible task > was made trivial with the QMEU support. Thank you for all your hard > work supporting Slackware on Arm. > _______________________________________________ > ARMedslack mailing list > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From frank at thor.baldar.de Fri Sep 21 12:28:47 2012 From: frank at thor.baldar.de (Frank Boehm) Date: Fri, 21 Sep 2012 14:28:47 +0200 (CEST) Subject: [ARMedslack] Raspberry Pi summary of my first installation Message-ID: Hello, got my 2nd Pi from Farnell before my 1st one from RC arrived. Tested with the official Raspibian image. Everything worked. apt-get udpate; apt-get upgrade Used the running Raspbian Image to create my slackware without the slackware installer. my summary for the raspberry if you just have the official raspbian image and a mirror of armedslack: Put a 16GB sdcard in a card reader and created three partitions with cfdisk: 1. 512MB fat32 2. 1GB swap 3. rest of card ext3 and not ext4! mke2fs -j -I128 /dev/sda3 copied the first partition /boot of the Raspian Image to the first partition on the sd card. mounted a mirror of armedslack with nfs from a lan server on /mnt/armedslack and /dev/sda3 of the card reader to /mnt/root. installed 4 packages on raspbian, cd / tar xvzf /mnt/armedslack/armedslack-current/slackware/a/pkgtools-*.tgz ; sh ./install/doinst.sh ; rm -rf ./install tar xvzf /mnt/armedslack/armedslack-current/slackware/a/tar-*.tgz ; sh ./install/doinst.sh ; rm -rf ./install tar xvzf /mnt/armedslack/armedslack-current/slackware/a/xz-*.tgz ; sh ./install/doinst.sh ; rm -rf ./install tar xvzf /mnt/armedslack/armedslack-current/slackware/a/findutils-*.tgz ; sh ./install/doinst.sh ; rm -rf ./install export ROOT=/mnt/root changed the link in /bin for sh from dash to bash change directory to my nfs mount of the slackware mirror and started my installation: installpkg */*t?z everything was ready the next morning for breakfast, flash is cheap, installed kde, I don't plan to use it, but I will need qt copied /etc/fstab of the raspian Image to my slackware Installation, and copied /lib/modules to my slackware /mnt/root/lib/modules changed fstab and boot/cmdline.txt from the 2nd partition to my 3rd partition and added ro changed inittab, but you don't have to for the first start chroot to /mnt/root and called pkgtool fired up with the slackware sd card and was happy, thank you for armedslack or slackwarearm slackware-current is ok for me, but I had one caveat, had to use udev from 13.37, couldn't use gpm and keyboard/mouse in X otherwise have fun, cu Frank PS: I'm keeping a local mirror of slackwarearm rsync -Pavv --delete li-la.de::slackwarearm/armedslack-13.37 . rsync -Pavv --delete li-la.de::slackwarearm/slackwarearm-current . ftp://li-la.de/pub/slackwarearm http://li-la.de/pub/slackwarearm PSS: I have read INSTALL_RASPBERRYPI.TXT will look in the raspi packages and hacks just want to keep it basic for starters PSSS: I'm using a hdmi2vga adapter for my old 16:10 LCD for 1680x1050 -- Mohandas K. Gandhi often changed his mind publicly. An aide once asked him how he could so freely contradict this week what he had said just last week. The great man replied that it was because this week he knew better. From m-lists at biscuit.org.uk Fri Sep 21 13:03:43 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 21 Sep 2012 14:03:43 +0100 (BST) Subject: [ARMedslack] Raspberry Pi summary of my first installation In-Reply-To: References: Message-ID: [..] > installed 4 packages on raspbian, cd / > tar xvzf /mnt/armedslack/armedslack-current/slackware/a/pkgtools-*.tgz ; sh > ./install/doinst.sh ; rm -rf ./install > tar xvzf /mnt/armedslack/armedslack-current/slackware/a/tar-*.tgz ; sh > ./install/doinst.sh ; rm -rf ./install tar xvzf > /mnt/armedslack/armedslack-current/slackware/a/xz-*.tgz ; sh > ./install/doinst.sh ; rm -rf ./install > tar xvzf /mnt/armedslack/armedslack-current/slackware/a/findutils-*.tgz ; sh > ./install/doinst.sh ; rm -rf ./install export ROOT=/mnt/root I'd add to this to install a/aaa_base first, then a/aaa_elflibs; otherwise you might find some packages don't install properly because a install/doinst.sh script refers to a directory on the filesystem, but where the dir is not part of the package's tar archive (it's a rarity but does happen). From frank at thor.baldar.de Fri Sep 21 13:59:42 2012 From: frank at thor.baldar.de (Frank Boehm) Date: Fri, 21 Sep 2012 15:59:42 +0200 (CEST) Subject: [ARMedslack] Raspberry Pi summary of my first installation In-Reply-To: References: Message-ID: On Fri, 21 Sep 2012, Stuart Winter wrote: a/pkgtools-*.tgz ; sh a/tar-*.tgz ; sh a/xz-*.tgz ; sh a/findutils-*.tgz ; sh > I'd add to this to install a/aaa_base first, then a/aaa_elflibs; these four packages are installed in my raspian image, to be able to install slackware packages when I'm using installpkg */*t?z to install the slackware packages, they are sorted and a/aaa_base and a/aaa_elflibs are the first packages that are installed, I don't have to take extra care for that > otherwise you might find some packages don't install properly because > a install/doinst.sh script refers to a directory on the > filesystem, but where the dir is not part of the package's tar archive > (it's a rarity but does happen). or do you mean, these two packages have to be installed in raspbian too? I created a logfile for my installation and didn't get any errors have fun, cu Frank -- Lawrence J. Peter, Das Peter-Prinzip: "In einer Hierarchie steigt jeder solange auf bis er die Stufe seiner maximalen Inkompetenz erreicht hat." From m-lists at biscuit.org.uk Fri Sep 21 14:31:51 2012 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 21 Sep 2012 15:31:51 +0100 (BST) Subject: [ARMedslack] Raspberry Pi summary of my first installation In-Reply-To: References: Message-ID: > when I'm using installpkg */*t?z to install the slackware packages, they > are sorted and a/aaa_base and a/aaa_elflibs are the first packages that are > installed, I don't have to take extra care for that They may become unsorted, or sorted differently depending on your setting of LC_COLLATE. I was referring to installing them inside of your Slackware installation 'root' only. If I was documenting it or scripting it, I'd always add the aaa* packages first, specificially to avoid any file name sorting issues since I've had the problem in the past. If it works for you without doing so, great :-) From frank at thor.baldar.de Fri Sep 21 14:57:09 2012 From: frank at thor.baldar.de (Frank Boehm) Date: Fri, 21 Sep 2012 16:57:09 +0200 (CEST) Subject: [ARMedslack] Raspberry Pi summary of my first installation In-Reply-To: References: Message-ID: On Fri, 21 Sep 2012, Stuart Winter wrote: > They may become unsorted, or sorted differently depending on your setting > of LC_COLLATE. checked it beforehand and kept a logfile from my installation to be able to check for errors but all the file names of slackware distribution packages are plain ascii within the range of 32-127 and without special chars I can't imagine a LC_COLLATE value that can mangle this > If I was documenting it or scripting it, I'd always add the aaa* packages > first, specificially to avoid any file name sorting issues since I've had > the problem in the past. If it works for you without doing so, great :-) better on the safe side, it's always good to mention this /broken/ filenames are common in mp3 archives, where the file names are created from the mp3 tags, but I had never problems with original slackware package names cu Frank -- Hrothgar is also the name of the Danish king whose mead house Heorot was invaded by the Grendel, and all the warriors inside were killed. So Beowulf ripped off his arm (Grendel's, not Hrothgar's). Pre-English literature is so much better than the new stuff. From mozes at slackware.com Fri Sep 28 21:53:21 2012 From: mozes at slackware.com (Stuart Winter) Date: Fri, 28 Sep 2012 14:53:21 -0700 (PDT) Subject: [ARMedslack] Slackware 14.0 is released Message-ID: Hi! Slackware x86, x86_64 and ARM v14.0 is released today. Instead of pasting the same content as the web site, you can read it here instead :-) http://www.armedslack.org/ Happy release day and have a good weekend upgrading Stuart.! -- Stuart Winter www.slackware.com/~mozes Slackware for ARM: www.armedslack.org From louigi600 at yahoo.it Sat Sep 29 15:34:35 2012 From: louigi600 at yahoo.it (Davide) Date: Sat, 29 Sep 2012 16:34:35 +0100 (BST) Subject: [ARMedslack] Slackware 14.0 is released In-Reply-To: References: Message-ID: <1348932875.12332.YahooMailNeo@web29702.mail.ird.yahoo.com> Thanks for all the effort you've been putting into ARM slackware port over the years. David ________________________________ Da: Stuart Winter A: Slackware ARM mailing list Inviato: Venerd? 28 Settembre 2012 23:53 Oggetto: [ARMedslack] Slackware 14.0 is released Hi! Slackware x86, x86_64 and ARM v14.0 is released today. Instead of pasting the same content as the web site, you can read it here instead :-) http://www.armedslack.org/ Happy release day and have a good weekend upgrading Stuart.! -- 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 stanley at stanleygarvey.com Sun Sep 30 20:45:46 2012 From: stanley at stanleygarvey.com (stanley garvey) Date: Sun, 30 Sep 2012 21:45:46 +0100 Subject: [ARMedslack] Slackware 14.0 is released In-Reply-To: <1348932875.12332.YahooMailNeo@web29702.mail.ird.yahoo.com> References: <1348932875.12332.YahooMailNeo@web29702.mail.ird.yahoo.com> Message-ID: <20120930204548.42EB750C4D9BF@bmail06.one.com> On Sep 29, 2012 16:34 "Davide" wrote: > Thanks for all the effort you've been putting into ARM slackware port > over the years. > > > > > David > > > > > Da: Stuart Winter > A: Slackware ARM mailing list > Inviato: Venerd? 28 Settembre 2012 23:53 > Oggetto: [ARMedslack] Slackware 14.0 is released > > > Hi! > Attachments > Slackware x86, x86_64 and ARM v14.0 is released today. > > Instead of pasting the same content as the web site, you can read it > here > instead :-) > > > > Happy release day and have a good weekend upgrading > > Stuart.! > > -- > Stuart Winter > www.slackware.com/~mozes > Slackware for ARM: www.armedslack.org > _______________________________________________ > ARMedslack mailing list > > > > Oh Dear, looks like my Slackware-13.37 tee shirt is now retro ;-) keep > up the good work! > -------------- next part -------------- An HTML attachment was scrubbed... URL: