Re: (PM) in.pmd documentation needed

Stephen Fisher (lithium@cia-g.com)
Fri, 28 Nov 1997 12:14:10 -0700 (MST)

What I keep wondering is why Livingston dislikes in.pmd so much? Can't
they make a new one then that works better (if needed)? All the other NAS
makers have applications to remotely use modems on terminal servers as
serial ports and ttys..

- Steve
- Systems Manager
- Community Internet Access, Inc.
- Gallup and Grants, New Mexico

On Fri, 28 Nov 1997, Rich Bauer wrote:

> >From: MegaZone <megazone@livingston.com>
> >Date: Thu, 27 Nov 1997 21:03:26 -0800 (PST)
> >Subject: (PM) IN.PMD (fwd)
> >
> >Once upon a time Rich Bauer shaped the electrons to say...
> >I found in.pmd at ftp://ftp.livingston.com/pub/livingston/software/sun4/
> >but where is the manual for it ? The aqua blue print edition
> >
> >in.pmd is, well, less than well documented. We're basically moving away
> >from it, we don't support it on most platforms now and a rapidly shrinking
> >percentage of customers use it.
>
> But there are customers who still require this functionality. Myself included.
> The least you could do is put some comprehensive documentation on the web site.
>
> >
> >How is the relationship between tty's and in.pmd established ? What
> >are the range of tty's available ? How are modem and terminal devices
> >differentiated ?
>
> >1. With the 'service_device' setting on the port of the NAS.
> >2. Any you want, just don't conflict with other services.
> >3. There is no differentiation. A tty is a tty - just like a local serial
> >port tty.
>
> I have to setup a VSI fax server on a Sparc, and I would like to use the
> modems attached to a PM2e, rather than have to buy a digiboard and do the
> whole thing on a Solaris x86 pc box. Please tell me how to configure
> in.pmd properly to support my application. I need to know specifically
> how the entries in /etc/services and /etc/inetd.conf need to be created,
> as well as their owner and file permissions. Also, a one pager of how
> to use in.pmd would be nice.
>
> Rich
> -
> To unsubscribe, email 'majordomo@livingston.com' with
> 'unsubscribe portmaster-users' in the body of the message.
>

-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.