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

Groups > comp.os.linux.misc > #14247 > unrolled thread

Re: HOW2 mobile, headless-rPi connect to LAN-printer?

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

Contents

  Re: HOW2 mobile, headless-rPi connect to LAN-printer? noSpam@gmail.com - 2015-03-25 03:13 +0000
    Re: HOW2 mobile, headless-rPi connect to LAN-printer? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2015-03-25 09:34 -0400
      Re: HOW2 mobile, headless-rPi connect to LAN-printer? Joe <joe@jretrading.com> - 2015-03-25 18:05 +0000
        Re: HOW2 mobile, headless-rPi connect to LAN-printer? Jerry Peters <jerry@example.invalid> - 2015-03-25 21:04 +0000
          Re: HOW2 mobile, headless-rPi connect to LAN-printer? Unknown <dog@gmail.com> - 2015-03-29 22:04 +0000
            Re: HOW2 mobile, headless-rPi connect to LAN-printer? The Natural Philosopher <tnp@invalid.invalid> - 2015-03-30 08:35 +0100
            Re: HOW2 mobile, headless-rPi connect to LAN-printer? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2015-03-30 09:06 -0400
        Re: HOW2 mobile, headless-rPi connect to LAN-printer? Dan Purgert <dan@djph.net> - 2015-03-25 23:55 +0000
          Re: HOW2 mobile, headless-rPi connect to LAN-printer? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2015-03-26 09:22 -0400
            Re: HOW2 mobile, headless-rPi connect to LAN-printer? Dan Purgert <dan@djph.net> - 2015-03-26 13:30 +0000
              Re: HOW2 mobile, headless-rPi connect to LAN-printer? The Natural Philosopher <tnp@invalid.invalid> - 2015-03-26 14:03 +0000
                Re: HOW2 mobile, headless-rPi connect to LAN-printer? Ahem A Rivet's Shot <steveo@eircom.net> - 2015-03-26 15:08 +0000
                  Re: HOW2 mobile, headless-rPi connect to LAN-printer? Unknown <dog@gmail.com> - 2015-03-28 08:45 +0000
                    Re: HOW2 mobile, headless-rPi connect to LAN-printer? mm0fmf <none@mailinator.com> - 2015-03-28 09:32 +0000
                Re: HOW2 mobile, headless-rPi connect to LAN-printer? Unknown <dog@gmail.com> - 2015-03-28 09:21 +0000
                  Re: HOW2 mobile, headless-rPi connect to LAN-printer? Joe <joe@jretrading.com> - 2015-03-28 10:09 +0000
                    Re: HOW2 mobile, headless-rPi connect to LAN-printer? Unknown <dog@gmail.com> - 2015-03-30 04:46 +0000
                      Re: HOW2 mobile, headless-rPi connect to LAN-printer? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2015-03-30 09:13 -0400
                      Re: HOW2 mobile, headless-rPi connect to LAN-printer? druck <news@druck.org.uk> - 2015-03-30 20:53 +0100
                  Re: HOW2 mobile, headless-rPi connect to LAN-printer? druck <news@druck.org.uk> - 2015-03-28 22:52 +0000
    Re: HOW2 mobile, headless-rPi connect to LAN-printer? alister <alister.nospam.ware@ntlworld.com> - 2015-03-25 19:59 +0000
    Re: HOW2 mobile, headless-rPi connect to LAN-printer? John Davis <wa8yxm@arrl.invalid.net> - 2015-03-25 19:39 -0400

Page 1 of 2  [1] 2  Next page →

#14247 — Re: HOW2 mobile, headless-rPi connect to LAN-printer?

Xref: mx02.eternal-september.org comp.sys.raspberry-pi:8086

>>I want to be able to visit a standard
>> Micro$lth-based office, with the portable rPi, programmed so that
>> when I replace-with-rPi's-eth0-cable, the [one] WinPC's eth0-connection
>> to the LAN and printer, and switch rPi on, it will
>> cause the printer to print my file/S from the USBstik.
>>

