How do I correct this?
When my machine boots up, I get this message
kissparms uses obsolete (PF_INET,SOCK_PACKET)
I understand that it is not really a problem, but it looks ugly, do I need to change
the format in which the data is sent to kissparms?
Signature · 5 lines
Chuck Hast To paraphrase my flight instructor; "the only dumb question is the one you DID NOT ask resulting in my going out and having to identify your bits and pieces in the midst of torn and twisted metal."
You could try directing messages to /dev/null. For instance:
<program-name> 2>&1 >/dev/null
This directs stderr to stdout and the whole thing to /dev/null, which is bascially a black hole. No messages should appear unless there is a call to do direct IO to the screen (which I wold imagine is not done in this case).
You will need to edit the rc file (/etc/rc.d or /etc/init.d depending on your linux flavor) and add the redirect there.
Good luck.
Quoted 17 lines · Chuck Hast
When my machine boots up, I get this message
kissparms uses obsolete (PF_INET,SOCK_PACKET)
I understand that it is not really a problem, but it looks ugly, do I need to change
the format in which the data is sent to kissparms?--
Chuck Hast
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going out and having to identify your bits and pieces in the midst of torn and twisted metal."
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 3 lines
'73' Jim - KC9AOP
Quoted 12 lines · Jim Bayer
You could try directing messages to
/dev/null. For instance:<program-name> 2>&1 >/dev/null
This directs stderr to stdout and the whole thing to
/dev/null, which is bascially a black hole. No messages should appear unless there is a call to do direct IO to the screen (which I wold imagine is not done in this case).You will need to edit the rc file (
/etc/rc.dor/etc/init.ddepending on your linux flavor) and add the redirect there.
Quoted 22 lines
Good luck.
Quoted 16 lines · Chuck Hast
When my machine boots up, I get this message
kissparms uses obsolete (PF_INET,SOCK_PACKET)
I understand that it is not really a problem, but it looks ugly, do I need to change
the format in which the data is sent to kissparms?--
Chuck Hast
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going out and having to identify your bits and pieces in the midst of torn and twisted metal."
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
I would rather fix it if possible then just hide it. If there is a fix I will try to do
so, if not I will just disregard it.
Thank you for the info. I had thought about doing something like that but really wanted to correct it.
Signature · 5 lines
Chuck Hast To paraphrase my flight instructor; "the only dumb question is the one you DID NOT ask resulting in my going out and having to identify your bits and pieces in the midst of torn and twisted metal."
The ax.25 tools use networking functions from the kernel that are pretty much obsolete. That's what is generating this message. If you're knowledgeable about coding, it might be possible to dig into the tools source code and fix the issue, but not really worth it. The message is harmless, and in fact, the directing of data to /dev/null as previously suggested will not do any good, as the message is coming from the kernel, not the program.
Jeremy, NW7JU
Quoted 59 lines · Chuck Hast
Quoted 12 lines · Jim Bayer
You could try directing messages to
/dev/null. For instance:<program-name> 2>&1 >/dev/null
This directs stderr to stdout and the whole thing to
/dev/null, which is bascially a black hole. No messages should appear unless there is a call to do direct IO to the screen (which I wold imagine is not done in this case).You will need to edit the rc file (
/etc/rc.dor/etc/init.ddepending on your linux flavor) and add the redirect there.Quoted 22 lines
Good luck.
Quoted 16 lines · Chuck Hast
When my machine boots up, I get this message
kissparms uses obsolete (PF_INET,SOCK_PACKET)
I understand that it is not really a problem, but it looks ugly, do I need to change
the format in which the data is sent to kissparms?--
Chuck Hast
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going out and having to identify your bits and pieces in the midst of torn and twisted metal."
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.htmlI would rather fix it if possible then just hide it. If there is a fix I will try to do
so, if not I will just disregard it.Thank you for the info. I had thought about doing something like that but really wanted to correct it.
--
Chuck Hast
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going out and having to identify your bits and pieces in the midst of torn and twisted metal."
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 3 lines · Jeremy Utley
The ax.25 tools use networking functions from the kernel that are pretty much obsolete. That's what is generating this message. If you're knowledgeable about coding, it might be possible to dig into
I believe the latest version of the ax.25 software fixes this problem, or maybe it was only fixed in CVS. If so, I'll look at making a new tarball release.
Okay, it looks like there are some related updates in ax25-tools that have not been made into a release. I will plan on doing a release.
Quoted 11 lines · M Taylor
Quoted 3 lines · Jeremy Utley
The ax.25 tools use networking functions from the kernel that are pretty much obsolete. That's what is generating this message. If you're knowledgeable about coding, it might be possible to dig into
I believe the latest version of the ax.25 software fixes this problem, or maybe it was only fixed in CVS. If so, I'll look at making a new tarball release.
Okay, it looks like there are some related updates in ax25-tools that have not been made into a release. I will plan on doing a release.
Looking forward to it. Will check it out as soon as it is released.
Signature · 5 lines
Chuck Hast To paraphrase my flight instructor; "the only dumb question is the one you DID NOT ask resulting in my going out and having to identify your bits and pieces in the midst of torn and twisted metal."