* How do I correct this? @ 2004-11-27 21:44 Chuck Hast 2004-11-28 3:08 ` Jim Bayer 0 siblings, 1 reply; 6+ messages in thread From: Chuck Hast @ 2004-11-27 21:44 UTC (permalink / raw) To: Linux-hams List 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." ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: How do I correct this? 2004-11-27 21:44 How do I correct this? Chuck Hast @ 2004-11-28 3:08 ` Jim Bayer 2004-11-28 4:19 ` Chuck Hast 0 siblings, 1 reply; 6+ messages in thread From: Jim Bayer @ 2004-11-28 3:08 UTC (permalink / raw) To: Chuck Hast; +Cc: Linux-hams List 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. On Sat, 27 Nov 2004 13:44:26 -0800, Chuck Hast <wchast@gmail.com> wrote: > 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 majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- '73' Jim - KC9AOP ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: How do I correct this? 2004-11-28 3:08 ` Jim Bayer @ 2004-11-28 4:19 ` Chuck Hast 2004-11-28 13:02 ` Jeremy Utley 0 siblings, 1 reply; 6+ messages in thread From: Chuck Hast @ 2004-11-28 4:19 UTC (permalink / raw) To: Jim Bayer; +Cc: Linux-hams List On Sat, 27 Nov 2004 21:08:11 -0600, Jim Bayer <kc9aop@gmail.com> wrote: > 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. > > > > > On Sat, 27 Nov 2004 13:44:26 -0800, Chuck Hast <wchast@gmail.com> wrote: > > 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 majordomo@vger.kernel.org > > 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. -- 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." ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: How do I correct this? 2004-11-28 4:19 ` Chuck Hast @ 2004-11-28 13:02 ` Jeremy Utley 2004-11-29 15:03 ` M Taylor 0 siblings, 1 reply; 6+ messages in thread From: Jeremy Utley @ 2004-11-28 13:02 UTC (permalink / raw) To: linux-hams 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 On Sat, 27 Nov 2004 20:19:58 -0800, Chuck Hast <wchast@gmail.com> wrote: > On Sat, 27 Nov 2004 21:08:11 -0600, Jim Bayer <kc9aop@gmail.com> wrote: > > > > 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. > > > > > > > > > > On Sat, 27 Nov 2004 13:44:26 -0800, Chuck Hast <wchast@gmail.com> wrote: > > > 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 majordomo@vger.kernel.org > > > 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. > > -- > > > 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 majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: How do I correct this? 2004-11-28 13:02 ` Jeremy Utley @ 2004-11-29 15:03 ` M Taylor 2004-11-30 3:32 ` Chuck Hast 0 siblings, 1 reply; 6+ messages in thread From: M Taylor @ 2004-11-29 15:03 UTC (permalink / raw) To: Linux-Hams On Sun, Nov 28, 2004 at 05:02:53AM -0800, Jeremy Utley wrote: > 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. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: How do I correct this? 2004-11-29 15:03 ` M Taylor @ 2004-11-30 3:32 ` Chuck Hast 0 siblings, 0 replies; 6+ messages in thread From: Chuck Hast @ 2004-11-30 3:32 UTC (permalink / raw) To: M Taylor; +Cc: Linux-Hams On Mon, 29 Nov 2004 15:03:16 +0000, M Taylor <mctylr@privacy.nb.ca> wrote: > On Sun, Nov 28, 2004 at 05:02:53AM -0800, Jeremy Utley wrote: > > 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. -- 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." ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-11-30 3:32 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2004-11-27 21:44 How do I correct this? Chuck Hast 2004-11-28 3:08 ` Jim Bayer 2004-11-28 4:19 ` Chuck Hast 2004-11-28 13:02 ` Jeremy Utley 2004-11-29 15:03 ` M Taylor 2004-11-30 3:32 ` Chuck Hast
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.