Re: mount -t tmpfs tmpfs fails

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

mount -t tmpfs tmpfs fails

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

Re: ntpd dies soon after start

On Wed, Jun 14, 2017 at 10:34 AM, Vladimir Zakharov wrote: > On Wed, Jun 14, 2017, Alan Somers wrote: >> On Wed, Jun 14, 2017 at 9:57 AM, Vladimir Zakharov >> >> This is by design. Your offset is so large (more than a year), that >> ntpd fails its basic sanity test. You

Re: ntpd dies soon after start

On Wed, Jun 14, 2017, Alan Somers wrote: > On Wed, Jun 14, 2017 at 9:57 AM, Vladimir Zakharov > > This is by design. Your offset is so large (more than a year), that > ntpd fails its basic sanity test. You need to do one of the > following: > 1) Manually set the time before starting ntpd for

Re: ntpd dies soon after start

On Wed, Jun 14, 2017 at 9:57 AM, Vladimir Zakharov wrote: > Hello! > > I have ntpd enabled to start during boot. I see, that it starts. But > querying it after booting fails: > # ntpq -p > ntpq: read: Connection refused > > After manual start, it works for several seconds

ntpd dies soon after start

Hello! I have ntpd enabled to start during boot. I see, that it starts. But querying it after booting fails: # ntpq -p ntpq: read: Connection refused After manual start, it works for several seconds and then dies. root@vzakharov:~ # service ntpd start Starting ntpd. root@vzakharov:~ # ntpq -p

Re: ERRATA: 12.0-CURRENT binaries 'stat' errors.

On 14 Jun 2017, at 13:51, Jeffrey Bouquet wrote: > > ne > /usr/local/bin/ne: Undefined symbol "stat" > ktrace -di ne > /usr/local/bin/ne: Undefined symbol "stat" Be sure to exactly follow the procedure mentioned in /usr/src/UPDATING entry 20170523. My guess is that

ERRATA: 12.0-CURRENT binaries 'stat' errors.

ne /usr/local/bin/ne: Undefined symbol "stat" ktrace -di ne /usr/local/bin/ne: Undefined symbol "stat" I may have posted in error an 'fstat' instead, unsure, to the ports list just yesterday or so. A workaround is to use pkg.freebsd.org to attain compat11x binaries which run. This is a

Re: Time to increase MAXPHYS?

On Sun, Jun 4, 2017 at 1:33 PM, Warner Losh wrote: > On Sat, Jun 3, 2017 at 2:59 PM, Colin Percival > wrote: > > > On January 24, 1998, in what was later renumbered to SVN r32724, dyson@ > > wrote: > > > Add better support for larger I/O clusters,