28.08.2015 Views

The Design and Implementation of the Anykernel and Rump Kernels

1F3KDce

1F3KDce

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

A–33<br />

RUMPHIJACK(3) NetBSD Library Functions Manual RUMPHIJACK(3)<br />

to <strong>the</strong> rump kernel. For example, if ‘‘path’’ is<br />

/rump, accessing /rump/dev/bpf will cause /dev/bpf to<br />

be accessed in <strong>the</strong> rump kernel. In contrast, if<br />

‘‘blanket’’ contains /dev/bpf, accessing /dev/bpf<br />

will cause an access to /dev/bpf in <strong>the</strong> rump kernel.<br />

In case <strong>the</strong> current working directory is changed to a<br />

blanketed directory, <strong>the</strong> current working directory<br />

will still be reported with <strong>the</strong> rump prefix, if<br />

available. Note, though, that some shells cache <strong>the</strong><br />

directory <strong>and</strong> may report something else. In case no<br />

rump path prefix has been configured, <strong>the</strong> raw rump<br />

directory is reported.<br />

It is recommended to supply blanketed pathnames as<br />

specific as possible, i.e. use /dev/bpf instead <strong>of</strong><br />

/dev unless necessary to do o<strong>the</strong>rwise. Also, note<br />

that <strong>the</strong> blanket prefix does not follow directory<br />

borders. In o<strong>the</strong>r words, setting <strong>the</strong> blanket for<br />

/dev/bpf means it is set for all pathnames with <strong>the</strong><br />

given prefix, not just ones in /dev.<br />

‘‘socket’’<br />

<strong>The</strong> specifier value contains a colon-separated list<br />

<strong>of</strong> which protocol families should be hijacked. <strong>The</strong><br />

special value ‘‘all’’ can be specified as <strong>the</strong> first<br />

element. It indicates that all protocol families<br />

should be hijacked. Some can <strong>the</strong>n be disabled by<br />

prepending ‘‘no’’ to <strong>the</strong> name <strong>of</strong> <strong>the</strong> protocol family.<br />

For example, ‘‘inet:inet6’’ specifies that only<br />

PF_INET <strong>and</strong> PF_INET6 sockets should be hijacked,<br />

NetBSD 5.99.48 March 14, 2011 NetBSD 5.99.48

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!