From owner-freebsd-questions@freebsd.org Thu Oct 15 19:21:21 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 47BF4A15B36 for ; Thu, 15 Oct 2015 19:21:21 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0CBAA1106 for ; Thu, 15 Oct 2015 19:21:20 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Zmo5V-0005lQ-HG for freebsd-questions@freebsd.org; Thu, 15 Oct 2015 21:21:18 +0200 Received: from 65.75.36.70 ([65.75.36.70]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 15 Oct 2015 21:21:17 +0200 Received: from gyliamos by 65.75.36.70 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 15 Oct 2015 21:21:17 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Will Parsons Subject: Re: creating devices under a regular file system Date: Thu, 15 Oct 2015 19:21:10 +0000 (UTC) Lines: 37 Message-ID: References: <20151015203119.7d46c4f14904f28ae41356db@yahoo.es> Reply-To: gyliamos@gmail.com X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 65.75.36.70 User-Agent: slrn/1.0.2 (FreeBSD) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Oct 2015 19:21:21 -0000 On Thursday, 15 Oct 2015 2:31 PM -0400, Eduardo Morras wrote: > On Wed, 14 Oct 2015 23:29:50 +0000 (UTC) > Will Parsons wrote: > >> I would like to know how to create a few selected devices >> (viz. dev/null and dev/urandom) under a regular directory tree using >> devfs. >> >> The background for this is the following: >> >> I use the fossil SCM system for various projects of mine, and keep the >> repositories under ~/FOSSIL. Fossil provides a web interface, which I >> employ using inetd, using the following line in /etc/inetd.conf: >> >> http stream tcp nowait root /usr/local/bin/fossil fossil >> http /home//FOSSIL >> >> This works, but I get a warning message "can't open /dev/null and >> /dev/urandom", because fossil does a chroot into ~/FOSSIL, where of >> course the referenced devices do not exist. I asked about this on the >> fossil mailing list and got the reply that the preferred method of >> avoiding the warning message was to create these devices in the >> chrooted environment. >> >> I presume that this can be done somehow via devfs, but am failing to >> discern how. > > I use fossil since its inception and never seen that warning. Is your user on wheel group? Yes. The warnings have been there since February, I think. I'm running version 1.33. When I go into Administration, I see: WARNING: Device "/dev/null" is not available for reading and writing. WARNING: Device "/dev/urandom" is not available for reading. This means that the pseudo-random number generator used by SQLite will be poorly seeded.