Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.networking > #2847 > unrolled thread

Portable text2eth0 printer?

Back to article view | Back to comp.os.linux.networking

Contents

  Portable text2eth0 printer? Avoid9Pdf@gmail.com - 2014-03-15 11:47 +0000
    Re: Portable text2eth0 printer? William Unruh <unruh@invalid.ca> - 2014-03-15 17:14 +0000
      Re: Portable text2eth0 printer? Unknown <dog@gmail.com> - 2014-03-21 09:35 +0000
        Re: Portable text2eth0 printer? Joe Beanfish <joebeanfish@nospam.duh> - 2014-03-21 13:25 +0000
          Re: Portable text2eth0 printer? Ian Zimmerman <itz@buug.org> - 2014-03-27 11:46 -0700
            Re: Portable text2eth0 printer? Unknown <dog@gmail.com> - 2014-04-07 12:40 +0000
              Re: Portable text2eth0 printer? Joe Beanfish <joebeanfish@nospam.duh> - 2014-04-07 13:59 +0000
              Re: Portable text2eth0 printer? Jerry Peters <jerry@example.invalid> - 2014-04-07 20:08 +0000

#2847 — Portable text2eth0 printer?

Presently I use rPi to listen to text-to-speech, by transfering the PC
generated *.wav files via a USBstik, to the battery-powered rPi.

Similarly, instead of finding some Windows-user, to print my text via
their eth0 connection, I want to just plug my battery-powered rPi into
the office ethernet that feeds the printer, and get the text on the
USBstik, printed.

The rPi will be hearderless: without any display + keyboard;
like when it plays my text-to-speech files.

So then I'd need to find out the printers IP?
How do I do that?
The 'one' user who may co-operate with my needs, would not know.

Perhaps the HP-printer's name is standard for the product, and
available via the net? But no; since it must be able to share
the ethN with other same-make printers?

What's the general syntax to drive the printer ?

== TIA.

[toc] | [next] | [standalone]

#2850

On 2014-03-15, Avoid9Pdf@gmail.com <Avoid9Pdf@gmail.com> wrote:
> Presently I use rPi to listen to text-to-speech, by transfering the PC
> generated *.wav files via a USBstik, to the battery-powered rPi.
>
> Similarly, instead of finding some Windows-user, to print my text via
> their eth0 connection, I want to just plug my battery-powered rPi into
> the office ethernet that feeds the printer, and get the text on the
> USBstik, printed.
>
> The rPi will be hearderless: without any display + keyboard;
> like when it plays my text-to-speech files.

You can always use ssh to log into the rpi from another computer, and
use its keyboard and display. 

>
> So then I'd need to find out the printers IP?

Is it the same always or does it change?
You do not want to be changing the setup each time you do it, as you
also then need to install the printer ppd file, edit /etc/cups/printers
etc.
What kind of printer is it?


> How do I do that?
> The 'one' user who may co-operate with my needs, would not know.
>
> Perhaps the HP-printer's name is standard for the product, and
> available via the net? But no; since it must be able to share
> the ethN with other same-make printers?
>
> What's the general syntax to drive the printer ?

you tell us nothing about the printer. 

>
>== TIA.
>
>

[toc] | [prev] | [next] | [standalone]

#2869

On Sat, 15 Mar 2014 17:14:16 +0000, William Unruh wrote:

> On 2014-03-15, Avoid9Pdf@gmail.com <Avoid9Pdf@gmail.com> wrote:
>> Presently I use rPi to listen to text-to-speech, by transfering the PC
>> generated *.wav files via a USBstik, to the battery-powered rPi.
>>
>> Similarly, instead of finding some Windows-user, to print my text via
>> their eth0 connection, I want to just plug my battery-powered rPi into
>> the office ethernet that feeds the printer, and get the text on the
>> USBstik, printed.
>>
>> The rPi will be hearderless: without any display + keyboard; like when
>> it plays my text-to-speech files.
> 
> You can always use ssh to log into the rpi from another computer, and
> use its keyboard and display.
> 
> 
No. I listen to the battery-powered-TTS, lying-down, at a location with
no electric supply. Similarly, I want to be able to just bring my
portable rPi to the eth0 And get printed paper.

