Date: Sun, 26 May 1996 12:01:51 +0800 (HKT) From: John Beukema <john@gateway.net.hk> To: Gary Aitken <garya@ics.com> Cc: Warner Losh <imp@village.org>, Sean Eric Fagan <sef@kithrup.com>, freebsd-hackers@FreeBSD.org Subject: Re: stty -- not Message-ID: <Pine.BSI.3.91.960526115158.8554B-100000@gateway.net.hk> In-Reply-To: <31A40C51.4BBF@ics.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I wish someone would sort this out. I remember when I first installed
FBSD I spent 2 days trying to get a simnple epson printer to work.
printcap had 50 varities of high speed line printer entries, teletypes
and devices that have not existed for years but no obvious way to hook up
the printers that make up 99% of the population out there. After 16 to
20 hours of reading man pages and questions I had to write my own filter
in c to put in cr's. Almost enough to turn newbies back to windoze.
The default configuration should have a setup for a pc printer and an
HPlj3 on both lpt0 and ttyd1, perhaps commented out.
This space unintentionally left unblank
jbeukema
On Thu, 23 May 1996, Gary Aitken wrote:
> > I'm not sure what the right and proper way to do this is, but I have a
> > printcap entry:
> ...
> > where addcr does the following:
> >
> > #!/bin/sh
> > sed -e 's/$/^M/'
> > echo ^L
> >
> > (the two character sequences above ^M, etc are really the actual
> > control characters).
> >
> > I then print lpr -Plc xxx to print something that isn't raw bits for
> > my printer. The ps entry is so I can print postscript files directly
> > on my non-postscript printer with the aid of gs. I lost my psfilt
> > program in the last great disk crash, but it was a simple hack of
> > gsbj. Since I use aladdin gs, I get free pdf printing too :-).
> >
> > A kludge I know, but it even worked when I had the LA-50 hooked up to
> > the machine, and that was a serial printer. I just let lpd open the
> > LA-50 in raw mode and dealt with the problem elsewhere.
> >
> > Pointers to the right way to do this would be accepted joyfully.
>
> I thought of doing that as well, but since the dang thing is *supposed*
> to work by tweaking the opost | onlcr bits, that seemed like the
> right way to do it. I figured since those bits have been in there
> working for years they couldn't possibly be broken (I may still be
> doing something wrong... At this point I can kludge it to work
> using stty or a filter; I guess it's time for some debugging.
>
> --
> Gary Aitken garya@ics.com (business)
> garya@dreamchaser.org (personal)
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.91.960526115158.8554B-100000>