Linux · Printing (CUPS)

In the early Unix days root could print by copying a PostScript file straight into a printer's device file. What problems did spooling systems like CUPS solve that this couldn't?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Printing (CUPS)

You just plugged a laser printer into a Linux desktop and it can't find an exact driver match. Why does it usually still print anyway?

A friend says just plugging in any USB or Wi-Fi printer on GNOME auto-configures it in seconds. What's the catch that makes this over-optimistic?

Your printer is a cheap inkjet that understands neither PostScript nor PDF. How does CUPS get a page onto it, and which component does the actual translation?

Where does CUPS keep its configuration, and which file holds the central daemon settings versus the per-printer definitions?

Printer-specific quirks like non-printable margins, duplex support, and paper-feed commands have to live somewhere. What kind of file stores them, and who originally defined the format?

You need the CUPS web interface for a headless print server, but browsing to its IP on port 631 from your laptop fails. Why, and what's the clean workaround?

Start learning today

Free to start — download the app or use it in your browser.