From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Donald Thompson <dlt@dataventures.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Stallion EasyIO and devfs
Date: Mon, 20 Aug 2001 10:15:38 -0600 [thread overview]
Message-ID: <200108201615.f7KGFcD01007@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <Pine.LNX.4.31.0108200124160.11127-100000@dv1.dataventures.com>
In-Reply-To: <200108122123.f7CLNDK03327@mobilix.ras.ucalgary.ca> <Pine.LNX.4.31.0108200124160.11127-100000@dv1.dataventures.com>
Donald Thompson writes:
> devfsd and the compatability links work correctly as of 2.4.8 with the
> patch you provided.
>
> This is quite possibly user error and not a kernel issue, but it seems
> pppd 2.4.1 breaks once I've got the stallion card under devfsd with
> compatability links.
>
> mgetty runs on device lets say, /dev/ttyE2 (symlink to /dev/ttyE/2), and
> passes off incoming connections to pppd. I'm expecting pppd is gonna want
> to look at /etc/ppp/options.ttyE2, but its not.
>
> If I change stallion.c at around line 145 from:
> static char *stl_serialname = "ttyE/%d";
>
> To:
> static char *stl_serialname = "ttyE%d";
>
> so that the real device becomes /dev/ttyE2 rather than a symlink to
> /dev/ttyE/2 pppd starts looking at the correct options file.
The recent versions of devfsd expect the Stallion devices to have the
name tts/E%d, so this suggests that you are running a virgin
kernel. So grab devfs-patch-v187 and devfsd-v1.3.17 (or later) and try
again. If you still have problems, run strace and analyse the result.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2001-08-20 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200108122123.f7CLNDK03327@mobilix.ras.ucalgary.ca>
2001-08-20 7:40 ` Stallion EasyIO and devfs Donald Thompson
2001-08-20 16:15 ` Richard Gooch [this message]
2001-07-16 17:36 Donald Thompson
2001-07-31 1:12 ` Richard Gooch
2001-08-12 21:08 ` Donald Thompson
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=200108201615.f7KGFcD01007@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=dlt@dataventures.com \
--cc=linux-kernel@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