It will be tested on my mate's M$Win & LAN & printer.
So that I can visit the office, with the portable headerless rPi, before
the office-girl arrives to use here WinTelPC.

On 21/03/15 17:03, Dennis Lee Bieber wrote:-
>It does sound like the OP intends to unplug the office computer's
>network access and plug his device into its place. 

EXACTLY !

>If he's lucky, the
>office just has a cheap DHCP capable router and not something tied to
>specific MAC addresses (for security).

Perhaps if I phone a Win-user, he can tell me if/where his system shows
the printer's IP, and how to ask the office-girl to 'get it' - from her PC.

> Good luck finding a Pi-compatible network printer driver -- for the
> specific model of  printer at that office.

The following initial google seem optimistic for 1 or both of the printers:--
Downloads | MFC-9120CN | United States | Brother Home AÄ United
   States AÄ MFC-9120CN; Downloads. MFC-9120CN. Downloads.  Select Your
   Operating System (OS). STEP 1: Select OS Family. Windows; Mac
   support.brother.com/g/b/downloadtop.aspx?c...mfc9120cn... - 15k -
   [19]Cached - [20]Similar pages
---------
MFC-9120CN | Australia | Brother Solutions Center Home AÄ Australia;
     MFC-9120CN. Support & ... Network Utilities AÄ Linux Information AÄ SAP
     Printing AÄ Secure Printing AÄ Barcode Printing AÄ Citrix Ready AÄ IPv6 AÄ
     SSL ...  support.brother.com/g/b/producttop.aspx?c=au...mfc9120cn... -
     12k - [22]Cached - [23]Similar pages
The other printer is the very common: NP lazer jet 3055

X wrote:-
]Actually if Pis run CUPS that should not be a problem - the config files 
]are text.
  and then there's:--
  
Subject: Re: Printing from.
Newsgroups: comp.sys.raspberry-pi
Date: Tue, 05 Aug 2014 15:47:22 -0500
From: T M Smith
>>>
>>> I have installed CUPS on the Pi I have added one printer, a brother
>>> laser which is in another room.
>>> I am using WiFi and Uniprint.

This seems similar; but I'll use an eth0 cable.

Surely there are utilities to plug the rPi's eth0-cable into
the LAN and get the printer/s IP?

And don't these printers have a simple mode, where they
accept an ASCII string, like the old printers did?

==TIA.

[toc] | [next] | [standalone]

#14250

On Wed, 25 Mar 2015 03:13:20 +0000 (UTC), noSpam@gmail.com declaimed the
following:


>Perhaps if I phone a Win-user, he can tell me if/where his system shows
>the printer's IP, and how to ask the office-girl to 'get it' - from her PC.
>
	Well, as I showed -- for me it's in the router's DHCP allocation table.
But that requires knowing the IP of the router along with its
login/password.

	Beyond that there are a number of protocols -- the printer may
broadcast its status for clients to pick up (need the appropriate software
running on the expected port to receive the broadcast), SNMP may be able to
ask what is out there... etc.

>
>The following initial google seem optimistic for 1 or both of the printers:--
>Downloads | MFC-9120CN | United States | Brother Home AÄ United
>   States AÄ MFC-9120CN; Downloads. MFC-9120CN. Downloads.  Select Your
>   Operating System (OS). STEP 1: Select OS Family. Windows; Mac
>   support.brother.com/g/b/downloadtop.aspx?c...mfc9120cn... - 15k -
>   [19]Cached - [20]Similar pages

	MFC would seem to indicate a multi-function unit
(printer/scanner/fax)... That makes it even less likely to have a pure
ASCII mode (and if it did, it probably requires direct serial/parallel
connection, as anything coming over Ethernet needs to be packetized with
enough information so that the printer can tell which job a packet belongs
to -- wouldn't want to mix data from two systems sending print jobs to the
one printer).
>And don't these printers have a simple mode, where they
>accept an ASCII string, like the old printers did?
>
	Getting much rarer, and likely only via serial connection (where the
device knows there is only one machine sending data)
-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
    wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/

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

