Re: Default date output format changed after an upgrade to buster

[deloptes]

John Hasler wrote:

> All clocks tick.  "Tick" no longer means "emit a noise once per second"
> in modern chronometry.

+1
The clock frequency is produced by oscillator at 32.768kHz which means that
15 flops at this frequency produce 1sec. This is one tick.

Re: 24-hour vs. 12-hour time, ambiguity, and abbreviations (was Re: Default date output format changed after an upgrade to buster)

[The Wanderer]

On 2019-09-12 at 23:20, John Hasler wrote:

> The Wanderer writes:
>
>> Wherever you need to specify midnight in a form where specifying any
>> other time would get the "AM"/"PM"/"M"(eridiem) abbreviation.
> 
>> To have a two-letter abbreviation for midnight but a one-letter one
>> for noon might be acceptable, although it would feel lopsided to me,
>> but just offhand I don't know of any suitable candidate to be that
>> two-letter abbreviation. Again, do you have any suggestions?
> 
> Why abbreviate at all?  It's been a long time since we stopped needing
> to save bytes.

Why do people abbreviate "AM" and "PM" when speaking out loud?

Again, "on a computer" - or even "in writing" - is not the only context
where these abbreviations get used.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: 24-hour vs. 12-hour time, ambiguity, and abbreviations (was Re: Default date output format changed after an upgrade to buster)

[John Hasler]

The Wanderer writes:
> Wherever you need to specify midnight in a form where specifying any
> other time would get the "AM"/"PM"/"M"(eridiem) abbreviation.

> To have a two-letter abbreviation for midnight but a one-letter one
> for noon might be acceptable, although it would feel lopsided to me,
> but just offhand I don't know of any suitable candidate to be that
> two-letter abbreviation. Again, do you have any suggestions?

Why abbreviate at all?  It's been a long time since we stopped needing
to save bytes.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: Default date output format changed after an upgrade to buster

[John Hasler]

 David Wright writes:
> Odd that they decided to employ that logic in the 21st century after
> (most) clocks had ceased to tick.

All clocks tick.  "Tick" no longer means "emit a noise once per second"
in modern chronometry.

> But it is remarkable to use logic to prove a contradiction...

What contradiction?

> ...and infinitesimals...

No infinitesimals here.  Perhaps some limits.

> ...to explain an arbitrary colloquialism.

Describe, not explain.  Most people use it so the rest of us have to
deal with it, like it or not.  They are going to assume that you know
what they mean by "12PM".  If you don't assign the same meaning to it
that they do you will be late for your meeting.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: 24-hour vs. 12-hour time, ambiguity, and abbreviations (was Re: Default date output format changed after an upgrade to buster)

[The Wanderer]

On 2019-09-12 at 21:49, David Wright wrote:

> On Thu 12 Sep 2019 at 12:42:01 (-0400), The Wanderer wrote:
>
>> On 2019-09-12 at 12:03, David Wright wrote:

>>> It might be ambiguous if m were also an abbreviation for midnight,
>>> which I've never come across.
>> 
>> Neither have I, but I also haven't come across any *other* abbreviation
>> for it which might be used in this type of context (have you?), and "M"
>> is just as intuitive a choice for abbreviating "midnight" as it is for
>> abbreviating "meridiem".
>> 
>> One could argue "M" for "midnight" and "N" for "noon", but then you lose
>> the intuitiveness of M for meridiem, and people would mishear the two as
>> each other in nonline conversation all the time anyway.
> 
> I don't see a need for a one-letter abbreviation for midnight, nor the
> wisdom in introducing one that's already used in the same context.
> Where would you use it?

Wherever you need to specify midnight in a form where specifying any
other time would get the "AM"/"PM"/"M"(eridiem) abbreviation.

To have a two-letter abbreviation for midnight but a one-letter one for
noon might be acceptable, although it would feel lopsided to me, but
just offhand I don't know of any suitable candidate to be that
two-letter abbreviation. Again, do you have any suggestions?

> Why not just drop 12-hour times? I don't think I've ever formatted a
> 12-hour time on a computer (unless you want to count the example
> quoted below).

This isn't limited to the context of "on a computer". I think I
originally came up with the notion of referring to noon as "12:00 M" in
a context of mentioning the times in out-loud conversation; the
abbreviations are certainly used in more than just computerized contexts.

For myself, I likely would drop 12-hour time. But as long as the world
isn't agreeing to do that, pursuing ways to make 12-hour time work more
logically and less ambiguously is still worthwhile.

And of course part of the reason I like the idea is because I find the
odd looks I get when I refer to "12:00 M" without previous explanation
to be amusing.

>>> When I read emails, I only see the Date: line from the header, and
>>> the timedates used in the quotation lines. One thing I find odd is
>>> mixing AM/PM with hours containing a leading zero. I was always
>>> taught that 7 p.m. or 7pm was not written as 07, but I see that a
>>> lot here. Contrast
>>> 
>>> $ TZ=Europe/Paris date +'%I.%M %p'
>>> 06.01 PM
>>> $ TZ=Europe/Paris date +'%l.%M %p'
>>>  6.01 PM
>>> $ 
>> 
>> That's probably to ease parsing by automated tools, such as sort, so
>> that they don't have to worry about handling field width.
> 
> That wouldn't be possible anyway, because you don't have control over,
> for example, whether the time follows the date, and other variability.

That just makes it even harder; not impossible, but unwieldy and
problematic enough that very few are likely to bother with trying.

> No. I think it's more likely that most people don't notice
> conventions unless they're brought to their attention. Of course, if
> you're old enough, you had years of pre-digital experience when no
> one thought of padding dates and times with 0s. That might be why I
> notice 'odd' formatting like this.

I may be confused. I thought we were talking about why some people /
tools use zero-padded hours fields with 12-hour time; I don't see how
the decision to do that could in any way arise from failure to notice a
convention without having it pointed out.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: Default date output format changed after an upgrade to buster

[David Wright]

On Thu 12 Sep 2019 at 14:13:19 (-0500), John Hasler wrote:
> rhkramer writes:
> > If 12:01 pm is two minutes after 11:59 am, then 12:00 is AM.
> 
> AM means "before the meridian", that is, before the Sun crosses the
> meridian[1].  PM means after the meridian.  Time is the ordering of
> events.  The Sun crossing the meridian is an event which we call noon:
> everything else happens either before or after it[2].  12:00 is noon
> (except when it's midnight[3]) so it makes no sense to call it either AM
> or PM: call it noon.  Say "12 noon" if you feel like being redundant.
> 
> It makes no sense to speak of something happening at noon: only noon
> itself happens then[2]. People are going to do so anyway, though, so one
> must assume that when they say "The event will occur at noon" they mean
> that it will occur during the interval between noon and the first clock
> tick after noon.  This makes "12:00 noon" 12:00PM.  Thus colloquially
> 12:00PM is in the middle of the day.

Odd that they decided to employ that logic in the 21st century after
(most) clocks had ceased to tick.

But it is remarkable to use logic to prove a contradiction,
and infinitesimals to explain an arbitrary colloquialism.

> [1] Notionally.  The ancients used local solar time.
> 
> [2] This applies to any tick of your clock.
> 
> [3] Same argument applies to midnight (it's when the Sun crosses the
> other meridian), making it 12:00AM.

Cheers,
David.

Re: 24-hour vs. 12-hour time, ambiguity, and abbreviations (was Re: Default date output format changed after an upgrade to buster)

[David Wright]

On Thu 12 Sep 2019 at 12:42:01 (-0400), The Wanderer wrote:
> On 2019-09-12 at 12:03, David Wright wrote:
> > On Thu 12 Sep 2019 at 09:42:03 (-0400), The Wanderer wrote:
> >> On 2019-09-12 at 06:30, Dan Ritter wrote:
> 
> >>> There is only one sensible interpretation:
> >>> 
> >>> If 11:59 AM is two minutes before 12:01 PM, then 12:00 is PM.
> >>> 
> >>> If 11:59 PM is two minutes before 12:01 AM, then 12:00 is AM.
> >> 
> >> I take a slightly different approach, based on the apparent actual
> >> meanings of the words for which "AM" and "PM are abbreviations.
> >> 
> >> It seems intuitively obvious to me that between 11:59 Ante-Meridiem and
> >> 12:01 Post-Meridiem must lie 12:00 Meridiem. (Though 12:00:01 - one
> >> second later - would be Post-Meridiem again.)
> >> 
> >> Similarly, though less an "obvious necessity" consequence, between 11:59
> >> Post-Meridiem and 12:01 Ante-Meridiem lies 12:00 Midnight. (I understand
> >> "meridiem" to be derived from a word which would have literally meant
> >> "mid-day".)
> > 
> > Meridies (nominative case in Latin).
> > 
> >> Both are intuitively represented as "12:00 M" - with no "A" or "P" - and
> >> that, in its turn, is ambiguous.
> > 
> > It might be ambiguous if m were also an abbreviation for midnight,
> > which I've never come across.
> 
> Neither have I, but I also haven't come across any *other* abbreviation
> for it which might be used in this type of context (have you?), and "M"
> is just as intuitive a choice for abbreviating "midnight" as it is for
> abbreviating "meridiem".
> 
> One could argue "M" for "midnight" and "N" for "noon", but then you lose
> the intuitiveness of M for meridiem, and people would mishear the two as
> each other in nonline conversation all the time anyway.

I don't see a need for a one-letter abbreviation for midnight, nor the
wisdom in introducing one that's already used in the same context.
Where would you use it? Why not just drop 12-hour times? I don't think
I've ever formatted a 12-hour time on a computer (unless you want to
count the example quoted below).

