Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #257755 > unrolled thread
| Started by | gene heskett <gheskett@shentel.net> |
|---|---|
| First post | 2023-05-01 01:10 +0200 |
| Last post | 2023-05-08 07:10 +0200 |
| Articles | 20 on this page of 89 — 15 participants |
Back to article view | Back to linux.debian.user
repeat of previous question that has gone unanswered several times. gene heskett <gheskett@shentel.net> - 2023-05-01 01:10 +0200
Re: repeat of previous question that has gone unanswered several times. Lee <ler762@gmail.com> - 2023-05-01 02:20 +0200
Re: repeat of previous question that has gone unanswered several times. gene heskett <gheskett@shentel.net> - 2023-05-01 09:40 +0200
Re: repeat of previous question that has gone unanswered several times. Brian <ad44@cityscape.co.uk> - 2023-05-01 15:00 +0200
Re: repeat of previous question that has gone unanswered severaltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 15:50 +0200
Re: repeat of previous question that has gone unanswered severaltimes. David Wright <deblis@lionunicorn.co.uk> - 2023-05-01 16:10 +0200
Re: repeat of previous question that has gone unanswered severaltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 16:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:00 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 17:40 +0200
Re: repeat of previous question that has gone unanswered severaltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 16:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 17:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 18:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 19:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 19:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 00:00 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-02 01:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 19:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 20:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 00:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. debian-user@howorth.org.uk - 2023-05-01 22:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 23:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 01:00 +0200
Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 00:30 +0200
Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 01:00 +0200
Re: repeat of previous question that has gone unanswered severaltimes. Jeffrey Walton <noloader@gmail.com> - 2023-05-01 16:20 +0200
Re: repeat of previous question that has gone unanswered severaltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:00 +0200
Re: repeat of previous question that has gone unanswered several times. David Wright <deblis@lionunicorn.co.uk> - 2023-05-01 06:30 +0200
Re: repeat of previous question that has gone unanswered several times. john doe <johndoe65534@mail.com> - 2023-05-01 09:40 +0200
Re: repeat of previous question that has gone unanswered several times. <tomas@tuxteam.de> - 2023-05-01 13:50 +0200
Re: repeat of previous question that has gone unanswered several times. Brian <ad44@cityscape.co.uk> - 2023-05-01 15:00 +0200
Re: repeat of previous question that has gone unanswered several times. zithro <slack@rabbit.lu> - 2023-05-04 21:50 +0200
Re: repeat of previous question that has gone unanswered severaltimes. gene heskett <gheskett@shentel.net> - 2023-05-04 22:00 +0200
Re: repeat of previous question that has gone unanswered severaltimes. Brian <ad44@cityscape.co.uk> - 2023-05-05 16:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-05 17:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-05 19:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-05 22:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-06 01:00 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-06 03:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Alex King <alex@king.net.nz> - 2023-05-07 01:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. David <curmudgeon@telaman.net.au> - 2023-05-07 02:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Byung-Hee HWANG <soyeomul@doraji.xyz> - 2023-05-07 03:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2023-05-07 13:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-07 17:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-07 18:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-08 06:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-08 13:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-08 19:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-09 00:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-09 10:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Greg Wooledge <greg@wooledge.org> - 2023-05-09 13:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-09 22:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-10 14:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 16:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. <tomas@tuxteam.de> - 2023-05-10 16:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-10 17:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 19:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-10 20:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 22:00 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-11 13:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-11 18:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 22:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. debian-user@howorth.org.uk - 2023-05-10 22:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-11 13:10 +0200
SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-11 18:10 +0200
Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-11 21:20 +0200
Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 00:00 +0200
Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. Greg Wooledge <greg@wooledge.org> - 2023-05-12 00:30 +0200
Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 01:50 +0200
Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 03:40 +0200
Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 11:20 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 12:30 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. Greg Wooledge <greg@wooledge.org> - 2023-05-12 13:30 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 13:50 +0200
Re: SOLVED:Re: repeat of previous question thathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 18:20 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 12:30 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 13:50 +0200
:Re: repeat of previous question thathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 18:10 +0200
Re: :Re: repeat of previous question thathasgoneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 23:30 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-12 20:50 +0200
Re: SOLVED:Re: repeat of previous question thathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 21:30 +0200
Re: SOLVED:Re: repeat of previous question thathasgoneunansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-13 13:20 +0200
Re: SOLVED:Re: repeat of previous questionthathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-13 17:10 +0200
Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 03:30 +0200
Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 03:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2023-05-07 19:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-08 07:10 +0200
Page 2 of 5 — ← Prev page 1 [2] 3 4 5 Next page →
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2023-05-01 20:40 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GqGBj-5Rd8-1@gated-at.bofh.it> |
| In reply to | #257808 |
On Mon 01 May 2023 at 13:22:47 -0400, gene heskett wrote: > On 5/1/23 12:30, Brian wrote: [...] > > The -l option asks the queue for the specific options it offers. The response > > indicates something wrong with CUPS on bpi51. I haven't any problem when doing > > this and getting sensible outputs on my Debian unstable machine. > > Which isn't quite a 1:1 comparison as that will be bookworm shortly. > > Or, should I update the bullseyes to unstable? IDK and I'm not even sure > how... Forget about doing that. I was merely commenting that my Debian did not behave like yours. Is yours a fruit-flavoured varian? > > Assuming your buster machines (which are working) have similar setups to bpi51, > > Which is a bullseye machine. And has a totally different content to the > /etc/cups directory as shown by my last post, much more complex on the > bullseye installs that don't work. THe difference is highly likely to be relevant. You are grasping at straws. > > you couls try the two commands (and all the others in this thread) on one of > > those. > > > I'd think I could start by comparing cupsd.conf's, but miss And I can't see > the trees for all this forest in the way in both, but missing is a > client.conf. I think... But that is probably whats wrong, me thinking. A client.conf is unneeded on a well-behaved CUPS system that obtains info from avahi-daemon. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-02 00:10 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GqJSx-5TiY-1@gated-at.bofh.it> |
| In reply to | #257815 |
On 5/1/23 14:31, Brian wrote: > On Mon 01 May 2023 at 13:22:47 -0400, gene heskett wrote: > >> On 5/1/23 12:30, Brian wrote: > > [...] > >>> The -l option asks the queue for the specific options it offers. The response >>> indicates something wrong with CUPS on bpi51. I haven't any problem when doing >>> this and getting sensible outputs on my Debian unstable machine. >> >> Which isn't quite a 1:1 comparison as that will be bookworm shortly. >> >> Or, should I update the bullseyes to unstable? IDK and I'm not even sure >> how... > > Forget about doing that. I was merely commenting that my Debian did not > behave like yours. Is yours a fruit-flavoured varian? > >>> Assuming your buster machines (which are working) have similar setups to bpi51, >> >> Which is a bullseye machine. And has a totally different content to the >> /etc/cups directory as shown by my last post, much more complex on the >> bullseye installs that don't work. > > THe difference is highly likely to be relevant. You are grasping at straws. > >>> you couls try the two commands (and all the others in this thread) on one of >>> those. >>> >> I'd think I could start by comparing cupsd.conf's, but miss And I can't see >> the trees for all this forest in the way in both, but missing is a >> client.conf. I think... But that is probably whats wrong, me thinking. > > A client.conf is unneeded on a well-behaved CUPS system that obtains info > from avahi-daemon. > in the past, its been required to nuke any and all instances found with avahi in its name in order to get rid of the totally bogus 169.xx.xxx.xxx. default route address as is now reported by ip r after a reboot. This has been true even before jessie. However I've now re-installed it on two of these armbian bullseye machines w/o losing my network. Perhaps it has learned some manners since jessie? Network Manager, my other major headache certainly has. Take care and stay well Brian. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
| From | debian-user@howorth.org.uk |
|---|---|
| Date | 2023-05-01 22:10 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GqI0p-5SaC-1@gated-at.bofh.it> |
| In reply to | #257808 |
gene heskett <gheskett@shentel.net> wrote: > I'd think I could start by comparing cupsd.conf's, but miss And I > can't see the trees for all this forest in the way in both, but > missing is a client.conf. I think... But that is probably whats > wrong, me thinking. Your directory listings showed that both had a ppd directory, but you didn't show the content of those directories. Since your error message was specifically that it couldn't find the PPD, the first thing I'd do is compare those two directories.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2023-05-01 23:30 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GqJfP-5SOz-1@gated-at.bofh.it> |
| In reply to | #257820 |
On Mon 01 May 2023 at 20:59:50 +0100, debian-user@howorth.org.uk wrote: > gene heskett <gheskett@shentel.net> wrote: > > > I'd think I could start by comparing cupsd.conf's, but miss And I > > can't see the trees for all this forest in the way in both, but > > missing is a client.conf. I think... But that is probably whats > > wrong, me thinking. > > Your directory listings showed that both had a ppd directory, but you > didn't show the content of those directories. Since your error message > was specifically that it couldn't find the PPD, the first thing I'd do > is compare those two directories. The message was not about not being able to *find* a PPD. Finding something implies it already exists. Here is the message againn: > lpoptions: Unable to get PPD file for HLL2320D_coyote: The printer or class > does not exist. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-02 01:00 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GqKEV-5TyW-3@gated-at.bofh.it> |
| In reply to | #257821 |
On 5/1/23 17:22, Brian wrote: > On Mon 01 May 2023 at 20:59:50 +0100, debian-user@howorth.org.uk wrote: > >> gene heskett <gheskett@shentel.net> wrote: >> >>> I'd think I could start by comparing cupsd.conf's, but miss And I >>> can't see the trees for all this forest in the way in both, but >>> missing is a client.conf. I think... But that is probably whats >>> wrong, me thinking. >> >> Your directory listings showed that both had a ppd directory, but you >> didn't show the content of those directories. Since your error message >> was specifically that it couldn't find the PPD, the first thing I'd do >> is compare those two directories. > > The message was not about not being able to *find* a PPD. Finding something > implies it already exists. Here is the message againn: > >> lpoptions: Unable to get PPD file for HLL2320D_coyote: The printer or class >> does not exist. > And it did not exist until the lpadmin created it. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-02 00:30 +0200 |
| Subject | Re: repeat of previous question that has goneunansweredseveraltimes. |
| Message-ID | <GqKbT-5ToX-1@gated-at.bofh.it> |
| In reply to | #257820 |
On 5/1/23 16:00, debian-user@howorth.org.uk wrote: > gene heskett <gheskett@shentel.net> wrote: > >> I'd think I could start by comparing cupsd.conf's, but miss And I >> can't see the trees for all this forest in the way in both, but >> missing is a client.conf. I think... But that is probably whats >> wrong, me thinking. > > Your directory listings showed that both had a ppd directory, but you > didn't show the content of those directories. Since your error message > was specifically that it couldn't find the PPD, the first thing I'd do > is compare those two directories. > The ppd dirs are empty. And if a copy/paste from this machine, hosting the printers fixes it on the other bullseye machines so these printers are available to whomever wants to use them, like geany or okular etc, can we create a cups bug entry? Perms on those empty ppd dirs are: gene@bpi54:~$ ls -l /etc/cups total 80 -rw-r--r-- 1 root root 30 Apr 8 20:07 client.conf -rw-r--r-- 1 root root 30456 Apr 14 03:14 cups-browsed.conf -rw-r--r-- 1 root root 6486 Apr 30 05:09 cupsd.conf -rw-r--r-- 1 root root 3047 May 23 2022 cups-files.conf drwxr-xr-x 2 root root 4096 May 23 2022 interfaces drwxr-xr-x 2 root lp 4096 May 23 2022 ppd -rw-r--r-- 1 root root 240 Oct 15 2022 raw.convs -rw-r--r-- 1 root root 211 Oct 15 2022 raw.types -rw-r--r-- 1 root root 142 May 23 2022 snmp.conf drwx------ 2 root lp 4096 May 23 2022 ssl -rw-r----- 1 root lp 93 Feb 6 23:41 subscriptions.conf -rw-r----- 1 root lp 335 Feb 6 23:35 subscriptions.conf.O gene@bpi54:~$ ls -l /etc/cups/ppd total 0 So it looks to me like cups, to add a printer, needs to be either root, ask a sudo pw, or be a member of group lp. But group lp is bereft of any other members with "lp:x:7:" as its one and only member, but cups on these machines has yet to ask me for a pw. This looks like it could be part of the original show stopper problem? Or, am I overthinking this again? Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-02 01:00 +0200 |
| Subject | Re: repeat of previous question that has goneunansweredseveraltimes. |
| Message-ID | <GqKEV-5TyW-7@gated-at.bofh.it> |
| In reply to | #257820 |
On 5/1/23 16:00, debian-user@howorth.org.uk wrote: > gene heskett <gheskett@shentel.net> wrote: > >> I'd think I could start by comparing cupsd.conf's, but miss And I >> can't see the trees for all this forest in the way in both, but >> missing is a client.conf. I think... But that is probably whats >> wrong, me thinking. > > Your directory listings showed that both had a ppd directory, but you > didn't show the content of those directories. Since your error message > was specifically that it couldn't find the PPD, the first thing I'd do > is compare those two directories. > The 1st armbian, bpi51, /etc/cups/ppd does contain the PDF generator PPD The 4th one, bpi54 /etc/cups/ppd is empty. All were installed with the same bullseye 11.6 installer. The other two are presently powered down in the middle of building a quad of 3d printers around them. I might be getting on in the middle of my 88th year here, but I can still carve useful things in OpenSCAD and in gcode. At the link in my sig you'll find a link to this machine, and in that link are some pix of what I'm doing. I wrote every byte of the gcode that carves those wooden screws in a couple of those pix. Stronger by quite a bit than anything you can get from fleabay at any price. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
| From | Jeffrey Walton <noloader@gmail.com> |
|---|---|
| Date | 2023-05-01 16:20 +0200 |
| Subject | Re: repeat of previous question that has gone unanswered severaltimes. |
| Message-ID | <GqCxH-5ONn-1@gated-at.bofh.it> |
| In reply to | #257786 |
On Mon, May 1, 2023 at 9:40 AM gene heskett <gheskett@shentel.net> wrote: > > [...] > > lpinfo -v > gene@bpi51:~$ lpinfo -v > -bash: lpinfo: command not found > gene@bpi51:~$ sudo apt install lpinfo > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > E: Unable to locate package lpinfo $ apt-cache search lpinfo $ dpkg -S lpinfo cups-client: /usr/share/man/de/man8/lpinfo.8.gz cups-client: /usr/share/man/man8/lpinfo.8.gz cups-server-common: /usr/share/cups/doc-root/help/man-lpinfo.html cups-client: /usr/sbin/lpinfo cups-client: /usr/share/man/fr/man8/lpinfo.8.gz
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-01 17:00 +0200 |
| Subject | Re: repeat of previous question that has gone unanswered severaltimes. |
| Message-ID | <GqDap-5P0Y-9@gated-at.bofh.it> |
| In reply to | #257783 |
On 5/1/23 08:56, Brian wrote: > On Mon 01 May 2023 at 03:29:28 -0400, gene heskett wrote: > >>> avahi-browse -rt _ipp._tcp >> gene@bpi51:~$ avahi-browse -rt _ipp._tcp >> + eth0 IPv4 Brother HL-L2320D series @ coyote Internet Printer >> local >> + eth0 IPv4 Brother MFC-J6920DW @ coyote Internet Printer >> local >> + eth0 IPv4 HLL2320D @ coyote Internet Printer >> local >> + eth0 IPv4 MFCJ6920DW _tray_2 @ coyote Internet Printer >> local > > You have exactly four (not five or six) print queues manually set up on > the CUPS server coyote (192.168.71.3). It is assumed that when sat at > coyote it is possible to print to any of Brother HL-L2320D series, Brother > MFC-J6920DW, HLL2320D and MFCJ6920DW _tray_2. Im particular - can you > print to HLL2320D from the server? > > [...] > >> = eth0 IPv4 HLL2320D @ coyote Internet Printer >> local >> hostname = [coyote.local] >> address = [192.168.71.3] >> port = [631] >> txt = ["printer-type=0x809016" "printer-state=3" "Duplex=T" "TLS=1.2" >> "UUID=36139eb5-df51-332f-4f80-ebf162ecc0ae" "URF=DM3" "pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf" >> "product=(Brother HL-L2320D series)" "priority=0" >> "adminurl=https://coyote.local.:631/printers/HLL2320D" "ty=Brother HL-L2320D >> for CUPS" "rp=printers/HLL2320D" "qtotal=1" "txtvers=1"] > > As well as three other printers, the host bpi51 sees the shared HLL2320D @ coyote > queue via mDNS/DNS-SD. All is well and good up to now. Let's have > > lpstat -l -e gene@bpi51:~$ lpstat -l -e Brother_HL_L2320D_series_coyote network none ipps://Brother%20HL-L2320D%20series%20%40%20coyote._ipps._tcp.local/cups Brother_MFC_J6920DW_coyote network none ipps://Brother%20MFC-J6920DW%20%40%20coyote._ipps._tcp.local/cups HLL2320D_coyote network none ipps://HLL2320D%20%40%20coyote._ipps._tcp.local/cups MFCJ6920DW_tray_2_coyote network none ipps://MFCJ6920DW%20_tray_2%20%40%20coyote._ipps._tcp.local/cups PDF permanent ipp://localhost/printers/PDF cups-pdf:/ > lpstat -a > lpinfo -v > > from bpi51. > Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2023-05-01 06:30 +0200 |
| Subject | Re: repeat of previous question that has gone unanswered several times. |
| Message-ID | <GqtkJ-5Itp-1@gated-at.bofh.it> |
| In reply to | #257755 |
On Sun 30 Apr 2023 at 19:05:21 (-0400), gene heskett wrote: > > I have a mixed home network, some buster, some bullseye, all up to > date a/o yesterday. > > I have 2 printers shared on this bullseye main box, available as 5 or > 6 printers, each configured in cups to do a specific job. Good > printers, both running on brother's own linux drivers for that > printer. > > All my buster machines can use both of these printers just as if they > were plugged into that machine, but a machine shop full of sawdust and > metal shavings is not a good printer environment, even if there was > room for them, which there isn't. > > All of my bullseye machines are locked out, printer screen at > localhost:631 is empty, and no printers can be found and added. > > But open a shell, and type "lpstat -t" and it gets the full list of > available printers on that same bullseye machine whose cups output is > empty. I thought you had uninstalled cups-browsed from the bullseye machines. Are the printers that you can't see actually on the network, or are they connected to a specific machine (I didn't understand their being "shared"). It was worrying that you said that one machine worked when using the IP address but not its FQDN. (Actually, I've always thought it misguided that that host, coyote, has the same name as the network.) Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | john doe <johndoe65534@mail.com> |
|---|---|
| Date | 2023-05-01 09:40 +0200 |
| Subject | Re: repeat of previous question that has gone unanswered several times. |
| Message-ID | <GqwiB-5Kit-3@gated-at.bofh.it> |
| In reply to | #257755 |
On 5/1/23 01:05, gene heskett wrote: > Greetings all; > > I have a mixed home network, some buster, some bullseye, all up to date > a/o yesterday. > > I have 2 printers shared on this bullseye main box, available as 5 or 6 > printers, each configured in cups to do a specific job. Good printers, > both running on brother's own linux drivers for that printer. > > All my buster machines can use both of these printers just as if they > were plugged into that machine, but a machine shop full of sawdust and > metal shavings is not a good printer environment, even if there was room > for them, which there isn't. > > All of my bullseye machines are locked out, printer screen at > localhost:631 is empty, and no printers can be found and added. > > But open a shell, and type "lpstat -t" and it gets the full list of > available printers on that same bullseye machine whose cups output is > empty. > > Why? > Please refrain from polluting the list when you do not get an answer. -- John Doe
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2023-05-01 13:50 +0200 |
| Subject | Re: repeat of previous question that has gone unanswered several times. |
| Message-ID | <GqAcx-5NgU-1@gated-at.bofh.it> |
| In reply to | #257767 |
[Multipart message — attachments visible in raw view] — view raw
On Mon, May 01, 2023 at 09:37:59AM +0200, john doe wrote: [...] > Please refrain from polluting the list when you do not get an answer. I think repeating a question after a while doesn't count as "polluting". That's what debian-user is for, after all. Cheers -- t
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2023-05-01 15:00 +0200 |
| Subject | Re: repeat of previous question that has gone unanswered several times. |
| Message-ID | <GqBih-5NSo-3@gated-at.bofh.it> |
| In reply to | #257777 |
On Mon 01 May 2023 at 13:41:10 +0200, tomas@tuxteam.de wrote: > On Mon, May 01, 2023 at 09:37:59AM +0200, john doe wrote: > > [...] > > > Please refrain from polluting the list when you do not get an answer. > > I think repeating a question after a while doesn't count as > "polluting". That's what debian-user is for, after all. Indeed. Persistaence has a place and may pay off. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | zithro <slack@rabbit.lu> |
|---|---|
| Date | 2023-05-04 21:50 +0200 |
| Subject | Re: repeat of previous question that has gone unanswered several times. |
| Message-ID | <GrN7H-6yUH-5@gated-at.bofh.it> |
| In reply to | #257781 |
On 01 May 2023 14:53, Brian wrote: > On Mon 01 May 2023 at 13:41:10 +0200, tomas@tuxteam.de wrote: > >> On Mon, May 01, 2023 at 09:37:59AM +0200, john doe wrote: >> >> [...] >> >>> Please refrain from polluting the list when you do not get an answer. >> >> I think repeating a question after a while doesn't count as >> "polluting". That's what debian-user is for, after all. > > Indeed. Persistaence has a place and may pay off. > Indeed, it seems it has paid off, as it works now for Gene ! The Brian-Gene exchanges are now set in stone, and can now serve as a step-by-step debug guide for CUPS. I'm glad Gene followed suggestions this time, right Gene ? ;) Although I was afraid when I saw : *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not> Is that expected at 1st avahi start ? Second question: is that possible to use CUPS/printing without avahi ?
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-04 22:00 +0200 |
| Subject | Re: repeat of previous question that has gone unanswered severaltimes. |
| Message-ID | <GrNhn-6yYc-13@gated-at.bofh.it> |
| In reply to | #257916 |
On 5/4/23 15:43, zithro wrote: > On 01 May 2023 14:53, Brian wrote: >> On Mon 01 May 2023 at 13:41:10 +0200, tomas@tuxteam.de wrote: >> >>> On Mon, May 01, 2023 at 09:37:59AM +0200, john doe wrote: >>> >>> [...] >>> >>>> Please refrain from polluting the list when you do not get an answer. >>> >>> I think repeating a question after a while doesn't count as >>> "polluting". That's what debian-user is for, after all. >> >> Indeed. Persistaence has a place and may pay off. >> > > Indeed, it seems it has paid off, as it works now for Gene ! > > The Brian-Gene exchanges are now set in stone, and can now serve as a > step-by-step debug guide for CUPS. > > I'm glad Gene followed suggestions this time, right Gene ? ;) > > Although I was afraid when I saw : > > *** WARNING: Detected another IPv4 mDNS stack running on this host. This > makes mDNS unreliable and is thus not> > > Is that expected at 1st avahi start ? > > Second question: is that possible to use CUPS/printing without avahi ? > Absolutely, up to bullseye for both buster and bullseye, but not from bullseye to bullseye. > . Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2023-05-05 16:10 +0200 |
| Subject | Re: repeat of previous question that has gone unanswered severaltimes. |
| Message-ID | <Gs4id-6O60-1@gated-at.bofh.it> |
| In reply to | #257918 |
On Thu 04 May 2023 at 15:57:49 -0400, gene heskett wrote: > On 5/4/23 15:43, zithro wrote: > > On 01 May 2023 14:53, Brian wrote: [...] > > Second question: is that possible to use CUPS/printing without avahi ? > > > Absolutely, up to bullseye for both buster and bullseye, but not from > bullseye to bullseye. avahi-daemon is recommended by cups-daemong. Printing is *always* possible without its being on the system, especially if it's desired to make things difficult for all users. I'm afraid the remainder of the sentence is very misleading and amounts to nonsense. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-05 17:50 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <Gs5R0-6OQz-7@gated-at.bofh.it> |
| In reply to | #257985 |
On 5/5/23 10:08, Brian wrote: > On Thu 04 May 2023 at 15:57:49 -0400, gene heskett wrote: > >> On 5/4/23 15:43, zithro wrote: >>> On 01 May 2023 14:53, Brian wrote: > > [...] > >>> Second question: is that possible to use CUPS/printing without avahi ? >>> >> Absolutely, up to bullseye for both buster and bullseye, but not from >> bullseye to bullseye. > > avahi-daemon is recommended by cups-daemong. Printing is *always* possible > without its being on the system, especially if it's desired to make things > difficult for all users. I'm afraid the remainder of the sentence is very > misleading and amounts to nonsense. > What nonsense? I have repeatedly asked why printers shared from this machine, that are seen and usable from any buster machine on my net, but cannot be seen or used by any other bullseye machine on this same net by localhost:631 on that bullseye machine. lpstat and friends can see and use them, but no cups related stuff installed on a bullseye install can. And no one can tell me why... none of the editors or pdf readers that have a print this dialog, geany, evince, etc, can't see or use these printers. I thought maybe we were on the trail of finding a solution, but you were happy & went away when an lp command line worked. But way too many of the other utils ignore any attempt to use lp if they can't use cups. For me, its a serious problem. Yes, lp works, but I'm back to the amiga, ghostscript 5.05 I had to build and an array of shell scripts I wrote to print a multipage document. That is 1990 stuff. I just looked at a calendar and found its now 2023. Seems to me that 33 years later, we should have made more progress than I can see here. Take care & stay well Brian. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2023-05-05 19:50 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <Gs7J8-6PXB-3@gated-at.bofh.it> |
| In reply to | #257990 |
On Fri 05 May 2023 at 11:40:21 -0400, gene heskett wrote: > On 5/5/23 10:08, Brian wrote: > > On Thu 04 May 2023 at 15:57:49 -0400, gene heskett wrote: > > > > > On 5/4/23 15:43, zithro wrote: > > > > On 01 May 2023 14:53, Brian wrote: > > > > [...] > > > > > > Second question: is that possible to use CUPS/printing without avahi ? > > > > > > > Absolutely, up to bullseye for both buster and bullseye, but not from > > > bullseye to bullseye. > > > > avahi-daemon is recommended by cups-daemong. Printing is *always* possible > > without its being on the system, especially if it's desired to make things > > difficult for all users. I'm afraid the remainder of the sentence is very > > misleading and amounts to nonsense. > > > What nonsense? I have repeatedly asked why printers shared from this > machine, that are seen and usable from any buster machine on my net, but > cannot be seen or used by any other bullseye machine on this same net by > localhost:631 on that bullseye machine. > > lpstat and friends can see and use them, but no cups related stuff installed > on a bullseye install can. A very general question was asked. You answered in terms of your own particular situation: * An unrevealed non-Debian OS on bpi51. * A well-known aversion to Avahi. * An aversion to the everywhere model. * An output from 'lpoptions -p HLL2320D_coyote -l' that indicates a broken system. Your conclusion is that the printing system is in itself is defective and that is reflected in your response. Their fault - not mine. > And no one can tell me why... none of the editors or pdf readers that have a > print this dialog, geany, evince, etc, can't see or use these printers. I > thought maybe we were on the trail of finding a solution, but you were happy > & went away when an lp command line worked. But way too many of the other > utils ignore any attempt to use lp if they can't use cups. For me, its a > serious problem. Yes, lp works, but I'm back to the amiga, ghostscript 5.05 > I had to build and an array of shell scripts I wrote to print a multipage > document. That is 1990 stuff. I just looked at a calendar and found its now > 2023. Seems to me that 33 years later, we should have made more progress > than I can see here. I gave you a classic printing solution because New Architecture printing fell apart *on your system*. I am very much disinclined to dig any further into the setup you have devised for printing. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-05 22:40 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GsanD-6RAe-7@gated-at.bofh.it> |
| In reply to | #257995 |
On 5/5/23 13:45, Brian wrote: > On Fri 05 May 2023 at 11:40:21 -0400, gene heskett wrote: > >> On 5/5/23 10:08, Brian wrote: >>> On Thu 04 May 2023 at 15:57:49 -0400, gene heskett wrote: >>> >>>> On 5/4/23 15:43, zithro wrote: >>>>> On 01 May 2023 14:53, Brian wrote: >>> >>> [...] >>> >>>>> Second question: is that possible to use CUPS/printing without avahi ? >>>>> >>>> Absolutely, up to bullseye for both buster and bullseye, but not from >>>> bullseye to bullseye. >>> >>> avahi-daemon is recommended by cups-daemong. Printing is *always* possible >>> without its being on the system, especially if it's desired to make things >>> difficult for all users. I'm afraid the remainder of the sentence is very >>> misleading and amounts to nonsense. >>> >> What nonsense? I have repeatedly asked why printers shared from this >> machine, that are seen and usable from any buster machine on my net, but >> cannot be seen or used by any other bullseye machine on this same net by >> localhost:631 on that bullseye machine. >> >> lpstat and friends can see and use them, but no cups related stuff installed >> on a bullseye install can. > > A very general question was asked. You answered in terms of your own particular > situation: > > * An unrevealed non-Debian OS on bpi51. The armbian version of debian bullseye 11.6 which except for the uboot stuff, uses the debian arm64 repo's for everything else. And which I'm pretty sure has been posted. > * A well-known aversion to Avahi. Which I have now reinstalled, much to my amazement has not insisted on replacing the default route with a 169.number. My aversion to avahi goes clear back to long before Jessie because it was not possible to achieve a working, local 192.168,xx.xx based network with avahi installed. Avahi, like NM has finally learned some manners. > * An aversion to the everywhere model. Because it reduces any printer to the lowest common denominator. No duplex, no multiple paper trays, huge borders & poor almost unreadable fonts. > * An output from 'lpoptions -p HLL2320D_coyote -l' that indicates a broken > system. this is bad? gene@coyote:~$ lpoptions -p HLL2320D_coyote -l PageSize/Media Size: 184.15x260mm 195.09x269.88mm 200.03x148.17mm 4x6 A4 A5 A6 B5 B6 Env10 EnvC5 EnvDL EnvMonarch EnvYou4 Executive FanFoldGermanLegal ISOB5 ISOB6 Legal *Letter Postcard roc16k Custom.WIDTHxHEIGHT InputSlot/Media Source: *Manual Tray1 ColorModel/Output Mode: FastGray *Gray Duplex/Duplex: *None DuplexNoTumble DuplexTumble OutputBin/OutputBin: *FaceDown cupsPrintQuality/cupsPrintQuality: *Normal The only thing I don't see is its shared state? but it is. So why can't another bullseye install use these printers? Buster machines have 100% transparent access. > Your conclusion is that the printing system is in itself is defective and that is > reflected in your response. Their fault - not mine. > >> And no one can tell me why... none of the editors or pdf readers that have a >> print this dialog, geany, evince, etc, can't see or use these printers. I >> thought maybe we were on the trail of finding a solution, but you were happy >> & went away when an lp command line worked. But way too many of the other >> utils ignore any attempt to use lp if they can't use cups. For me, its a >> serious problem. Yes, lp works, but I'm back to the amiga, ghostscript 5.05 >> I had to build and an array of shell scripts I wrote to print a multipage >> document. That is 1990 stuff. I just looked at a calendar and found its now >> 2023. Seems to me that 33 years later, we should have made more progress >> than I can see here. > > I gave you a classic printing solution because New Architecture printing fell apart > *on your system*. I am very much disinclined to dig any further into the setup > you have devised for printing. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2023-05-06 01:00 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <Gscz7-6SMG-1@gated-at.bofh.it> |
| In reply to | #257996 |
On Fri 05 May 2023 at 16:32:36 -0400, gene heskett wrote: > On 5/5/23 13:45, Brian wrote: [...] > > * An output from 'lpoptions -p HLL2320D_coyote -l' that indicates a broken > > system. > > this is bad? > gene@coyote:~$ lpoptions -p HLL2320D_coyote -l > PageSize/Media Size: 184.15x260mm 195.09x269.88mm 200.03x148.17mm 4x6 A4 A5 > A6 B5 B6 Env10 EnvC5 EnvDL EnvMonarch EnvYou4 Executive FanFoldGermanLegal > ISOB5 ISOB6 Legal *Letter Postcard roc16k Custom.WIDTHxHEIGHT > InputSlot/Media Source: *Manual Tray1 > ColorModel/Output Mode: FastGray *Gray > Duplex/Duplex: *None DuplexNoTumble DuplexTumble > OutputBin/OutputBin: *FaceDown > cupsPrintQuality/cupsPrintQuality: *Normal The commaand has been executed on the server, the machine named coyote. The machine of interest is bpi51, which gives > gene@bpi51:~$ lpoptions -p HLL2320D_coyote -l > lpoptions: Unable to get PPD file for HLL2320D_coyote: The printer or class > does not exist. bpi51 is unable to the printer attributes from coyote. Contrast that with a buster machine: gene@sixty40:~$ lpoptions -p HLL2320D_coyote -l > PageSize/Media Size: Custom.WIDTHxHEIGHT *Letter Legal Executive > FanFoldGermanLegal A4 A5 A6 Env10 EnvMonarch EnvDL EnvC5 ISOB5 B5 > ISOB6 B6 4x6 Postcard DoublePostcardRotated EnvYou4 195x270mm > 184x260mm 197x273mm CUSTOM1 CUSTOM2 CUSTOM3 > BrMediaType/MediaType: *PLAIN THIN THICK THICKERPAPER2 BOND ENV > ENVTHICK ENVTHIN RECYCLED > InputSlot/InputSlot: MANUAL *TRAY1 > Duplex/Duplex: DuplexTumble *DuplexNoTumble None > Resolution/Resolution: 300dpi *600dpi 2400x600dpi > TonerSaveMode/Toner Save: *OFF ON > Sleep/Sleep Time [Min.]: *PrinterDefault 2minutes 10minutes 30minutes This output would be expected on bpi51. > The only thing I don't see is its shared state? but it is. > So why can't another bullseye install use these printers? Buster machines > have 100% transparent access. Because bpi51 is unable to get attributes from the server to form a PPD file for HLL2320D_coyote. That is what needs sorting. -- Brian.
[toc] | [prev] | [next] | [standalone]
Page 2 of 5 — ← Prev page 1 [2] 3 4 5 Next page →
Back to top | Article view | linux.debian.user
csiph-web