On Thu, Jun 02, 2022 at 08:03:05PM +, Rick Macklem wrote:
> John-Mark Gurney wrote:
> > Rick Macklem wrote this message on Thu, Jun 02, 2022 at 14:44 +:
> > > John-Mark Gurney wrote:
> > > > I just booted FreeBSD-current diskless, using NFS root, and I ended
> > > > up having issues becau
John-Mark Gurney wrote:
> Rick Macklem wrote this message on Thu, Jun 02, 2022 at 14:44 +:
> > John-Mark Gurney wrote:
> > > I just booted FreeBSD-current diskless, using NFS root, and I ended
> > > up having issues because by default, NFS root is only v2.
> > >
> > > One of things that happe
Rick Macklem wrote this message on Thu, Jun 02, 2022 at 14:44 +:
> John-Mark Gurney wrote:
> > I just booted FreeBSD-current diskless, using NFS root, and I ended
> > up having issues because by default, NFS root is only v2.
> >
> > One of things that happened was disk space available was list
Rick Macklem wrote:
> John-Mark Gurney wrote:
> > I just booted FreeBSD-current diskless, using NFS root, and I ended
> > up having issues because by default, NFS root is only v2.
> >
> > One of things that happened was disk space available was listed as
> > -138G, or -144830429K. I assume this
John-Mark Gurney wrote:
> I just booted FreeBSD-current diskless, using NFS root, and I ended
> up having issues because by default, NFS root is only v2.
>
> One of things that happened was disk space available was listed as
> -138G, or -144830429K. I assume this is because the server is reportin
