Snapshots

4mig4 edited this page Mar 30, 2016 · 6 revisions

Table of Contents

Snapshots

Snapshots are currently built from master branch sources, every week on Sunday (note that build machines are in GMT-5) and pushed to the mirrors on Mondays. A weekly snapshot may not be available depending on issues encountered during the scheduled build.

Mirrors

Currently, there are 4 mirrors serving snapshots via HTTP(S) or FTP or RSYNC depending on the server

Chicago, IL, USA
http://mirror2.us.bitrig.org/pub/bitrig/
Harrisonburg, VA, USA
http://mirror.jmu.edu/pub/bitrig/
ftp://mirror.jmu.edu/pub/bitrig/
Norway
http://bitrig.antarctica.no/
Japan
http://mirror1.jp.bitrig.org/pub/bitrig/
https://pub.allbsd.org/bitrig/
ftp://ftp.allbsd.org/pub/bitrig/
rsync://rsync.allbsd.org/bitrig-ftp/

Mirror Hierarchy

All Bitrig mirrors have the same hierarchy, with pub/bitrig/ being the top level directory. The layout is roughly as follows:

  • pub/bitrig/ - Top level.
    • releases/ - Currently empty as no release has been made.
    • snapshots/
      • ${ARCH}/ - amd64 (x86_64) / i386 / arm (Coming soon!)
        • ${DATE}/ - A full binary snapshot with a packages subdirectory created on ${DATE}.
        • current/ - The most recent snapshot - Usually a symlink to the most recent ${DATE}.

Getting started with a snapshot

Users familiar with OpenBSD should recognize the sets, but keep in mind that Bitrig only has two base system sets, that is baseXY.tgz and etcXY.tgz along with the well known X sets.

The most straightforward way to install Bitrig is either via PXE booting of bsd.rd or by using the cdXY.iso.

Something that might suprise BSD users is the fact that by default, Bitrig does not ship with a toolchain, as it has been moved into the ports system. This is a consequence of a few factors

  • Bitrig switched from using GCC as the system compiler to LLVM, so there has been a fair deal of flux in the build toolchain
  • Managing the new dependencies introduced by using LLVM as the system compiler is much easier using the ports infrastructure than importing it into base
  • By keeping the build toolchain outside of base it is not necessary to worry about the license on the toolchain components
For further information about the toolchain and getting started with Bitrig development see the current issues page.