Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Jim Bayer <kc9aop@gmail.com>
To: Chuck Hast <wchast@gmail.com>
Cc: Linux-hams List <linux-hams@vger.kernel.org>
Subject: Re: How do I correct this?
Date: Sat, 27 Nov 2004 21:08:11 -0600	[thread overview]
Message-ID: <e524c53204112719084d0b998@mail.gmail.com> (raw)
In-Reply-To: <620c9057041127134410eff0ee@mail.gmail.com>

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

  reply	other threads:[~2004-11-28  3:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-27 21:44 How do I correct this? Chuck Hast
2004-11-28  3:08 ` Jim Bayer [this message]
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e524c53204112719084d0b998@mail.gmail.com \
    --to=kc9aop@gmail.com \
    --cc=linux-hams@vger.kernel.org \
    --cc=wchast@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox