From owner-freebsd-questions@FreeBSD.ORG Sun Mar 8 17:48:02 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6E0941F5; Sun, 8 Mar 2015 17:48:02 +0000 (UTC) Received: from BLU004-OMC4S27.hotmail.com (blu004-omc4s27.hotmail.com [65.55.111.166]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2554AAC6; Sun, 8 Mar 2015 17:48:01 +0000 (UTC) Received: from BLU436-SMTP164 ([65.55.111.136]) by BLU004-OMC4S27.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Sun, 8 Mar 2015 10:47:55 -0700 X-TMN: [zlyEEsEP7ZdAGEjuOvo6rqA7vsQWK4WW] X-Originating-Email: [bourne.identity@hotmail.com] Message-ID: Date: Sun, 8 Mar 2015 23:17:43 +0530 From: Manish Jain User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Is there any plan to adopt devtmpfs ? References: In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 08 Mar 2015 17:47:52.0740 (UTC) FILETIME=[00513E40:01D059C8] Cc: "freeb >> User Questions" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2015 17:48:02 -0000 On 03/05/2015 22:30, Adrian Chadd wrote: > It's not devtmpfs - it's likely some USB bugs that haven't been nailed down. > > can you gather some debugging output (dmesg > file.txt would be a good > start) and email that to freebsd-usb@freebsd.org ? It may be something > that's been fixed since 10.1 was released. > > Thanks! > > > > -adrian > It does not work. I tried adding all clauses/lines to /etc/hosts, but still X would refuse to come up if the name ends with .domain.super_domain (specifically roundabouttech.com) I have opted for QMail, specifically hoping that hostname is not a problem and, more importantly, that it seems to have better documentation available than even for the inbuilt sendmail system. Even QMail documentation is not exactly state-of-the-art, but it seems adaptable. Thanks Manish jain