Even accepting that 24:00 Thursday and 00:00 Friday express the same
time could be risky unless you know and trust that the source is
consistent. That's why people like insurance companies often use 23:59
and 00:01, because to them the exact day matters.

> >> That being part of why I stick with 24-hour time whenever possible.
> > 
> > When I read emails, I only see the Date: line from the header, and
> > the timedates used in the quotation lines. One thing I find odd is
> > mixing AM/PM with hours containing a leading zero. I was always
> > taught that 7 p.m. or 7pm was not written as 07, but I see that a
> > lot here. Contrast
> > 
> > $ TZ=Europe/Paris date +'%I.%M %p'
> > 06.01 PM
> > $ TZ=Europe/Paris date +'%l.%M %p'
> >  6.01 PM
> > $ 
> 
> That's probably to ease parsing by automated tools, such as sort, so
> that they don't have to worry about handling field width.

That wouldn't be possible anyway, because you don't have control over,
for example, whether the time follows the date, and other variability.
No. I think it's more likely that most people don't notice conventions
unless they're brought to their attention. Of course, if you're old
enough, you had years of pre-digital experience when no one thought of
padding dates and times with 0s. That might be why I notice 'odd'
formatting like this.

Cheers,
David.

Problème majeur avec Buster 10.1 sur KDE. Gel avec Dolphin en root

[Martin Vézina]

J'ai eu le problème en ouvrant un Dolphin en root (dans la configuration
du menus KDE dans Avancé, Exécuter en tant qu’utilisateur différent,
avec root).

Lors du démarrage, je saisie le mot de passe root (je ne veux pas
activer le sudo) et la fenêtre "kdesu" du mot de passe gel. Ça
fonctionnait bien avec Jessie et Stretch. Je ne sais pas si le problème
est connu et sera corrigé.

C'est sûr que je ne peux pas demander à mon père ou un ami d'utiliser
une linge de commande (Konsole) pour faire certaines taches.

Si quelqu’un a une idée pour ce problème?

Merci à l’avance! Bonne journée ou bonne nuit, selon le fuseau horaire...

Re: apt-offline

[Alexandre Rossi]

Hi,

> > I see that apt-offline is not part of buster. Is there any plan to add it?
> 
> Only the maintainer would know about that. It is unlikely he reads this
> list.

https://bugs.debian.org/871656 is what keeps apt-offline out of testing
and thus stable.

Alex

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[deloptes]

David wrote:

> I didn't bother with the heatsinks that came with it. I just wanted a
> fan and some ventilation instead of a sealed little plastic oven.

Yes, a similar was ordered and arrived as well. I tend to plan all of this
in my head and usually it works so well, that I do not have to run to the
shop after. It simply kills the excitement. And imagine it is a Sunday -
you have to wait a whole day or may be longer if you can not find what you
need in the local IT shop and then complain like Gene :)

regards

Re: apt-offline

[Brian]

On Thu 12 Sep 2019 at 13:36:35 -0400, Paul Thomas wrote:

> Hello,
> 
> I see that apt-offline is not part of buster. Is there any plan to add it?

Only the maintainer would know about that. It is unlikely he reads this
list.

-- 
Brian.

Re: Default date output format changed after an upgrade to buster

[John Hasler]

rhkramer writes:
> If 12:01 pm is two minutes after 11:59 am, then 12:00 is AM.

AM means "before the meridian", that is, before the Sun crosses the
meridian[1].  PM means after the meridian.  Time is the ordering of
events.  The Sun crossing the meridian is an event which we call noon:
everything else happens either before or after it[2].  12:00 is noon
(except when it's midnight[3]) so it makes no sense to call it either AM
or PM: call it noon.  Say "12 noon" if you feel like being redundant.

It makes no sense to speak of something happening at noon: only noon
itself happens then[2]. People are going to do so anyway, though, so one
must assume that when they say "The event will occur at noon" they mean
that it will occur during the interval between noon and the first clock
tick after noon.  This makes "12:00 noon" 12:00PM.  Thus colloquially
12:00PM is in the middle of the day.



[1] Notionally.  The ancients used local solar time.

[2] This applies to any tick of your clock.

[3] Same argument applies to midnight (it's when the Sun crosses the
other meridian), making it 12:00AM.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Thomas D Dial]

On Tue, 2019-09-10 at 07:18 -0400, Gene Heskett wrote:
> On Monday 09 September 2019 23:06:27 Thomas D Dial wrote:
> 
> > On Mon, 2019-09-09 at 12:21 -0400, Gene Heskett wrote:
(unrelated material omitted)
> > > $PITA problem, raspian insists the first, usr 1000 is
> > > "pi".  Is there a foolproof way to convert that to "gene", or am I
> > > stuck
> > > logging into it as "pi"?
> >
> > I do not know if it is foolproof, but I would try
> >
> > usermod -l gene pi
> >
> > as root (or maybe with sudo; I am not sure that it would work while
> pi
> > is logged in, though).
> >
> > I have used it occasionally, and the only issue is with (mostly
> gnome-
> > related) dotfiles in the login directory that contain the old login
> as
> > a string and after the change need to have that replaced by the new
> > login. An unfortunate number of them are in sqlite files and unless
> > the details are important it probably is easiest to delete them and
> > start over.
> >
> That sounds like its fraught with all sorts of login cockups. 
> Inconvenient at best, so I'll probably skip it.

I would not expect it to be a significant on a fairly fresh install (for
instance, if you haven't used the GUI or, maybe, the web browser), where
those dotfiles are few and often empty.

My recollection was that files under .config were the most trouble, that
on a system where the renamed account had been used extensively and had
absolute paths containing the former username in various configuration
files.
 
Tom Dial.

> (more omissions)

> Question posted on their forum.
> 
> 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 

apt-offline

[Paul Thomas]

Hello,

I see that apt-offline is not part of buster. Is there any plan to add it?

thanks,
Paul

Re: 24-hour vs. 12-hour time, ambiguity, and abbreviations (was Re: Default date output format changed after an upgrade to buster)

[The Wanderer]

On 2019-09-12 at 12:03, David Wright wrote:

> On Thu 12 Sep 2019 at 09:42:03 (-0400), The Wanderer wrote:
>
>> On 2019-09-12 at 06:30, Dan Ritter wrote:

>>> There is only one sensible interpretation:
>>> 
>>> If 11:59 AM is two minutes before 12:01 PM, then 12:00 is PM.
>>> 
>>> If 11:59 PM is two minutes before 12:01 AM, then 12:00 is AM.
>> 
>> I take a slightly different approach, based on the apparent actual
>> meanings of the words for which "AM" and "PM are abbreviations.
>> 
>> It seems intuitively obvious to me that between 11:59 Ante-Meridiem and
>> 12:01 Post-Meridiem must lie 12:00 Meridiem. (Though 12:00:01 - one
>> second later - would be Post-Meridiem again.)
>> 
>> Similarly, though less an "obvious necessity" consequence, between 11:59
>> Post-Meridiem and 12:01 Ante-Meridiem lies 12:00 Midnight. (I understand
>> "meridiem" to be derived from a word which would have literally meant
>> "mid-day".)
> 
> Meridies (nominative case in Latin).
> 
>> Both are intuitively represented as "12:00 M" - with no "A" or "P" - and
>> that, in its turn, is ambiguous.
> 
> It might be ambiguous if m were also an abbreviation for midnight,
> which I've never come across.

Neither have I, but I also haven't come across any *other* abbreviation
for it which might be used in this type of context (have you?), and "M"
is just as intuitive a choice for abbreviating "midnight" as it is for
abbreviating "meridiem".

One could argue "M" for "midnight" and "N" for "noon", but then you lose
the intuitiveness of M for meridiem, and people would mishear the two as
each other in nonline conversation all the time anyway.

>> That being part of why I stick with 24-hour time whenever possible.
> 
> When I read emails, I only see the Date: line from the header, and
> the timedates used in the quotation lines. One thing I find odd is
> mixing AM/PM with hours containing a leading zero. I was always
> taught that 7 p.m. or 7pm was not written as 07, but I see that a
> lot here. Contrast
> 
> $ TZ=Europe/Paris date +'%I.%M %p'
> 06.01 PM
> $ TZ=Europe/Paris date +'%l.%M %p'
>  6.01 PM
> $ 

That's probably to ease parsing by automated tools, such as sort, so
that they don't have to worry about handling field width.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: Default date output format changed after an upgrade to buster

[rhkramer]

On Thursday, September 12, 2019 08:26:23 AM Nate Bargmann wrote:
> Not all Walmarts are like that.  ;-)
> 
> The one in Beatrice, NE is as you describe, at least the north most
> entrance.  The ones in Marysviile, KS and Fairbury, NE are "normal",
> i.e. ingress on the right when outside the store and egress on the right
> when inside the store.

Well, I'm glad some Walmarts are true "red blooded" Americans ;-)
 
> Apologies for more clock drift.  ;-D

Yeah, me too!

Re: Default date output format changed after an upgrade to buster

[rhkramer]

