-
Notifications
You must be signed in to change notification settings - Fork 3
Rump Working Env.
Robbie Gifford edited this page Feb 26, 2015
·
14 revisions
The current directory tree looks like this:
- rump
- rumprun-posix (rr)
- This is where the client-side of rump-kernels are. The programs located in this folder will be used to interact with rump_server (see below)
- rr/src/ <- for rump-kernel platform
- buildrump (br)
- Here is where the NetBSD source code is located along with all the rump drivers. These rump drivers are what form the components which make up a rump kernel; all code modifications should be within buildrump. This is also where rump_server is located which is used to host your rump-kernerinos! rump_server loads up as many components as desired. However, some components have dependencies within other components. Use rump_wmd to check a component's dependencies. You can also use rump_allserver to load up all components, but this is not recommended.
- br/src/ <- for BSD
- br/rumptools rumpmake <- for compiling
- br/rumptools rumpmake install <- installing into the rump component (after compilation)
- rumprun-posix (rr)
For basic bootstrapping please read Getting Started and Kernel Development provided by the rump-kernel wiki pages. For setting up your build environment, issue the following commands instructed in the Kernel Development:
For buildrump.sh, run:
$ git clone http://repo.rumpkernel.org/buildrump.sh br
$ cd br
$ ./buildrump.sh -T rumptools -q
$ cd ..
For rumprun-posix, run:
$ git clone http://repo.rumpkernel.org/rumprun-posix rr
$ cd rr
$ ./buildnb.sh
$ make
$ cd ..
- Current Issues
rumprun-posix contains its own buildrump, changes to the rump source can therefore be done by only installing rr. No extra br installation needed. Why might the tutorial have us download a second, separate build rump directory? * rr = rumprun_posix * br = buildrump