#14252

On Wed, 25 Mar 2015 09:34:41 -0400
Dennis Lee Bieber <wlfraed@ix.netcom.com> wrote:

> On Wed, 25 Mar 2015 03:13:20 +0000 (UTC), noSpam@gmail.com declaimed
> the following:
> 
> 
> >Perhaps if I phone a Win-user, he can tell me if/where his system
> >shows the printer's IP, and how to ask the office-girl to 'get it' -
> >from her PC.
> >
> 	Well, as I showed -- for me it's in the router's DHCP
> allocation table. But that requires knowing the IP of the router
> along with its login/password.
> 
> 	Beyond that there are a number of protocols -- the printer may
> broadcast its status for clients to pick up (need the appropriate
> software running on the expected port to receive the broadcast), SNMP
> may be able to ask what is out there... etc.
> 
Most large office printers today are fairly complex, contain a hard
drive, take ages to boot and many run Linux... typically, the printer
driver installation software will scan the network for one or more of
its target printers.

> >And don't these printers have a simple mode, where they
> >accept an ASCII string, like the old printers did?
> >
> 	Getting much rarer, and likely only via serial connection
> (where the device knows there is only one machine sending data)

The last one I was involved with was a Ricoh device, that used TCP/9100
for 'raw' data, whatever that was. But it could be configured for
several ports and protocols, including lpr and IPX.

-- 
Joe

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

#14255

In comp.os.linux.misc Joe <joe@jretrading.com> wrote:
> On Wed, 25 Mar 2015 09:34:41 -0400
> Dennis Lee Bieber <wlfraed@ix.netcom.com> wrote:
> 
>> On Wed, 25 Mar 2015 03:13:20 +0000 (UTC), noSpam@gmail.com declaimed
>> the following:
>> 
>> 
>> >Perhaps if I phone a Win-user, he can tell me if/where his system
>> >shows the printer's IP, and how to ask the office-girl to 'get it' -
>> >from her PC.
>> >
>>       Well, as I showed -- for me it's in the router's DHCP
>> allocation table. But that requires knowing the IP of the router
>> along with its login/password.
>> 
>>       Beyond that there are a number of protocols -- the printer may
>> broadcast its status for clients to pick up (need the appropriate
>> software running on the expected port to receive the broadcast), SNMP
>> may be able to ask what is out there... etc.
>> 
> Most large office printers today are fairly complex, contain a hard
> drive, take ages to boot and many run Linux... typically, the printer
> driver installation software will scan the network for one or more of
> its target printers.
> 
>> >And don't these printers have a simple mode, where they
>> >accept an ASCII string, like the old printers did?
>> >
>>       Getting much rarer, and likely only via serial connection
>> (where the device knows there is only one machine sending data)
> 
> The last one I was involved with was a Ricoh device, that used TCP/9100
> for 'raw' data, whatever that was. But it could be configured for
> several ports and protocols, including lpr and IPX.
> 

I have a Brother printer and it does the same, tcp/9100 needs to be
configured for whatever protocol you're using. 

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

#14269

On Wed, 25 Mar 2015 21:04:14 +0000, Jerry Peters wrote:

> In comp.os.linux.misc Joe <joe@jretrading.com> wrote:
>> On Wed, 25 Mar 2015 09:34:41 -0400
>> Dennis Lee Bieber <wlfraed@ix.netcom.com> wrote:
>> 
>>> On Wed, 25 Mar 2015 03:13:20 +0000 (UTC), noSpam@gmail.com declaimed
>>> the following:
>>> 
>>> 
>>> >Perhaps if I phone a Win-user, he can tell me if/where his system
>>> >shows the printer's IP, and how to ask the office-girl to 'get it' -
>>> >from her PC.
-- snip --
>> The last one I was involved with was a Ricoh device, that used TCP/9100
>> for 'raw' data, whatever that was. But it could be configured for
>> several ports and protocols, including lpr and IPX.
>> 
>> 
> I have a Brother printer and it does the same, tcp/9100 needs to be
> configured for whatever protocol you're using.

