Re: Difference between ipp, ipps, http, https CUPS protocols?

[Anthony DeRobertis]

Quick search of 
https://sources.debian.org/src/cups/2.3.0-7/backend/ipp.c/ shows there 
is no different between ipp and http, and no difference between ipps and 
https.


ipps and https force encryption, using SSL/TLS (just like you'd expect 
from https) (so if your printer doesn't offer encryption, say due to no 
certificates, it'll fail).


ipp and http do not require encryption (but may use it anyway, if 
available, via a TLS upgrade).


Probably CUPS offers both because some printers' documentation gives 
http:// URLs and some give ipp:// URLs.

Re: convert english+greek emacs file to pdf - SOLVED

[刘涛]

deloptes wrote:Russell L. Harris wrote:



> On StackExchange I found two solutions.  The first, which was the

> recommended, did not work.  The second did work, and is simple:

> 

> \documentclass{article}

> 

> \usepackage[utf8]{inputenc}

> \usepackage[greek,english]{babel}

> \usepackage{alphabeta}

> 

> \begin{document}

> 

> Αυτή η πρόταση ειναι στα ελληνικά, but this one is in english

> 

> \end{document}



In your original post this is a problem



    Content-Type: text/plain; charset=unknown-8bit; format=flowed

    Content-Transfer-Encoding: 8bit
now the Greek characters can be displayed OK,  while they were displayed as ??? in original postRegards

Little problem with rights on a script

[Hans]

Hi folks, 

on debian/testing I am running into a rights problem with a little script.

The script is called "sakis3g" and it is intended to dial out into a UMTS-
connection. 

The script should be run as root, but it also can be run as a normal user, who 
is in group "dip". (In the manual it is called "dig", but this is probably a 
typo. There is no group "dig" on debian).

Starting as root is working well. But when starting as a normal user (who is 
in group "dip") when the modem is inistializing, and it is calling the ppp-
demon, then the system hangs, cause of the lack of rights.

The script settings are >  rwsr-xr-- root:dip
and as far as I know, it should start with the rights of root.

What my failure? What do I do wrong? Where do I think wrong?

Thanks for any help!

Best regards

Hans
 

signature.asc
Description: This is a digitally signed message part.

Re: Little problem with rights on a script

[Nicolas George]

Hans (12019-11-17):
> The script settings are >  rwsr-xr-- root:dip
> and as far as I know, it should start with the rights of root.

Linux does not honor SUID bits for scripts, because it is very tricky to
implement without security issue and most interpreters do not make the
effort.

You need another way of increasing privileges. Possibly nothing at all,
since the privileges of the group may be enough.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature

Re: Little problem with rights on a script

[Reco]

Hi.

On Sun, Nov 17, 2019 at 03:29:58PM +0100, Hans wrote:
> The script settings are >  rwsr-xr-- root:dip
> and as far as I know, it should start with the rights of root.

Both suid and sgid bits are ignored for scripts.
If you need this script to be run as root you either use sudo (and
restrict "dip" group to this particular script), or you write your own
binary executable.

Reco

Re: Little problem with rights on a script

[Gene Heskett]

On Sunday 17 November 2019 09:44:21 Nicolas George wrote:

> Hans (12019-11-17):
> > The script settings are >  rwsr-xr-- root:dip
> > and as far as I know, it should start with the rights of root.
>
> Linux does not honor SUID bits for scripts, because it is very tricky
> to implement without security issue and most interpreters do not make
> the effort.
>
> You need another way of increasing privileges. Possibly nothing at
> all, since the privileges of the group may be enough.
>
> Regards,

i have a similar situation with heyu, which runs as a normal user. But 
udev insists all the ttyUSB# ports are root:root, so I've put a couple 
lines in my rc.local for the last decade or so to make me own, with 0666 
rights, the port the cm11a is plugged into. heyu then fires itself up as 
me and works, doing its job of managing the exterior lights around my 
home at night.

You may have to resort to similar measures. 

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Little problem with rights on a script

[Nicolas George]

Gene Heskett (12019-11-17):
> i have a similar situation with heyu, which runs as a normal user. But 
> udev insists all the ttyUSB# ports are root:root, so I've put a couple 
> lines in my rc.local for the last decade or so to make me own

You could have read the doc for udev instead of wasting your time on a
fragile solution.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature

Re: Little problem with rights on a script

[Gene Heskett]

On Sunday 17 November 2019 09:59:52 Nicolas George wrote:

> Gene Heskett (12019-11-17):
> > i have a similar situation with heyu, which runs as a normal user.
> > But udev insists all the ttyUSB# ports are root:root, so I've put a
> > couple lines in my rc.local for the last decade or so to make me own
>
> You could have read the doc for udev instead of wasting your time on a
> fragile solution.
>
> Regards,

The docs for udev are too paranoid to show one how, and the next package 
upgrade undoes your work anyway so why bother.

Fragile?

This has worked non-stop since ubuntu 6.04, nothing fragile about it 
although I did have to change the perms once because heyu got pickier.

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Little problem with rights on a script

[tomas]

On Sun, Nov 17, 2019 at 10:07:23AM -0500, Gene Heskett wrote:
> On Sunday 17 November 2019 09:59:52 Nicolas George wrote:
> 
> > Gene Heskett (12019-11-17):
> > > i have a similar situation with heyu, which runs as a normal user.
> > > But udev insists all the ttyUSB# ports are root:root, so I've put a
> > > couple lines in my rc.local for the last decade or so to make me own
> >
> > You could have read the doc for udev instead of wasting your time on a
> > fragile solution.
> >
> > Regards,
> 
> The docs for udev are too paranoid to show one how, and the next package 
> upgrade undoes your work anyway so why bother.

Sorry, but man 7 udev seems pretty clear to me. A bit terse, yes, but
complete and useful enough whenSomething like

  KERNEL=="ttyUSB0", MODE="0660", GROUP="dialout",

should roughly do (perhaps DEVPATH instead of KERNEL -- whatever floats
your boat). Go have a look into

  /lib/udev/rules.d/80-debian-compat.rules

to get an idea of how to set permissions on special device files.

And oh, the standard convention here is to use some special group
for a device file and to add those users supposed to much around
with that device to said group (e.g. "dialout", "cdrom", you name
it -- Debian comes with a bunch of those). Then you can set the
device to 0660, not 0666.

But those are just advises. It's your box.

Cheers
-- t


signature.asc
Description: Digital signature

Re: Little problem with rights on a script

[Andy Smith]

On Sun, Nov 17, 2019 at 09:57:39AM -0500, Gene Heskett wrote:
> You may have to resort to similar measures. 

Hopefully though, most people asking questions here are more willing
to read documentation and accept advice, and so will end up with
more sensible solutions.

Regards,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Please consider the environment before reading this e-mail.
 — John Levine

Re: Little problem with rights on a script

[Gene Heskett]

On Sunday 17 November 2019 11:05:36 to...@tuxteam.de wrote:

> On Sun, Nov 17, 2019 at 10:07:23AM -0500, Gene Heskett wrote:
> > On Sunday 17 November 2019 09:59:52 Nicolas George wrote:
> > > Gene Heskett (12019-11-17):
> > > > i have a similar situation with heyu, which runs as a normal
> > > > user. But udev insists all the ttyUSB# ports are root:root, so
> > > > I've put a couple lines in my rc.local for the last decade or so
> > > > to make me own
> > >
> > > You could have read the doc for udev instead of wasting your time
> > > on a fragile solution.
> > >
> > > Regards,
> >
> > The docs for udev are too paranoid to show one how, and the next
> > package upgrade undoes your work anyway so why bother.
>
> Sorry, but man 7 udev seems pretty clear to me. A bit terse, yes, but
> complete and useful enough whenSomething like
>
>   KERNEL=="ttyUSB0", MODE="0660", GROUP="dialout",
>
I am and always have been a member of group dialout. Didn't work.

> should roughly do (perhaps DEVPATH instead of KERNEL -- whatever
> floats your boat). Go have a look into
>
>   /lib/udev/rules.d/80-debian-compat.rules
included here to show lack of clarity:

# Debian specific udev rules for backwards compatibility

# needed for old tape drivers, http://bugs.debian.org/657948
SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_device", TEST!="[module/sg]", 
RUN{builtin}+="kmod load sg"

# device permissions
KERNEL=="mISDNtimer", GROUP="dialout"
KERNEL=="mwave", GROUP="dialout"
KERNEL=="nvram", GROUP="kmem", MODE="0640"
KERNEL=="pktcdvd", GROUP="cdrom", MODE="0644"
KERNEL=="lirc[0-9]*", GROUP="video"
KERNEL=="legousbtower*", MODE="0666"
KERNEL=="sonypi", MODE="0666"
KERNEL=="mmtimer", MODE="0644"
KERNEL=="sgi_*", MODE="0666"
KERNEL=="z90crypt", MODE="0666"

# These rules will create symlinks for CD/DVD drives, to help old
# programs which are unable to automatically discover the devices.
# The first detected device gets the symlink, but this is not stable 
across
# reboots.
ENV{ID_CDROM_CD_RW}=="?*", \
  PROGRAM="/bin/sh -c 'ln -s %k /run/udev/link.cdrw 2>/dev/null; [ 
`readlink /run/udev/link.cdrw` = %k ]", \
  SYMLINK+="cdrw", OPTIONS+="link_priority=-100"
