From: Tomi Manninen <oh2bns@sral.fi>
To: Linux-hams List <linux-hams@vger.kernel.org>
Subject: Re: Kernel 2.6 Oddness
Date: Wed, 14 Jul 2004 23:26:49 +0300 [thread overview]
Message-ID: <1089836809.1302.59.camel@oh2bns.ampr.org> (raw)
In-Reply-To: <40F58DD3.7080600@utoronto.ca>
On Wed, 2004-07-14 at 22:47, Dave Stubbs wrote:
> Recently I upgraded to kernel 2.6 and updated
> a bunch of other packages, and now node won't allow connections any
> more. It says "rsconfig: port rose not active
This is only a warning. Edit the rsports file and remove all
rose port definitions.
> *** configuration
> error" and then quits.
Node should print the real cause of this to the system logs.
Check /var/log/messages for starters.
--
Tomi Manninen / OH2BNS / KP20ME04
next prev parent reply other threads:[~2004-07-14 20:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 17:31 ANN: mt63lx version 0.5 Tomi Manninen
2004-07-13 3:05 ` chuck gelm
2004-07-13 6:01 ` Matti Aarnio
2004-07-15 3:23 ` chuck gelm
2004-07-15 7:47 ` Matti Aarnio
2004-07-15 13:42 ` ? software requirements: MT63lx " chuck gelm
2004-07-13 20:25 ` [MT63] ANN: mt63lx " Karl Larsen
2004-07-14 19:47 ` Kernel 2.6 Oddness Dave Stubbs
2004-07-14 20:26 ` Tomi Manninen [this message]
2004-07-14 21:08 ` Dave Stubbs
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=1089836809.1302.59.camel@oh2bns.ampr.org \
--to=oh2bns@sral.fi \
--cc=linux-hams@vger.kernel.org \
/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 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.