This seems to be getting close to a solution.

Perhaps I can try `ping 192.168.0.9100`
But it will be from a headerless rPi, with only an on/off switch.

== Let's test the idea from the x86 to the rPi.
~:ping 192.168.0.2 >> /pingTrace
^C~:less /pingTrace
PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
64 bytes from 192.168.0.2: icmp_seq=1 ttl=64 time=1.18 ms
64 bytes from 192.168.0.2: icmp_seq=2 ttl=64 time=0.433 ms
64 bytes from 192.168.0.2: icmp_seq=3 ttl=64 time=0.481 ms

That's a start.

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

#14271

On 29/03/15 23:04, Unknown wrote:
> Perhaps I can try `ping 192.168.0.9100`

It is at this point one realises one is dealing with  a clueless 
fuckwit, and retreats very quietly..


-- 
Everything you read in newspapers is absolutely true, except for the 
rare story of which you happen to have first-hand knowledge. – Erwin Knoll

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

#14272

On Sun, 29 Mar 2015 22:04:49 +0000 (UTC), Unknown <dog@gmail.com> declaimed
the following:


>Perhaps I can try `ping 192.168.0.9100`

	And that command will fail -- the largest value allowed in any dotted
IPv4 address is 255. 9100 is a PORT, not part of the address.

	If the printers are on a DHCP LAN, you'll likely need to use some
discovery protocol to find the printer (either you have to send a broadcast
message of some type and collect all the responses, then query each
responder [you now have the IP from the response] to find out if it is a
printer; or the printer routinely broadcasts some identification packet
that you have to intercept and parse).
-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
    wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/

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

#14257

On Wed, 25 Mar 2015 18:05:40 +0000, Joe wrote:

> [snip...]
>
> The last one I was involved with was a Ricoh device, that used TCP/9100
> for 'raw' data, whatever that was. But it could be configured for
> several ports and protocols, including lpr and IPX.

TCP 9100 is the ephemeral port listener, generally associated with HP 
JetDirect cards (or equivalent).

IIRC it's assuming data is coming across as formatted PCL or PJL (or 
whatever the "raw data" type the printer is expecting)[1].  Depends on 
what the printer is trying to emulate; though PCL is more common on 
regular printers -- big copiers / printers that include automated 
stapling / hole punching will likely be PJL wrapped though.

In addition to the JetDirect interface, they usually have LPD/IPP queues 
as you mentioned (name dependent on mfg and model, most seem to have a 
"PASSTHRU" and "RAW" [or "raw"], as well as several set for either 
PostScript or other specific printing languages).


[1] -- Assuming I'm recalling it correctly, this is from "Network 
Printing" book published by O'Reilly.  

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

#14258

On Wed, 25 Mar 2015 23:55:11 +0000 (UTC), Dan Purgert <dan@djph.net>
declaimed the following:


>TCP 9100 is the ephemeral port listener, generally associated with HP 
>JetDirect cards (or equivalent).
>
	I'd downloaded a sample Brother MFC manual (didn't bother to look up
whatever model the OP stated) but it did list port 9100, along with
LPR/LPD, and half a dozen other protocols (SNMP, some M$ location protocol,
etc.).

>IIRC it's assuming data is coming across as formatted PCL or PJL (or 
>whatever the "raw data" type the printer is expecting)[1].  Depends on 
>what the printer is trying to emulate; though PCL is more common on 
>regular printers -- big copiers / printers that include automated 
>stapling / hole punching will likely be PJL wrapped though.
>
	Couldn't find anything for a RIP format/language for it -- closest was
a spec sheet that listed "GDI Emulation"; which makes it sound like a very
big/fancy "winprinter"

	It also only listed Windows and OS-X as supported... Unlike my HP
printer whose documentation also gave a link to Linux support.
-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
    wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/

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

#14259