On Thursday, September 12, 2019 08:09:18 AM Michael Stone wrote:
> The railroads solved this more than a century ago: you just never use
> 12:00 and stick with 11:59 or 12:01. Sometimes communicating clearly is
> more important than being right.

I like that (but getting everyone to adhere to that ...

Re: Quels packages pour logguer le NAT ?

[Olivier]

Le jeu. 12 sept. 2019 à 15:28, hamster  a écrit :

>
> Je vais sans doute répondre a ta demande, mais pourquoi du NAT ? Il est
> beaucoup plus simple d'attribuer directement une adresse publique fixe a
> chaque poste. Bien sur c'est difficile a faire en IPv4 par manque
> d'adresses, mais si tu le fais déjà en IPv6 ca va soulager le trafic v4
> et simplifier d'autant ta gestion des logs.
>
> C'est pas faux !

Re: 24-hour vs. 12-hour time, ambiguity, and abbreviations (was Re: Default date output format changed after an upgrade to buster)

[David Wright]

On Thu 12 Sep 2019 at 09:42:03 (-0400), The Wanderer wrote:
> On 2019-09-12 at 06:30, Dan Ritter wrote:
> > David Wright wrote:
> >> 
> >> What surprised me is the use of 12am and 12pm in the States. When I
> >> was at grammar school (in the days of 12hour times), you lost marks
> >> for writing either of these contradictions. It was either 12 noon,
> >> 12 midnight, or 12 o'clock (where there's no ambiguity).
> > 
> > 12 o'clock is the only one of those which is ambiguous.
> > 
> >> Even more astonishing is the fact that the US Government switched 
> >> their am/pm meanings sometime between 2000 and 2008, which shows 
> >> just how ambiguous they are.
> > 
> > There is only one sensible interpretation:
> > 
> > If 11:59 AM is two minutes before 12:01 PM, then 12:00 is PM.
> > 
> > If 11:59 PM is two minutes before 12:01 AM, then 12:00 is AM.
> 
> I take a slightly different approach, based on the apparent actual
> meanings of the words for which "AM" and "PM are abbreviations.
> 
> It seems intuitively obvious to me that between 11:59 Ante-Meridiem and
> 12:01 Post-Meridiem must lie 12:00 Meridiem. (Though 12:00:01 - one
> second later - would be Post-Meridiem again.)
> 
> Similarly, though less an "obvious necessity" consequence, between 11:59
> Post-Meridiem and 12:01 Ante-Meridiem lies 12:00 Midnight. (I understand
> "meridiem" to be derived from a word which would have literally meant
> "mid-day".)

Meridies (nominative case in Latin).

> Both are intuitively represented as "12:00 M" - with no "A" or "P" - and
> that, in its turn, is ambiguous.

It might be ambiguous if m were also an abbreviation for midnight,
which I've never come across. One can understand why, in the days of
12-hour clocks, midday was something distinctive, whereas the
precise time of midnight (as contrasted with "the middle of the night")
was largely irrelevant.

Many of the times we use were originally derived from counting the
hours after dawn: logical to the way people lived their lives.
So people took their siesta at the sixth hour and monks prayed in
nones at the ninth, mid-afternoon (ironically: noon, like the
start of the new year, has since drifted).

> That being part of why I stick with 24-hour time whenever possible.

When I read emails, I only see the Date: line from the header, and
the timedates used in the quotation lines. One thing I find odd is
mixing AM/PM with hours containing a leading zero. I was always
taught that 7 p.m. or 7pm was not written as 07, but I see that a
lot here. Contrast

$ TZ=Europe/Paris date +'%I.%M %p'
06.01 PM
$ TZ=Europe/Paris date +'%l.%M %p'
 6.01 PM
$ 

> > The problem stems from 12 actually indicating what anybody sensible
> > would consider 0.
> 
> As is likely part of the reason why the usual 24-hour clock goes from
> 23:59 to 00:00, yes.

Not forgetting 23:59:60 on occasions.

Cheers,
David.

Re: Quels packages pour logguer le NAT ?

[Olivier]

Le jeu. 12 sept. 2019 à 17:35, Frédéric MASSOT <
frede...@juliana-multimedia.com> a écrit :

>
>
> Si tu as un fichier de règles iptables, tu peux utiliser la cible "-j
> LOG" ainsi que les options "--log-level" et "--log-prefix".
>
> Avec une règle:
iptables -t nat -A POSTROUTING -o eth0 -j LOG  --log-prefix "NAT Log: "
--log-level 7

j'ai:
Sep 12 17:57:29 foobar kernel: [   33.486363] NAT Log: IN= OUT=ens3.832
SRC=192.168.32.134 DST=51.255.197.148 LEN=76 TOS=0x10 PREC=0x00 TTL=64
ID=45974 DF PROTO=UDP SPT=37568 DPT=123 LEN=56

Il y manque soit l'adresse source (192.168.1.10/5) soit l'adresse
translatée ( 5.6.7.8/4)
Certes comme mes IP publique sont fixes, je connais l'adresse translatée
mais le port utilisé m'est inconnu.
Or malheureusement, je n'ai que ce couple 5.6.7.8/4 et l'heures, pour
identifier la source (192.168.1.10/5). 

Re: Quels packages pour logguer le NAT ?

[Frédéric MASSOT]

Le 12/09/2019 à 15:18, Olivier a écrit :
> Bonjour,
> 
> J'ai une machine sous Stretch qui fait office de routeur sur un réseau
> local.
> Elle implémente une fonction NAT avec une centaine d'utilisateurs sur le
> réseau local et un trafic de l'ordre de 200Mb/s (j'ai du mal à évaluer
> le nombre de paquets par seconde) voire d'avantage.
> 
> Je souhaite logguer chaque translation d'adresse fin de pouvoir a
> posteriori, déterminer quel utilisateur interne s'est connecté à une
> machine sur Internet.
> 
> Sur un seul enregistrement (ou plusieurs), je souhaite pouvoir lire les
> 7 informations ci-après:
> - l'heure
> - l'IP source interne/port source interne
> - l'IP publique source/port source public
> - l'IP destination interne/port destination
> 
> En d'autres termes, si l'utilisateur 192.168.1.10 consulte le site web
> 1.2.3.4, je souhaite retrouver un enregistrement avec:
> - 192.168.1.10/5  (le navigateur utilise
> le port source 5 )
> - 5.6.7.8/4  (mon routeur translate
> 192.168.1.10/5  vers 5.6.7.8/4
> )
> - 1.2.3.4/80  (site web de destination)
> 
> Vu le grand nombre de connexions DNS crées par la moindre page DNS,
> j'aimerai ne pas logguer les connexions DNS.
> 
> Dans un premier temps, copier des logs dans un fichier local me suffit.
> À terme, je consignerai les logs dans une BDD.
> 
> J'ai lu [1] qui fait référence à conntrack et ulogd mais je suis un peu
> surpris de n'y voir aucune référence à iptables.


Si tu as un fichier de règles iptables, tu peux utiliser la cible "-j
LOG" ainsi que les options "--log-level" et "--log-prefix".





-- 
==
|  FRÉDÉRIC MASSOT   |
| http://www.juliana-multimedia.com  |
|   mailto:frede...@juliana-multimedia.com   |
| +33.(0)2.97.54.77.94  +33.(0)6.67.19.95.69 |
===Debian=GNU/Linux===

Hi Dear,

[Lisa Williams]

Hi Dear,

  How are you doing hope you are fine and OK?

I was just going through the Internet search when I found your email address, I 
want to make a new and special friend, so I decided to contact you to see how 
we can make it work out if we can. Please I wish you will have the desire with 
me so that we can get to know each other better and see what happens in future.

My name is Lisa Williams, I am an American, but presently I live in the UK, I 
will be glad to see your reply via my private ID (lisa.williams0...@yahoo.com) 
for us to know each other better to exchange pictures and details about us.

Yours
Lisa

Re: GIMP crashed with a fatal error: fatal error: Violación de segmento

[Paynalton]

Si un ave no rompe su huevo morirá antes de nacer.
Nosotros somos el ave y el mundo es nuestro huevo.
POR LA REVOLUCIÓN DEL MUNDO

Ciudad de México


El mié., 11 sept. 2019 a las 23:30, santo motorola ()
escribió:

> ```
> GNU Image Manipulation Program version 2.10.8
> git-describe: GIMP_2_10_6-294-ga967e8d2c2
> C compiler:
> Using built-in specs.
> COLLECT_GCC=gcc
> COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
> OFFLOAD_TARGET_NAMES=nvptx-none:hsa
> OFFLOAD_TARGET_DEFAULT=1
> Target: x86_64-linux-gnu
> Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-6'
> --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs
> --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2
> --prefix=/usr --with-gcc-major-version-only --program-suffix=-9
> --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
> --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
> --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu
> --enable-libstdcxx-debug --enable-libstdcxx-time=yes
> --with-default-libstdcxx-abi=new --enable-gnu-unique-object
> --disable-vtable-verify --enable-plugin --enable-default-pie
> --with-system-zlib --with-target-system-zlib=auto --enable-multiarch
> --disable-werror --with-arch-32=i686 --with-abi=m64
> --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
> --enable-offload-targets=nvptx-none,hsa --without-cuda-driver
> --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
> --target=x86_64-linux-gnu
> Thread model: posix
> gcc version 9.2.1 20190827 (Debian 9.2.1-6)
>
> using GEGL version 0.4.12 (compiled against version 0.4.14)
> using GLib version 2.60.6 (compiled against version 2.60.6)
> using GdkPixbuf version 2.38.1 (compiled against version 2.38.1)
> using GTK+ version 2.24.32 (compiled against version 2.24.32)
> using Pango version 1.42.3 (compiled against version 1.42.3)
> using Fontconfig version 2.13.1 (compiled against version 2.13.1)
> using Cairo version 1.16.0 (compiled against version 1.16.0)
>
> ```
> > fatal error: Violación de segmento
>


Primero: usa memtest para revisar que tu memoria ram esté bien.
Segundo: pasanos detalles sobre tu hardware,


>
> Stack trace:
> ```
> /lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x398)[0x7f89a879ff98]
> gimp-2.10(+0xd1590)[0x5625eabba590]
> gimp-2.10(+0xd19b8)[0x5625eabba9b8]
> gimp-2.10(+0xd2029)[0x5625eabbb029]
> /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f89a7c98730]
> gimp-2.10(gimp_gegl_mask_is_empty+0x91)[0x5625eafa5411]
> gimp-2.10(+0x3b7810)[0x5625eaea0810]
> gimp-2.10(+0x42ec18)[0x5625eaf17c18]
> gimp-2.10(+0x3d5b50)[0x5625eaebeb50]
> gimp-2.10(+0x42f2aa)[0x5625eaf182aa]
> gimp-2.10(gimp_drawable_set_buffer_full+0x1cb)[0x5625eaebd9bb]
> gimp-2.10(gimp_drawable_set_buffer+0x11d)[0x5625eaebdf9d]
> gimp-2.10(gimp_drawable_new+0x106)[0x5625eaebe296]
> gimp-2.10(gimp_layer_new+0x90)[0x5625eaf1b4d0]
> gimp-2.10(+0x3319cc)[0x5625eae1a9cc]
> gimp-2.10(gimp_procedure_execute+0x237)[0x5625eae53577]
> gimp-2.10(gimp_pdb_execute_procedure_by_name_args+0x1e9)[0x5625eae4ca39]
> gimp-2.10(gimp_plug_in_handle_message+0x216)[0x5625eae57626]
> gimp-2.10(+0x36cf91)[0x5625eae55f91]
>
> /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x158)[0x7f89a7e7d898]
> /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4ec88)[0x7f89a7e7dc88]
>
> /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0xb2)[0x7f89a7e7df82]
> gimp-2.10(gimp_plug_in_manager_call_run+0x5fc)[0x5625eae6735c]
> gimp-2.10(+0x376dbe)[0x5625eae5fdbe]
> gimp-2.10(gimp_procedure_execute+0x237)[0x5625eae53577]
> gimp-2.10(gimp_pdb_execute_procedure_by_name_args+0x1e9)[0x5625eae4ca39]
> gimp-2.10(gimp_pdb_execute_procedure_by_name+0x3cd)[0x5625eae4cefd]
> gimp-2.10(file_open_image+0x33d)[0x5625eaf4d6fd]
> gimp-2.10(file_open_with_proc_and_display+0x29d)[0x5625eaf4e64d]
> gimp-2.10(+0x113573)[0x5625eabfc573]
> gimp-2.10(+0x1138b7)[0x5625eabfc8b7]
>
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f89a7f63e8d]
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x27555)[0x7f89a7f77555]
>
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7f89a7f804ae]
>
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f89a7f80b6f]
>
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f89a7f63e8d]
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x27555)[0x7f89a7f77555]
>
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7f89a7f804ae]
>
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f89a7f80b6f]
> /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x8de25)[0x7f89a894ce25]
>
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f89a7f63e8d]
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x276a4)[0x7f89a7f776a4]
>
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7f89a7f804ae]
>
> 

Re: Default date output format changed after an upgrade to buster

[David Wright]

On Thu 12 Sep 2019 at 13:48:07 (-), Curt wrote:
> On 2019-09-12, Greg Wooledge  wrote:
> > On Wed, Sep 11, 2019 at 07:31:13PM -0500, David Wright wrote:
> >> Even more astonishing is the fact that the US Government switched
> >> their am/pm meanings sometime between 2000 and 2008, which shows
> >> just how ambiguous they are.
> >
> > [citation needed]
> 
> https://en.wikipedia.org/wiki/12-hour_clock#cite_note-26
> 
>  The style manual of the United States Government Printing Office used 12 a.m.
>  for noon and 12 p.m. for midnight until its 2008 edition, when it reversed
>  these designations,[14][15] later maintained in its 2016 revision.[23]

https://www.govinfo.gov/collection/gpo-style-manual?path=/GPO/U.S.%20Government%20Publishing%20Office%20Style%20Manual

During the 20th century, they used 12 m. for noon apparently (meridies).
I notice that the section heading confuses meridiem with meridian:

"9.54. References to meridian in statements of time are abbre-
viated as follows:"

Cheers,
David.

Re: Default date output format changed after an upgrade to buster

[Greg Wooledge]

On Thu, Sep 12, 2019 at 01:48:07PM -, Curt wrote:
> On 2019-09-12, Greg Wooledge  wrote:
> > On Wed, Sep 11, 2019 at 07:31:13PM -0500, David Wright wrote:
> >> Even more astonishing is the fact that the US Government switched
> >> their am/pm meanings sometime between 2000 and 2008, which shows
> >> just how ambiguous they are.
> >
> > [citation needed]
> 
> https://en.wikipedia.org/wiki/12-hour_clock#cite_note-26
> 
>  The style manual of the United States Government Printing Office used 12 a.m.
>  for noon and 12 p.m. for midnight until its 2008 edition, when it reversed
>  these designations,[14][15] later maintained in its 2016 revision.[23]

Interesting, thank you.  I guess I should not be surprised that my
government had it *wrong* for 148 years.

Re: Default date output format changed after an upgrade to buster

[Curt]

On 2019-09-12, Greg Wooledge  wrote:
> On Wed, Sep 11, 2019 at 07:31:13PM -0500, David Wright wrote:
>> Even more astonishing is the fact that the US Government switched
>> their am/pm meanings sometime between 2000 and 2008, which shows
>> just how ambiguous they are.
>
> [citation needed]
>
>

https://en.wikipedia.org/wiki/12-hour_clock#cite_note-26

 The style manual of the United States Government Printing Office used 12 a.m.
 for noon and 12 p.m. for midnight until its 2008 edition, when it reversed
 these designations,[14][15] later maintained in its 2016 revision.[23]


-- 
Thug: This is a stickup! Now come on. Your money or your life.
[long pause]
Thug: [repeating] Look, bud, I said, 'Your money or your life.'
Jack Benny: I'm thinking, I'm thinking!

Re: 24-hour vs. 12-hour time, ambiguity, and abbreviations (was Re: Default date output format changed after an upgrade to buster)

[Michael Stone]

On Thu, Sep 12, 2019 at 09:42:03AM -0400, The Wanderer wrote:

I take a slightly different approach, based on the apparent actual
meanings of the words for which "AM" and "PM are abbreviations.

It seems intuitively obvious to me that between 11:59 Ante-Meridiem and
12:01 Post-Meridiem must lie 12:00 Meridiem. (Though 12:00:01 - one
second later - would be Post-Meridiem again.)

Similarly, though less an "obvious necessity" consequence, between 11:59
Post-Meridiem and 12:01 Ante-Meridiem lies 12:00 Midnight. (I understand
"meridiem" to be derived from a word which would have literally meant
"mid-day".)


Historically one would simply say "12 noon" or "12 midnight". The entire 
am/pm controversy is caused by trying to cram the time into limited 
displays.

24-hour vs. 12-hour time, ambiguity, and abbreviations (was Re: Default date output format changed after an upgrade to buster)

[The Wanderer]

On 2019-09-12 at 06:30, Dan Ritter wrote:

> David Wright wrote:
>> 
>> What surprised me is the use of 12am and 12pm in the States. When I
>> was at grammar school (in the days of 12hour times), you lost marks
>> for writing either of these contradictions. It was either 12 noon,
>> 12 midnight, or 12 o'clock (where there's no ambiguity).
> 
> 12 o'clock is the only one of those which is ambiguous.
> 
>> Even more astonishing is the fact that the US Government switched 
>> their am/pm meanings sometime between 2000 and 2008, which shows 
>> just how ambiguous they are.
> 
> There is only one sensible interpretation:
> 
> If 11:59 AM is two minutes before 12:01 PM, then 12:00 is PM.
> 
> If 11:59 PM is two minutes before 12:01 AM, then 12:00 is AM.

I take a slightly different approach, based on the apparent actual
meanings of the words for which "AM" and "PM are abbreviations.

It seems intuitively obvious to me that between 11:59 Ante-Meridiem and
12:01 Post-Meridiem must lie 12:00 Meridiem. (Though 12:00:01 - one
second later - would be Post-Meridiem again.)

Similarly, though less an "obvious necessity" consequence, between 11:59
Post-Meridiem and 12:01 Ante-Meridiem lies 12:00 Midnight. (I understand
"meridiem" to be derived from a word which would have literally meant
"mid-day".)

Both are intuitively represented as "12:00 M" - with no "A" or "P" - and
that, in its turn, is ambiguous.

That being part of why I stick with 24-hour time whenever possible.

> The problem stems from 12 actually indicating what anybody sensible
> would consider 0.

As is likely part of the reason why the usual 24-hour clock goes from
23:59 to 00:00, yes.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: Default date output format changed after an upgrade to buster

[David Wright]

On Thu 12 Sep 2019 at 06:30:21 (-0400), Dan Ritter wrote:
> David Wright wrote: 
> > 
> > What surprised me is the use of 12am and 12pm in the States. When
> > I was at grammar school (in the days of 12hour times), you lost
> > marks for writing either of these contradictions. It was either
> > 12 noon, 12 midnight, or 12 o'clock (where there's no ambiguity).
> 
> 12 o'clock is the only one of those which is ambiguous.

Perhaps, for some, I have to rewrite the last sentence so they can
understand it.

  It was either 12 noon or 12 midnight. However, it would have been
  permissible to write 12 o'clock where there was no ambiguity, as in
  "Lunch is at 12 o'clock".

> > Even more astonishing is the fact that the US Government switched
> > their am/pm meanings sometime between 2000 and 2008, which shows
> > just how ambiguous they are.
> 
> There is only one sensible interpretation:
> 
> If 11:59 AM is two minutes before 12:01 PM, then 12:00 is PM.
> 
> If 11:59 PM is two minutes before 12:01 AM, then 12:00 is AM.
> 
> The problem stems from 12 actually indicating what anybody
> sensible would consider 0.

I'm not sure why you think that 0 has any relevance to the 12-hour
clock: glancing up, I see no "0" inscribed anywhere (except as the
second digit of "10").

Your argument above is arbitrary, placing 12:00 at the *start* of
the period of time 12:00, 12:01, 12:02 …

The counterargument can be held by anybody actually looking at the
face of a clock, where 12 is at the *end* of the sequence … 10, 11, 12.

You might see some logic in either, but I can see no logic in
maintaining what is a contradiction in terms. So it's just a
convention, and one that the US Government changed its view on
some years ago.

Cheers,
David.

Re: Quels packages pour logguer le NAT ?

[hamster]

Le 12/09/2019 à 15:18, Olivier a écrit :
> Bonjour,
>
> J'ai une machine sous Stretch qui fait office de routeur sur un réseau
> local.
> Elle implémente une fonction NAT avec une centaine d'utilisateurs sur
> le réseau local et un trafic de l'ordre de 200Mb/s (j'ai du mal à
> évaluer le nombre de paquets par seconde) voire d'avantage.
>
> Je souhaite logguer chaque translation d'adresse fin de pouvoir a
> posteriori, déterminer quel utilisateur interne s'est connecté à une
> machine sur Internet.

Je vais sans doute répondre a ta demande, mais pourquoi du NAT ? Il est
beaucoup plus simple d'attribuer directement une adresse publique fixe a
chaque poste. Bien sur c'est difficile a faire en IPv4 par manque
d'adresses, mais si tu le fais déjà en IPv6 ca va soulager le trafic v4
et simplifier d'autant ta gestion des logs.

Re: conseils généraux -pour un vieux geek- pour tablette Android & Debian

[Romain Gobert]

L'app UserLAnd devrait vous plaire : 
https://play.google.com/store/apps/details?id=tech.ula


On 11/09/2019 20:35, Basile Starynkevitch wrote:
Utiliser le plus possible ma tablette comme j'utilise mon PC Linux. La 
ligne de commande est mon interface préférée.

Quels packages pour logguer le NAT ?

[Olivier]

Bonjour,

J'ai une machine sous Stretch qui fait office de routeur sur un réseau
local.
Elle implémente une fonction NAT avec une centaine d'utilisateurs sur le
réseau local et un trafic de l'ordre de 200Mb/s (j'ai du mal à évaluer le
nombre de paquets par seconde) voire d'avantage.

Je souhaite logguer chaque translation d'adresse fin de pouvoir a
posteriori, déterminer quel utilisateur interne s'est connecté à une
machine sur Internet.

Sur un seul enregistrement (ou plusieurs), je souhaite pouvoir lire les 7
informations ci-après:
- l'heure
- l'IP source interne/port source interne
- l'IP publique source/port source public
- l'IP destination interne/port destination

En d'autres termes, si l'utilisateur 192.168.1.10 consulte le site web
1.2.3.4, je souhaite retrouver un enregistrement avec:
- 192.168.1.10/5 (le navigateur utilise le port source 5 )
- 5.6.7.8/4 (mon routeur translate 192.168.1.10/5 vers 5.6.7.8/4
)
- 1.2.3.4/80 (site web de destination)

Vu le grand nombre de connexions DNS crées par la moindre page DNS,
j'aimerai ne pas logguer les connexions DNS.

Dans un premier temps, copier des logs dans un fichier local me suffit.
À terme, je consignerai les logs dans une BDD.

J'ai lu [1] qui fait référence à conntrack et ulogd mais je suis un peu
surpris de n'y voir aucune référence à iptables.

Quels logiciels sont strictement nécessaires et suffisants pour implémenter
ceci ?

[1]
https://home.regit.org/2014/02/logging-connection-tracking-event-with-ulogd/

Slts

Re: Display resolution 3840x2160@24rb stopped working after Upgrade from Stretch to Buster

[David Wright]

On Thu 12 Sep 2019 at 06:23:04 (+), Jan Michael Greiner wrote:
> On Monday, September 9, 2019, 1:55:06 PM GMT+2, Charles Curley wrote:
> >> On Mon, 9 Sep 2019 10:20:37+ (UTC) Jan Michael Greiner wrote:
> >> With Debian Stretch (9.8) I had the display running with 3840x2160
> >> resolution at 24Hz reduced blank.
> 
> >> [What worked with Debian Stretch (9.9)]
> >> export modename="3840x2160_24.00_rb"
>  >> xrandr --newmode $modename 209.75 3840 3888 3920 4000 2160 2163 2168 2185 
> +HSync -Vsync
>  >> xrandr --addmode HDMI-1 $modename
>  >> xrandr --output HDMI-1 --mode $modename
> 
>  >> [Problem with Debian Buster (10.1)]
>  >> xrandr --output XWAYLAND1 --mode $modename
>  >> xrandr: Configure crtc0 failed
> 
>  >And I take it you want to reproduce that on Debian 10 (buster). I
>  > suggest you:
>  > * Install arandr.
>  >[...]
> 
>  Thank you for making me aware of arandr. However, from what I learned:
> 
> - arandr is merely a graphical tool for xrandr, so if something does not work 
> with xrandr, arandr will not be able to help 
> 
> - I did not see any option in the arandr gui to add a non yet existing 
> resolution (and I would like to add a 24Hz reduced blank resolution)
> 
>  To rephrase my question: How can I enable a custom screen resolution and 
> refresh rate (with my specific modeline) with Debian Buster (Wayland)?

I can't speak for Wayland. When I plug my laptop into a TV¹, I run a
function that sets up the video and sound, which starts:

my-hdmi is a function
my-hdmi () 
{ 
[ -z "$DISPLAY" ] && printf '%s\n' "No display as not running X$DISPLAY" && 
return 1;
local Hdmi="$(-gethdminame)";
xrandr --addmode "$Hdmi" 1600x900;
xrandr --output "$Hdmi" --mode 1600x900;
…

where

-gethdminame is a function
-gethdminame () 
{ 
[ -n "$DISPLAY" ] && printf '%s\n' "$(xrandr | sed -e '/^HDMI/!d;s/ .*//;')"
}

(Sometimes it seems to be HDMI-1, sometimes HDMI1.)

For some reason, our US-bought Samsung TV is coy about revealing its
video modes when compared with the same model in its UK incarnation.

Cheers,
David.

Re: Default date output format changed after an upgrade to buster

[Greg Wooledge]

On Wed, Sep 11, 2019 at 07:31:13PM -0500, David Wright wrote:
> Even more astonishing is the fact that the US Government switched
> their am/pm meanings sometime between 2000 and 2008, which shows
> just how ambiguous they are.

[citation needed]

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Thursday 12 September 2019 08:16:57 David wrote:

> On Thu, 12 Sep 2019 at 16:14, deloptes  wrote:
> > My RPI4 arrived as well - need to pick up also power supply and
> > cables, which arrived too. Excited to see how it performs.
>
> I have one of the official cases as well but after setting eyes on it
> I never even bothered to try it,  due to the thermal issues.
> I use one of these instead, very happy with it:
> https://www.ebay.com.au/itm/GeeekPi-Raspberry-Pi-Acrylic-Case-with-Coo
>ling-Fan-Heatsinks-for-Raspberry-Pi-4/183870693770
>
> I didn't bother with the heatsinks that came with it. I just wanted a
> fan and some ventilation instead of a sealed little plastic oven.

I have a combo top/heat sink coming all fins on top. Since it will be 
mounted upside down and there is a fan under it, it should be ok. 
Turning it over puts the gpio pins in a straight line to the iface card, 
cable is only an inch long.

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: conseils généraux -pour un vieux geek- pour tablette Android & Debian

[didier . gaumet]

Le mercredi 11 septembre 2019 20:40:02 UTC+2, Basile Starynkevitch a écrit :
[...] 
> Je rêve de pouvoir faire sur ma tablette ce que je sais faire
>   avec aisance sur un ordinateur portable Linuxien:
> 
>   Compiler un GCC récent pour ma tablette (peut-être en
> "canadian cross build", compilé sur mon desktop Debian). 
> 
>   
>   Utiliser GCC sur ma tablette en ligne de commande.
>   Utiliser le plus possible ma tablette comme j'utilise mon PC
> Linux. La ligne de commande est mon interface préférée.
> 
>   
>   Développer -sur ma tablette, dans le RER ou le TGV, sans Wifi-
> pour m'amuser une petite application Android en GPLv3+ qui mixe
> du code natif C++ ou même Guile ou Ocaml (que je sais déjà
> écrire) avec du code Java (que je saurais écrire; j'ai déjà
> écrit un ou deux milles lignes de Java mais il y a environ dix
> ans; j'ai potassé  au siècle dernier la spécification de la JVM
> et de son bytecode et j'avais rédigé un rapport technique
> interne à son sujet). 
[...]

Comme je ne maîtrise pas le sujet (donc pas la peine de me demander plus de 
détails, je ne connais pas), j'énonce juste quelques points dont tu as 
peut-être déjà connaissance ou qui seront sans intérêt pour toi, mais dans le 
doute:

- tu peux activer le "mode développeur" sous Android, qui après paramétrage te 
donne la possibilité d'utiliser un terminal. Plus de détails sur l'activation 
là:
https://www.frandroid.com/comment-faire/tutoriaux/184906_comment-acceder-au-mode-developpeur-sur-android

- en passant, d'après ce que j'ai compris, Android a suivi le même chemin que 
les *BSD pour passer de gcc à clang comme compilo principal il ya quelques 
années

- directement sous Android, il existe une appli C4droid qui peut être 
complémentée par un plugin gcc. Donc je suppose que yu dois te trouver à 
certains moments dans une interface styme terminal et que tu dois être à même , 
une fois le plugin installé, d'appeler les commandes gcc depuis le vrai 
terminal android. 
https://play.google.com/store/apps/details?id=com.n0n3m4.droidc

- il y a un article du wiki Debian concernant l'installation de Debian sur 
Android:
https://wiki.debian.org/ChrootOnAndroid

Re: Default date output format changed after an upgrade to buster

[Nate Bargmann]

* On 2019 12 Sep 06:16 -0500, rhkra...@gmail.com wrote:
> Now I consider establishments like Walgreens, Rite-Aid, Walmart, and others 
> to 
> be foreign infiltrators, as, when they have an In and an Out door side by 
> side, 
> the In is on the left.  (Ok, Walmart is only a halfway foreign infiltrator, 
> as 
> they typically have at least two entrances with In and Out doors, one of them 
> has the In door on the left, the other has the In door on the right.)

Not all Walmarts are like that.  ;-)

The one in Beatrice, NE is as you describe, at least the north most
entrance.  The ones in Marysviile, KS and Fairbury, NE are "normal",
i.e. ingress on the right when outside the store and egress on the right
when inside the store.

Apologies for more clock drift.  ;-D

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[David]

On Thu, 12 Sep 2019 at 16:14, deloptes  wrote:

> My RPI4 arrived as well - need to pick up also power supply and cables,
> which arrived too. Excited to see how it performs.

I have one of the official cases as well but after setting eyes on it
I never even bothered to try it,  due to the thermal issues.
I use one of these instead, very happy with it:
https://www.ebay.com.au/itm/GeeekPi-Raspberry-Pi-Acrylic-Case-with-Cooling-Fan-Heatsinks-for-Raspberry-Pi-4/183870693770

I didn't bother with the heatsinks that came with it. I just wanted a
fan and some ventilation instead of a sealed little plastic oven.

Re: Linux Journal epub files

[Nate Bargmann]

* On 2019 11 Sep 11:28 -0500, Jonathan Dowland wrote:
> On Mon, Sep 09, 2019 at 07:15:16AM -0500, Nate Bargmann wrote:
> > I did manage to grab all of the available PDF files and then grabbed
> > everything in HTML for good measure in my personal archive.  I could
> > pass along the needed PDF files if that would help you.  Note that I
> > have no expressed permission from Linux Journal to do so.
> 
> That's a kind offer, Nate. In the event that archive.org do *not* have
> these all already (and I'm trying to verify), then it would be best IMHO
> to arrange to get the PDFs to them. I can facilitate that, if you want.
> Please contact me off-list if you are happy to proceed.

Are the files unavailable from the link Steve gave in this thread?  It
looks like even that is changing and redirects to
https://linuxjournal.rocks/issue-archive  The base URL now is a CRM and
actually has a new post dated Tuesday.

I'm not sure who is running it and it seems to be tied to GitHub (has a
Fork Me link).

Anyway, I'd be glad to share what I grabbed.  Just let me know.

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature

Re: Default date output format changed after an upgrade to buster

[Michael Stone]

On Thu, Sep 12, 2019 at 06:30:21AM -0400, Dan Ritter wrote:

David Wright wrote:


What surprised me is the use of 12am and 12pm in the States. When
I was at grammar school (in the days of 12hour times), you lost
marks for writing either of these contradictions. It was either
12 noon, 12 midnight, or 12 o'clock (where there's no ambiguity).


12 o'clock is the only one of those which is ambiguous.


Even more astonishing is the fact that the US Government switched
their am/pm meanings sometime between 2000 and 2008, which shows
just how ambiguous they are.


There is only one sensible interpretation:

If 11:59 AM is two minutes before 12:01 PM, then 12:00 is PM.

If 11:59 PM is two minutes before 12:01 AM, then 12:00 is AM.

The problem stems from 12 actually indicating what anybody
sensible would consider 0.


The railroads solved this more than a century ago: you just never use 
12:00 and stick with 11:59 or 12:01. Sometimes communicating clearly is 
more important than being right.

Re: Default date output format changed after an upgrade to buster

[Curt]

On 2019-09-12, rhkra...@gmail.com  wrote:
>
> But, ok, I'll try to burn that into my memory -- at night (when it is dark) 
> 12:00 (midnight) is the beginning of morning (12:00 am).  During the day, 
> when 
> it is light 12:00 (noon) is the beginning of night (12:00 pm).
>
>> If 11:59 PM is two minutes before 12:01 AM, then 12:00 is AM.
>> 
>> The problem stems from 12 actually indicating what anybody sensible
>> would consider 0.
>> 

There is a special-case moment straddling the previous as well as the
next day simultaneously. In 24-hour clockland, if you wish that instant
in time to belong to the day that is ending, you write 24:00 (to denote
midnight at the end of the calender day); on the other hand, if you
desire the instant to belong to the following day, you write 00:00 (a
much more common notation, but I suppose the former has its uses also).


-- 
Thug: This is a stickup! Now come on. Your money or your life.
[long pause]
Thug: [repeating] Look, bud, I said, 'Your money or your life.'
Jack Benny: I'm thinking, I'm thinking!

Re: Trapped in Gnome

[songbird]

Thomas George wrote:
> At login after booting up there is a symbol like a gear below the 
> password entry line. I moved the mouse and clicked on this symbol. 
> Several options appeared and I decided to try Classic Gnome. This worked 
> but the next time I booted up the mouse was frozen. The symbol to change 
> desktops is there but there is no way to reach it, the mouse is stuck in 
> the lower right side of the screen
>
> How can I escape? I don't like the version of Gnome I an stuck in

  do the tab or arrow keys do anything?  ESC, 
Control Alt Delete, Control Alt F11, Control Alt F1 - F8?  
do any of these do anything?

  i'm not familiar with Gnome keyboard commands any more
but some of these should get you somewhere.  :)  the
Control Alt F1 should get you to a command line login.


  songbird

Re: Default date output format changed after an upgrade to buster

[rhkramer]

On Thursday, September 12, 2019 06:30:21 AM Dan Ritter wrote:
> David Wright wrote:
> > Even more astonishing is the fact that the US Government switched
> > their am/pm meanings sometime between 2000 and 2008, which shows
> > just how ambiguous they are.

Wow!  I believe that, I just didn't realize that (and I might have a rambling 
old man story / rant that I'll tell (below) about change (sometimes by 
government, sometimes by others).  (I was going to try to avoid telling it, 
but I'm a rambling old man.  By putting it at the end, it will be easy to 
ignore ;-)

Regretfully, I always get confused.

> There is only one sensible interpretation:
> 
> If 11:59 AM is two minutes before 12:01 PM, then 12:00 is PM.

@Dan Ritter -- I don't understand your logic -- oh, now I see, you consider 12 
to be zero -- I have trouble seeing why sensible people wouldn't consider the 
next number after 11:59 to be 12?

And why not: (no need to reply!)

If 12:01 pm is two minutes after 11:59 am, then 12:00 is AM.

But, ok, I'll try to burn that into my memory -- at night (when it is dark) 
12:00 (midnight) is the beginning of morning (12:00 am).  During the day, when 
it is light 12:00 (noon) is the beginning of night (12:00 pm).

> If 11:59 PM is two minutes before 12:01 AM, then 12:00 is AM.
> 
> The problem stems from 12 actually indicating what anybody
> sensible would consider 0.
> 
> -dsr-



People in the US drive on the right hand side of the road (except for special 
cases like one way roads or such.)

Some number of years ago, somebody (presumably a police commissioner or other 
high muckety much decided that, at the entrance and exit to the underground 
parking garage under our town's city hall complex, they would reverse that.

Just crazy (imho).

That could have been 20 years ago (or not, but it's been a long time).

Fairly recently, somebody (who I credit with good sense) reversed it again -- 
of course, that caught be by surprise, but fortunately, no one was coming the 
other way.

I'm not explicitly aware of accidents that occurred during the ~20 years while 
the entrance and exit were the other way, but I can imagine some confusion and 
close calls by drivers not used to that strangeness.

(To try to clarify, there are two entrances / exits to the underground garage, 
you can enter or exit at either one.)


Children in the US are (were??) taught to walk on the right (and adults to the 
extent adults might be taught to walk).

Now I consider establishments like Walgreens, Rite-Aid, Walmart, and others to 
be foreign infiltrators, as, when they have an In and an Out door side by side, 
the In is on the left.  (Ok, Walmart is only a halfway foreign infiltrator, as 
they typically have at least two entrances with In and Out doors, one of them 
has the In door on the left, the other has the In door on the right.)

Regardless, when I got to Walmart, I enter the right hand door, whether it is 
marked in or out.  If anybody complains, I tell them I am an American ;-)

I avoid going to places like Walgreens, Rite-Aid, and similar unless I really 
have to.

Re: Display resolution 3840x2160@24rb stopped working after Upgrade from Stretch to Buster

[Dan Ritter]

Jan Michael Greiner wrote: 
> Dear all,
> 
> My laptop: Lenovo E520
> Graphics: Intel HD Graphics 3000 (kernel module i915)
> 
> External display AOC U2879VF, 28 inch, connected by HDMI cable
> 
> With Debian Stretch (9.8) I had the display running with 3840x2160 resolution 
> at 24Hz reduced blank.
> 
> 
> I did this with something like:
> 
> export modename="3840x2160_24.00_rb"
> xrandr --newmode $modename  209.75  3840 3888 3920 4000  2160 2163 2168 2185  
> +HSync -Vsync
> xrandr --addmode HDMI-1 $modename
> xrandr --output HDMI-1 --mode $modename
> xrandr --output HDMI-1 --primary
> xrandr --output LVDS-1 --off # switch laptop display off
> 
> After upgrade to Buster (Debian 10)
> 
> This does not work any more:
> xxx@yyy:~$ xrandr --verbose
>  Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
> XWAYLAND1 connected 1920x1080+0+0 (0x25) normal (normal left inverted right x 
> axis y axis) 620mm x 340mm
>     Identifier: 0x23
>     Timestamp:  42126
>     Subpixel:   unknown
>     Gamma:  1.0:1.0:1.0
>     Brightness: 0.0
>     Clones:
>     CRTC:   0
>     CRTCs:  0
>     Transform:  1.00 0.00 0.00
>     0.00 1.00 0.00
>     0.00 0.00 1.00
>        filter:
>     non-desktop: 0
>     supported: 0, 1
>   1920x1080 (0x25) 173.000MHz -HSync +VSync *current +preferred
>     h: width  1920 start 2048 end 2248 total 2576 skew    0 clock  
> 67.16KHz
>     v: height 1080 start 1083 end 1088 total 1120   clock  59.96Hz
>  xxx@yyy:~$ export modename="3840x2160_24.00_rb"
> xxx@yyy:~$ xrandr --newmode $modename  209.75  3840 3888 3920 4000  2160 2163 
> 2168 2185  +HSync -Vsync
> xxx@yyy:~$ xrandr --addmode XWAYLAND1 $modename
> xxx@yyy:~$ xrandr --output XWAYLAND1 --mode $modename
> xrandr: Configure crtc 0 failed
> xxx@yyy:~$ xrandr --output XWAYLAND1 --mode $modename --verbose
> screen 0: 3840x2160 1237x696 mm  78.83dpi
> crtc 0: 3840x2160_24.00_rb  24.00 +0+0 "XWAYLAND1"
> xrandr: Configure crtc 0 failed
> crtc 0: disable
> screen 0: revert
> crtc 0: revert 
> 
> 
> After searching the internet, and trying to understand the relationship 
> between Wayland - graphics driver - graphics configuration - X etc. (which I 
> was not successful at), I hope to get help here on this mailing list.

Your problem is likely to be Wayland, which is trying to replace
X. Switching back will probably solve your issue.

-dsr-

Re: Default date output format changed after an upgrade to buster

[Dan Ritter]

David Wright wrote: 
> 
> What surprised me is the use of 12am and 12pm in the States. When
> I was at grammar school (in the days of 12hour times), you lost
> marks for writing either of these contradictions. It was either
> 12 noon, 12 midnight, or 12 o'clock (where there's no ambiguity).

12 o'clock is the only one of those which is ambiguous.
 
> Even more astonishing is the fact that the US Government switched
> their am/pm meanings sometime between 2000 and 2008, which shows
> just how ambiguous they are.

There is only one sensible interpretation:

If 11:59 AM is two minutes before 12:01 PM, then 12:00 is PM.

If 11:59 PM is two minutes before 12:01 AM, then 12:00 is AM.

The problem stems from 12 actually indicating what anybody
sensible would consider 0.

-dsr-

Re: Gnu sieve vs Dovecot sieve-filter - sieve-filter extremely slow at lda (writing emails to local mbox files)

[elvis]

On 12/9/19 8:06 am, Zenaan Harkness wrote:

On Thu, Sep 12, 2019 at 07:55:23AM +1000, Zenaan Harkness wrote:

Why is Gnu sieve so extremely fast to batch process an mbox file, but
while Dovecot's sieve-filter is an order of magnitude slower?

Sequence:

- mpop or getmail to pipeline download emails into temp mbox file
- filter that file



Have you tried piping the mail directly into the Dovecot lda so that it 
calls sieve.


There is so many moving parts to postfix and dovecot that it does my 
head in trying to figure out what I did everytime I look at it.


And for my virtual domains I have dovecot lmtp listening on tcp and that 
calls sieve.






Gnu sieve just flies through a local mbox file and saving emails to
other local mbox files.

Gnu sieve rejects too many emails with "malformed" errors, so after a
few years I bit the bullet and upgraded to Dovecot's sieve-filter.

Dovecot's sieve-filter, at present, is an order of magnitude slower.

Here's my filter command (one line):
tried
/usr/bin/sieve-filter -veW -c 
$HOME/etc/email/sieve-dovecot-config.conf -o 
mail_location=mbox:~/mail:INBOX=~/mail/Inbox:INDEX=:UTF-8:VOLATILEDIR=/tmp/dovecot-volatile/%2.256Nu/%u:SUBSCRIPTIONS=dovecot_subscriptions 
~/etc/email/sieve.rc email-incoming-unsorted


The sieve script is fine now that I have the correct "require"
clauses (hint: "capability strings").

File ~/etc/email/sieve-dovecot-config.conf:

protocols = pop
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
mail_fsync = never

There's no re-sending of emails into my local Postfix SMTP server - I
checked the system logs and confirmed this (journalctl -f).

I suspect that Gnu sieve was directly writing each email to the
appropriate sieve-determined mbox file (perhaps with only a sync at
the end of a single batch process - what I've attempted to achieve
above with sieve-filter), and that sieve-filter is instead passing
each email through some (dovecot) lda?

Here's the output for a sieve-filter batch processing of 11 emails:

$ /usr/bin/sieve-filter -veW -c 
/home/zen/etc/email/sieve-dovecot-config.conf -o 
mail_location=mbox:/home/zen/mail:INBOX=/home/zen/mail/Inbox:INDEX=:UTF-8:VOLATILEDIR=/tmp/dovecot-volatile/%2.256Nu/%u:SUBSCRIPTIONS=dovecot_subscriptions 
/home/zen/etc/email/sieve.rc email-incoming-unsorted

# PS0 Timestamp: 20190912@07:02:23
info: filtering: [Tue, 3 Sep 2019 05:17:16 -0500; 10240 bytes] `Re: 
VentureBeat: The death of disk? H...'.
info: 
msgid=: 
stored mail into mailbox 'l/cp/cp'.

