1 |
Lindsay Haisley <fmouse-gentoo@×××.com> wrote: |
2 |
|
3 |
> Printers are an Issue in Linux, and it's not just Gentoo. Eric |
4 |
> Raymond sent |
5 |
> a flame letter to the CUPS people a while back detailing his horror |
6 |
> story of |
7 |
> setting up a CUPS printer. His story was chillingly similar to my own |
8 |
> experience. It was a nightmare! Maybe the Gentoo devs could pick up |
9 |
> the |
10 |
> ball and make CUPS a little easier to use. |
11 |
|
12 |
For what it's worth, I think that some band-aid could lessen the problem |
13 |
ESR ran into a bit. |
14 |
|
15 |
The problem is that everyone assumes that they have to do some |
16 |
configuration work on the client, especially if the thing refuses to |
17 |
print. |
18 |
|
19 |
Warn them! The default install is actually perfectly able to find any |
20 |
correctly set up CUPS print server. If it doesn't print, it's the server |
21 |
that's incorrectly set up. I've tried several distros and they have all |
22 |
found my server without me touching any config. I recently installed |
23 |
Macos X on my Mac, and the first time I hit Command-P, the Oki 4w on my |
24 |
cups server came up as the default printer and it printed without a |
25 |
hitch. |
26 |
|
27 |
Warn them! Add some text to the ebuild postinst bit that says that one |
28 |
should generally not have to touch the config to set Cups up as a |
29 |
client. Do the same in the admin web interface so they don't start |
30 |
tinkering with setting up queues on their clients and so on. Tell them |
31 |
that problems tend to be caused by incorrectly set up servers. And do it |
32 |
in less geeky words than mine. |
33 |
|
34 |
This, of course, does not solve the other problem: That setting up the |
35 |
server is a nightmare, and that the docs on how to do it also is. |
36 |
|
37 |
I'm treating cancer with aspirin, but hopefully it's a good start. |
38 |
|
39 |
/Rasmus Wiman |
40 |
|
41 |
-- |
42 |
gentoo-desktop@g.o mailing list |