>> So then I'd need to find out the printers IP?
> 
> Is it the same always or does it change? You do not want to be changing
> the setup each time you do it, as you also then need to install the
> printer ppd file, edit /etc/cups/printers etc.
> What kind of printer is it?
> 
> 
>> How do I do that?
>> The 'one' user who may co-operate with my needs, would not know.
>>
>> Perhaps the HP-printer's name is standard for the product, and
>> available via the net? But no; since it must be able to share the ethN
>> with other same-make printers?
>>
>> What's the general syntax to drive the printer ?
> 
> you tell us nothing about the printer.
> 
> 
I was thinking 1980's: you give a strean of bytes, and get the paper
printed. Perhaps it's easier to just fax the text to the printer/fax
combo? 

>>== TIA.
>>
>>

[toc] | [prev] | [next] | [standalone]

#2871

On Fri, 21 Mar 2014 09:35:04 +0000, Unknown wrote:

> On Sat, 15 Mar 2014 17:14:16 +0000, William Unruh wrote:
> 
>> On 2014-03-15, Avoid9Pdf@gmail.com <Avoid9Pdf@gmail.com> wrote:
>>> Presently I use rPi to listen to text-to-speech, by transfering the PC
>>> generated *.wav files via a USBstik, to the battery-powered rPi.
>>>
>>> Similarly, instead of finding some Windows-user, to print my text via
>>> their eth0 connection, I want to just plug my battery-powered rPi into
>>> the office ethernet that feeds the printer, and get the text on the
>>> USBstik, printed.
>>>
>>> The rPi will be hearderless: without any display + keyboard; like when
>>> it plays my text-to-speech files.
>> 
>> You can always use ssh to log into the rpi from another computer, and
>> use its keyboard and display.
>> 
>> 
> No. I listen to the battery-powered-TTS, lying-down, at a location with
> no electric supply. Similarly, I want to be able to just bring my
> portable rPi to the eth0 And get printed paper.
> 
>>> So then I'd need to find out the printers IP?
>> 
>> Is it the same always or does it change? You do not want to be changing
>> the setup each time you do it, as you also then need to install the
>> printer ppd file, edit /etc/cups/printers etc.
>> What kind of printer is it?
>> 
>> 
>>> How do I do that?
>>> The 'one' user who may co-operate with my needs, would not know.
>>>
>>> Perhaps the HP-printer's name is standard for the product, and
>>> available via the net? But no; since it must be able to share the ethN
>>> with other same-make printers?
>>>
>>> What's the general syntax to drive the printer ?
>> 
>> you tell us nothing about the printer.
>> 
>> 
> I was thinking 1980's: you give a strean of bytes, and get the paper
> printed. Perhaps it's easier to just fax the text to the printer/fax
> combo?

If the printer has serial or parallel connection maybe you could do that.
Ethernet is shared wire with packetized protocols. You can't just spew
byte streams to it.

Your rPi will have to be configured with an IP address appropriate for the
network with the printer. Hopefully the office has DHCP server so the rPi
can auto-configure it's network settings. Once on the network you'll need
the IP or hostname of the printer as well as the type/model ("HP" is not
enough). Use that info to configure lpr or cups on the rPi. Once all
that's done you can print with "lpr filename" or similar.

[toc] | [prev] | [next] | [standalone]

#2876

Avoid> Similarly, instead of finding some Windows-user, to print my text
Avoid> via their eth0 connection, I want to just plug my battery-powered
Avoid> rPi into the office ethernet that feeds the printer, and get the
Avoid> text on the USBstik, printed.

Joe> Your rPi will have to be configured with an IP address appropriate
Joe> for the network with the printer. Hopefully the office has DHCP
Joe> server so the rPi can auto-configure it's network settings. Once on
Joe> the network you'll need the IP or hostname of the printer as well
Joe> as the type/model ("HP" is not enough). Use that info to configure
Joe> lpr or cups on the rPi. Once all that's done you can print with
Joe> "lpr filename" or similar.

There is a DHCP lpr-server datum.  I don't expect many DHCP
installations to provide it, though.

Also, there is Bounjour aka Zeroconf aka Rendezvous.  CUPS implements
that via libavahi.  So if the print spooler on the Pi is CUPS and the
network provides Bonjour service you should be able to find the printer
information automatically that way.

-- 
Please *no* private copies of mailing list or newsgroup messages.

gpg public key: 2048R/984A8AE4
fingerprint: 7953 ADA1 0E8E AB57 FB79  FFD2 360A 88B2 984A 8AE4
Funny pic: http://bit.ly/ZNE2MX

[toc] | [prev] | [next] | [standalone]

#2895

On Thu, 27 Mar 2014 11:46:06 -0700, Ian Zimmerman wrote:

