Date: Sat, 17 Jun 2017 16:14:39 -0700 From: Bryan Drewery <bdrewery@FreeBSD.org> To: Bob Willcox <bob@immure.com>, current list <freebsd-current@freebsd.org> Subject: Re: mount -t tmpfs tmpfs fails Message-ID: <260d04dd-64a4-0bb3-f1a1-3cdc38f8c9c2@FreeBSD.org> In-Reply-To: <20170614205034.GD5608@rancor.immure.com> References: <20170614191445.GC5608@rancor.immure.com> <20170614205034.GD5608@rancor.immure.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --IlT4bkpWeOqFXeGFdhxJX6EjJASTrCpfL Content-Type: multipart/mixed; boundary="sH9ugnTK8E2p9laqLXiUTm000BKCE8OVN"; protected-headers="v1" From: Bryan Drewery <bdrewery@FreeBSD.org> To: Bob Willcox <bob@immure.com>, current list <freebsd-current@freebsd.org> Message-ID: <260d04dd-64a4-0bb3-f1a1-3cdc38f8c9c2@FreeBSD.org> Subject: Re: mount -t tmpfs tmpfs fails References: <20170614191445.GC5608@rancor.immure.com> <20170614205034.GD5608@rancor.immure.com> In-Reply-To: <20170614205034.GD5608@rancor.immure.com> --sH9ugnTK8E2p9laqLXiUTm000BKCE8OVN Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 6/14/2017 1:50 PM, Bob Willcox wrote: > On Wed, Jun 14, 2017 at 02:14:45PM -0500, Bob Willcox wrote: >> I was attempting to run 'synth status' on my 12-current (drm-next) sys= tem >> 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 =3D> 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 =20 >> mount: x: Operation not supported by device >> >> synth used to work on this system prior to my recent upgrade to the la= test >> 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 da5= f90154f1(drm-next): Tue Jun 13 16:58:52 CDT 2017 bob@tavion.austin.ib= m.com:/usr/obj/usr/freebsd-base-graphics/sys/TAVION amd64 >> >> Any suggestions on what I should be looking for (or fixing)? >> >> Thanks, >> Bob >=20 > Ok, I finally figured out that my previous kernel must have had the tmp= fs (and > nullfs, it was a problem also with synth) built into the kernel, probab= ly by > default. Further, the tmpfs.ko and nullfs.ko modules weren't built and > installed. >=20 > I wound up building and installing both tmpfs and nullfs manually (cdin= g to > their respective src direcdories and running make; make install) to get= synth > to run. >=20 > My only question remaining now is was the removal of the building and > installing of these modules a fairly recent change in 12.0, or is somet= hing in > my system hosed up? Oddly I don't see TMPFS ever being in the x86 GENERIC kernel files. Only in some arm and mips kernel configurations. Even if not built into the kernel there should be a loadable module built unless you are using MODULES_OVERRIDE. --=20 Regards, Bryan Drewery --sH9ugnTK8E2p9laqLXiUTm000BKCE8OVN-- --IlT4bkpWeOqFXeGFdhxJX6EjJASTrCpfL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJZRbffAAoJEDXXcbtuRpfPbNEIALEvYPspt0l3NR4urXB65Osq p3P+2eAsG/IVDBhiKpbRugk3d899P/4hE1jfXBTHiGjRUm0oBcMfw8eVAJFEoJWY Qnp3fHYIpQRIYjEAldlRtQlrqsYMSfPyyePTPxAv9WThhKmUvLm0T9uaaE11raYq ZIlXdKU/46AAwAaIgnFYFvBMjCyZfG3rCXHzlWfqfmbwVMzziBZQjCqiFii6O/Xy /bNXARjGED6VTWrEc3Rjhlqgb9KycMR9+z8DLW42BDVSjvSj51BEUC/8VHyrJyIO GKfjFbm1F7fIT5WPJvrDAv+A2icciSXQ0iBsbKQSXiqQjIEA1aIep1tHWr9KAks= =h12n -----END PGP SIGNATURE----- --IlT4bkpWeOqFXeGFdhxJX6EjJASTrCpfL--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?260d04dd-64a4-0bb3-f1a1-3cdc38f8c9c2>