ENV{ID_CDROM_DVD}=="?*", \
  PROGRAM="/bin/sh -c 'ln -s %k /run/udev/link.dvd 2>/dev/null; [ 
`readlink /run/udev/link.dvd` = %k ]", \
  SYMLINK+="dvd", OPTIONS+="link_priority=-100"
ENV{ID_CDROM_DVD_RW}=="?*", \
  PROGRAM="/bin/sh -c 'ln -s %k /run/udev/link.dvdrw 2>/dev/null; [ 
`readlink /run/udev/link.dvdrw` = %k ]", \
  SYMLINK+="dvdrw", OPTIONS+="link_priority=-100"

Doesn't appear to be complete, I see no mentions of the ttyUSB# family of 
devices,and no suggestions as to how to edit it.

So I reasoned that by the time it got to rc.local, udev would have gone 
away and as rc.local runs with root privs, I could do what needed to be 
done in rc.local, so I did and its worked for yonks. And since heyu is 
not officially in the repos due to a licencing incompatibility, the only 
place to ask for help is heyu.  Shrug, its your OS, but its my machine.

> to get an idea of how to set permissions on special device files.
>
> And oh, the standard convention here is to use some special group
> for a device file and to add those users supposed to much around
> with that device to said group (e.g. "dialout", "cdrom", you name
> it -- Debian comes with a bunch of those). Then you can set the
> device to 0660, not 0666.
>
> But those are just advises. It's your box.
That it is. ;-)

Thanks Tomas.

> Cheers
> -- t


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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: UVC device.

[Dan Ritter]

Dan Ritter wrote: 
> 
> I like the looks of that Inogeni, and you'd think that a public
> sector org in Vancouver would like to buy from a Canadian
> company. Or I think so, anyway.

Recently seen, might be useful for you:

https://blog.benjojo.co.uk/post/userspace-usb-drivers

-dsr-

Re: Little problem with rights on a script

[Gene Heskett]

On Sunday 17 November 2019 11:44:40 Andy Smith wrote:

> On Sun, Nov 17, 2019 at 09:57:39AM -0500, Gene Heskett wrote:
> > You may have to resort to similar measures.
>
> Hopefully though, most people asking questions here are more willing
> to read documentation and accept advice, and so will end up with
> more sensible solutions.
>
> Regards,
> Andy

I don't want to be offensive Andy, but those docs do not tell you what to 
do if it doesn't work. See the man page copy that was posted as a link, 
and I re posted as part of my last post shows this lack of real help.  
I've no clue what 3/4 of those words actually translate to, so 75% of 
that man page might as well be written in Swahili.

My first linux install was from the floppy's included in the big red 
Redhat 5.0 book in 1998. 21 years ago I think.  When they started 
charging a seat fee for support, I went 5 or 6 versions of fedora, but 
got tired of always being a half sick lab rat.  About that time another 
of my interests, metal carving with what is now called LinuxCNC, started 
publishing a ubuntu variant with an RTAI patched kernel for realtime 
control of manufacturing machines, then gradually making it official 
with wheezy, went to debian.  So I am used to asking questions and 
hacking up my own fixes. When one of those fixes seems to fit another's 
posted problem, I offer it as one possible fix.

