Node:Building, Next:Build Problems, Previous:Requirements, Up:Installation
Once you have setup your system as described in Requirements, you are ready to build SFS.
sfs. For instance, you might add
the following line to /etc/passwd:
sfs:*:71:71:Self-certifying file system:/:/bin/true
And the following line to /etc/group:
sfs:*:71:
Do not put any users in sfs-group, not even root. Any user
in sfs-group will not be able to make regular use of the SFS file
system. Moreover, having an unprivileged users in sfs-group
causes a security hole.
% gzip -dc sfs-0.6.tar.gz | tar xvf - % cd sfs-0.6
If you determined that you need gmp see Requirements, you should
unpack gmp into the top-level of the SFS source tree:
% gzip -dc ../gmp-2.0.2.tar.gz | tar xvf -
CC and CXX environment variables to point to the C
and C++ compilers you wish to use to compile SFS. Unless you are using
OpenBSD-2.6, your operating system will not come with a recent enough
version of gcc see Requirements.
./configure. You may additionally specify the following
options:
--with-sfsuser=sfs-user
sfs. Do not use an
existing account for sfs-user--even a trusted account--as
processes running with that user ID will not be able to access SFS.
[Note: If you later change your mind about user-name, you do not
need to recompile SFS, sfs_config.]
--with-sfsgroup=sfs-group
--with-gmp=gmp-path
configure should look for gmp (for example,
gmp-path might be /usr/local).
--with-sfsdir=sfsdir
/var/sfs. [You can change this later, sfs_config.]
--with-etcdir=etcdir
/etc/sfs.
--datadir=datadir
/usr/local/share.
configure accepts all the traditional GNU configuration
options such as --prefix. It also has several options that are
only for developers. Do not use the --enable-repo or
--enable-shlib options (unless you are a gcc maintainer
looking for some wicked test cases for your compiler).
make.
make install. If you are short
on disk space, you can alternatively install stripped binaries by
running make install-strip.
sfscd.