From: Chuck Hast <wchast@gmail.com>
To: Linux-Hams <linux-hams@vger.kernel.org>, fpac@home.f6fbb.org
Subject: rose_routes file
Date: Sun, 15 May 2005 20:06:01 -0400 [thread overview]
Message-ID: <620c905705051517067ba6cedb@mail.gmail.com> (raw)
Folks,
Amoung the files found in /proc/net is one called rose_routes, according to
some of the rose documentation, this file should contain the following:
/proc/net/rose_routes
contains a list of all established ROSE connections.
I have established connections through my switch but never see this file
populated, any ideas?
--
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."
reply other threads:[~2005-05-16 0:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=620c905705051517067ba6cedb@mail.gmail.com \
--to=wchast@gmail.com \
--cc=fpac@home.f6fbb.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).