Just bought a Raspberry Pi at the local electronics store from which I
reserved one a few weeks ago. Also bought an 8GB class 10 SD card.

Wrote the Arch Linux ARM image to the SD card, only to realize that
although sshd is running by default, root logins are not permitted, so I
couldn't even login to the device. Seriously... what's the point of
enabling sshd by default if you can't even use it to log in? I wasn't about
to unplug my monitor and keyboard and stuff, so I proceeded to modify the
SD card image and burn it again. I had to mount the original image and edit
/etc/ssh/sshd_config to add "RSAAuthentication yes PasswordAuthentication
yes PermitRootLogin yes", and then rewrite the image to the SD card.

If anyone wants to modify the SD card image before burning it to the SD
card (for whatever reason), here's how. On your host computer, do the
following:

1. Note the start sector offset for the main partition of the SD card
image. Mine was 194560 (sector size of 512B).
$ fdisk -l archlinux-hf-2012-09-18.img

2. Mount the disk image somewhere so you can edit it.
$ sudo mount -o loop,offset=3D$((512*your noted offset))
archlinux-hf-2012-09-18.img mnt

3. Make your changes, unmount, and burn the modified image to the SD card.

Booted up again. Good, finally logged in via SSH - only to realize that
Arch Linux ARM desecrated the Arch Linux philosophy of "keeping it simple"
by replacing /etc/rc.conf with systemd. I loved the BSD-style init - that
was like, half the point of Arch Linux. These guys replaced it with some
silly init program that makes it just as complicated as SysV init. Why? Why
would you guys do that? This is precisely why I *didn't* want to install
Debian.

Anyway, Arch Linux boots up in less than 10 seconds and works well here.
Everything looks good so far.
--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.