If you'd followed my install guide step-by-step then you would've already copied the rootfs tarball (in its unextracted form) onto your SD card but I presume thats not the case here.
Think I must have deleted the file at some point as the 2GB card was almost full..... will make a new backup SD card on a larger capacity card.....
Think it would be good if you mention in your instructions page that card should be larger than 2GB to allow for keeping various package files on it.
The bit of terminal output you pasted showed you trying to download the tarball but where to, direct to the SD card? It says it cannot write to the current device so either:
* You didn't run the command as root
* There isn't enough space on your SD card or
* Your SD card is write protected
One of those was most likely tripping you up.
Yep, you're right, not enough room on the SD card as noted above.....had to delete a bunch of other package files to free up space to be able to put the rootfs file back on the card....
I wonder if daal will return now the rugby is over (and they won, again, of course)?
OK, that explains it......
EDIT
If you do end up doing a re-install / upgrade Mark it would be useful for us if you tried out systemd 226-3. You may be better off with that than running 226-2 and you may not need the IgnorePkg?
OK, will do......
Reinstalling Arch now......
Hey gang. I gave this a go today.
I ran into some issues with the KEXECBOOT updater not working on my Zaurus. I wound up having to do a complete NAND restore to factory settings to be able to install KEXECBOOT. The SD / CF updater would always fail.
After doing that, I was able to at least install KEXECBOOT and boot into ALARM on my CF card.
I then attempted to replace the internal 4GB microdrive with a 64GB microSD card housed in a Type 2 CF to MicroSD card adapter. I had planned on setting up the internal drive from the CF install of ALARM but to my surprise ALARM would not boot properly after putting in the new internal drive. I suspect that KEXECBOOT (or the NAND app) writes some data to the partitions on the Microdrive normally.
So I took out the internal CF / MicroSD card and partitioned it so that the two Sharp original partitions and files (.SYS directory) were on the new card.
I had planned on reinstalling from scratch (reinstall KEXECBOOT, etc) but even after the new partitioning of the SD / CF adapter, the KEXECBOOT install script tells me the microdrive is not found. Suxxor.
I'll continue with it some time next week. I don't know much about Arch Linux (avid OpenBSD user) so I'll have to learn the ecosystem. It's different enough for me to not know how to do a majority of the stuff I'd like to.
Glad you finally gave it a go, but sorry to hear of your issues.....
Regarding your 64GB card issue......wondering if either
a. Issue with system recognizing such a large card
or
b. Issue with system dealing with an adapter with card in it?
Arch is definitely different than using OBSD.....but with your background in it plus the info and resources here and on Arch Wiki pages, I'm sure you'll make the transition pretty quickly......
Keep us posted.....