From owner-freebsd-current@freebsd.org Sun Jun 18 01:41:00 2017 Return-Path: Delivered-To: freebsd-current@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 2BFADC799CB for ; Sun, 18 Jun 2017 01:41:00 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (108-84-10-9.lightspeed.austtx.sbcglobal.net [108.84.10.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "darth.immure.com", Issuer "darth.immure.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id ED31B7EAB5; Sun, 18 Jun 2017 01:40:59 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (localhost [127.0.0.1]) by rancor.immure.com (8.15.2/8.15.2) with ESMTPS id v5I1eqVm018161 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 17 Jun 2017 20:40:52 -0500 (CDT) (envelope-from bob@rancor.immure.com) Received: (from bob@localhost) by rancor.immure.com (8.15.2/8.15.2/Submit) id v5I1eqXp018160; Sat, 17 Jun 2017 20:40:52 -0500 (CDT) (envelope-from bob) Date: Sat, 17 Jun 2017 20:40:52 -0500 From: Bob Willcox To: Bryan Drewery Cc: current list Subject: Re: mount -t tmpfs tmpfs fails Message-ID: <20170618014052.GW72404@rancor.immure.com> Reply-To: Bob Willcox References: <20170614191445.GC5608@rancor.immure.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.0 (2017-02-23) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jun 2017 01:41:00 -0000 On Sat, Jun 17, 2017 at 04:10:53PM -0700, Bryan Drewery wrote: > On 6/14/2017 12:14 PM, Bob Willcox wrote: > > I was attempting to run 'synth status' on my 12-current (drm-next) system > > and I got this error: > > > > root@tavion:0 /> synth status > > Querying system about current package installations. > > Stand by, comparing installed packages against the ports tree. > > > > raised REPLICANT.SCENARIO_UNEXPECTED : /sbin/mount -t tmpfs tmpfs /usr/obj/synth-live/SL09 => failed with code 1 > > > > So then I attempted just to do a mount of tmpfs command and got this: > > > > root@tavion:0 /> mount -t tmpfs x /tmp/xxx > > mount: x: Operation not supported by device > > I'm betting 'kldload tmpfs' fixes it. > > > > > synth used to work on this system prior to my recent upgrade to the latest > > drm-next branch (cloned from github and build from source). > > > > root@tavion:1 /> uname -a > > FreeBSD tavion.austin.ibm.com 12.0-CURRENT FreeBSD 12.0-CURRENT #1 da5f90154f1(drm-next): Tue Jun 13 16:58:52 CDT 2017 bob@tavion.austin.ibm.com:/usr/obj/usr/freebsd-base-graphics/sys/TAVION amd64 > > > > Any suggestions on what I should be looking for (or fixing)? > > > > Thanks, > > Bob > > If I could have loaded tmpfs it would have. But the tmpfs.ko module was not being built so it couldn't be loaded. I wound up cding into /usr/src/sys/modules/tmpfs and running make and make install to build and install it. After that kldload tmpfs did work. For some reason it isn't getting built on the system. Not when the kernel or world are built. Bob -- Bob Willcox | Lawsuit, n.: A machine which you go into as a pig and bob@immure.com | come out as a sausage. Austin, TX | -- Ambrose Bierce