From 412cd13636fa5678b597f33d4bf731b38daed223 Mon Sep 17 00:00:00 2001 From: Stig Otnes Kolstad Date: Thu, 6 Feb 2020 20:04:20 +0100 Subject: [PATCH] Fix language errors and typos --- .../2019-12-14-print-on-network-printer-without-cups.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/collections/_posts/2019-12-14-print-on-network-printer-without-cups.md b/collections/_posts/2019-12-14-print-on-network-printer-without-cups.md index d3c24c9..bf2212c 100644 --- a/collections/_posts/2019-12-14-print-on-network-printer-without-cups.md +++ b/collections/_posts/2019-12-14-print-on-network-printer-without-cups.md @@ -6,15 +6,15 @@ categories: linux --- I think CUPS is too much. I just want to print simple files from the command -line. This is how it works for me with the printers I have been connecting too. +line. This is how it works for me with the printers I have been connecting to. -Depending on how your printer is connected, the target to which you can pipe -to will be either +Depending on how your printer is connected, the target to which you pipe +will differ - if connected through the **local network**, you can use `netcat`, `nc`, `lp`, or even just pipe to `/dev/tcp//` on some systems. - if connected through **USB**, the printer might have been made available - as a USB device in `/dev/usb/`. + as a USB device in `/dev/usb/` or `/dev/usb0` (...or `usb1`). In the examples below I am using a network printer and connecting to it using the following information: