On Sat, 27 Feb 2021 at 01:38, Tim via users
wrote:
> On Fri, 2021-02-26 at 13:53 -0400, George N. White III wrote:
> > At some point, RFC's need to address error reporting and diagnostics.
> > There is also Java, which spews out 10^2 lines of tracing data with
> > nothing to highlight the line
On Fri, 2021-02-26 at 13:53 -0400, George N. White III wrote:
> At some point, RFC's need to address error reporting and diagnostics.
> There is also Java, which spews out 10^2 lines of tracing data with
> nothing to highlight the line that has the key to the problem.
>
> I suspect the compiler
On Fri, 26 Feb 2021 at 10:43, Tom Horsley wrote:
> On Fri, 26 Feb 2021 08:33:54 -0600
> Ian Pilcher wrote:
>
> > I stand by my position that NFS mount errors are almost sadistically
> > useless.
>
> Not enough scope. Almost all linux errors are sadistically useless :-).
>
At some point, RFC's
On Fri, 26 Feb 2021 08:33:54 -0600
Ian Pilcher wrote:
> I stand by my position that NFS mount errors are almost sadistically
> useless.
Not enough scope. Almost all linux errors are sadistically useless :-).
___
users mailing list --
On 2/26/21 8:20 AM, Ian Pilcher wrote:
172.31.248.0(rw,no_subtree_check,no_root_squash,insecure)
^
|
/24
Aargh! I wasted a couple of hours on this last night. Amazing how
seeing something in a different context enables one to spot the error.
I stand
