On Oct 01, 2001 08:47 +0000, Henning P. Schmiedehausen wrote:
> netconsole listener offers the "receive console messages" service -> server
> netconsole.o uses the "receive console message" service -> client
>
> So both definitions are right/wrong. Choose any you like. Just
> document it and stick to it. =:-)
It is ironic that the most popular thread about netconsole is a foolish
semantic argument, instead of a steady stream of patches for the various
network cards.
> I am happy to have a network console no matter what is the client and
> what is the server.
I agree. I was actually thinking just now that I would "enhance" the
netconsole-server script so that:
1) it can start both the client and the server (I will just call it
"netconsole", and use a config file to get the settings). Maybe
options like "--send" and "--receive" are unambiguous enough?
2) we don't need to specify the IP address of the local host for the
"client" (possibly enhancing the client to listen on all configured
interfaces by default.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Oct 07 2001 - 21:00:15 EST