https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264059
Michael Meiszl changed:
What|Removed |Added
CC||mich...@meiszl.de
--- Comment #13
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264059
--- Comment #14 from Hans Petter Selasky ---
Maybe something can be done by devd and the device driver loading framework.
Currently the mlx4en driver is old and not actively maintained.
--
You are receiving this mail because:
You are on
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264059
--- Comment #15 from Michael Meiszl ---
(In reply to Hans Petter Selasky from comment #14)
if old and not maintained does not really matter as long as it works. I doubt
it would do any harm to be automatically be included as the main mlx4 d
I recently noticed the following behavior:
% ping6 redrock
ping6: Name does not resolve
% host redrock
redrock.karels.net has address 10.0.2.2
redrock.karels.net mail is handled by 10 mail.karels.net.
% ping6 nonexistenthost
ping6: Name does not resolve
The first error message is misleading, beca
On Tue, Sep 27, 2022 at 03:53:12PM -0500, Mike Karels wrote:
> I recently noticed the following behavior:
>
> % ping6 redrock
> ping6: Name does not resolve
> % host redrock
> redrock.karels.net has address 10.0.2.2
> redrock.karels.net mail is handled by 10 mail.karels.net.
> % ping6 nonexistenth
On Tue, Sep 27, 2022 at 03:53:12PM -0500, Mike Karels wrote:
> The first error message is misleading, because the name *does* resolve,
> but has no record, and it is the same error message as for a name
> that truly does not exist.
FWIW, the distinction between NODATA and NXDOMAIN is these d
On 27 Sep 2022, at 17:41, Viktor Dukhovni wrote:
> On Tue, Sep 27, 2022 at 03:53:12PM -0500, Mike Karels wrote:
>
>> The first error message is misleading, because the name *does* resolve,
>> but has no record, and it is the same error message as for a name
>> that truly does not exist.
>
> F
