Rerun this step if you move your source
tree to a different computer that is running a different OS.
This document assumes you are working on OS/161 in a directory ~/cse451 (immediately under your home directory) and that you have a source tree in ~/cse451/os161. If you are working in a somewhere else or have arranged things differently, make the appropriate substitutions.
The first step is to run the configure script in the top-level directory of the source tree. This sets things up to work with the OS you are working on and tells the makefiles what to do with certain things.
Use the --ostree option to tell it where you want the system to be installed. A good place for this (given the directory assumptions above) is ~/cse451/root. Then you would run:
cd ~/cse451/os161 ./configure --ostree=$HOME/cse451/rootNote that you need $HOME rather than just ~ because the shell won't expand the tilde when it's in the middle of an argument.
The script creates a file defs.mk that holds definitions used by the makefiles. You can edit this manually if necessary, although any such edits will be lost if you rerun the script. Do not commit this file to your version control system, because it will be different for different source trees. The .gitignore control file already in your repository will instruct git to ignore defs.mk, among other files.
Rerun this step if you move your source
tree to a different computer that is running a different OS.
To build the C library and user programs (including the test programs and everything else) just type bmake in the top level of the source tree. When this completes, type bmake install to copy the results into ~/cse451/root.
You can compile a single program by typing bmake in its source directory; typing bmake install will install just that program into the right place in ~/cse451/root.
The makefiles support the other conventional make rules; bmake depend updates the header file depend information, bmake clean erases the compiled objects, and bmake distclean returns the tree to a fully pristine state. You can also run bmake includes from the top level (or from the kernel or any library) to update the header files used by the build process.
If you are on a multiprocessor or multicore machine, you can speed the build by doing a parallel make. Use the -j option to bmake: bmake -j4. The number is the maximum number of parallel jobs to run at once. Currently the best rule of thumb for this seems to be twice the number of cores you have.
All the build results are created in the build directory under the top level of the source tree. This can be placed elsewhere if desired, such as on a RAM disk, or a local disk if your working tree is a network volume. Read the file mk/os161.config.mk to learn about the things you can set in defs.mk to adjust how the build works.
Rerun this step if you change any of the
kernel headers exported to userland (the ones in
os161/kern/include/kern or os161/arch/*/include/kern) or
if you make changes to the userlevel libraries. If you make changes to
a single program, it is sufficient to recompile and restall just it.
Historically, most Unix systems would run kernels that had been customized for a particular piece of hardware. Such kernels would have only the device drivers needed for that system, and would include only the kernel features that were going to be used. (Leaving out everything else saves memory.) They would also sometimes have custom tuned settings for things like scheduler or pageout behavior.
OS/161 has a similar mechanism. The kernel configurations are kept in the directory os161/kern/conf and are by convention named with all caps. You can copy one of the configs and edit it to remove drivers that you aren't using, in the traditional way; however, with System/161's simple hardware there's not much point to that, so you will probably just use the standard configurations. Choose the one you currently want to build. (The one you will use when first starting off is called DUMBVM.)
Now run the OS/161 config program. This is a shell and awk script, and it lives in the same directory as the config files. Assuming you mean to configure DUMBVM you run:
./config DUMBVMNote the ./ to run the script out of the current directory. If you leave this off, you will probably end up running your host OS's kernel config tool, which probably will not like OS/161's kernel config files very much.
The config script creates a kernel compile directory for the configuration you choose. The kernel is compiled there.
Rerun this step if you change the kernel
config, add new source files to the build, or add new build options.
To compile a kernel, first move to its compile directory:
cd os161/kern/compile/DUMBVMThen run first bmake depend, then bmake. Running bmake install will copy the kernel to ~/cse451/root where you can boot it in System/161. The conventional clean and distclean targets will do the expected thing.
Remember to install your newly built kernel before trying to test it. (The reason builds are numbered and the kernel prints the build number when booted is so you can easily tell if the kernel you just ran is really the one you just compiled.)
Rerun bmake depend if/when you
change header file inclusions, or after re-running config.
Otherwise, there is no need to repeat it. Rerun bmake to
recompile as needed.