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 arc
> 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.
e? That is the search engine is
> aware of the archival site for the list?
> -
> Gregg C Levine gregg.drw...@gmail.com
> "This signature fought the Time Wars, time and again."
>
>
> On Thu, Nov 21, 2013 at 10:35 AM, Stuart Winter
> wrote:
> >
> > Hel
x27;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 W
ckware.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
___
ARM
o a similar error.
>
> ATB
> David
>
>
>
>
> Il Domenica 17 Novembre 2013 3:04, "openpand...@free.fr"
> ha scritto:
>
> Thanks !
> I appreciate.
>
> - Mail original -
> De: "Stuart Winter"
> À: "Slackware ARM port"
> 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
>
> I think that's the root cause ...
> I'm not sure on this but I suppose the kernel ai
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 t
18)
[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
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists
> "'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).
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
>
> > Also seamonkey and thunderbird ?
>
> I wasn't planning on it any time soon - they have been removed from 14.1 -
> check the change log.
I have updated Firefox and it'll go out with the RC3 push today.
I will update the others you mention as time permits, but that may be
after the 14.1 releas
Hello
> Also seamonkey and thunderbird ?
I wasn't planning on it any time soon - they have been removed from 14.1 -
check the change log.
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedsla
[..]
> 2) This morning I did a "slackpkg update-all" and got the 3.10.17 kernel
> update. The package updated successfully deleting the 3.10.16 files and
> installing the correct symlinks, but I did notice that the dtb-3.10.16
> directory was not deleted although the dtb symlink was updated to po
x27; section here:
http://docs.slackware.com/howtos:hardware:arm:start
--
Stuart Winter
Slackware ARM: http://arm.slackware.com
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
Hello
As the subject says - it's rc1 is now released.
Please have a look at it (preferably using a new installation) and let me
know if there are any issues.
Thanks
s.
--
Stuart Winter
Slackware ARM: http://arm.slackware.com
___
ARMedslack ma
>
> Would it be possible to add the following offsets in the stock
> /etc/fw_env.conf file?
Yes I've added it into the config file and it'll be pushed out in the next
batch.
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armeds
he link:
> http://git.linaro.org/gitweb?p=arm/xorg/driver/xf86-video-armsoc.git
I've updated this to the latest snapshot.
--
Stuart Winter
Slackware ARM: http://arm.slackware.com
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http
anyway.
I don't have any Allwiner machines, but I did add some Allwinner SoC
configs into the Linux 3.10 kernels. If there are any patches, I could
apply them to Linux 3.10. I think we'll be using Linux 3.10 for the
Slackware 14.1 release. I did try Linux 3.11 but it wa
> I'm making some test compilations with -current, using sbopkg, and i
> have a ton of non-downloads because of missing https certificates.
> Anyone else experiences this ?
Missing HTTPs certificates where? if it's on the server to which you're
connecting, then contact the administrator of that s
t I was trying to say. Different story if you want me
> to add it to the non officially supported platforms section on the
> http://arm.slackware.com/supportedplatforms/ page.
I've moved the community platforms and linked it from that page, so the
community can
apart
> from manipulating the flash.
I didn't fix 14.0. I'll fix it before the next batch goes out.
--
Stuart Winter
Slackware ARM: http://arm.slackware.com___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armeds
s to be modified in inittab?
http://ftp.arm.slackware.com/slackwarearm/slackwarearm-current/source/a/sysvinit-scripts/sources/doinst.sh.openttyS0
Could the change be added into here? The less changes you have to keep
adding in the better - especially when I'm already doing it for the
others!
AC100 site and my short how-to as a specific tutorial
> on a possible way to get Slackware ARM on the AC100.
> The link in http://arm.slackware.com/supportedplatforms/ still only points
> to http://ac100.grandou.net/
I'
content easier to
find although it may break up the structure of the site a little bit.
--
Stuart Winter
Slackware ARM: http://arm.slackware.com
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
>
> Would http://docs.slackware.com or http://slackwiki.com be a good place
> to put this in ? Regards David
docs.slackware.com is the best place, IMO. alienBOB is keen to have more
docs there! :-)
___
ARMedslack mailing list
ARMedslack@lists.armedslack.
essentially becomes the gate keeper so has to be
able to dedicate some time to folding requests and fixes back in to the
distributed images.
Thoughts? Any takers?
--
Stuart Winter
Slackware ARM: http://arm.slackware.com
___
ARMedslack mailing list
A
> > There's probably something wrong with me or with my browser or some other
> dumb thing ... but I recognize a menu that's resembles remotely what used
> to be on tosh-ac100 ... but I looked on every element of the menu and could
> not recognise my armedslack (it was not slackware arm at the tim
is shouldn't be a reason for the 14.1 release -
you should treat this as new rather than a patch to someone else's work
(even
if that's what it started out as).
Deadline:
-
I'll stop taking submissions at the release of RC1 of Slackware 14.1 x86.
auto"
WLAN_CHANNEL[4]="auto"
WLAN_KEY[4]="YOURWLANKEY"
#WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set
WPAPSK=YOURWLAKEY"
WLAN_WPA[4]="wpa_supplicant"
WLAN_WPADRIVER[4]="wext"
WLAN_WPAWAIT[4]=10
-
ebook), but might be useful.
--
Stuart Winter
Slackware ARM: http://arm.slackware.com
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
On Thu, 18 Apr 2013, Davide wrote:
> So I updated the uboot image with the install script (I did it by hand
> the first time around and I;ll savemyself the trouble if possible) and
> nor the kernel gets loaded properly. I still have an issue concerning
> that the root filesystem on the usb stick i
latest Kirkwood kernel on a Plug machine, but I know
it does work on the OpenRD client. I added the 'earlyprintk' debugging to
the Tegra20 kernel which'd show you what was wrong, but I don't think this
is available in the kirkwood implementation (although I'll
On Tue, 16 Apr 2013, Davide wrote:
> Well actually on my live slackware 14 (x86) vi is a link to elvis
>
> Although both are installed, by default vi is linked to elvis (and it's
> not something I did manually). looking at the sizes I cannot but agree
> that on the miniroot vim is just eating up
th elvis as this works without bundling
additional packages.
--
Stuart Winter
Slackware ARM: http://arm.slackware.com___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
> Segfault:
> [ 372.736] (II) omapfb(0): XRandR extension initialized
> [ 372.736] (--) omapfb(0): Virtual size is 800x1440 (pitch 800)
> [ 372.736] (**) omapfb(0): Mode "720x574": 13.5 MHz, 15.6 kHz, 25.0 Hz
> [ 372.736] (II) omapfb(0): Modeline "720x574"x25.0 13.50 720 732 788 864
>
> Tired your package. Same result as mine:
What about the fb versio?
http://armed.slackware.com/slackwarearm-current/test/x/xf86-video-omapfb-0.1.1.1-arm-1.tgz
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mail
> > The omap driver isn't included in Slackware ARM:
> > http://cgit.freedesktop.org/xorg/driver/xf86-video-omap/
> >
>
> The source is in the "slackware64-current/source/x/x11/src/driver"
> repo. can you build it from there? (And is it supposed to work on
> ARM?)
It builds...
http://armed.slack
> Just saw it's in /extra .
The 'patches' directory is only used once a tree has been marked as
a stable release.
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
o see some Rpi kernel upgrades to the
latest release -- is the Rpi support not yet in the upstream kernels?
--
Stuart Winter
Slackware ARM: http://arm.slackware.com
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
.1. Is there anyone who's distributing anything that's older than
this version? It looks like I'll need to respin glibc to change the
mimimum kernel to be 3.1.0 so that RPi users can upgrade to Slackware ARM
14.0 to 14.1.
--
Stuart Winter
www.slackware.com/~mozes
Slackware for A
n't
really a candidate for your favourite OS - it's just about what apps you
can install upon it; thus it would never cross my mind to want to install
Slackware on my ARM powered phone.
--
Stuart Winter
Slackware ARM: http://arm.slackware.com
___
> On the other hand if you release a new rootfs say every month, all that a
> smart user has to do is umount /home and untar the new rootfs over the old
> one and some post install cleanup. Alternatively they can be educated to
> update properly.
Untarring would lead to cruft lying around which w
On Sun, 31 Mar 2013, Ottavio Caruso wrote:
> The default method now is to untar a rootfs, there's no point using an
> installer. That is a remainder of the pc world. I did try it though and may
> recall it didn't work.
For me, the reasons to use the installer are:
1 - Someone has to provide root
> Are you using the default chrome os kernel or is it a native one?
The default one at the moment but if I make the work public, I'll have
built my own 3.4.0 from the ChromeOS Git repo.
I do keep my notes in the 'slackwarearm-devtools/chromebook' dir on the
FTP site though. It's a bit random at
media efficiently.
That said, for general usage (non multi media) I really don't think
there's much in it with soft vs hard float. Running Firefox and some
other stuff on this Chromebook is *fast* even with the default Slackware
ARM packages.
--
S
> The build order of Slackware is not deterministic - the distribution evolves
> upon itself.
> There is no sort of 'make world' type script.
I was just looking at the comments I put in the bootstrap script that I
wrote for Slackware ARM's x11 packages:
As you can see, it's not a simple affair.
> Just a quick one, is there a top level script / slackbuild esq script that
> starts a build of a complete Slackware distro ?..
The build order of Slackware is not deterministic - the distribution evolves
upon itself.
There is no sort of 'make world' type script.
Eric's documenting his build p
> Now i would like to use the toolchain directly on my x86 64 bit host.
> For instance, i'd like to compile a kernel for ARM. I'd also like to use
> the other ARM distcc on my network.
>
> How do i setup the pathes, launch the stuff etc ?
You don't. It's not a full cross compiler - as it says in
t again can you up it somewhere? I might be able to
> > work something from it.
> >
> > I'll try to look for instructions from other distros and if I arrive at a
> > working solution, I'll try to post it.
> >
> > Regards,
> > Sam
> >
&g
> I would like to respond to
> http://lists.armedslack.org/pipermail/armedslack/2013-February/001548.html ,
> but
> as i never used a mailing list (i'm more a boards or mail guy), i don't know
> how.
As you're a new joiner who doesn't have their own local copy, the only way
you can do that is b
e entire life time of
"-current" up until the next release, then it will never appear in the
ChangeLog.txt for that release. However, it may appear in "patches" if a
security patch appears after the release is made.
This isn't the reason why OpenJDK isn't in Slackware A
> So an installer of some description could be performed, perhaps the
> simplest would be a pxe boot to boot a minimalistc image to bring up the
> 10/100 ethernet and install over the internet from a repo.
Have you had a chance to look through the INSTALL_* docs in the main tree
yet? This will g
Hi Nigel,
> So maybe do an image that then starts off running the ncurses slackware
> configuration tool to setup networking / wifi etc etc. may require some
> changes / additions for wpa_supplicant. Under all distro's ive tested with
> none deal with wpa_supplicant, so it requires manual editi
ook
at the miniroot build script.
I can help with the Slackware installer stuff where need be.
--
Stuart Winter
Slackware ARM: http://arm.slackware.com
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
Hi
> The file "/usr/bin/slocate" has wrong permission. Could this be corrected?
Thanks I'll put that out in the next patch batch.
The fix is this change:
chown root:slocate /{var/lib/slocate,usr/bin/slocate}
chmod 0750 /var/lib/slocate
chmod 2755 /usr/bin/slocate
--
Stuar
h, it is a pity that it remains unused
> when it could be used as the root partition.
I think I've seen it documented a couple of years ago and shouldn't be too
hard to setup.
Robby - I think you did this on your Guruplug didn't you?
--
Stuart Winte
#x27; definitley needs a
machine with a HFPU, but may or may not also contain the armv7 NEON
instructions.
Needless to say I am pleased to have dropped Mozilla. What a ball ache
that thing was with every release.
--
Stuart Winter
Slackware ARM: www.armedslack.org
___
build.
> > Also needed to upgrade to /a/usbutils.006 as source not in
> > slackware64
ls slackware64-current/source/a/usbutils/
slack-desc usbutils-006.tar.xz usbutils.SlackBuild* usbutils.url
--
Stuart Winter
Slackware ARM: www.armedslack.org
compiled for 3
> > > > days the got stuck with ld in deep sleep 98%wait.
> > > > so I might want to x-compile that one. Thanks for the great slackit!
>
> I don't cross compile it and it works for me - takes an hour or less to
>
to
build, IIRC. Perhaps you don't have enough RAM on your machine?
--
Stuart Winter
Slackware ARM: www.armedslack.org
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
ge when
x-compiling.
> The big problem is setting the appropriate switches.
Once you know what systems you're targetting, it's easy.
--
Stuart Winter
Slackware ARM: www.armedslack.org
___
ARMedslack mailing list
ARMedslack@lists.armedslack
is is the same CPU as the Raspberry, so check what everyone else's
using for the RPI.
--
Stuart Winter
Slackware ARM: www.armedslack.org
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
> There is a difference in file permissions of /var/lib/php/ between slack and
> armed slack:
[..]
Thanks Hans, I know why that is. I'll put out a patch package for 14.0 &
a -current update soon.
--
Stuart Winter
Slackware ARM: www
e ARM's.
You can find his email address here: http://www.slackware.org.uk/
--
Stuart Winter
Slackware ARM: www.armedslack.org
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
need to work on how to upgrade
> the system and preserve my content...
It doesn't matter what version of gcc you build the kernel with really, as
long as it's reasonably recent. You'd need a cross compiler anyway,
which is independent from the host toolchain.
Unless you wa
to lucid dreaming where they can act the stuff
out again, as far as I can tell.
Vi? heh. I wish '!Zap' could be ported to Linux.
http://zap.tartarus.org/screenshots
It was the best editor in the entire solar system.
--
Stuart Winter
Slackware ARM: www.armedslack.org
___
Also, it just occurred to me that an App Store isn't much different from a
big 5.25" floppy disk containing loads of BASIC programs you could load in
and run.
The concepts are the same, just the name and the format changes.
--
Stuart W
7;ve read, they
want to try and provide a system on which youngsters can develop software,
scripts and so on. On the BBC, we had direct access to BBC BASIC and 6502
Assembler. People made some great software in BBC BASIC, and it's where I
learnt started learning about programming and computer
itful,
where did you get the 2010 firmware from?
--
Stuart Winter
Slackware ARM: www.armedslack.org
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
atch the init script to accept both parameters.
--
Stuart Winter
Slackware ARM: www.armedslack.org
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
So your issue is your u-boot parameters:
http://pastebin.com/XLyCFiGV
[0.00] Kernel command line: console=ttyS0,115200 root=/dev/sda3
rootdelay=10 rootfstype=ext4
mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
It should be 'rootfs=' not 'rootfstype='.
Also Slackware's i
> > When I had a similar problem myself, I unpacked the kirkwood's initrd and
> > put in the classic "print" statements into the init script to find out
> > where it was broken.
>
> I've built my own kernel now (same version like 14.0 and based on your
> config). I've just added the needed drivers
> On 30 November 2012 13:03, Thorsten Mühlfelder wrote:
>
> > 4. changed some U-Boot settings to match my USB stick (rootfs=sda3, ext4)
>
> I am not familiar with that device but shouldn't you add "rootwait" ?
Yes - try adding that.
The fact that it worked with 13.37 doesn't really mean a lot,
> > Exactly - if your WLAN is secured (most likely) then you'd need another
> > service to help bring up the interface, so it doesn't seem that there's
> > any value in adding this at boot.
> >
>
> But would it bring mlan0 up anyway, instead of typing:
> ifconfig mlan0 up
I don't think it'll make
't seem that there's
any value in adding this at boot.
--
Stuart Winter
Slackware ARM: www.armedslack.org
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
> But while booting the initrd system fails to mount the rootfs. You can find a
> complete log here:
> http://pastebin.com/XLyCFiGV
You have four partitions not 3. What is on /dev/sda4?
Is your /etc/fstab setup?
You have a root shell there - can you share what you have done to
investigate it?
> slackbuilds.org has a few versions of fltk - perhaps you can compile it?
>
> http://slackbuilds.org/repository/14.0/libraries/fltk/
I'm in the giving mood ;-)
http://armed.slackware.com/misc/
It got me thinking that it'd be great to have a set of the most commonly
requested packages from SBo
On Fri, 23 Nov 2012, Davide wrote:
>
> Anyone know where to get an arm binary for fltk-1.1 that also works on
> Slackware ARM 14 ?
slackbuilds.org has a few versions of fltk - perhaps you can compile it?
http://slackbuilds.org/repository/14.0/libraries/fltk/
--
Stuart Winter
Slac
ike is on about though regarding supporting ARM hard
float. You don't "migrate away" to hard ware floating point, as then you
cannot support the devices that do not have a hardware floating point
unit.
--
Stuart Winter
Slackware ARM: www.armedslack.org
__
> > You might not have that symlink.
> > root@pepa:~# ls -la /lib/ld-linux.so.3
> > lrwxrwxrwx 1 root root 10 Nov 12 10:01 /lib/ld-linux.so.3 -> ld-2.15.so*
>
> localhost / # find / -name ld-linux.so.3
> localhost / #
>
> localhost / # find / -name ld-2.15.so
> /lib/ld-2.15.so
>
> localhost / # ls
10:01 /lib/ld-linux.so.3 -> ld-2.15.so*
It also might be that the kernel is unable to execute soft float binaries.
--
Stuart Winter
Slackware ARM: www.armedslack.org
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.or
> Thanks, the problem is I don't have cpio on Chrome OS. I am working on
What stops you from downloading the package and extracting the cpio
binary?
You can clearly mount an external device, so I'm not really sure what the
issue is.
___
ARMedslack mailin
tile image:
mkdir installerdir
cpio -di < ../Downloads/initrd-versatile
--
Stuart Winter
Slackware ARM: www.armedslack.org
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
> before I attempt to so something stupid, would it work if I mounted
> the Slackware installer initrd onto Chrome OS and then I attemped an
> installation on a local partition? (Yes, I know it's not elegant, but
You wouldn't mount it, you'd just unpack it into a dir and chroot
into it.
You'd n
> I am not even sure this is the right package but anyway, I have
> unpacked this zip file into my home directory. I think I have
> installed all dependencies but the only unfullfilled one is
> libjppeg.so.62.
libjpeg6b isn't included in Slackware which is why it's not available.
I compiled it a
Hi
The rsync module 'armedslack' has now been removed from ftp.armedslack.org
If you have the 'armedslack' name in any config files or scripts, now's
the time to rename it 'slackwarearm'
Cheers
s.
--
Stuart Winte
It's patch-o-rama this week!
> I copied the rt2* and rt3* firmware files from /lib/firmware on my laptop to
> the trimslice and that fixed the problem. Wireless interface is now up.
I did wonder if anybody'd ever notice that I was bundling the firmware
from the kernel source tree rather than th
other people's kernels. If there is, I'll be getting one of these as it
matches my goal of having a laptop running Slackware ARM.
But then the dream will be fulfilled so I might have to stop working on
Slackeare and get a new hobby ;-)
--
Stuart Wi
On Tue, 30 Oct 2012, chekkizhar N wrote:
> ok. I will wait and meanwhile will do searching as Stuart told.
> I got this mail today [30/10/2012 in India ] only.
> But, the question and the reply was made on that day [ Sun, 21 Oct 2012 ]
> itself.
> So, what went wrong?
Time zone config on the l
Thanks - I'll be putting out a patched package in 14.0 that contains Xvnc.
--
Stuart Winter
Slackware ARM: www.armedslack.org
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
On Sun, 21 Oct 2012, chekkizhar N wrote:
[..]
> 1. Created soft link, uImage, which points to uImage-kirkwood-2.6.38.4, in
> /etc/boot dir.
> 2. Edited the console port number to ttyS2 from ttyS0 in /etc/fstab file
/etc/boot? what is using /etc/boot ?
serial console in /etc/fstab? I assume you
> before I had my own Xvnc I used x11vnc, but I need Xvnc for xrdp
> # CAUTION: make raspberrypi X server accessible without password!
> /usr/bin/x11vnc -display :0 &
x11vnc is in /extra already and works for me.
Is there something wrong with it?
--
Stuart Winter
[..]
> I'll add the new packages into patches in 14.0.
Done!
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
ifysign/s verify/s
dsa 512 bits 0.000886s 0.000960s 1128.6 1041.7
dsa 1024 bits 0.002722s 0.003172s367.4315.3
dsa 2048 bits 0.009785s 0.011479s102.2 87.1
I'll add the new packages into patches in 14.0.
--
Stuart Winter
Slackware ARM: www.armeds
[..]
> I think it might be that the variable inside u-boot has changed. I don't
> don't have an ESATA Sheevaplug, and would have had to look up the arch
> numbers from another source -- which I assume were correct at the time.
Yes that's what's happened - this is the upstream version, as it says
Hi Michael,
Thanks for your mail.
[..]
> U-Boot:
> It seems like you can't boot the new kernel that is delivered with Slackware
> 14.0 (3.4.11) with an older U-Boot version (mine was from mid 2011, iirc). The
> bootup process will hang after "Uncompressing linux kernel...". My first guess
> was
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
> 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.
[..]
> 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
> /
1 - 100 of 374 matches
Mail list logo