I'll also restate that the pulmonary embolism I had at age 79, which only 
2% survive is a very scary way to die, but I made the grim reaper blink, 
but it cost me some IQ points, then the heart attack in late Sept  
probably cost a few more, but thats the 2nd time I made him blink.

Tested at 147 in '48, one could say I had some to spare, but can now see 
and admit there is a difference.

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: UVC device.

[peter]

I've included 5 References.  Lets see what the server does 
with them.  Just for the record, I'm not subscribed.

From: Dan Ritter 
Date: Sun, 17 Nov 2019 12:01:57 -0500
> Recently seen, might be useful for you:
> 
> https://blog.benjojo.co.uk/post/userspace-usb-drivers

Thanks.  

For a nominal charge, Inogeni can adjust firmware to match the top 
resolution emitted by these cameras.  Also, expense appears to be 
acceptable.  By the new year, I might be able to report a nice 
success.

Regards,   ... Peter E.


-- 
https://en.wikibooks.org/wiki/Medical_Machines
Tel: +1 604 670 0140Bcc: peter at easthope. ca

Reporting Spam in Debian Bugs (and geogebra 4.2+ is non-free btw)?

[Linux-Fan]

Hello fellow list members,

I just came across the following bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692728
It is really a shame that the program is no longer licensed freely*** :(

If one scrolls down to the last message of the bug, it seems to be spam and
a dangerous one at that with a suspicious .zip attachment. I have not
checked it's contents though.

However, wanting to report it as spam, I pressed the link at
"Send a report that this bug log contains spam." which leads to a
confirmation page:

Verify report for bug 692728
Yes, report that bug 692728 has spam

Now I am not sure (maybe it's a language thing): Is it OK to continue
eventhough most of the bug is quite important discussion and only the last
message is spam? Will that work as intended (only removing the last message)
when I continue on that page?

TIA
Linux-Fan
(academic /and/ commercial user)

~~~ ~~~ ~~~ ~~~

***OT for those interested:

I actually came there because I went on Geogebra's website to check how one
does 3D points. It seems to work with Version 5+, but on the website it has
"noncommercial" all over. Now that I knew that it is in Debian, my first
reaction was: What it must be in non-free? Then $ apt-cache policy geogebra
revealed `main` so I thought: It's free, nice! Then I went to check and saw
that Debian sid has this old version 4.X where 6 seems to be current... I
wondered if there was a bug about it and yes: That harmless wishlist bug has
all the stuff of interest. Thank you very much all Debian maintainers that
you take so much effort to steer back those "noncommercial" folks back to
free software... although in this case it seems not to have been fruitful
(one might be hopeful: yet?)?

I have been recommending geogebra ever since I knew about its existence.
Seems this came to a sudden end today (the last time such a thing happened
was literally years ago:
https://lists.debian.org/debian-user/2012/06/msg02248.html).

Re: Reporting Spam in Debian Bugs (and geogebra 4.2+ is non-free btw)?

[Brian]

On Sun 17 Nov 2019 at 21:01:16 +0100, Linux-Fan wrote:

> I just came across the following bug:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692728
> It is really a shame that the program is no longer licensed freely*** :(
> 
> If one scrolls down to the last message of the bug, it seems to be spam and
> a dangerous one at that with a suspicious .zip attachment. I have not
> checked it's contents though.
> 
> However, wanting to report it as spam, I pressed the link at
> "Send a report that this bug log contains spam." which leads to a
> confirmation page:
> 
>   Verify report for bug 692728
>   Yes, report that bug 692728 has spam
> 
> Now I am not sure (maybe it's a language thing): Is it OK to continue
> eventhough most of the bug is quite important discussion and only the last
> message is spam? Will that work as intended (only removing the last message)
> when I continue on that page?

Continue with reporting the spam message. It does not remove the bug
record. You will not bring the BTS to its knees by doing this.

In fact, it does not remove the spam. That has to be done by hand by
a user who is involved in spam removal.

-- 
Brian.

Re: Reporting Spam in Debian Bugs (and geogebra 4.2+ is non-free btw)?

[Linux-Fan]

Brian writes:


On Sun 17 Nov 2019 at 21:01:16 +0100, Linux-Fan wrote:


[...]


>Verify report for bug 692728
>Yes, report that bug 692728 has spam
>
> Now I am not sure (maybe it's a language thing): Is it OK to continue
> eventhough most of the bug is quite important discussion and only the last
> message is spam? Will that work as intended (only removing the last
> message)
> when I continue on that page?

Continue with reporting the spam message. It does not remove the bug
record. You will not bring the BTS to its knees by doing this.

In fact, it does not remove the spam. That has to be done by hand by
a user who is involved in spam removal.


[...]

Thank you very much for the clarification. I proceeded with reporting the
spam and it now says:

Report accepted
Thank you for reporting that this bug log contains spam. These reports 
are
reviewed regularly and used to clean the bug logs and train the spam
filters.

Which makes it perfectly clear for me :)

Thanks again
Linux-Fan

Re: Reporting Spam in Debian Bugs (and geogebra 4.2+ is non-free btw)?

[Brian]

On Sun 17 Nov 2019 at 21:36:11 +0100, Linux-Fan wrote:

> Brian writes:
> 
> > On Sun 17 Nov 2019 at 21:01:16 +0100, Linux-Fan wrote:
> 
> [...]
> 
> > >   Verify report for bug 692728
> > >   Yes, report that bug 692728 has spam
> > >
> > > Now I am not sure (maybe it's a language thing): Is it OK to continue
> > > eventhough most of the bug is quite important discussion and only the last
> > > message is spam? Will that work as intended (only removing the last
> > > message)
> > > when I continue on that page?
> > 
> > Continue with reporting the spam message. It does not remove the bug
> > record. You will not bring the BTS to its knees by doing this.
> > 
> > In fact, it does not remove the spam. That has to be done by hand by
> > a user who is involved in spam removal.
> 
> [...]
> 
> Thank you very much for the clarification. I proceeded with reporting the
> spam and it now says:
> 
>   Report accepted
>   Thank you for reporting that this bug log contains spam. These reports 
> are
>   reviewed regularly and used to clean the bug logs and train the spam
>   filters.
> 
> Which makes it perfectly clear for me :)

Reviewing is the issue. It needs a real person to read the mail, make
a judgement and do it. Half-a-dozen dedicated volunteers would probably
be enough to keep the BTS clean of spam.

-- 
Brian.

Lenovo Ideapad 320 requires non-free firmware vega 20. In sid, but not Buster

[Kenneth Parker]

Hello,

I am running Buster 10.2 on a Lenovo Ideapad 320, and having significant
Graphics issues.  I went through the usual suspects
(linux-firmware-nonfree, firmware-amd-graphics, etc) and am mostly there.

In /lib/firmware/amdgpu, there are lots of entries beginning with vega
(i.e. vega10 and vega12), but the error messages on bootup state that the
missing firmware begins with vega20, which I find in Debian Sid, but not in
Buster Stable.

Is there a suggested way to install this Firmware into Buster from Sid,
without creating a Franken-Debian?  (And forever living with broken
Graphics isn't my first choice.  Also, doing a Complete Install from Sid
isn't my Second Choice).

Note:  I didn't check "Backports", when I did the install.  I could add it,
if someone thinks vega20 might be there.  Is there a way for me to check?

Thank you in advance!

Kenneth Parker

Re: Reporting Spam in Debian Bugs (and geogebra 4.2+ is non-free btw)?

[Sven Joachim]

On 2019-11-17 20:48 +, Brian wrote:

> On Sun 17 Nov 2019 at 21:36:11 +0100, Linux-Fan wrote:
>
>> Brian writes:
>>
>> > On Sun 17 Nov 2019 at 21:01:16 +0100, Linux-Fan wrote:
>>
>> [...]
>>
>> > >  Verify report for bug 692728
>> > >  Yes, report that bug 692728 has spam
>> > >
>> > > Now I am not sure (maybe it's a language thing): Is it OK to continue
>> > > eventhough most of the bug is quite important discussion and only the 
>> > > last
>> > > message is spam? Will that work as intended (only removing the last
>> > > message)
>> > > when I continue on that page?
>> >
>> > Continue with reporting the spam message. It does not remove the bug
>> > record. You will not bring the BTS to its knees by doing this.
>> >
>> > In fact, it does not remove the spam. That has to be done by hand by
>> > a user who is involved in spam removal.
>>
>> [...]
>>
>> Thank you very much for the clarification. I proceeded with reporting the
>> spam and it now says:
>>
>>  Report accepted
>>  Thank you for reporting that this bug log contains spam. These reports 
>> are
>>  reviewed regularly and used to clean the bug logs and train the spam
>>  filters.
>>
>> Which makes it perfectly clear for me :)
>
> Reviewing is the issue. It needs a real person to read the mail, make
> a judgement and do it. Half-a-dozen dedicated volunteers would probably
> be enough to keep the BTS clean of spam.

AFAICT the number of volunteers has been zero for many years.  I have
reported dozens if not hundreds of spam-infested bugs, and never saw the
spam actually removed.

So reporting a bug as spam does not do any harm, but it is a minor waste
of time in my experience.

Cheers,
   Sven

Re: Lenovo Ideapad 320 requires non-free firmware vega 20. In sid, but not Buster

[Anthony DeRobertis]

On 11/17/19 3:51 PM, Kenneth Parker wrote:


Note:  I didn't check "Backports", when I did the install. I could add 
it, if someone thinks vega20 might be there.  Is there a way for me to 
check?


You can check the versions of packages at https://packages.debian.org, 
so for firmware-amd-graphics that'd be 
https://packages.debian.org/search?keywords=firmware-amd-graphics which 
shows 20190717-2 in sid and the same version (with the ~bpo… suffix) in 
buster-backports.


So enabling buster-backports and installing firmware-amd-graphics from 
there ought to work.

Re: UVC device.

[Dan Ritter]

pe...@easthope.ca wrote: 
> I've included 5 References.  Lets see what the server does 
> with them.  Just for the record, I'm not subscribed.

It looks perfectly reasonable.


> From: Dan Ritter 
> Date: Sun, 17 Nov 2019 12:01:57 -0500
> > Recently seen, might be useful for you:
> > 
> > https://blog.benjojo.co.uk/post/userspace-usb-drivers
> 
> Thanks.  
> 
> For a nominal charge, Inogeni can adjust firmware to match the top 
> resolution emitted by these cameras.  Also, expense appears to be 
> acceptable.  By the new year, I might be able to report a nice 
> success.

I'm sure we all wish you the best of luck.

-dsr-

Re: Lenovo Ideapad 320 requires non-free firmware vega 20. In sid, but not Buster

[Kenneth Parker]

On Sun, Nov 17, 2019 at 5:04 PM Anthony DeRobertis 
wrote:

> On 11/17/19 3:51 PM, Kenneth Parker wrote:
> >
> > Note:  I didn't check "Backports", when I did the install. I could add
> > it, if someone thinks vega20 might be there.  Is there a way for me to
> > check?
>
> You can check the versions of packages at https://packages.debian.org,
> so for firmware-amd-graphics that'd be
> https://packages.debian.org/search?keywords=firmware-amd-graphics which
> shows 20190717-2 in sid and the same version (with the ~bpo… suffix) in
> buster-backports.
>
> So enabling buster-backports and installing firmware-amd-graphics from
> there ought to work.
>

That did it.  Success!  Many thanks!  (Now on to the next, unrelated
issue.  LOL!)

Kenneth Parker

Re: convert english+greek emacs file to pdf - SOLVED

[David Wright]

On Sat 16 Nov 2019 at 20:07:42 (+0100), deloptes wrote:
> Russell L. Harris wrote:
> 
> > On StackExchange I found two solutions.  The first, which was the
> > recommended, did not work.  The second did work, and is simple:
> > 
> > \documentclass{article}
> > 
> > \usepackage[utf8]{inputenc}
> > \usepackage[greek,english]{babel}
> > \usepackage{alphabeta}
> > 
> > \begin{document}
> > 
> > Αυτή η πρόταση ειναι στα ελληνικά, but this one is in english
> > 
> > \end{document}
> 
> In your original post this is a problem
> 
> Content-Type: text/plain; charset=unknown-8bit; format=flowed
> Content-Transfer-Encoding: 8bit

You don't say how the problem manifested itself. My buster/mutt
displays the post as I assume the writer desired it to appear.
The email was in UTF-8 despite not declaring itself to be so.

Cheers,
David.

Re: Little problem with rights on a script

[David Wright]

On Sun 17 Nov 2019 at 12:56:06 (-0500), Gene Heskett wrote:
> On Sunday 17 November 2019 11:44:40 Andy Smith wrote:
> > On Sun, Nov 17, 2019 at 09:57:39AM -0500, Gene Heskett wrote:
> > > You may have to resort to similar measures.
> >
> > Hopefully though, most people asking questions here are more willing
> > to read documentation and accept advice, and so will end up with
> > more sensible solutions.
> 
> I don't want to be offensive Andy, but those docs do not tell you what to 
> do if it doesn't work. See the man page copy that was posted as a link, 
> and I re posted as part of my last post shows this lack of real help.  
> I've no clue what 3/4 of those words actually translate to, so 75% of 
> that man page might as well be written in Swahili.

Your last post appears to quote the contents of
/lib/udev/rules.d/80-debian-compat.rules
and not the man page. AIUI 80-debian-compat.rules was referenced
just to show you examples of setting permissions.

The man page (man udev) goes through all the words that you don't
understand, and explains their roles. However, it lacks examples,
but there are an overwhelming number of examples in /lib/udev/rules.d/.

If you grep them, you'll see:
/lib/udev/rules.d/40-usb_modeswitch.rules:# Adds a symlink "gsmmodem[n]" to the 
lowest ttyUSB port with interrupt
/lib/udev/rules.d/40-usb_modeswitch.rules:KERNEL=="ttyUSB*", 
ATTRS{bNumConfigurations}=="*", PROGRAM="usb_modeswitch --symlink-name %p 
%s{idVendor} %s{idProduct} %E{PRODUCT}", SYMLINK+="%c"
/lib/udev/rules.d/60-serial.rules:KERNEL!="ttyUSB[0-9]*|ttyACM[0-9]*", 
GOTO="serial_end"
which might give you a clue as to which files will interest you.

> My first linux install was from the floppy's included in the big red 
> Redhat 5.0 book in 1998. 21 years ago I think.  When they started 
> charging a seat fee for support, I went 5 or 6 versions of fedora, but 
> got tired of always being a half sick lab rat.  About that time another 
> of my interests, metal carving with what is now called LinuxCNC, started 
> publishing a ubuntu variant with an RTAI patched kernel for realtime 
> control of manufacturing machines, then gradually making it official 
> with wheezy, went to debian.  So I am used to asking questions and 
> hacking up my own fixes. When one of those fixes seems to fit another's 
> posted problem, I offer it as one possible fix.
> 
> I'll also restate that the pulmonary embolism I had at age 79, which only 
> 2% survive is a very scary way to die, but I made the grim reaper blink, 
> but it cost me some IQ points, then the heart attack in late Sept  
> probably cost a few more, but thats the 2nd time I made him blink.
> 
> Tested at 147 in '48, one could say I had some to spare, but can now see 
> and admit there is a difference.

TL;DR

Cheers,
David.

Re: convert english+greek emacs file to pdf - mutt configuration

[Russell L. Harris]

On Sun, Nov 17, 2019 at 07:44:48PM -0600, David Wright wrote:

On Sat 16 Nov 2019 at 20:07:42 (+0100), deloptes wrote:
You don't say how the problem manifested itself. My buster/mutt
displays the post as I assume the writer desired it to appear.
The email was in UTF-8 despite not declaring itself to be so.


I found in the mutt manual about half a dozen mentions of charset, but
I do not at the moment have the time or energy to dig through all that
and figure out what needs to be done.

But if my Mutt is mis-configured and someone can tell me how to
correct it, I shall be happy to comply.

My cc: of the message in question displays ? instead of Greek
characters, but that is of no concern to me, inasmuch as my inquiry
was regarding printing stuff displayed on a web page, in connection
with Bible study.  I do not at this time have need for Greek in email.

Besides, I am running neoMutt simply because that is the only option I
have in Debian 9.  Whenever I upgrade to Debian 10 or 11, I plan to
run Mutt, rather than neoMutt.

Re: convert english+greek emacs file to pdf - mutt configuration

[David Wright]

On Mon 18 Nov 2019 at 03:15:06 (+), Russell L. Harris wrote:
> On Sun, Nov 17, 2019 at 07:44:48PM -0600, David Wright wrote:
> > On Sat 16 Nov 2019 at 20:07:42 (+0100), deloptes wrote:
> > You don't say how the problem manifested itself. My buster/mutt
> > displays the post as I assume the writer desired it to appear.
> > The email was in UTF-8 despite not declaring itself to be so.
> 
> I found in the mutt manual about half a dozen mentions of charset, but
> I do not at the moment have the time or energy to dig through all that
> and figure out what needs to be done.
> 
> But if my Mutt is mis-configured and someone can tell me how to
> correct it, I shall be happy to comply.

My own configuration file ~/.mutt/muttrc contains the line:
set send_charset="us-ascii:utf-8"
and this causes emails to be sent with:
  Content-Type: text/plain; charset=us-ascii
unless there is any non-ASCII character in the email, in which case
it switches to:
  Content-Type: text/plain; charset=utf-8
instead.

> My cc: of the message in question displays ? instead of Greek
> characters, but that is of no concern to me, inasmuch as my inquiry
> was regarding printing stuff displayed on a web page, in connection
> with Bible study.  I do not at this time have need for Greek in email.

By your cc:, do you mean the locally written file copy or the post
sent to you by the list server (assuming you're subscribed, which you
appear to be). If you don't have any other occurrence of the string
"charset" in your muttrc configuration file, then I'm wondering
what your locale is set to. Mine is:
$ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
$ grep '^[a-z]' /etc/locale.gen 
en_US.UTF-8 UTF-8
en_GB.UTF-8 UTF-8
$ 

> Besides, I am running neoMutt simply because that is the only option I
> have in Debian 9.  Whenever I upgrade to Debian 10 or 11, I plan to
> run Mutt, rather than neoMutt.

I just booted up my old stretch system, and I get the same contents
displayed as with buster. Like you, I'm using what Debian provides
for mutt. I made no change to my configuration when upgrading.

(I haven't taken an interest in the mutt/neomutt debate/argument.)

Cheers,
David.