> Avoid> Similarly, instead of finding some Windows-user, to print my text
> Avoid> via their eth0 connection, I want to just plug my battery-powered
> Avoid> rPi into the office ethernet that feeds the printer, and get the
> Avoid> text on the USBstik, printed.
> 
> Joe> Your rPi will have to be configured with an IP address appropriate
> Joe> for the network with the printer. Hopefully the office has DHCP
> Joe> server so the rPi can auto-configure it's network settings. Once on
> Joe> the network you'll need the IP or hostname of the printer as well
> Joe> as the type/model ("HP" is not enough). Use that info to configure
> Joe> lpr or cups on the rPi. Once all that's done you can print with
> Joe> "lpr filename" or similar.
> 
> There is a DHCP lpr-server datum.  I don't expect many DHCP
> installations to provide it, though.
> 
> Also, there is Bounjour aka Zeroconf aka Rendezvous.  CUPS implements
> that via libavahi.  So if the print spooler on the Pi is CUPS and the
> network provides Bonjour service you should be able to find the printer
> information automatically that way.

Wow! And they call that progress.
30 years ago, I could just send an ASCII string and get the printed paper.

Why do you people allow yourself to be fooled?

[toc] | [prev] | [next] | [standalone]

#2896

On Mon, 07 Apr 2014 12:40:17 +0000, Unknown wrote:
> On Thu, 27 Mar 2014 11:46:06 -0700, Ian Zimmerman wrote:
> 
>> Avoid> Similarly, instead of finding some Windows-user, to print my
>> text Avoid> via their eth0 connection, I want to just plug my
>> battery-powered Avoid> rPi into the office ethernet that feeds the
>> printer, and get the Avoid> text on the USBstik, printed.
>> 
>> Joe> Your rPi will have to be configured with an IP address appropriate
>> Joe> for the network with the printer. Hopefully the office has DHCP
>> Joe> server so the rPi can auto-configure it's network settings. Once
>> on Joe> the network you'll need the IP or hostname of the printer as
>> well Joe> as the type/model ("HP" is not enough). Use that info to
>> configure Joe> lpr or cups on the rPi. Once all that's done you can
>> print with Joe> "lpr filename" or similar.
>> 
>> There is a DHCP lpr-server datum.  I don't expect many DHCP
>> installations to provide it, though.
>> 
>> Also, there is Bounjour aka Zeroconf aka Rendezvous.  CUPS implements
>> that via libavahi.  So if the print spooler on the Pi is CUPS and the
>> network provides Bonjour service you should be able to find the printer
>> information automatically that way.
> 
> Wow! And they call that progress.
> 30 years ago, I could just send an ASCII string and get the printed
> paper.
> 
> Why do you people allow yourself to be fooled?

30 years ago you connected the printer directly to your computer through
serial or parallel. Why do you try to use this ethernet boondoggle?

[toc] | [prev] | [next] | [standalone]

#2900

Unknown <dog@gmail.com> wrote:
> On Thu, 27 Mar 2014 11:46:06 -0700, Ian Zimmerman wrote:
> 
>> Avoid> Similarly, instead of finding some Windows-user, to print my text
>> Avoid> via their eth0 connection, I want to just plug my battery-powered
>> Avoid> rPi into the office ethernet that feeds the printer, and get the
>> Avoid> text on the USBstik, printed.
>> 
>> Joe> Your rPi will have to be configured with an IP address appropriate
>> Joe> for the network with the printer. Hopefully the office has DHCP
>> Joe> server so the rPi can auto-configure it's network settings. Once on
>> Joe> the network you'll need the IP or hostname of the printer as well
>> Joe> as the type/model ("HP" is not enough). Use that info to configure
>> Joe> lpr or cups on the rPi. Once all that's done you can print with
>> Joe> "lpr filename" or similar.
>> 
>> There is a DHCP lpr-server datum.  I don't expect many DHCP
>> installations to provide it, though.
>> 
>> Also, there is Bounjour aka Zeroconf aka Rendezvous.  CUPS implements
>> that via libavahi.  So if the print spooler on the Pi is CUPS and the
>> network provides Bonjour service you should be able to find the printer
>> information automatically that way.
> 
> Wow! And they call that progress.
> 30 years ago, I could just send an ASCII string and get the printed paper.

Double sided, with graphics? A laser printer for USD 99? Oh and it's
also a copier.

> 
> Why do you people allow yourself to be fooled?
> 

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.networking

csiph-web