info: message expunged from source mailbox upon successful move.
info: filtering: [Tue, 3 Sep 2019 07:29:53 -0400; 12968 bytes] 
`[zfs-devel] xattr naming format in Zo...'.
info: 
msgid=<15675101930.d5ba2e.12...@composer.zfsonlinux.topicbox.com>: 
stored mail into mailbox 'l/z/zdev'.

info: message expunged from source mailbox upon successful move.
info: filtering: [Tue, 03 Sep 2019 15:29:09 +0300; 20461 bytes] `Re: 
[zfs-devel] xattr naming format i...'.
info: msgid=<23955051567513...@sas1-02732547ccc0.qloud-c.yandex.net>: 
stored mail into mailbox 'l/z/zdev'.

info: message expunged from source mailbox upon successful move.
info: filtering: [Tue, 3 Sep 2019 18:20:42 +0530; 18065 bytes] `Re: 
[Gluster-users] Issues with Geo-r...'.
info: 
msgid=: 
stored mail into mailbox 'l/gl/user'.

info: message expunged from source mailbox upon successful move.
info: filtering: [Tue, 3 Sep 2019 09:34:20 -0400; 13342 bytes] `Re: 
tasksel'.
info: msgid=<20190903133420.gs6...@eeg.ccf.org>: stored mail into 
mailbox 'l/deb/user'.