On Thu, 26 Mar 2015 09:22:28 -0400, Dennis Lee Bieber wrote:

> On Wed, 25 Mar 2015 23:55:11 +0000 (UTC), Dan Purgert <dan@djph.net>
> declaimed the following:
> 
> 
>>TCP 9100 is the ephemeral port listener, generally associated with HP
>>JetDirect cards (or equivalent).
>>
> 	I'd downloaded a sample Brother MFC manual (didn't bother to look 
up
> whatever model the OP stated) but it did list port 9100, along with
> LPR/LPD, and half a dozen other protocols (SNMP, some M$ location
> protocol,
> etc.).
> 
>>IIRC it's assuming data is coming across as formatted PCL or PJL (or
>>whatever the "raw data" type the printer is expecting)[1].  Depends on
>>what the printer is trying to emulate; though PCL is more common on
>>regular printers -- big copiers / printers that include automated
>>stapling / hole punching will likely be PJL wrapped though.
>>
> 	Couldn't find anything for a RIP format/language for it -- 
closest was
> a spec sheet that listed "GDI Emulation"; which makes it sound like a
> very big/fancy "winprinter"
> 
> 	It also only listed Windows and OS-X as supported... Unlike my HP
> printer whose documentation also gave a link to Linux support.


Yeah, I'm not entirely sure I'm recalling the thing right, and really 
don't care enough to hunt down said book.  Thing is, even if I do dig it 
up, I think it's 10 or 15 years old at this point; so it'll only give 
information on what TCP9100 was used for back then (and, as I recall, it 
was primarily focused on HP Printers and LPR / LPRng ... so none of this 
fancy CUPS stuff we have today).

I would be a little surprised that a Brother printer is primarily running 
GDI, as most of their stuff is pretty well supported in *nix - either 
right out of the box, or with a quick LPR(ng) filter and printcap 
download.  Though, they are a bit sparse, and forgot to mention that you 
also needed 1 or 2 "extra" programs installed along side it as prereqs ... 
but that could've been my mistake with using dpkg.

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

#14260

On 26/03/15 13:30, Dan Purgert wrote:
> what TCP9100 was used for back then

Basically its about as high level as a parallel serial or USB port. 9100 
was a RAW protocol.

How to get bytes from computer to printer. They still need to be the 
RIGHT bytes.


MOST printers today are postcript capable and that means CUPS =- which 
is very very postcript oriented - will be able to make a stab at 
supporting them.

Problems occur with winprinters that accept some weird PCL language that 
need a special rasterisation setup to accept a full image or 
postscript-in-a-weird-font type stuff, or need special commands to 
select specail features like duplex printing.

The latter can be handled by writing a PPD file. I've actually dome that 
for a printer that wasn't fully supported.


But rasterisation may be more difficult. I am not sure how cups handles 
that.

It seems on research there are a bundle of image and postcript to raster 
programs that cups uses - these should be totally portable to any 
architecture, and therefore part of any full CUPS and Ghostscript port.

And PPDs are just text files.

So I would say there is no part of CUPS that requires an architecture 
specific device driver beyond USB, serial, parallel or tcp socket level.

So cups on a Pi should 'just work' *once set up*. As well as it does on *86.

Now of the 'printer discovery tools' that allow automagic detection and 
installation of network printers, that is another matter.

Id google bonjour, as that seems to be the latest wheeze.


-- 
Everything you read in newspapers is absolutely true, except for the 
rare story of which you happen to have first-hand knowledge. – Erwin Knoll

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

#14262

On Thu, 26 Mar 2015 14:03:37 +0000
The Natural Philosopher <tnp@invalid.invalid> wrote:

> But rasterisation may be more difficult. I am not sure how cups handles 
> that.
> 
> It seems on research there are a bundle of image and postcript to raster 
> programs that cups uses - these should be totally portable to any 
> architecture, and therefore part of any full CUPS and Ghostscript port.

	Thare are also third party rasterising programs that can be used
