Re: Mosh regression between 10.x and 11-stable

That's interesting (not in a good way). Next thing to try: mosh --server='/usr/local/bin/mosh-server 2>/dev/null' peter@VPS (with an unmodified mosh-server) Mosh prints the 'MOSH CONNECT ...' message on stdout, then forks. The parent exits immediately, and the child prints verbose and

Wayland work status

Hi Here's a status update of my work and some questions. SETUP: System: FreeBSD 12-CURRENT ( https://github.com/FreeBSDDesktop/freebsd-base-graphics/tree/drm-next-4.6) Ports: https://github.com/freebsd/freebsd-ports-graphics/tree/wayland Package installed from this tree graphics/wayland (built

Re: kernel panic caused by virtualbox(?)

On 11 Aug, Konstantin Belousov wrote: > On Wed, Aug 10, 2016 at 04:47:15PM -0700, Don Lewis wrote: >> On 10 Aug, Jung-uk Kim wrote: >> > On 08/09/16 05:12 AM, Konstantin Belousov wrote: >> >> On Mon, Aug 08, 2016 at 04:44:20PM -0700, Don Lewis wrote: >> >>> On 8 Aug, Konstantin Belousov wrote: >>

Re: Mosh regression between 10.x and 11-stable

On 2016-Aug-11 10:06:35 -0700, Ngie Cooper wrote: > >> On Aug 11, 2016, at 09:30, John Hood wrote: >> >> I still can't reproduce this on 3 different 11.0-BETA4 servers and a >> variety of clients and networks. Can you try and identify a more >> portable

Re: Mosh regression between 10.x and 11-stable

On 2016-Aug-11 12:30:23 -0400, John Hood wrote: >I still can't reproduce this on 3 different 11.0-BETA4 servers and a >variety of clients and networks. Can you try and identify a more >portable repro or at least figure out why it fails on your system? > >Please try applying this

Re: Passwordless accounts vi ports!

Am Thu, 11 Aug 2016 11:30:37 +0200 Jan Bramkamp schrieb: > On 11/08/16 07:05, O. Hartmann wrote: > > I just checked the security scanning outputs of FreeBSD and found this > > surprising result: > > > > [...] > > Checking for passwordless accounts: > >

Re: Mosh regression between 10.x and 11-stable

> On Aug 11, 2016, at 09:30, John Hood wrote: > > I still can't reproduce this on 3 different 11.0-BETA4 servers and a > variety of clients and networks. Can you try and identify a more > portable repro or at least figure out why it fails on your system? > > Please try

Re: Mosh regression between 10.x and 11-stable

I still can't reproduce this on 3 different 11.0-BETA4 servers and a variety of clients and networks. Can you try and identify a more portable repro or at least figure out why it fails on your system? Please try applying this patch, too. It's a shot in the dark, though. regards, --jh

Re: Passwordless accounts vi ports!

+--On 11 août 2016 11:26:58 +0200 Mathieu Arnold wrote: | | | +--On 11 août 2016 07:05:05 +0200 "O. Hartmann" | wrote: || I just checked the security scanning outputs of FreeBSD and found this || surprising result: || || [...] || Checking for

Re: Fwd: Failed to boot -Current snapshot memstick img with EFI

This is fixed by r303944. On Fri, Jul 29, 2016 at 1:24 AM Howard Su wrote: > It turns out a USB driver problem. the usb disk size is not correctly > detected. But the disk works fine in BIOS. > > Here is dmesg information: > ugen7.2: at usbus7 > umass0: on > usbus7 >

Re: Mosh regression between 10.x and 11-stable

On 2016-Aug-10 14:32:15 -0400, john hood wrote: >On 8/10/16 4:18 AM, Peter Jeremy wrote: >> I recently updated one of my VPS hosts from 10.3-RELEASE-p5 to 11.0-BETA4 >> r303811 and mosh to that host from my Linux laptop stopped working. All >> I get on the laptop is: >> $ mosh

HPETs and userspace gettimeofday()

I implemented fast userspace gettimeofday(2) support for machines which have to use HPET for timecounters. Details and measurements, as well as the patch, are put at https://reviews.freebsd.org/D7473 . I am interested in the testing by people using Core2 and older hardware. Thanks.

Re: Passwordless accounts vi ports!

On 11/08/16 07:05, O. Hartmann wrote: I just checked the security scanning outputs of FreeBSD and found this surprising result: [...] Checking for passwordless accounts: polkitd::565:565::0:0:Polkit Daemon User:/var/empty:/usr/sbin/nologin pulse::563:563::0:0:PulseAudio System

Re: Passwordless accounts vi ports!

+--On 11 août 2016 07:05:05 +0200 "O. Hartmann" wrote: | I just checked the security scanning outputs of FreeBSD and found this | surprising result: | | [...] | Checking for passwordless accounts: | polkitd::565:565::0:0:Polkit Daemon

Re: kernel panic caused by virtualbox(?)

On Wed, Aug 10, 2016 at 04:47:15PM -0700, Don Lewis wrote: > On 10 Aug, Jung-uk Kim wrote: > > On 08/09/16 05:12 AM, Konstantin Belousov wrote: > >> On Mon, Aug 08, 2016 at 04:44:20PM -0700, Don Lewis wrote: > >>> On 8 Aug, Konstantin Belousov wrote: > On Mon, Aug 08, 2016 at 10:22:44AM

CURRENT: NFSv4/autofs and ZFS weirdness: permission denied

Both server and clients are running most recent 12-CURRENT. The server is exporting a ZFS volume via NFSv4. I recently copied that volume from another volume via zfs send/receive from one vilume on the same server to another volume, created on another sorage device. The specific volume worked

Re: Boot environments and zfs canmount=noauto

On 28/07/2016 13:34, Andriy Gapon wrote: > Locally I have the following rc script to handle subordinate datasets of > a boot environment: http://dpaste.com/0Q0JPGN.txt > It is designed for exactly the scenario described above. > The script is automatically enabled when zfs_enable is enabled. > >

Re: Passwordless accounts vi ports!

On 11/08/2016 1:16 PM, Ngie Cooper wrote: On Aug 10, 2016, at 22:05, O. Hartmann wrote: I just checked the security scanning outputs of FreeBSD and found this surprising result: [...] Checking for passwordless accounts: polkitd::565:565::0:0:Polkit Daemon

Re: Passwordless accounts vi ports!

> On 11 Aug 2016, at 14:35, O. Hartmann wrote: > [...] > Checking for passwordless accounts: > polkitd::565:565::0:0:Polkit Daemon User:/var/empty:/usr/sbin/nologin > pulse::563:563::0:0:PulseAudio System User:/nonexistent:/usr/sbin/nologin > saned::194:194::0:0:SANE

Re: Passwordless accounts vi ports!

> On 11 Aug 2016, at 15:36, O'Connor, Daniel wrote: > My clamav and pulse users have a password field of * - i.e. they're disabled > (AND the shell is nologin) > > I suspect this is a bug in the check not the ports. Sorry, I just saw your next email, please disregard. It