nullfs-autopsy after crash

[Tim Robbins]

On Mon, May 10, 2004 at 09:00:10AM +0200, Volker Stolz wrote:

> /bin on /usr/tmp/jail/bin (null, local, read-only)
> /sbin on /usr/tmp/jail/sbin (null, local, read-only)
> /etc on /usr/tmp/jail/etc (null, local, read-only)
> /dev on /usr/tmp/jail/dev (null, local, read-only)
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Accessing special (non-directory, non-regular) files through nullfs
is known to cause panics. You'll need to create a dev directory
for each jail and populate it with makedev.

> /usr/bin on /usr/tmp/jail/usr/bin (null, local, read-only)
> /usr/sbin on /usr/tmp/jail/usr/sbin (null, local, read-only)
> /usr/include on /usr/tmp/jail/usr/include (null, local, read-only)
> /usr/lib on /usr/tmp/jail/usr/lib (null, local, read-only)
> /usr/libexec on /usr/tmp/jail/usr/libexec (null, local, read-only)
> /usr/ports on /usr/tmp/jail/usr/ports (null, local)


Tim