with CUPS - Brother have a number of them for various models. AFAICT the
one for my Brother works by using ghostrscript to generate a pnm which
the proprietary code sends to the printer in some undocumented format. These
tend to be only available as compiled binaries for x86 or x86-64 platforms
so if you have a printer that needs one you're out of luck on a Pi.

-- 
Steve O'Hara-Smith                          |   Directable Mirror Arrays
C:>IN                                      | A better way to focus the sun
The computer obeys and wins.                |    licences available see
You lose and Bill collects.                 |    http://www.sohara.org/

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

#14263

On Thu, 26 Mar 2015 15:08:11 +0000, Ahem A Rivet's Shot wrote:

> On Thu, 26 Mar 2015 14:03:37 +0000
> The Natural Philosopher <tnp@invalid.invalid> wrote:
> 
>> But rasterisation may be more difficult. I am not sure how cups handles
>> that.
>> 
>> It seems on research there are a bundle of image and postcript to
>> raster programs that cups uses - these should be totally portable to
>> any architecture, and therefore part of any full CUPS and Ghostscript
>> port.
> 
> 	Thare are also third party rasterising programs that can be used
> with CUPS - Brother have a number of them for various models. AFAICT the
> one for my Brother works by using ghostrscript to generate a pnm which
> the proprietary code sends to the printer in some undocumented format.
> These tend to be only available as compiled binaries for x86 or x86-64
> platforms so if you have a printer that needs one you're out of luck on
> a Pi.

Thanks, I could never have imagined the computing had "progressed" to
such absurd difficulty.

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

#14265

On 28/03/2015 08:45, Unknown wrote:
> On Thu, 26 Mar 2015 15:08:11 +0000, Ahem A Rivet's Shot wrote:
>
>> On Thu, 26 Mar 2015 14:03:37 +0000
>> The Natural Philosopher <tnp@invalid.invalid> wrote:
>>
>>> But rasterisation may be more difficult. I am not sure how cups handles
>>> that.
>>>
>>> It seems on research there are a bundle of image and postcript to
>>> raster programs that cups uses - these should be totally portable to
>>> any architecture, and therefore part of any full CUPS and Ghostscript
>>> port.
>>
>> 	Thare are also third party rasterising programs that can be used
>> with CUPS - Brother have a number of them for various models. AFAICT the
>> one for my Brother works by using ghostrscript to generate a pnm which
>> the proprietary code sends to the printer in some undocumented format.
>> These tend to be only available as compiled binaries for x86 or x86-64
>> platforms so if you have a printer that needs one you're out of luck on
>> a Pi.
>
> Thanks, I could never have imagined the computing had "progressed" to
> such absurd difficulty.
>

Congratuations to all those people who have fed the troll for the last 
few days helping him complete his mission of wasting your time.

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

#14264

On Thu, 26 Mar 2015 14:03:37 +0000, The Natural Philosopher wrote:

> On 26/03/15 13:30, Dan Purgert wrote:
>> what TCP9100 was used for back then
> 
> Basically its about as high level as a parallel serial or USB port. 9100
> was a RAW protocol.
> 
> How to get bytes from computer to printer. They still need to be the
> RIGHT bytes.
> 
> 
> MOST printers today are postcript capable and that means CUPS =- which
> is very very postcript oriented - will be able to make a stab at
> supporting them.
> 
> Problems occur with winprinters that accept some weird PCL language that
> need a special rasterisation setup to accept a full image or
> postscript-in-a-weird-font type stuff, or need special commands to
> select specail features like duplex printing.
> 
> The latter can be handled by writing a PPD file. I've actually dome that
> for a printer that wasn't fully supported.
> 
> 
> But rasterisation may be more difficult. I am not sure how cups handles
> that.
> 
> It seems on research there are a bundle of image and postcript to raster
> programs that cups uses - these should be totally portable to any
> architecture, and therefore part of any full CUPS and Ghostscript port.
> 
> And PPDs are just text files.
> 
> So I would say there is no part of CUPS that requires an architecture
> specific device driver beyond USB, serial, parallel or tcp socket level.
> 
> So cups on a Pi should 'just work' *once set up*. As well as it does on
> *86.
> 
> Now of the 'printer discovery tools' that allow automagic detection and
> installation of network printers, that is another matter.
> 
> Id google bonjour, as that seems to be the latest wheeze.
--
Obviously, many writers here are 'in the industry'.
So for them: the more complex the better.
But how/why do you USERS tolerate the absurdity: compared to printing
a page of plain text 40 years ago?!

