virt(4) [netbsd man page]

VIRT(4) 						   BSD Kernel Interfaces Manual 						   VIRT(4)

NAME

     virt -- rump virtual network interface

SYNOPSIS

     #include <rump/rump.h>

     int
     rump_pub_virtif_create(int num);

DESCRIPTION

     The virt interface acts as a link between a rump virtual kernel and a host tap(4) interface.  Interface number <n> always corresponds with
     the host tap interface tap<n>.  All data sent by virt is written into /dev/tap<n> and all data read from /dev/tap<n> is passed as Ethernet
     input to the rump virtual kernel.

     A virt interface can be created in two ways:

     o	 Programmatically by calling rump_pub_virtif_create().

     o	 Dynamically at runtime with ifconfig(8) or equivalent using the create command.

     Destroying a virt interface is possible only through ifconfig(8) destroy.

     The host's tap(4) interface can be further bridged with hardware interfaces to provide full Internet access to a rump kernel.

SEE ALSO

     rump(3), bridge(4), tap(4), brconfig(8), ifconfig(8)

BSD
								 November 15, 2010							       BSD

RUMP_SMBFS(8)						    BSD System Manager's Manual 					     RUMP_SMBFS(8)

NAME

     rump_smbfs -- mount a smbfs share with a userspace server

SYNOPSIS

     file-system PUFFS
     pseudo-device putter

     rump_smbfs [options] share mountpoint

DESCRIPTION

     NOTE! This manual page describes features specific to the rump(3) file server.  Please see mount_smbfs(8) for a full description of the
     available command line options.

     The rump_smbfs utility can be used to mount smbfs file systems.  It uses rump(3) and p2k(3) to facilitate running the file system as a server
     in userspace.  As opposed to mount_smbfs(8), rump_smbfs does not use file system code within the kernel and therefore does not require kernel
     support except puffs(4).  Apart from a minor speed penalty there is no downside with respect to in-kernel code.

     Even though the rump_smbfs file system client runs within a virtual rump kernel in userspace, it uses host network services (by means of
     ``rump sockin'').	This means that regardless of whether using rump_smbfs or mount_smbfs(8), the same network configurations will be used.
     Currently, ``sockin'' supports IPv4.

     To use rump_smbfs via mount(8), the flags -o rump and -t smbfs should be given.  Similarly, rump_smbfs is used instead of mount_smbfs(8) if
     ``rump'' is added to the options field of fstab(5).

SEE ALSO

     p2k(3), puffs(3), rump(3), mount_smbfs(8)

HISTORY

     The rump_smbfs utility first appeared in NetBSD 6.0.

BSD
								 November 21, 2010							       BSD