info: message expunged from source mailbox upon successful move.
info: filtering: [Tue, 3 Sep 2019 06:56:07 -0700 (PDT); 12390 bytes] 
`[awx-project] Re: AWX on Kubernetes m...'.
info: msgid=<0715adb7-540f-4cff-9282-e1252c53c...@googlegroups.com>: 
stored mail into mailbox 'l/ansible/awx'.

info: message expunged from source mailbox upon successful move.
info: filtering: [Tue, 3 Sep 2019 07:01:27 -0700 (PDT); 12220 bytes] 
`[awx-project] Re: AWX on Kubernetes m...'.
info: msgid=<949b2c17-4254-49f1-83b4-cd54d15aa...@googlegroups.com>: 
stored mail into mailbox 'l/ansible/awx'.

info: message expunged from source mailbox upon successful move.
info: filtering: [Tue, 3 Sep 2019 10:14:58 -0400; 25313 bytes] `Re: 
[zfs-devel] xattr naming format i...'.
info: 
msgid=: 
stored mail into mailbox 'l/z/zdev'.

info: message expunged from source mailbox upon successful move.
info: filtering: [Tue, 3 Sep 2019 17:10:22 +0200; 7567 bytes] `Re: 
[asterisk-users] Playing MP3's in...'.
info: msgid=<20190903151022.354xpe6ds2vglher@red.localdomain>: stored 
mail into mailbox 'l/as/users'.

