9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Fax problem
Date: Thu, 31 May 2001 17:07:46 -0400	[thread overview]
Message-ID: <20010531210747.D5634199E9@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]

Oops, that's local configuration that we shouldn't have let slip out.
The directory /sys/lib/fax and the command /rc/bin/fax are full of
local refrences.

This needs a manual.  The machine that has the modem attached should
be running a telco with the appropriate dev in the command line.  For
example, out system dinar has the following in it's cpurc:

telco -vs 19200 /dev/eia011 &				# FAX

Then you should have a cron entry that kicks it ever now and then
just like for mail.  For example, we have in /cron/upas/cron:

5,15,25,35,45,55 * * * *	dinar		/sys/lib/fax/faxtickle

Now edit /rc/bin/fax and everything in /sys/lib/fax to reflect
your local environment.  Basicly change everything that mentions
emelie into a pointer to your file server.

If you only have one system, then just remove from /rc/bin/fax the
line:
	rx dinar /sys/lib/fax/faxgoose
with
	upas/runq -t3 /mail/faxoutqueue /sys/lib/fax/faxtry < /dev/null > /dev/null >[2=1] &

A bit of a pain all around.  We never got around to making this generic and
it fell through the cracks in the release.  This is part of why releases are
hard.  We (i.e. Rob) usually have to go over the system with a fine tooth
comb to comb out all this local lice.


[-- Attachment #2: Type: message/rfc822, Size: 1959 bytes --]

From: William Staniewicz <wstan@localhostnl.demon.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] Fax problem
Date: Thu, 31 May 2001 22:43:53 +0000
Message-ID: <20010531224353.B389@localhostnl.demon.nl>


I never tried faxing before. But when I did try it
recently I got this...

term% fax 5551212 Someone faxtest.txt
rx: can't dial dinar: cs: can't translate address(tcp!dinar!shell)

(note: prior to this I did "telco '#t/eia1' as I normally
 do to set up that feature.)

What do I do next to set it up to work?

-- 
Bill                             William Staniewicz
                                 Amsterdam, NL

             reply	other threads:[~2001-05-31 21:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-31 21:07 presotto [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-02 16:58 presotto
2001-06-02 13:57 Richard Miller
2001-06-01 13:09 Richard Miller
2001-05-31 22:43 William Staniewicz
2001-05-31 21:06 Russ Cox

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=20010531210747.D5634199E9@mail.cse.psu.edu \
    --to=presotto@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).