You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
||3 months ago|
|bin||5 months ago|
|distrib||4 months ago|
|etc||4 months ago|
|games||5 months ago|
|gnu||3 months ago|
|include||5 months ago|
|lib||4 months ago|
|libexec||5 months ago|
|regress||3 months ago|
|sbin||3 months ago|
|share||3 months ago|
|sys||3 months ago|
|usr.bin||3 months ago|
|usr.sbin||3 months ago|
|Makefile||5 months ago|
|Makefile.cross||5 months ago|
|README||5 months ago|
SecBSD's official source code repository.
Building SecBSD from source involves a number of steps:
* Upgrading to the closest available binaries.
* Fetching the source code.
* Building a new kernel and userland, as explained in steps 2 and 3 of release(8).
* Optionally, making a release and building X.
Active SecBSD development is known as the -current branch. These sources are
frequently compiled into releases known as snapshots.
Aggressive changes are sometimes pushed in this branch, and complications can
arise when building the latest code or upgrading from a previous point in time.
Upgrading to -current by compiling your own source code is discouraged for
everyone except for experts, as difficult build-time crossing-points can occur
often, and no assistance will be provided. In case of failure, use a snapshot to
How do I contribute to SecBSD?
We are looking for developers, C programmers, Unix architects, OS designers and
people interested to create a great project and hacker community.
To learn more please visit https://www.secbsd.org