If you examine a typical http of a big organisation, via lynx today,
each "page" is 95% redundant/repeated garbage; for 5% new info.
The kiddies cheer-on-with-delight each new layer of complexity.
It's like the lawers: "why use 10 words, when 10'000 will do?"

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

#14266

On Sat, 28 Mar 2015 09:21:30 +0000 (UTC)
Unknown <dog@gmail.com> wrote:


> Obviously, many writers here are 'in the industry'.
> So for them: the more complex the better.
> But how/why do you USERS tolerate the absurdity: compared to printing
> a page of plain text 40 years ago?!
> 

The same way as any other kind of user. Cars are a couple of orders of
magnitude more complex than they were 100 years ago while being much
easier for users to drive.

Printers (the big office multifunction ones) do vastly more than my
9-pin dot-matrix device of 30 years ago would do, and even that was
much more versatile than the teletypes of 10-20 years earlier.

The users never see the complexity, they just click that 'print' icon.
Even the ones on their mobile phone screens. It all Just Works, for
users of mass-market operating systems, anyway.

-- 
Joe

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

#14270

On Sat, 28 Mar 2015 10:09:36 +0000, Joe wrote:

> On Sat, 28 Mar 2015 09:21:30 +0000 (UTC) Unknown <dog@gmail.com> wrote:
> 
> 
>> Obviously, many writers here are 'in the industry'. So for them: the
>> more complex the better. But how/why do you USERS tolerate the
>> absurdity: compared to printing a page of plain text 40 years ago?!
>> 
>> 
> The same way as any other kind of user. Cars are a couple of orders of
> magnitude more complex than they were 100 years ago while being much
> easier for users to drive.
> 
> Printers (the big office multifunction ones) do vastly more than my
> 9-pin dot-matrix device of 30 years ago would do, and even that was much
> more versatile than the teletypes of 10-20 years earlier.
> 
> The users never see the complexity, they just click that 'print' icon.
> Even the ones on their mobile phone screens. It all Just Works, for
> users of mass-market operating systems, anyway.

Yes but the suposedly 'technos' allow themselves to be blinded by the 
marketers. 

Even I missed the obvious first-step-probe/solution !!
Just plug the rPi's eth0 to the printer/S socket in place of the LAN's.

What script-code would allow the rPi to test/probe the printer/S?

I only print 5 x 4 == 20 pages a year, so I can do that before the 
printer/s are powered-up in the morning.

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

#14273

On Mon, 30 Mar 2015 04:46:04 +0000 (UTC), Unknown <dog@gmail.com> declaimed
the following:


>
>Even I missed the obvious first-step-probe/solution !!
>Just plug the rPi's eth0 to the printer/S socket in place of the LAN's.
>
>What script-code would allow the rPi to test/probe the printer/S?
>

http://en.wikipedia.org/wiki/Universal_Plug_and_Play
http://en.wikipedia.org/wiki/Simple_Service_Discovery_Protocol

And maybe the use of Wireshark to capture network traffic looking for
announcements from the printer...
-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
    wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/

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

#14277

On 30/03/2015 05:46, Unknown wrote:
> I only print 5 x 4 == 20 pages a year, so I can do that before the
> printer/s are powered-up in the morning.

And look how many pages the fools replying to this troll have wasted.

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

#14267

On 28/03/2015 09:21, Unknown wrote:
> It's like the lawers: "why use 10 words, when 10'000 will do?"

Or Trolls.

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

Page 1 of 2  [1] 2  Next page →

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

csiph-web