FreeBSD Images for Beagle Bone and Raspberry Pi ARM-based Hardware
These are images build using Tim Kientle's Crochet-FreeBSD build scripts. This site hosts recent images with certain customizations for the Raspberry Pi and Beagle Bone, both the white and black versions.
This is a New York City *BSD User Group-based project run by a couple of its members. The server is colocated in the NYC*BUG cabinet at New York Internet in Manhattan.
We want to make FreeBSD, not to mention the other BSDs, easy to install on these two ARM-based devices.
• Raspberry Pi Image for an SD Card
nycbug-fbsd-rpi.img.gz Subversion revision number sha256 checksum
• Beagle Bone Image for a microSD Card
nycbug-fbsd-bbone.img.gz Subversion revision number sha256 checksum
Checksums are (supposed to be) unique strings that provide a fingerprint of a file. A file's integrity can be judged by the checksum value. A single bit change in a file will change the checksum. Verifying the checksum of a download, like one of the images, is the best way to ensure the integrity of the file.
After you download the image, we recommend you do a checksum confirmation on the image. Not only will it ensure the image you downloaded is the one you intended to download, but a valid checksum will confirm that the image is uncorrupted.
NOTE: Veryifing the checksum on confirms that the asc checksum matches the checksum of the downloaded file. It assumes the server hasn't been compromised.
$ sha256 filename.img
Of course replacing file name with the downloaded image's name. Compare the output to the asc checksum value accompanying the file. It matches? Well, you're in business.
$ gunzip nycbug-fbsd-bbone.img.gz
Which outputs nycbug-fbsd-bbone.img. Then we'll put it onto the microSD card, which is the disk used by the Beagle Bone.
$ dd if=nycbug-fbsd-bbone.img of=/dev/da0 bs=1m
In this example, the input file ("if") is the image name, and the output file ("of") is the first direct access device labeled "da0", with "bs" indicating the block size. Unix-like operating systems use different file names for the direct access devices. For FreeBSD and DragonFly BSD, it's a da(4) device. For NetBSD and OpenBSD, it's sd(4). On OSX, look at the disks in /dev, and figure it out from there. For other operating systems, please wade carefully through the documentation.
The images are rebuilt daily with FreeBSD-CURRENT (10-) source. Overall these are "stock" images, i.e., they are built from the source using scripts from Tim Kientzle. Any and all mistakes with the images are either caused by our own foolishness or solar flares. They provided the tool, and we use to make and sometimes break things. There are, however, some modifications in the overlay files and in the build source:
Once the image has been written to the particular flash media, boot the ARM board. Without going into the details here, you can access the board through USB serial with cu(1). The BeagleBone Black requires a special serial cable available from a number of vendors. The Raspberry Pi provides an HDMI port or RCA out to connect via analog display, with a USB keyboard.
There is a proliferation of ARM-based boards. They are getting cheaper with better specifications. More boards, however, means more development work and the more difficult it may be to utilize standardized build scripts. But who knows? Feel free to send us a Cubieboard or a Pandaboard if you want to see this happen sooner than later.
And we're even considering creating images based on specific network functions, such as caching DNS or monitoring with something like sysmon.
Yes, it's a big hole here. The site is meant for people without a FreeBSD box, but we don't account for Windows. This is not meant to be petty or deliberate. It's on the to-do list.
Ideally, we would like to not just host stock images of FreeBSD. It would be nice to add images for NetBSD's "ARM evaluation boards" or "evbarm" port for the Beagle Bone and Raspberry Pi, which is the only other BSD we are aware of that is actively porting to these particular ARM boards.
OpenBSD seems unlikely to provide official support for the Raspberry Pi as per Theo de Raadt. But if you feel compelled to knock him and the OpenBSD project about this, then why don't you remove OpenSSH from all your boxes and devices? Their "attitude" means that you are not handcuffed with your SSH server and client today with restrictive licensing and fees. You could always just use rlogin or telnet. On that note, maybe thank them for their attitude while you're contemplating that fact.
We are building 2G images, but AutoSize is enabled, and 500M swap files are created. On boot, the root partition will expand to the full available space on the media. And if there is appropriate space, a 500M swap file is created on this disk at /usr/swap0
We are not responsible for any damage, hardship or heartaches caused by these operating system images. If your device gets fried, splatters Pb and kills your cat(1), it is your risk, and not our issue. Although we would love to see pictures of the cat after such a calamity. These images are provided solely for entertainment and testing purposes. If it's not fun, please stop what you're doing and find another line of work and/or hobby.
Comments? Questions? Don't ask us. Jump onto the NYC*BUG talk list and chime in. Okay, okay, if there is something specific to this site and the images, then we can be indirec tly pinged at mirror-admin AT nycbug DOT org. We might even reply.
We are two highly paper certified front-end web designers focused on presentation and client-side scripting based applications. We stick to "client-side" scripting since we'd rather waste your CPU cycles than those in the data center. The color palette selected for this site reflects our decades of experience. Observant web site visitors will note that we utilize both colors: black and white, in addition to their synthesis, grey. We are unclear why some text happens to be blue. We are open to enqueries about professional services for our front-end skills.
A huge thanks to the following people, parties, entities, projects:
To learn more about the other lost souls who come here, visit our Site Statistics
Yes, this site was done entirely in vi(1), the only web site creation software we needed. And the only one we know.