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) 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 > > 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 > b...@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
Ok, I finally figured out that my previous kernel must have had the tmpfs (and nullfs, it was a problem also with synth) built into the kernel, probably by default. Further, the tmpfs.ko and nullfs.ko modules weren't built and installed. I wound up building and installing both tmpfs and nullfs manually (cding to their respective src direcdories and running make; make install) to get synth to run. 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 something in my system hosed up? Thanks, Bob -- Bob Willcox | Lawsuit, n.: A machine which you go into as a pig and b...@immure.com | come out as a sausage. Austin, TX | -- Ambrose Bierce _______________________________________________ email@example.com mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"