On Sun, Nov 17, 2002 at 04:35:38PM -0800, Jacob Meuser wrote: > > I would still absolutely love to see a presentation on configuring CUPS > > the hard way. > > Why? Perhaps you should read the sources for lpadmin and some IPP > documentation.
Have you actually looked at the CUPS documentation? It's terrible! That
said, I did manage to figure out how it all works, and could probably help
someone else do it now, but it was a total pain to do the first time.
> > Most dists still use lpr or lprng, and CUPS is an all
> > around better print system.
>
> Well, again, read the sources and docs. Both have their "optimal"
> uses. At an OpenBSD hackathon, lpr/lpd was used to spool mp3s ...
> CUPS is not really that flexible.
I think ... um ... I think this is not what lpr was intended for. =)
> > This is especially useful since CUPS is
> > available for Linux and other UNIX platforms, is the standard print system
> > used by MacOS X, and CUPS can cooperate with Windows relatively easily
> > once you actually configure it.
> >
> > Like everything else, there many options for filtering whatever type of
> > input you have and turning it into postscript..
>
> Yes, CUPS does make things "simpler", and AFAIK, the is only IPP
> implementation for *nix.
Nothing is simpler than magicfilterconfig, really. Getting from here to
there, however, is not so trivial.
Consider:
- Several distributions now use CUPS
- Those which don't probably offer it or will soon
- MacOS X uses CUPS
- Windows 2000/XP use Internet Printing Protocol
- CUPS supports talking to and listening to lpd servers
All in all, there aren't many reasons to use anything else anymore for
printing. =)
--
Joseph Carter <[EMAIL PROTECTED]> You're entitled to my opinion
<Cylord> Would it be acceptable to debian policy if we inserted a crontab
by default into potato that emailed [EMAIL PROTECTED]
every morning with an email that read, "Don't worry, linux is a
fad..."
msg11781/pgp00000.pgp
Description: PGP signature
