I have been using 8.0_RC1 amd64 for several days, though first time there
was a crash during boot, which is not reproducible. If at all, it may
relate to my connecting USB kbd/mouse while it was booting, not sure.
I noticed following files, as indicated in boot messages:
# ls -l /var/crash/
On Sun, May 20, 2018 at 10:36:27PM +0530, Mayuresh wrote:
> I have been using 8.0_RC1 amd64 for several days, though first time there
> was a crash during boot, which is not reproducible. If at all, it may
> relate to my connecting USB kbd/mouse while it was booting, not sure.
>
> I noticed
Leaving aside Samba for the moment (which as noted has nothing
to do with NetBSD), how does all this affect nsmb(4) and mount_smbfs(8)?
I'm guessing given the age of these, that they don't implement
newer versions of the protocol (the manpages are silent on this).
jnem...@cue.bc.ca (John Nemeth) writes:
> Leaving aside Samba for the moment (which as noted has nothing
>to do with NetBSD), how does all this affect nsmb(4) and mount_smbfs(8)?
>I'm guessing given the age of these, that they don't implement
>newer versions of the protocol (the manpages are
On Thu, May 17, 2018 at 05:14:13PM +, Steve Blinkhorn wrote:
> The Windows 10 box I use alongside a clutch of NetBSD boxes is
> suddenly refusing to map my samba shares as disks, and refusing
> smbclient connections, saying they are SMBv1 which is insecure. This
> happened without any