info: message expunged from source mailbox upon successful move.
info: filtering: [Wed, 4 Sep 2019 01:04:49 +0900; 14858 bytes] `Re: 
[Hyperledger Fabric] a primitive ...'.
info: msgid=<160901d8-b903-9e9a-91ac-267571b0e...@gmx.com>: stored 
mail into mailbox 'l/hl/fabric'.

info: message expunge

Re: Display resolution 3840x2160@24rb stopped working after Upgrade from Stretch to Buster

[Torben Schou Jensen]

Hi
I have a kind of same problem.

A monitor able of displaying at 1920x1080.
Intel HD Graphics 620 with driver i915/modesetting.

With old Stable (kernel 4.9.0-9) it was working fine.
With new Stable (kernel 4.19.0-6) it set max display 1024x768.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892939

White waiting for a solution you can boot new kernel with "nomodeset"
kernel parameter, then X will use vesa driver, and it is better than
nothing, but not good for heavy graphics.

Alternative keep kernel 4.9.0-9.

Brgds
Torben

AW: Re: PRoblems uninstalling nvidia

[01793666059]

The installer "NVidia-something-bla*.run" can be started with the 
--uninstall tag.

Have fun

Hans



Am Thu, 12 Sep 2019 10:10:58 +0200, Dominique Dumont  schrieb:

On Thursday, 12 September 2019 04:44:50 CEST Carlos Kosloff wrote:
> Probem is I cannot uninstall old version because dpkg halts:
>
> Welcome to the NVIDIA Software Installer for Unix/Linux

uh, no. That's not dpkg, it Nvidia's own installer. You should ask this
question on nvidia user forum.

All the best


 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[Gene Heskett]

On Thursday 12 September 2019 02:14:06 deloptes wrote:

> Gene Heskett wrote:
> >> https://wiki.debian.org/RaspberryPiImages
> >> https://www.raspberrypi.org/documentation/installation/
> >
> > Potential timeline?
> >
> > Cheers, Gene Heskett
>
> My RPI4 arrived as well - need to pick up also power supply and
> cables, which arrived too. Excited to see how it performs.

My micro hdmi adapters and heat sink are still on a junk somewhere. 
Considering the troubles in Hong Kong, its probably going to be late.  I 
had a 5v, 5a in the spares box. I've seen activity in the led's like its 
booting, but video remains invisible. I don't think the $16 adapter I 
got from wallies is any good.  I took the monitor to my pi-3b and it 
worked ok there.  So I wait.

Trying to build a fully preemptable kernel for raspian buster 1.1 on the 
pi-3b, but the raspian forum isn't co-operating. video on buster 1.1 is 
around 20x faster, and with a realtime kernel, it would run my big lathe 
very well. I have the src for that kernel, but as the pi-3b is a 
u-booter, no step by step howto that I have found. Debhelper isn't any 
help, demanding a debian/control file, all of which is pure unobtainium 
from raspian.

debian buster for arm isn't pi4 ready, no device tree for it yet. It does 
use grub to boot though, and that greatly simplifies installing a new 
kernel.  And I've already on site, a new hm2_rpspi.ko module that should 
talk to a mesa 7i90HD card, using the same spi interface the pi-3b is 
using.

Its possible raspian might beat debian to working release forthe 4.

Sitting on the proverbial park bench waiting for linux to catch up with 
new hardware sure is boring though. I feel like I'm running out of time. 
I go for a stress test at 9 tomorrow, Friday, and will likely be equipt 
with a new aortic valve before Friday in done. :-(  And I'll likely 
drive myself both ways.

Keep me posted please.

Thanks deloptes.

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: PRoblems uninstalling nvidia

[Dominique Dumont]

On Thursday, 12 September 2019 04:44:50 CEST Carlos Kosloff wrote:
> Probem is I cannot uninstall old version because dpkg halts:
> 
> Welcome to the NVIDIA Software Installer for Unix/Linux

uh, no. That's not dpkg, it Nvidia's own installer. You should ask this 
question on nvidia user forum.

All the best

Re: Trapped in Gnome

[Jimmy Johnson]

On 9/11/19 8:41 AM, Thomas George wrote:
At login after booting up there is a symbol like a gear below the 
password entry line. I moved the mouse and clicked on this symbol. 
Several options appeared and I decided to try Classic Gnome. This worked 
but the next time I booted up the mouse was frozen. The symbol to change 
desktops is there but there is no way to reach it, the mouse is stuck in 
the lower right side of the screen


How can I escape? I don't like the version of Gnome I an stuck in


If you got a new kernel or kernel upgrade, then that is where I would 
put the blame. I've seen the problem before, reverting back to the old 
kernel got it going again.

--
Jimmy Johnson

MX-19-XFCE-4.14 - AMD E2-6110 - EXT4 at sda11
Registered Linux User #380263

AW: PRoblems uninstalling nvidia

[01793666059]

What is alsways helping me was

apt-get --purge remove `nvidia-*`

or alternatively

aptitude purge ~nnvidia-*

(not a typo, it is ~nnvidia-*)

Hope this helps. Good luck!

Best Hans


Am Wed, 11 Sep 2019 22:44:50 -0400, Carlos Kosloff papim...@gmail.com 
schrieb:


Hello list,

Running buster + backports.

Instaled nvidia from an alternate source an ran into problems because not 
packaged for Debian.

Probem is I cannot uninstall old version because dpkg halts:

Welcome to the NVIDIA Software Installer for Unix/Linux

Detected 8 CPUs online; setting concurrency level to 8.

If you plan to no longer use the NVIDIA driver, you should make sure that no X 
screens
are configured to use the NVIDIA X driver in your X configuration file. If you 
used
nvidia-xconfig to configure X, it may have created a backup of your original
configuration. Would you like to run `nvidia-xconfig --restore-original-backup` 
to
attempt restoration of the original X configuration file?
 [default: (N)o]: N

Progress: [ 0%] 
[..] 

this does not even return the prompt.

After this I can no longer update system apt refuses to run dist-upgrade.

SO, how can I uninstall old version of nvidia?

Re: Display resolution 3840x2160@24rb stopped working after Upgrade from Stretch to Buster

[Jan Michael Greiner]

Dear Charles,

On Monday, September 9, 2019, 1:55:06 PM GMT+2, Charles Curley wrote:

>> On Mon, 9 Sep 2019 10:20:37+ (UTC) Jan Michael Greiner wrote:
>> With Debian Stretch (9.8) I had the display running with 3840x2160
>> resolution at 24Hz reduced blank.


>> [What worked with Debian Stretch (9.9)]
>> export modename="3840x2160_24.00_rb"
 >> xrandr --newmode $modename 209.75 3840 3888 3920 4000 2160 2163 2168 2185 
 >> +HSync -Vsync
 >> xrandr --addmode HDMI-1 $modename
 >> xrandr --output HDMI-1 --mode $modename

 >> [Problem with Debian Buster (10.1)]
 >> xrandr --output XWAYLAND1 --mode $modename
 >> xrandr: Configure crtc0 failed

 >And I take it you want to reproduce that on Debian 10 (buster). I
 > suggest you:
 > * Install arandr.
 >[...]

 Thank you for making me aware of arandr. However, from what I learned:

- arandr is merely a graphical tool for xrandr, so if something does not work 
with xrandr, arandr will not be able to help 

- I did not see any option in the arandr gui to add a non yet existing 
resolution (and I would like to add a 24Hz reduced blank resolution)

 To rephrase my question: How can I enable a custom screen resolution and 
refresh rate (with my specific modeline) with Debian Buster (Wayland)?


 Thank you and best regards

 JM 

Re: attempted install of buster arm64 net-install on rp4 fails instantly

[deloptes]

Gene Heskett wrote:

>> https://wiki.debian.org/RaspberryPiImages
>> https://www.raspberrypi.org/documentation/installation/
> 
> Potential timeline?
> 
> Cheers, Gene Heskett

My RPI4 arrived as well - need to pick up also power supply and cables,
which arrived too. Excited to see how it performs.