RE: Serial port sniffing?
Hi, Perhaps the script below works… # set up the baud rate and no parity stty -F /dev/ttyUSB0 9600 -parenb # listen on TCP port 8001 and forward all traffic to the serial port while [ 1 ] ; do nc -l $(hostname -i) 8001 /dev/ttyUSB0; echo reconnecting ...; done Then intercept all network traffic from port 8001 (tcpdump?) Best wishes. From: Richard Shaw Sent: 19 July 2020 22:23 To: Development discussions related to Fedora Subject: Serial port sniffing? I would like to monitor serial port communications read only, but I haven't found a tool that makes that easy in the Fedora repos. Anyone have suggestions? Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
RE: CPE Weekly: 2020-06-21
Thanks for your message. > See our wiki page here for more > information:https://docs.fedoraproject.org/en-US/cpe/ I am replying because the link in your message reports "403 Forbidden" I copy below the message from firefox. Best wishes, R Mercado Forbidden You don't have permission to access this resource. Apache Server at docs.fedoraproject.org Port 443 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: How to deal with large number of bugs related to the, "multiple definition of..." issue
Hello, > The most common fix I used was, using "extern" in all but one place. > Well I guess what I was looking for was for us non-C/C++ programmers. :) > I can grep the source and arbitrarily choose which one not to use extern > with, but is there a right way? I would like to see an example package where you experience this problem. One way I have seen this solved is to have a #define, say '#define MAIN' On the header file "header.h" you would have a declaration and a definition only if MAIN is defined, e.g. extern int y; /* declaration */ #ifdef MAIN int y; /* definition */ #endif Most c files would include "header.h" and main.c would do this instead #define MAIN #include "header.h" Thanks, Ronaldo ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
