diff -ruN qjail-3.3/Makefile qjail/Makefile
--- qjail-3.3/Makefile	2014-06-20 10:06:13.000000000 -0400
+++ qjail/Makefile	2014-06-21 15:51:34.000000000 -0400
@@ -2,7 +2,7 @@
 # $FreeBSD: head/sysutils/qjail/Makefile 354105 2014-05-15 10:40:19Z pi $
 
 PORTNAME=	qjail
-PORTVERSION=	3.3
+PORTVERSION=	3.4
 CATEGORIES=	sysutils
 MASTER_SITES=	SF/${PORTNAME}
 
@@ -11,7 +11,6 @@
 
 USES=		tar:bzip2
 NO_BUILD=	yes
-NEED_ROOT=	yes
 
 CONFLICTS_INSTALL=	qjail-2.* qjail-3.0 qjail-3.1 
 
@@ -27,11 +26,6 @@
 	${INSTALL_MAN}   ${WRKSRC}/${i}.8 ${STAGEDIR}${MAN8PREFIX}/man/man8
 .endfor
 
-#	@${MKDIR}          ${STAGEDIR}${EXAMPLESDIR}
-#	${INSTALL_DATA}   ${WRKSRC}/jail-primer.html            \
-#		${STAGEDIR}${DOCSDIR}
-
-
 # note examples are mandatory. qjail will not function without them
 	@${MKDIR} ${STAGEDIR}${EXAMPLESDIR}
 	@(cd ${WRKSRC}/examples/ \
diff -ruN qjail-3.3/distinfo qjail/distinfo
--- qjail-3.3/distinfo	2014-06-20 10:06:13.000000000 -0400
+++ qjail/distinfo	2014-06-21 15:38:19.000000000 -0400
@@ -1,2 +1,2 @@
-SHA256 (qjail-3.3.tar.bz2) = 263bf7ff60a2d266ff3a4b39c1ccaf6a1114e22128fa0110351bc6c5d782c525
-SIZE (qjail-3.3.tar.bz2) = 61485
+SHA256 (qjail-3.4.tar.bz2) = c86a5396ba46555a6f59818d8b29c4d2da10bdd0359dfaf3851ad45398e45348
+SIZE (qjail-3.4.tar.bz2) = 62344
diff -ruN qjail-3.3/pkg-descr qjail/pkg-descr
--- qjail-3.3/pkg-descr	2014-06-20 10:06:13.000000000 -0400
+++ qjail/pkg-descr	2014-06-21 16:03:03.000000000 -0400
@@ -4,15 +4,16 @@
 large scale jail environments consisting of 100's of jails.
 
 This version of qjail has been converted from using the legacy rc.d-method as 
-used in all previous versions of qjail, to using the jail(8) jail.conf-method 
-available in RELEASE-9.1 which contained many bugs, some that were fixed in
-RELEASE-9.2 and others fixed in RELEASE-10.0. This upgrade provides the ability
-to enable the following new options on a per-jail basis. exec.fib, securelevel,
-allow.raw_sockets, allow.quotas, allow.mount.nullfs, allow.mount.zfs, cpuset.id,
-vnet.interface, and vnet. The vnet option gives a jail its own network stack 
-using the experimental vimage software. This qjail version is not intended
-for RELEASES older than RELEASE-10.0. The vnet option has only been tested on 
-i386 and amd64 equipment.
+used in all previous versions of qjail-2.x, to using the jail(8) 
+jail.conf-method available in RELEASE-9.1 which contained many bugs, some that 
+were fixed in RELEASE-9.2 and others that were finally fixed in RELEASE-9.3
+and RELEASE-10.0. This upgrade provides the ability to enable the following 
+new options on a per-jail basis. exec.fib, securelevel, allow.sysvipc, 
+devfs_rulesets, allow.raw_sockets, allow.quotas, allow.mount.nullfs, 
+allow.mount.zfs, cpuset.id, vnet.interface, and vnet. The vnet option gives a 
+jail its own network stack using the experimental vimage software. This qjail
+version is not intended for RELEASES older than RELEASE-9.3. The vnet option 
+has only been tested on i386 and amd64 equipment.
 
 Qjail requires no knowledge of the jail command usage. It uses "nullfs" for
 read-only system executables, sharing one copy of them with all the jails.
diff -ruN qjail-3.3/pkg-message qjail/pkg-message
--- qjail-3.3/pkg-message	2014-06-20 10:06:13.000000000 -0400
+++ qjail/pkg-message	2014-06-21 16:22:59.000000000 -0400
@@ -10,11 +10,9 @@
 
 ########################################################################
 
-If your host is running 10.0-RELEASE be sure you apply system security 
-update. You need to be at 10.0-RELEASE-p2.  Run the following commands
-to apply system security updates.
-   freebsd-update  fetch 
-   freebsd-update  install
+If your host is running 9.3-RELEASE or 10.0-RELEASE, please verify that
+/etc/defaults/rc.conf parameter "devfs_load_rulesets" looks like this
+                devfs_load_rulesets="YES"
 
 ########################################################################