date:20191216

On Mon, Dec 16, 2019 at 10:37:12PM -0500, Celejar wrote:
> Hi,
> 
> I have a Debian Sid system with generally working networking. Recently,
> I experienced some strange connectivity problems with a particular
> network connection  [...]

> PING 1.1.1.1 (1.1.1.1) 1492(1520) bytes of data.
> ping: local error: message too long, mtu=1500

I don't know the error message by heart, but here, it seems
the message size is too big for your local MTU...

> With  = 1472, I get, at least sometimes:
> 
> >From 192.168.43.245 icmp_seq=2 Frag needed and DF set (mtu = 1472)

This is definitely an ICMP message you receive from some upstream

> followed by (for various values of ):
> 
> ping: local error: message too long, mtu=1472
> 
> until I drop below 1444, at which point I once again get no reply,
> until  <= 1412, at which point I once again get normal ping replies.

Someone upstream is dropping the packets, perhaps sending an ICMP
back (possibly "fragmentation needed"), perhaps someone else is
dropping that ICMP (your firewall, perhaps?)

> For comparison purposes, on a normal, properly behaving network
> connection, I get normal ping replies for  <= 1472, and "message
> too long" for  > 1472.
> 
> Am I understanding this correctly, that there's some kind of PMTUD /
> ICMP blackhole problem here?

This would be my interpretation too.

> If so, what can I do about it? My
> understanding is that I can either set the MTU lower on the client, or
> do MSS clamping. Any suggestions? Is this something Mint / T-Mobile, or
> someone upstream, is just messing up?

Since you're not getting the ICMPs back, your only choice seems to be
to reduce your MTU, manually yes.

Cheers
-- t


signature.asc
Description: Digital signature

Re: Impossible to type "ù"

On Mon, Dec 16, 2019 at 07:33:15PM -0600, David Wright wrote:

[...]

> You don't say what the dedicated key for ù is [...]

The French keyboard has one key for ù (in the whereabouts of
your ' key, I'd guess).

> but I would expect that
> you might need something like lv3:ralt_switch in your XKBOPTIONS
> to get it from one keystroke. I think I'm assuming you have a R-Alt
> key, sometimes engraved AltGr.

No -- on the French keyboard the ù is accessible without modifiers.

> (Being English, I compose ù with `u.)

Spanish on a German keyboard here. I compose a lot too :-)

> All that said, your use of "anymore" might suggest a bug in sid.

That would make sense. Perhaps some key mapping got "lost" somewhere.

Cheers
-- t

signature.asc
Description: Digital signature

Re: Impossible to type "ù"

On Mon, Dec 16, 2019 at 06:27:57PM -0600, Mark Allums wrote:
> On 12/16/19 3:53 PM, Pétùr wrote:
> >Hi,
> >
> >I cannot type "ù" anymore on Debian Xfce Sid (French keyboard).
> >
> >All other accented character (éàûè) work but the cursor just
> >blinked when using the dedicated key for "ù".
> >
> >Any clue?
> 
> Bad key?

Hm. That would be my first guess too, but the "blink" of the cursor
at least hints towards "the key is doing something", which goes counter
that hypothesis.

You might try two things:

 - first, hitting your ù key twice (or hitting space, then ù).
   Who knows, perhaps ù mutated into a dead key

 - second, start "xev" (package xutils) and hit the key. This
   would describe what your X is seeing.

Cheers
-- tomás


signature.asc
Description: Digital signature

Re: iptables, routing problems

2019-12-16 Thread Richard Hector

On 17/12/19 5:06 pm, Richard Hector wrote:
> Hi all,
> 
> I've got a networking issue that's confusing me.

Got it, I think.

I had previously been applying rules before switching to iptables-legacy
- so I'd been adding nftables rules. Then I switched, without flushing
(or rebooting), so both rulesets were in effect.

I had thought that both were interfaces to the same internal stuff, so
hadn't realised that iptables -F wouldn't flush nftables rules (or even
thought about it, really).

Richard

signature.asc
Description: OpenPGP digital signature

iptables, routing problems

2019-12-16 Thread Richard Hector

Hi all,

I've got a networking issue that's confusing me.

When I try to ssh out, I can see the packets being accepted by the rule
in the OUTPUT chain, but I can't see them with TCPDUMP. Nothing is
hitting the rules in the nat POSTROUTING chain, either.

I can see from the ACCEPT rule (in the iptables output) that the packet
is going through the interface I expect (enp4s0.1441)

Any ideas? I suspect it's something silly I've just failed to spot ...

Note that yesterday, when I was on site, I wasn't trying this, but had
similar problems with traffic going out - dns packets were being
accepted, but not hitting the postrouting snat rule. Today, I can't get
to the machine I was testing from, which is how I found the current problem.

In both cases, ping works - I can ping the machine I'm trying to ssh to
(10.144.1.10), and yesterday I could ping the dns server (8.8.8.8 for
test purposes)

Background and other info:

The system is (supposed to be) a router, based on an old (atom-based) HP
thin client connected to a VLAN switch. It's running buster.

I've built routers before, but not using VLANs and not (I think) on buster.

I'm using iptables-legacy (because I'm relatively familiar with it).

Other oddities are:

- it's running OpenVPN (which is working; that's how I'm connecting to
it today)
- there's an odd route I've added to allow talking to bits of my home
LAN, despite the external interface of this router being on the same
address range (too many people choose 192.168.1.0/24)

Here's the routing table:
8<
richard@svrouter:~$ sudo ip route
default via 192.168.1.1 dev enp4s0.1 onlink
10.144.1.0/24 dev enp4s0.1441 proto kernel scope link src 10.144.1.1
10.144.2.0/24 dev enp4s0.1442 proto kernel scope link src 10.144.2.1
192.168.1.0/24 dev enp4s0.1 proto kernel scope link src 192.168.1.15
192.168.1.96/27 via 192.168.94.1 dev tun0
192.168.94.0/24 dev tun0 proto kernel scope link src 192.168.94.10
8<

/etc/network/interfaces:
8<
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# # The primary network interface
# auto enp4s0
# iface enp4s0 inet dhcp

auto enp4s0.1
iface enp4s0.1 inet static
  address 192.168.1.15/24
  gateway 192.168.1.1

auto enp4s0.1441
iface enp4s0.1441 inet static
  address 10.144.1.1/24

auto enp4s0.1442
iface enp4s0.1442 inet static
  address 10.144.2.1/24
8<
(interfaces.d is empty)

iptables -vnL:
8<
Chain INPUT (policy ACCEPT 26 packets, 8528 bytes)
 pkts bytes target prot opt in out source
destination
0 0 LOGtcp  --  *  *   0.0.0.0/0
0.0.0.0/0tcp spt:22 LOG flags 0 level 4
 1109 99188 ACCEPT all  --  *  *   0.0.0.0/0
0.0.0.0/0ctstate RELATED,ESTABLISHED
0 0 ACCEPT icmp --  *  *   0.0.0.0/0
0.0.0.0/0
0 0 ACCEPT tcp  --  *  *   0.0.0.0/0
0.0.0.0/0tcp dpt:22

Chain FORWARD (policy ACCEPT 25 packets, 1750 bytes)
 pkts bytes target prot opt in out source
destination
0 0 ACCEPT all  --  *  *   0.0.0.0/0
0.0.0.0/0ctstate RELATED,ESTABLISHED
0 0 ACCEPT icmp --  *  *   0.0.0.0/0
0.0.0.0/0
0 0 ACCEPT tcp  --  enp4s0.1 enp4s0.1441  0.0.0.0/0
  0.0.0.0/0tcp dpt:22
0 0 ACCEPT tcp  --  enp4s0.1441 enp4s0.1  0.0.0.0/0
  0.0.0.0/0tcp dpt:22
0 0 ACCEPT tcp  --  enp4s0.1441 enp4s0.1  0.0.0.0/0
  0.0.0.0/0tcp dpt:53
0 0 ACCEPT tcp  --  enp4s0.1441 enp4s0.1  0.0.0.0/0
  0.0.0.0/0tcp dpt:80
0 0 ACCEPT tcp  --  enp4s0.1441 enp4s0.1  0.0.0.0/0
  0.0.0.0/0tcp dpt:443
0 0 ACCEPT tcp  --  enp4s0.1441 enp4s0.1  0.0.0.0/0
  0.0.0.0/0tcp dpt:587
  676 46636 LOGudp  --  enp4s0.1441 enp4s0.1  0.0.0.0/0
  0.0.0.0/0udp dpt:53 LOG flags 0 level 4 prefix "PRE-ACCEPT "
  676 46636 ACCEPT udp  --  enp4s0.1441 enp4s0.1  0.0.0.0/0
  0.0.0.0/0udp dpt:53
   25  1750 LOGall  --  *  *   0.0.0.0/0
0.0.0.0/0LOG flags 0 level 4 prefix "FWD "

Chain OUTPUT (policy ACCEPT 53 packets, 3180 bytes)
 pkts bytes target prot opt in out source
destination
  731  128K ACCEPT all  --  *  *   0.0.0.0/0
0.0.0.0/0ctstate RELATED,ESTABLISHED
0 0 ACCEPT icmp --  *  *   0.0.0.0/0
0.0.0.0/0
0 0 ACCEPT udp  --  *  *   0.0.0.0/0
203.118.153.20   udp spt:1194 dpt:1194
0 0 ACCEPT udp  --  *  *   0.0.0.0/0
0.0.0.0/0udp dpt:53
0 0 ACCEPT tcp  --  *  *   0.0.0.0/0
0.0.0.0/0tcp

Re: Més discs SSD

2019-12-16 Thread Josep Lladonosa

On Mon, 16 Dec 2019 at 21:04, Orestes Mas  wrote:
>
> Bon dia a tothom,
>
> El primer símptoma ha estat que l'apt-get petava perquè el paquet 
> openssh-client no podia actualitzar el fitxer /etc/ssh/ssh-config
>
> Si provava de fer un "cat" del fitxer donava error d'entrada/sortida
>
> Ara estic fent un "e2fsck -f -c" i amb el 50% executat ja ha trobat 44 errors 
> de blocs que no pot llegir.
>
> Suposo que la recomanació és disc nou, oi? És SSD. Les dades no són problema, 
> les tinc més que replicades.

També podria ser el cable fluix o bé que els connectors s'hagin donat.
Pot provar a usar smartcl, a vejam si t'aporta informació:

smartctl --all /dev/sda


Salutacions,
Josep

>
> Orestes.
> --
> Enviat des del meu dispositiu Android amb el K-9 Mail. Disculpeu la brevetat.



-- 
--
Salutacions...Josep
--

Re: Macbook Post-Installation Issue

2019-12-16 Thread Keith Bainbridge


On 17/12/19 5:46 am, Kent West wrote:



Unless things have changed recently (and I don't believe they have), you 
could also run "sudo tasksel" and pick the Desktop Environment[s] you 
prefer.



Just worked for me, when I tried it just for fun

--
Keith Bainbridge

keith.bainbridge.3...@gmail.com
+61 (0)447 667 468

Broken PMTUD / ICMP blackhole?

2019-12-16 Thread Celejar

Hi,

I have a Debian Sid system with generally working networking. Recently,
I experienced some strange connectivity problems with a particular
network connection (tethering via wifi to a cell phone running
LineageOS, using Mint Mobile, a T-Mobile MVNO), notably TLS handshakes
hanging and failing to complete. Following some clues I found on the
internet [1], I suspected, and believe I've found evidence of, a
PMTUD / ICMP blackhole problem. Testing with 'ping -M do 1.1.1.1 -s
', I find that for  <= 1412, I get normal ping replies, but for
 > 1412, I get no replies, until I get closer to 1500 (generally
with  > 1472), at which point I get something like:

PING 1.1.1.1 (1.1.1.1) 1492(1520) bytes of data.
ping: local error: message too long, mtu=1500

With  = 1472, I get, at least sometimes:

>From 192.168.43.245 icmp_seq=2 Frag needed and DF set (mtu = 1472)

followed by (for various values of ):

ping: local error: message too long, mtu=1472

until I drop below 1444, at which point I once again get no reply,
until  <= 1412, at which point I once again get normal ping replies.

For comparison purposes, on a normal, properly behaving network
connection, I get normal ping replies for  <= 1472, and "message
too long" for  > 1472.

Am I understanding this correctly, that there's some kind of PMTUD /
ICMP blackhole problem here? If so, what can I do about it? My
understanding is that I can either set the MTU lower on the client, or
do MSS clamping. Any suggestions? Is this something Mint / T-Mobile, or
someone upstream, is just messing up?

[1] E.g., 
https://www.reddit.com/r/WireGuard/comments/cy13jt/tls_handshake_errors_behind_wireguard_vpn/

Celejar

Re: looking for a replacement for debian since systemd

2019-12-16 Thread Jimmy Johnson


On 12/15/19 11:45 PM, Jonas Smedegaard wrote:

Quoting Jimmy Johnson (2019-12-16 02:13:08)

On 12/14/19 5:29 AM, Jonas Smedegaard wrote:

Hi Alessandro,

Quoting Alessandro Vesely (2019-12-14 13:23:14)

On Sat 14/Dec/2019 03:18:39 +0100 Kenneth Parker wrote:


I use Devuan, especially on older hardware.   Works well.



Good to know.  For the time being, I see SysV is working.  I'm on
old-stable Debian.  As, in a few months, it will be time to
migrate, I'll have to decide on Devuan (current) vs. Buster.  Any
recommendation on that?  Will the voted resolution shred any light
on migration strategies?


Since this is a Debian list, I recommend to discuss Debian here, and
consult Devuan mailinglist for details of what they can offer.

The vote currently in Debian will affect _future_ releases of
Debian, not the current stable release, Buster.

For Debian Buster (regardless of the outcome of the vote) SysV is a
supported init system: Please do report any flaws you may encounter!


Kde5 on buster without systemd don't work,


True, and also what I wrote (and even mentioned KDE explicitly): Depends
on which kind of system you need and how much of systemd must be gone.

In case you missed, here it is again:


Beware in discussions here and elsewhere to distinguish between these:

  a) running a system with SysV as init system
  b) running a system without systemd installed
  c) running a system without libsystemd0 installed

If you need a), then quite likely Debian Buster is fine for you.

If you need b) and don't need a complex¹ X11/Wayland desktop
environment, then Debian Buster is likely fine as well.

If you need c) and/or a complex¹ X11/Wayland desktop environment, then
Debian Buster is most likely no fun for you - might be possible, but
you will feel alone and bugreports will be harder to debug due to your
complex setup (in particular your suppressing package
recommendations).

¹ In this context, "complex" desktop environments include GNOME, KDE,
Cinnamon, MATE and more - as a rule of thumb anything which directly
or indirectly recommends dbus-user-session.


It's nice to see that you agree.

blessings,
--
Jimmy Johnson

Slackware64 11.19.KDE5 - AMD A8-7600 - EXT4 at sda7
Registered Linux User #380263

Re: Impossible to type "ù"

On Mon 16 Dec 2019 at 22:53:23 (+0100), Pétùr wrote:
> I cannot type "ù" anymore on Debian Xfce Sid (French keyboard).
> 
> All other accented character (éàûè) work but the cursor just blinked
> when using the dedicated key for "ù".

[…]

> I tried different keyboard configuration with
> 
> # dpkg-reconfigure keyboard-configuration
> 
> the current one:
> 
> # cat /etc/default/keyboard
> # KEYBOARD CONFIGURATION FILE
> 
> # Consult the keyboard(5) manual page.
> 
> XKBMODEL="pc105"
> XKBLAYOUT="fr"
> XKBVARIANT=""
> XKBOPTIONS="compose:lwin,terminate:ctrl_alt_bksp"
> 
> BACKSPACE="guess"

You don't say what the dedicated key for ù is, but I would expect that
you might need something like lv3:ralt_switch in your XKBOPTIONS
to get it from one keystroke. I think I'm assuming you have a R-Alt
key, sometimes engraved AltGr. (Being English, I compose ù with `u.)

All that said, your use of "anymore" might suggest a bug in sid.

Cheers,
David.

Re: apparent change in hostnames on LAN without admin intervention

2019-12-16 Thread John Hasler

David writes:
> "… … home network, it's recommended that you use the domain name
> home.arpa on all your computers".

Use .UUCP .  That'll fix 'em.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: Re : Re: Erreur d'URL pour la liste debian user french



>> L'éditeur de la page en question n'est pas forcément abonné
>> à la liste (je pense qu'il n'y a jamais posté, en tout cas),
>> mieux vaux lui envoyer un mail directement à lui, son
>> adresse étant bien en évidence au bas de la page...
>>
>> Y.
>
> C'est fait.
Sauf que non, mon mail n'est pas arrivé.

: host mailly.debian.org[82.195.75.114] said: 550 Unrouteable
address (in reply to RCPT TO command)

Re: Re : Re: Erreur d'URL pour la liste debian user french



Le 16/12/2019 à 22:01, Yves Rutschle a écrit :
> On Mon, Dec 16, 2019 at 11:53:51AM +0100, G2PC wrote:
>> Le but du message était évidement de :
>> -1 Corriger le lien qui ne fonctionne plus ( Remplacer, ou, supprimer )
>> -2 De ce fait, de faire remonter l'information à une personne pouvant
>> éditer la page en question.
> L'éditeur de la page en question n'est pas forcément abonné
> à la liste (je pense qu'il n'y a jamais posté, en tout cas),
> mieux vaux lui envoyer un mail directement à lui, son
> adresse étant bien en évidence au bas de la page...
>
> Y.


C'est fait.

Re: Debian 10.2 ne démarre pas



>>
>> Si cela apparait dans le Bios dans les choix de démarrage, c'est
>> qu'il s'agit donc de la MBR ?
>
> Non. Visiblement tu ne comprends rien et tu fais n'importe quoi, mais
> j'ai la flemme de t'expliquer.

De plus en plus désagréable la communauté du libre.
En attendant, mon n'importe quoi a bien fonctionné, me permet de booter
depuis le SSD, et, a bien ajouté une entrée depuis le BIOS.
Pour du n'importe quoi, ça semble mine de rien, plutôt opérationnel et
cohérent, c'est ce que j'aurais pu attendre de mieux pour le moment.

Le seul problème qui reste, c'est les entrée du debian qui ne fonctionne
pas sur mon système, mais ça, on ne peut pas lui demander de fonctionner
partout, puisque la communauté fait n'importe quoi.

>> J'aimerais bien me débarrasser de ses deux lignes concernant Debian,
>> affichées dans les périphériques de démarrage, avant de continuer à
>> bidouiller, puisque Debian n'est plus installé.
>
> man efibootmgr

Re: Impossible to type "ù"

2019-12-16 Thread Mark Allums


On 12/16/19 3:53 PM, Pétùr wrote:

Hi,

I cannot type "ù" anymore on Debian Xfce Sid (French keyboard).

All other accented character (éàûè) work but the cursor just blinked 
when using the dedicated key for "ù".


Any clue?


Bad key?

Re: unstable: directory pulse in root directory : /pulse where from?

2019-12-16 Thread Cindy Sue Causey

On 12/14/19, Andrei POPESCU  wrote:
> On Sb, 14 dec 19, 10:04:34, Jörg-Volker Peetz wrote:
>> Brian wrote on 13/12/2019 21:29:
>> > On Fri 13 Dec 2019 at 20:26:32 +0100, Jörg-Volker Peetz wrote:
>> >>
>> >> does anybody know which package generates the directory /pulse ? This
>> >> is a bug
>> >> in unstable I think, but I can't find which package is the culprit.
>> >
>> > https://www.debian.org/distrib/packages
>> >
>> That doesn't help, the same way as
>>
>> $ dpkg -S /pulse
>> dpkg-query: no path found matching pattern /pulse
>>
>> fails to give any clue.
>> The directory is generated at boot-time. But I wasn't able to find any
>> hint in
>> systemd or udev conf-files.
>
> You could try to use inotify to find out what is creating it.
>
> My money is on pulseaudio ;)

Something about pulseaudio, maybe a "pa" in a file name somehow, is
what coincidentally hit my radar, too... just a few seconds ago.

Got forced offline another 3 weeks with more hardware failure. Am
trying to get ANOTHER dialup modem running directly via Debian. That
meant poking around in /etc where there sits, of all things, a /pulse
directory in *my* setup..

I THINK... I saw one or more files ending in... maybe DOTca? In case
that helps..

What I was already thinking when I read this thread hours ago is that
it sounds like a misfire in where the /pulse directory is setting up
its home base. Mine appears basically permanent. Maybe this other one
is a cranky sort that keeps re-establishing itself the way I've seen
some packages do with files if they're missing at startup.

BUT... my experience with THOSE files reappearing as needed (if
deleted intentionally or otherwise) is that THOSE files are usually
something found under /home/user buried within all those dot
directories accessed via CTRL+H.

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with birdseed... annnd... a dial-up modem that is SO CLOSE to
working directly through Debian. SO CLOSE. *

Re: apparent change in hostnames on LAN without admin intervention

On Mon 16 Dec 2019 at 12:28:13 (+), Bonno Bloksma wrote:
> > > I could be quite wrong, but I thought that "local" was actually 
> > > suggested as a domain name at one time by the installer. (And I 
> 
> Don't know if Debian did that but ... a LOONG time ago, at least looong in 
> "internet years", it was indeed recommended to use the "real" domain name for 
> the servers that could be reached from the internet and to use the same corp 
> part but .local as TLD for the internal network. That was supposed to avoid 
> confusion with duplicate names in use for different servers/services.
> In our case I was supposed to use tio.nl for public stuff and tio.local for 
> internal stuff.

Sounds like:
https://www.microsoftpressstore.com/articles/article.aspx?p=2195190=2
dated May 15, 2011.

> Me, I never understood that. If it has the same name it should be the same 
> server/service, both internal and external. For internal stuff I simply use a 
> subdomain name like staff.tio.nl for stuff that relates to the staff and 
> student.tio.nl for stuff that relates to the students.
> But at one time it was the "official policy" to use .local for internal 
> stuff. It was even in documentation and course material in those days.
> That was of course years before someone decided to use .local for mDns which 
> then led to the current confusion. :-(

Actually the example above looks as it lasted about 3 weeks,
whereupon:

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc738121(v=ws.10)?redirectedfrom=MSDN
dated June 6, 2011.

Not quite seven days in May, but close.

I've read that using {staff,student}.tio.nl, as you do, is the correct
thing to do, using a technique called "split-horizon", which is
something I'd prefer not to involve myself in.

If Debian is into making suggestions, perhaps "If you are setting up a
home network, you can make something up, but make sure you use the
same domain name on all your computers" could be replaced by something
like "… … home network, it's recommended that you use the domain name
home.arpa on all your computers".

Cheers,
David.

RE: apparent change in hostnames on LAN without admin intervention

2019-12-16 Thread Bonno Bloksma

Hi,

> > I could be quite wrong, but I thought that "local" was actually 
> > suggested as a domain name at one time by the installer. (And I 

Don't know if Debian did that but ... a LOONG time ago, at least looong in 
"internet years", it was indeed recommended to use the "real" domain name for 
the servers that could be reached from the internet and to use the same corp 
part but .local as TLD for the internal network. That was supposed to avoid 
confusion with duplicate names in use for different servers/services.
In our case I was supposed to use tio.nl for public stuff and tio.local for 
internal stuff.

Me, I never understood that. If it has the same name it should be the same 
server/service, both internal and external. For internal stuff I simply use a 
subdomain name like staff.tio.nl for stuff that relates to the staff and 
student.tio.nl for stuff that relates to the students.
But at one time it was the "official policy" to use .local for internal 
stuff. It was even in documentation and course material in those days.
That was of course years before someone decided to use .local for mDns which 
then led to the current confusion. :-(

Bonno Bloksma

Impossible to type "ù"

2019-12-16 Thread Pétùr


Hi,

I cannot type "ù" anymore on Debian Xfce Sid (French keyboard).

All other accented character (éàûè) work but the cursor just blinked 
when using the dedicated key for "ù".


Any clue?

$ locale
LANG=fr_FR.UTF-8
LANGUAGE=
LC_CTYPE="fr_FR.UTF-8"
LC_NUMERIC="fr_FR.UTF-8"
LC_TIME="fr_FR.UTF-8"
LC_COLLATE="fr_FR.UTF-8"
LC_MONETARY="fr_FR.UTF-8"
LC_MESSAGES="fr_FR.UTF-8"
LC_PAPER="fr_FR.UTF-8"
LC_NAME="fr_FR.UTF-8"
LC_ADDRESS="fr_FR.UTF-8"
LC_TELEPHONE="fr_FR.UTF-8"
LC_MEASUREMENT="fr_FR.UTF-8"
LC_IDENTIFICATION="fr_FR.UTF-8"
LC_ALL=

I tried different keyboard configuration with

# dpkg-reconfigure keyboard-configuration

the current one:

# cat /etc/default/keyboard
# KEYBOARD CONFIGURATION FILE

# Consult the keyboard(5) manual page.

XKBMODEL="pc105"
XKBLAYOUT="fr"
XKBVARIANT=""
XKBOPTIONS="compose:lwin,terminate:ctrl_alt_bksp"

BACKSPACE="guess"

Re: Re : Re: Erreur d'URL pour la liste debian user french

2019-12-16 Thread Yves Rutschle

On Mon, Dec 16, 2019 at 11:53:51AM +0100, G2PC wrote:
> Le but du message était évidement de :
> -1 Corriger le lien qui ne fonctionne plus ( Remplacer, ou, supprimer )
> -2 De ce fait, de faire remonter l'information à une personne pouvant
> éditer la page en question.

L'éditeur de la page en question n'est pas forcément abonné
à la liste (je pense qu'il n'y a jamais posté, en tout cas),
mieux vaux lui envoyer un mail directement à lui, son
adresse étant bien en évidence au bas de la page...

Y.

Buster 10.2, new mediawiki install unable to connect to database

2019-12-16 Thread Keith Christian

Fresh format-disk-and-install Buster 64-bit.
This is my third attempt, with the mediawiki installer having problems
logging in to MariaDB every time.
I've installed mediawiki (Jessie?) with zero problems.

NOTE-MariaDB was installed with a simple "sudo apt -y install
mediawiki" as described below.
Ran "sudo apt -y install mediawiki" without installing any other software.
Rebooted.

Opened browser to http://localhost/mediawiki/.
Got this screen:
MediaWiki 1.31.4
LocalSettings.php not found.
Please set up the wiki first.

Clicked the "set up the wiki" link.
Got this status "The environment has been checked. You can install MediaWiki."

Clicked Continue.
Got this:
Cannot access the database: No such file or directory (localhost).
Check the host, username and password and try again.

Started MariaDB with this command line:
sudo mysqld_safe --skip-grant-tables &

Able to log in as the MariaDB root user via mysql -u root.
Attempted to set the root password since mediawiki setup didn't like
the login info.
Unable to reset the root password:
MariaDB [(none)]> SET PASSWORD FOR 'root'@'localhost' =
PASSWORD('secret_password');
ERROR 1131 (42000): You are using MariaDB as an anonymous user
and anonymous users are not allowed to modify user settings
MariaDB [(none)]> select user();
++
| user() |
++
| root@  |
++
Exit mysql client.

Ran "sudo apt -y purge mediawiki" hoping to destroy the MariaDB
databases so I could get a fresh start solving mediawiki's db login
problems.
Rebooted.

Ran "sudo apt -y install mediawiki" again, no MariaDB installation
messages which meant the "purge mediawiki" did not also purge MariaDB
(which it installed.)
No success.

Seems that the mediawiki installer has defaults for the 'root'
database user with a blank password, doesn't work with that either.

What is wrong?

Thanks.

Re: apparent change in hostnames on LAN without admin intervention

On 12/16/19 3:25 PM, David Wright wrote:

On Mon 16 Dec 2019 at 13:36:27 (-0500), Jape Person wrote:

On 12/16/19 11:39 AM, David Wright wrote:

On Mon 16 Dec 2019 at 10:53:02 (-0500), Jape Person wrote:

On 12/16/19 12:42 AM, David Wright wrote:

On Sat 14 Dec 2019 at 13:49:25 (-0500), Jape Person wrote:

On 12/14/19 1:24 AM, john doe wrote:

...

The file '/etc/resolv.conf' should let you know what TLD is sent from
the DHCP server.

Debian shouldn't modify your configuration files '/etc' without your nolage.

Depending on the packages chosen, /etc/resolv.conf is one file in /etc
that is modified by Debian. The resolvconf package lists 23 other
programs that it is designed to adjudicate between, for want of a
better term.

...

That has been my understanding, and it's why I never edit /etc/resolv.conf
myself.

Note that the TLD '.lan' is sometime used.

That's another choice, like .local, that could always be issued as a
real TLD at some point in the future.

1) https://www.xfinity.com/support/articles/list-of-approved-cable-modems

I'm using my own router behind the modem provided by the ISP. I've
never used a router provided by an ISP for controlling my network.

I'm using a Luxul XWR-1750 which has been kept on the latest firmware
available. Last upgrade was done early this year, long before the
noted change in names.

The router is set to provide static IP addresses and has the names of
each of the systems associated with their MAC Addresses and IP
Addresses.

Can you just clarify this? My router provides static IP addresses on
the basis of the MAC addresses, all the information being typed in¹
by me. It also lists the names of the other hosts, but only because
those hosts told it their names. IOW the router (cheap, $35) doesn't
issue hostnames, nor provide a DNS service itself. It also neither
knows nor cares what the domain name of the network is.

How much of this is the same on the router in your network?

¹ actually, of course, it deduces all but the last number in the
dotted quad.

Yes, it's my understanding that my router does provide DNS on the
local network and will provide the 208.67.222.222, 208.67.220.220
OpenDNS servers or whatever the ISP provides for DNS servers,
depending upon entries made in its setup pages. I do not think that it
actually issues the hostnames, but it does detect whatever hostnames
the devices provide and shows them associated with the IP addresses
its DHCP server issues in a table. Do you think that I'm
misunderstanding the arrangement? Could well be. I have ASSumed that
it worked this way from the appearance of the tables in the setup
software.

The software running the router is licensed under Luxul Open Source Code for
Programmers (GPL).

Others will have to comment on the functionality provided by this
software as I'm not familiar with it.

But a table of names doesn't convince me that your router is providing
a DNS service (or a domain name). My router maintains a list of names,
but they're not strictly hostnames unless I edit them to be so. For
example, when we bought our last Roku¹, it told the router it was
called "ROKU PREMIEREPLUS - 964" which I edited to "rokupw²", the name
by which I can ping it if I want to know whether it's powered up.

Try typing
$ nslookup chip-nuc 192.168.1.1
where 192.168.1.1 is the IP address for *your* router.

¹ a TV streamer. ² and "rokupe" for its ethernet interface.

Okay. I reset all of the hostnames on the network to avoid using
improper names for the domain and to correct an issue where I would
have had a user name and hostname being the same.

I did what you suggested and got the following.

$ nslookup hostname 192.168.0.1
Server: 192.168.0.1
Address:192.168.0.1#53

Name: hostname
Address: 192.168.0.116

Note: I replaced the actual hostname with the word "hostname" in the example.

My understanding is that you do have a DNS server in the router then,
so you could avoid having to maintain lists of hostnames and IP
addresses on any of the other hosts if the router is always on.

I assume you can expand this to include the domain name, because the
default dhclient.conf appears to ask for it from the dhcp server.
But I certainly prefer to have each host know its own hostname and
domain name before it configures the network, and IIRC the default
Debian configuration is to put
127.0.1.1 hostname.domain hostname
into /etc/hosts which ensures this.

Understood. I have my /etc/hosts files set that way, and I add a list of domains I want blocked to
these files as well.

I can't really help with what changed and when, but can only point out
that people who've used .local seem to report intermittent behaviour
in various forums that google has turned up.

Cheers,
David.

Understood. I have had "weirdness" on this network for quite a while. Have assumed it was something
amiss in the wireless drivers because it always corrected itself when systems were rebooted. I
should have known that

Re: apparent change in hostnames on LAN without admin intervention

On Mon 16 Dec 2019 at 13:36:27 (-0500), Jape Person wrote:
> On 12/16/19 11:39 AM, David Wright wrote:
> > On Mon 16 Dec 2019 at 10:53:02 (-0500), Jape Person wrote:
> > > On 12/16/19 12:42 AM, David Wright wrote:
> > > > On Sat 14 Dec 2019 at 13:49:25 (-0500), Jape Person wrote:
> > > > > On 12/14/19 1:24 AM, john doe wrote:
> > > ...
> > > > > > The file '/etc/resolv.conf' should let you know what TLD is sent 
> > > > > > from
> > > > > > the DHCP server.
> > > > > > 
> > > > > > Debian shouldn't modify your configuration files '/etc' without 
> > > > > > your nolage.
> > > > 
> > > > Depending on the packages chosen, /etc/resolv.conf is one file in /etc
> > > > that is modified by Debian. The resolvconf package lists 23 other
> > > > programs that it is designed to adjudicate between, for want of a
> > > > better term.
> > > > 
> > > ...
> > > 
> > > That has been my understanding, and it's why I never edit 
> > > /etc/resolv.conf myself.
> > > 
> > > > > > Note that the TLD '.lan' is sometime used.
> > > > 
> > > > That's another choice, like .local, that could always be issued as a
> > > > real TLD at some point in the future.
> > > > 
> > > > > > 1)  
> > > > > > https://www.xfinity.com/support/articles/list-of-approved-cable-modems
> > > > > 
> > > > > I'm using my own router behind the modem provided by the ISP. I've
> > > > > never used a router provided by an ISP for controlling my network.
> > > > > 
> > > > > I'm using a Luxul XWR-1750 which has been kept on the latest firmware
> > > > > available. Last upgrade was done early this year, long before the
> > > > > noted change in names.
> > > > > 
> > > > > The router is set to provide static IP addresses and has the names of
> > > > > each of the systems associated with their MAC Addresses and IP
> > > > > Addresses.
> > > > 
> > > > Can you just clarify this? My router provides static IP addresses on
> > > > the basis of the MAC addresses, all the information being typed in¹
> > > > by me. It also lists the names of the other hosts, but only because
> > > > those hosts told it their names. IOW the router (cheap, $35) doesn't
> > > > issue hostnames, nor provide a DNS service itself. It also neither
> > > > knows nor cares what the domain name of the network is.
> > > > 
> > > > How much of this is the same on the router in your network?
> > > > 
> > > > ¹ actually, of course, it deduces all but the last number in the
> > > > dotted quad.
> > > 
> > > Yes, it's my understanding that my router does provide DNS on the
> > > local network and will provide the 208.67.222.222, 208.67.220.220
> > > OpenDNS servers or whatever the ISP provides for DNS servers,
> > > depending upon entries made in its setup pages. I do not think that it
> > > actually issues the hostnames, but it does detect whatever hostnames
> > > the devices provide and shows them associated with the IP addresses
> > > its DHCP server issues in a table. Do you think that I'm
> > > misunderstanding the arrangement? Could well be. I have ASSumed that
> > > it worked this way from the appearance of the tables in the setup
> > > software.
> > > 
> > > The software running the router is licensed under Luxul Open Source Code 
> > > for Programmers (GPL).
> > 
> > Others will have to comment on the functionality provided by this
> > software as I'm not familiar with it.
> > 
> > But a table of names doesn't convince me that your router is providing
> > a DNS service (or a domain name). My router maintains a list of names,
> > but they're not strictly hostnames unless I edit them to be so. For
> > example, when we bought our last Roku¹, it told the router it was
> > called "ROKU PREMIEREPLUS - 964" which I edited to "rokupw²", the name
> > by which I can ping it if I want to know whether it's powered up.
> > 
> > Try typing
> > $ nslookup chip-nuc 192.168.1.1
> > where 192.168.1.1 is the IP address for *your* router.
> > 
> > ¹ a TV streamer. ² and "rokupe" for its ethernet interface.
> > 
> Okay. I reset all of the hostnames on the network to avoid using
> improper names for the domain and to correct an issue where I would
> have had a user name and hostname being the same.
> 
> I did what you suggested and got the following.
> 
> $ nslookup hostname 192.168.0.1
> Server:   192.168.0.1
> Address:  192.168.0.1#53
> 
> Name: hostname
> Address: 192.168.0.116
> 
> Note: I replaced the actual hostname with the word "hostname" in the example.

My understanding is that you do have a DNS server in the router then,
so you could avoid having to maintain lists of hostnames and IP
addresses on any of the other hosts if the router is always on.

I assume you can expand this to include the domain name, because the
default dhclient.conf appears to ask for it from the dhcp server.
But I certainly prefer to have each host know its own hostname and
domain name before it configures the network, and IIRC the default
Debian configuration is to put
  127.0.1.1  hostname.domain  hostname
into

Més discs SSD

2019-12-16 Thread Orestes Mas

Bon dia a tothom,

El primer símptoma ha estat que l'apt-get petava perquè el paquet 
openssh-client no podia actualitzar el fitxer /etc/ssh/ssh-config

Si provava de fer un "cat" del fitxer donava error d'entrada/sortida

Ara estic fent un "e2fsck -f -c" i amb el 50% executat ja ha trobat 44 errors 
de blocs que no pot llegir.

Suposo que la recomanació és disc nou, oi? És SSD. Les dades no són problema, 
les tinc més que replicades.

Orestes.
-- 
Enviat des del meu dispositiu Android amb el K-9 Mail. Disculpeu la brevetat.

Re: unstable: directory pulse in root directory : /pulse where from?

2019-12-16 Thread Stephan Seitz


On Mo, Dez 16, 2019 at 08:32:01 +0100, Jörg-Volker Peetz wrote:

Does anybody else see such a /pulse directory?


Yes, here as well (two testing systems).

Shade and sweet water!

Stephan

--
|If your life was a horse, you'd have to shoot it.|

Re: unstable: directory pulse in root directory : /pulse where from?

2019-12-16 Thread Jörg-Volker Peetz

Greg Wooledge wrote on 16/12/2019 17:29:
> On Sat, Dec 14, 2019 at 10:04:34AM +0100, Jörg-Volker Peetz wrote:
>> $ dpkg -S /pulse
>> dpkg-query: no path found matching pattern /pulse
>>
>> fails to give any clue.
>> The directory is generated at boot-time. But I wasn't able to find any hint 
>> in
>> systemd or udev conf-files.
> 
> Well, the first thing I would try would be "grep -r /pulse /etc".
> And if that fails, "grep -r /pulse /lib/systemd".

Did that, also

$ grep -rI pulse /lib/udev

to no avail.
> 
> If *those* both fail... well, I might be crazy enough to try removing
> the offending directory, doing "chattr +i /", then rebooting, and seeing
> who complains when they can't create the /pulse directory.  Only on a
> system where I have local hardware access, of course -- not a remote.
> 
> Do not forget to remove the immutable bit after your test is complete.
> 
> And as a wise reader already said, it's probably pulseaudio.  Meaning,
> you might be able to test without rebooting, by stopping pulseaudio,
> removing the directory, and starting pulseaudio, to see if it gets
> recreated.

The /pulse directory is created at boot-time. The pulseaudio process is started
at login on this system. Also, pulseaudio continues to work after removal of
/pulse which is always an empty directory. It has uid 0 and gid 0 an is not
readable for group or others.

Does anybody else see such a /pulse directory?

Regards,
Jörg.

Re: gestionnaire de liste léger, interface FastCGI

2019-12-16 Thread ajh-valmer

On Friday 13 December 2019 23:14:53 Basile Starynkevitch wrote:
> Connaissez vous un gestionnaire de "mailing list" léger, efficace 
> (préférentiellement codé dans un language compilé: C++,  Ocaml, Go...), 
> avec une interface FastCGI?
> Donc ni sympa  ni mailman .
> Je vois listmonk.app  (mais ça ne semble pas FastCGI 
> compatible)
> Pour les curieux, c'est pour les échanges autour de 
> http://refpersys.org/ ; je m'attends à quelques centaines d'abonnés et 
> quelques dizaines de message par jour. Ce sont des messages HTML, pas 
> text/plain.

Il y a Mailman,
pas mal de Python, il semble CGI,
l'adresse est /cgi-bin/mailman/
mais Fast, je sais pas.

Je l'utilise et j'en profite, je ne sais pas du tout ou
sont les abonnés (quel répertoire ou fichier).

Bonne soirée,

A. Valmer

E-Mail-Benachrichtigung (Dringend behandeln)

2019-12-16 Thread Cultura Amán

Beachtung:

Ihr E-Mail-Konto wurde kürzlich an einem unbekannten Ort angemeldet.
Bitte klicken Sie hier zur Bestätigung, um die Schließung Ihres E-Mail-Kontos 
zu vermeiden

Um diese Überprüfung abzuschließen, klicken Sie einfach 
hier

Mit freundlichen Grüßen,
Email 
Unterstützung

Este mensaje se dirige exclusivamente a su destinatario. Si usted no es el 
destinatario indicado y ha recibido este mensaje por error, le rogamos que nos 
lo comunique inmediatamente por esta misma vía y proceda a su destrucción. 
Queda informado de que este correo electrónico y, en su caso, cualquier fichero 
adjunto al mismo, puede contener información confidencial, exclusivamente 
dirigida a la persona o entidad a la que se le envía y su utilización, 
divulgación y/o copia sin autorización está prohibida en virtud de la 
legislación vigente. Queda prohibido cualquier uso indebido, revisión, 
retransmisión o distribución del contenido por personas ajenas al destinatario. 
Así mismo queda prohibido cualquier uso distinto al de la mera visualización de 
la información y/o documentos contenidos en este correo electrónico. Todo el 
material incluido en este correo pertenece al Instituto Cervantes y no puede 
ser usado, de ningún modo, sin el consentimiento expreso del propietario.

Re: Debian 10.2 ne démarre pas

2019-12-16 Thread Pascal Hambourg


Le 16/12/2019 à 19:24, G2PC a écrit :


Si cela apparait dans le Bios dans les choix de démarrage, c'est qu'il
s'agit donc de la MBR ?


Non. Visiblement tu ne comprends rien et tu fais n'importe quoi, mais 
j'ai la flemme de t'expliquer.



J'aimerais bien me débarrasser de ses deux lignes, avant de continuer à
bidouiller.


man efibootmgr

Re: New Install Boots to Grub

2019-12-16 Thread Pascal Hambourg


Le 16/12/2019 à 16:55, Dr. Jason Amerson a écrit :

Hello,

I installed Debian 10.2.0 from a USB drive and the installation finished 
without errors. The only thing that happened during install is that it was 
unable to setup the network. Anyways, I removed the USB drive and rebooted the 
computer. It then booted into grub.


This is expected, as GRUB is Debian's default boot loader.


There was a message telling me I can press TAB to get a list of commands


This is less expected. GRUB should display a menu.
What was the GRUB prompt, simply "grub>" or "grub rescue>" ?
If "grub>", the config file grub.cfg is missing.
If "grub rescue>", GRUB was not installed properly.


but I know nothing about grub and I do not know how to fix the computer so that 
it boots into Debian. Will someone please help me with this?


If you don't know GRUB shell's syntax, then I guess the easier way is to 
boot the Debian installer, select "rescue", follow the steps and 
reinstall GRUB when the option is offered. Make sure you select the 
proper root/boot partition.

Re: Gnucash broken after Update

On Mon, Dec 16, 2019 at 01:42:35PM -0500, Jape Person wrote:
> On 12/16/19 12:41 PM, Markus Grunwald wrote:
> >Hi,
> >
> >a few days ago, I ran an apt update of my debian/desting machine and got
> >a new gnucash version [...]

[...]

> libaqbanking (5.99.43beta-2) unstable; urgency=medium
> 
>   Important notice for users upgrading from versions prior to 6.x
>   ===
> 

[...]

>   Luckily a migration of the old settings to the new location is possible.
>   Just copy all files from ~/.aqbanking/settings/ to ~/.aqbanking/settings6
> 
>   cd ~/.aqbanking
>   mkdir -p settings6
>   cp -r settings/* settings6

As Jape says -- this could be due to an update to libaqbanking 6. Which
version of libaqbanking do you have installed? (apt search libaqbanking
or similar should help with that).

(Note that aqbanking 5.99.x is already "6")

If you follow the above instructions, make sure ~/.aqbanking/settings6
doesn't exist (yet). If there is one, I'd make first a backup and then
move it out of the way.

Cheers
-- tomás

signature.asc
Description: Digital signature

Re: looking for a replacement for debian since systemd

2019-12-16 Thread 0...@caiway.net

On Mon, 16 Dec 2019 16:40:52 +0100
Alberto Luaces  wrote:

> "0...@caiway.net" writes:
> 
> > But I do like systemd-container very much.
> 
> What is that thing? Another name for systemd-nspawn?
> 

package systemd-container provides systemd's tools for nspawn and
container/VM management:
 * systemd-nspawn
 * systemd-machined and machinectl
 * systemd-importd

Re: New Install Boots to Grub

2019-12-16 Thread Kent West

On Mon, Dec 16, 2019 at 9:56 AM Dr. Jason Amerson 
wrote:

> Hello,
>
> I installed Debian 10.2.0 from a USB drive and the installation finished
> without errors. The only thing that happened during install is that it was
> unable to setup the network. Anyways, I removed the USB drive and rebooted
> the computer. It then booted into grub. There was a message telling me I
> can press TAB to get a list of commands but I know nothing about grub and I
> do not know how to fix the computer so that it boots into Debian. Will
> someone please help me with this?
>
> Thank you,
>
> Jason
>

Grub should have given you a menu with (probably) two options; something
like:

Debian GNU/Linux
Advanced Options

If you did not get such a menu, something went wrong during the install.

-- 
Kent West<")))><
Westing Peacefully - http://kentwest.blogspot.com

Re: Macbook Post-Installation Issue

2019-12-16 Thread Kent West

On Mon, Dec 16, 2019 at 11:43 AM Dan Ritter  wrote:

> Dr. Jason Amerson wrote:
> > Dan,
> >
> > I cannot login to my desktop. I am just presented with the Debian
> GNU/Linux 10 tty1.
> >
> >
> > Jason
> >
> >
> > On 12/16/2019 12:04:09 PM, Dan Ritter  wrote:
> > Dr. Jason Amerson wrote:
> > > Hello,
> > >
> > > Me again. Different computer with a different problem. I may ask about
> other computers later. I am in the process of migrating my laptops from
> Windows 10 to Debian. This computer is a Macbook Pro. I installed Debian
> without errors, not even network errors like my other computer. I rebooted
> the computer and I was taken to a grub screen where I can select ???Debian
> GNU/Linux??? or ???Advanced Options for Debian GNU/Linux.??? I chose the
> first option. Then I was taken to a tty1 prompt for me to login. I know how
> to login into the shell and issue commands, I just do not know what to do
> at this point. This is something that I have not had happen before. I just
> would like to login to my KDE desktop.
> > >
> >
> > You've probably not installed kde.
> >
> > Log in. Gain root privileges via su or sudo. apt install kde and
> > an x display manager.
> >
> > You should be happy after that.
> >
>
> Don't top post here.
>
> Always continue conversations on the mailing list, not in
> private, unless someone asks you to take it private. That way,
> other people get the benefit (and other people can help).
>
> Nobody's impressed by a doctoral degree here, whether it be
> MD or Ph.D. or JD.
>
> You said "I know how to login into the shell and issue
> commands"; and I told you to do that, and then what to do
> afterwards in order to install KDE.
>
> Where it says login: give your username.
> Where it says password: give your password.
>
> You are now in a shell.
>
> Gain root privileges either by typing
> su -
> (and give the root password)
> or
> sudo -s
> (and give your own password)
>
> Now you have root privileges.
>
> type
> apt install kde-full
> to install KDE.
>
>
>
>
Unless things have changed recently (and I don't believe they have), you
could also run "sudo tasksel" and pick the Desktop Environment[s] you
prefer.

-- 
Kent West<")))><
Westing Peacefully - http://kentwest.blogspot.com

Re: Gnucash broken after Update


On 12/16/19 12:41 PM, Markus Grunwald wrote:

Hi,

a few days ago, I ran an apt update of my debian/desting machine and got
a new gnucash version. Apt DID tell me that there was something to do to
keep gnucash working. I had no time to do that, then, but I was used to
getting the instructions per e-mail. But at the time my e-mail setup was
broken and I didn't notice. Bummer.

Now I need to use gnucash and online banking is completely broken. I
searched everywhere, found the hint in
/usr/share/doc/aqbanking-tools/README.keyfile-update, but that didn't
help...

I /think/ the message had something to do with moved configuration files
for gnucash, but am not sure.

Do you have any hint for me? I urgendly need gnucash for my homebanking...

TIA,



I looked through my mailbox and found the following:

--8<--

libaqbanking (5.99.43beta-2) unstable; urgency=medium

  Important notice for users upgrading from versions prior to 6.x
  ===

  With AqBanking 6.x (including the preceding 5.99.x beta versions) the file
  location where AqBanking applications store their online banking related
  settings got changed again.  Previously the AqBanking settings were stored in
  the directory ~/.aqbanking/settings/.  After the upgrade settings are now
  stored in the directory ~/.aqbanking/settings6/.  This means without manual
  interaction all the online banking account setup will be unavailable to the
  applications using it.

  Luckily a migration of the old settings to the new location is possible.
  Just copy all files from ~/.aqbanking/settings/ to ~/.aqbanking/settings6

  cd ~/.aqbanking
  mkdir -p settings6
  cp -r settings/* settings6

  This should make the old online banking account settings available to the new
  library version.

  Updating the TAN methods to use for inline banking
  --

  Due to legal changes (PSD2) most banks in Germany were forced to switch to a
  different TAN method for authorizing transactions.  When upgrading from a
  libaqbanking version prior to 6.x, outdated TAN methods might still be cached
  in the library settings.  Please follow these steps to update the TAN methods
  for your accounts after the upgrade:

  * in the online banking application open the settings dialog for AqBanking
(varies, depending on the used application)
  * select the relevant user and click "Edit User"
  * in the dialog please click the "Get Bank Info" button (this will
anonymously fetch the current bank and user parameter data from the
bank's server)
  * in the dialog please click the "Get System Id" button (this will fetch
a new system identifier and the list of allowed TAN modes from the
bank's server)
  * after success, select a TAN method attributed with "Version 6" or higher
  * maybe close the dialog for now to open the "Edit User" dialog anew
  * in the dialog click the "Retrieve Account List" button (this will fetch
the current account list from the bank's server, from now on TAN in
version 6 will be used).

  In case you struggle with this update process, consider subscribing to the
  https://mailman.aqbanking.de/listinfo/aqbanking-user mailing list and ask for
  help (German and English language welcome).

 -- Micha Lenk   Tue, 05 Nov 2019 21:15:06 +0100

--8<--

Is it helpful?

Re: apparent change in hostnames on LAN without admin intervention


On 12/16/19 11:39 AM, David Wright wrote:

On Mon 16 Dec 2019 at 10:53:02 (-0500), Jape Person wrote:

On 12/16/19 12:42 AM, David Wright wrote:

On Sat 14 Dec 2019 at 13:49:25 (-0500), Jape Person wrote:

On 12/14/19 1:24 AM, john doe wrote:

...

The file '/etc/resolv.conf' should let you know what TLD is sent from
the DHCP server.

Debian shouldn't modify your configuration files '/etc' without your nolage.


Depending on the packages chosen, /etc/resolv.conf is one file in /etc
that is modified by Debian. The resolvconf package lists 23 other
programs that it is designed to adjudicate between, for want of a
better term.


...

That has been my understanding, and it's why I never edit /etc/resolv.conf 
myself.


Note that the TLD '.lan' is sometime used.


That's another choice, like .local, that could always be issued as a
real TLD at some point in the future.


1)  https://www.xfinity.com/support/articles/list-of-approved-cable-modems


I'm using my own router behind the modem provided by the ISP. I've
never used a router provided by an ISP for controlling my network.

I'm using a Luxul XWR-1750 which has been kept on the latest firmware
available. Last upgrade was done early this year, long before the
noted change in names.

The router is set to provide static IP addresses and has the names of
each of the systems associated with their MAC Addresses and IP
Addresses.


Can you just clarify this? My router provides static IP addresses on
the basis of the MAC addresses, all the information being typed in¹
by me. It also lists the names of the other hosts, but only because
those hosts told it their names. IOW the router (cheap, $35) doesn't
issue hostnames, nor provide a DNS service itself. It also neither
knows nor cares what the domain name of the network is.

How much of this is the same on the router in your network?

¹ actually, of course, it deduces all but the last number in the
dotted quad.


Yes, it's my understanding that my router does provide DNS on the
local network and will provide the 208.67.222.222, 208.67.220.220
OpenDNS servers or whatever the ISP provides for DNS servers,
depending upon entries made in its setup pages. I do not think that it
actually issues the hostnames, but it does detect whatever hostnames
the devices provide and shows them associated with the IP addresses
its DHCP server issues in a table. Do you think that I'm
misunderstanding the arrangement? Could well be. I have ASSumed that
it worked this way from the appearance of the tables in the setup
software.

The software running the router is licensed under Luxul Open Source Code for 
Programmers (GPL).


Others will have to comment on the functionality provided by this
software as I'm not familiar with it.

But a table of names doesn't convince me that your router is providing
a DNS service (or a domain name). My router maintains a list of names,
but they're not strictly hostnames unless I edit them to be so. For
example, when we bought our last Roku¹, it told the router it was
called "ROKU PREMIEREPLUS - 964" which I edited to "rokupw²", the name
by which I can ping it if I want to know whether it's powered up.

Try typing
$ nslookup chip-nuc 192.168.1.1
where 192.168.1.1 is the IP address for *your* router.

¹ a TV streamer. ² and "rokupe" for its ethernet interface.

Cheers,
David.

Okay. I reset all of the hostnames on the network to avoid using improper names for the domain and 
to correct an issue where I would have had a user name and hostname being the same.


I did what you suggested and got the following.

$ nslookup hostname 192.168.0.1
Server: 192.168.0.1
Address:192.168.0.1#53

Name:   hostname
Address: 192.168.0.116

Note: I replaced the actual hostname with the word "hostname" in the example.

Thanks,
JP

Re: Debian 10.2 ne démarre pas


Le 16/12/2019 à 19:01, G2PC a écrit :
>
>> ... soit, je tombe sur un écran grub, noir, avec un petit message et la 
>> ligne grub >
>>
>> Le message :
>> Minimal BASH-like editing is supported. For the first word, TAB lists 
>> possible command completions. Anywhere else TAB lists possible device or 
>> file completions.
>> grub>_
>
> Comme dit, ce message est affiché si je positionne mon SSD en premier,
> pour le boot.
>
> J'ai tenté, une fois connecté sur le Mint du disque SATA, de forcer
> l'installation de grub sur le SSD, sans succès :
>
> ( Correspond à la partition du linux mint sur le disque SSD )
> sudo grub-install /dev/nvme0n1p5
> Installation pour la plate-forme i386-pc.
> grub-install : attention : Le système de fichiers « ext2 » ne prend pas en 
> charge l'embarquage.
> grub-install : erreur : l'embarquage est impossible, il est pourtant 
> nécessaire pour les installations interdisques.
> sudo grub-install /dev/nvme0n1
> Installation pour la plate-forme i386-pc.
> grub-install : attention : cette étiquette de partition GPT ne contient pas 
> de partition d'amorçage BIOS ; l'embarquage ne sera pas possible.
> grub-install : erreur : l'embarquage est impossible, il est pourtant 
> nécessaire pour les installations interdisques.

Bon, j'avance, je me dis, tant qu'à faire, je vais tenter la même
commande, mais, depuis le linux mint du SSD.
Je me connecte donc au Linux Mint du SSD ( /dev/nvme0n1p5  ) et je lance
depuis le terminal : sudo grub-install /dev/nvme0n1p5

Cette fois, pas de message d'erreur.
Étrange non ? Je suis logué sur le système qui tourne sur la partition,
et, j'arrive à écrire dessus, pour le Grub ?
Je reboot, et, je vais voir dans le Bios. Surprise, j'ai une nouvelle
invite, Linux Mint SSD, que je vais positionner en premier.
Je reboot, et, j'ai immédiatement le menu du grub ( Exactement le même
que celui que j'avais avec le Mint du disque SATA, mais, je suppose que
c'est normal. )

Si je ne me trompe pas, c'est bien le SSD cette fois, qui lance le grub.

Par contre, un problème persiste, j'ai toujours les deux lignes,
identiques, dans le Bios, concernant DEBIAN SSD.
En gros, j'ai deux entrées Debian, qui ne correspondent plus à rien.

Si cela apparait dans le Bios dans les choix de démarrage, c'est qu'il
s'agit donc de la MBR ?
J'aimerais bien me débarrasser de ses deux lignes, avant de continuer à
bidouiller.

Re: Debian 10.2 ne démarre pas


> ... soit, je tombe sur un écran grub, noir, avec un petit message et la ligne 
> grub >
>
> Le message :
> Minimal BASH-like editing is supported. For the first word, TAB lists 
> possible command completions. Anywhere else TAB lists possible device or file 
> completions.
> grub>_

Comme dit, ce message est affiché si je positionne mon SSD en premier,
pour le boot.

J'ai tenté, une fois connecté sur le Mint du disque SATA, de forcer
l'installation de grub sur le SSD, sans succès :

( Correspond à la partition du linux mint sur le disque SSD )
sudo grub-install /dev/nvme0n1p5
Installation pour la plate-forme i386-pc.
grub-install : attention : Le système de fichiers « ext2 » ne prend pas en 
charge l'embarquage.
grub-install : erreur : l'embarquage est impossible, il est pourtant nécessaire 
pour les installations interdisques.

sudo grub-install /dev/nvme0n1
Installation pour la plate-forme i386-pc.
grub-install : attention : cette étiquette de partition GPT ne contient pas de 
partition d'amorçage BIOS ; l'embarquage ne sera pas possible.
grub-install : erreur : l'embarquage est impossible, il est pourtant nécessaire 
pour les installations interdisques.

Gnucash broken after Update

2019-12-16 Thread Markus Grunwald

Hi,

a few days ago, I ran an apt update of my debian/desting machine and got
a new gnucash version. Apt DID tell me that there was something to do to
keep gnucash working. I had no time to do that, then, but I was used to
getting the instructions per e-mail. But at the time my e-mail setup was
broken and I didn't notice. Bummer.

Now I need to use gnucash and online banking is completely broken. I
searched everywhere, found the hint in
/usr/share/doc/aqbanking-tools/README.keyfile-update, but that didn't
help...

I /think/ the message had something to do with moved configuration files
for gnucash, but am not sure.

Do you have any hint for me? I urgendly need gnucash for my homebanking...

TIA,
-- 
Markus Grunwald
https://www.the-grue.de/~markus/markus_grunwald.gpg



signature.asc
Description: OpenPGP digital signature

Re: Macbook Post-Installation Issue

2019-12-16 Thread Dan Ritter

Dr. Jason Amerson wrote: 
> Dan,
> 
> I cannot login to my desktop. I am just presented with the Debian GNU/Linux 
> 10 tty1.
> 
> 
> Jason
> 
> 
> On 12/16/2019 12:04:09 PM, Dan Ritter  wrote:
> Dr. Jason Amerson wrote:
> > Hello,
> >
> > Me again. Different computer with a different problem. I may ask about 
> > other computers later. I am in the process of migrating my laptops from 
> > Windows 10 to Debian. This computer is a Macbook Pro. I installed Debian 
> > without errors, not even network errors like my other computer. I rebooted 
> > the computer and I was taken to a grub screen where I can select ???Debian 
> > GNU/Linux??? or ???Advanced Options for Debian GNU/Linux.??? I chose the 
> > first option. Then I was taken to a tty1 prompt for me to login. I know how 
> > to login into the shell and issue commands, I just do not know what to do 
> > at this point. This is something that I have not had happen before. I just 
> > would like to login to my KDE desktop.
> >
> 
> You've probably not installed kde.
> 
> Log in. Gain root privileges via su or sudo. apt install kde and
> an x display manager.
> 
> You should be happy after that.
> 

Don't top post here.

Always continue conversations on the mailing list, not in
private, unless someone asks you to take it private. That way,
other people get the benefit (and other people can help).

Nobody's impressed by a doctoral degree here, whether it be
MD or Ph.D. or JD.

You said "I know how to login into the shell and issue
commands"; and I told you to do that, and then what to do
afterwards in order to install KDE.

Where it says login: give your username.
Where it says password: give your password.

You are now in a shell.

Gain root privileges either by typing
su -
(and give the root password)
or
sudo -s
(and give your own password)

Now you have root privileges.

type
apt install kde-full
to install KDE.

Re: Debian 10.2 ne démarre pas



Le 16/12/2019 à 17:05, G2PC a écrit :
> Le 16/12/2019 à 15:30, Jo Engo a écrit :
>> Le Sun, 15 Dec 2019 10:20:01 +0100, didier.gaumet a Ã©critÂ :
>>
>>
>>> - ça te dit de vérifier /var/log/Xorg.0.log pour plus de détails:
>>> l'as-tu fait? peut-être y trouveras-tu d'autres indices...
>> Quand il y a le curseur qui clignote que se passe-t-il quand tu (pardon 
>> Didier, je m'adresse à g2pc) tapes Ctrl+Alt+Fn (1≤n≤6) as-tu accès alors 
>> à un terminal virtuel (getty)) Tu peux partir de là, essayer en peone, 
>> (pas en root) 'startx', ou en root 'X'.
> Excellente question mais comme dit, j'ai finalement installé Linux Mint.
>
> Ce que je peux dire pour le moment, c'est que j'ai aussi testé une
> Debian Live et même soucis d'écran noir.
>
> Maintenant que Linux Mint est installé sur le premier SSD, je me rend
> compte qu'en faisant update grub, c'est l'ancienne Mint sur le disque
> SATA qui a prit le relais pour le grub ( heu, oui, j'ai installé semble
> t'il plusieurs grub. Aille. )
>
> Autre chose, dans le bios, lors du choix des séquences de démarrage, je
> trouve toujours encore 2 lignes mentionnant Debian pour le SSD. Hors, si
> je les utilises, j'ai soit une erreur typique de UEFI et une alerte de
> sécurité qui propose d'aller dans le BIOS pour désactiver UEFI, soit, je
> tombe sur un écran grub, noir, avec un petit message et la ligne grub >
>
> De ce fait, pour le moment, je suis " bloqué " dans une situation
> fonctionnelle en utilisant le grub du disque SATA, mais, qui ne me
> semble pas être optimisée correctement.

... soit, je
tombe sur un écran grub, noir, avec un petit message et la ligne grub >

Le message :
Minimal BASH-like editing is supported. For the first word, TAB lists possible 
command completions. Anywhere else TAB lists possible device or file 
completions.
grub>_

Re: Macbook Post-Installation Issue

2019-12-16 Thread Dan Ritter

Dr. Jason Amerson wrote: 
> Hello,
> 
> Me again. Different computer with a different problem. I may ask about other 
> computers later. I am in the process of migrating my laptops from Windows 10 
> to Debian. This computer is a Macbook Pro. I installed Debian without errors, 
> not even network errors like my other computer. I rebooted the computer and I 
> was taken to a grub screen where I can select ???Debian GNU/Linux??? or 
> ???Advanced Options for Debian GNU/Linux.??? I chose the first option. Then I 
> was taken to a tty1 prompt for me to login. I know how to login into the 
> shell and issue commands, I just do not know what to do at this point. This 
> is something that I have not had happen before. I just would like to login to 
> my KDE desktop.
> 

You've probably not installed kde.

Log in. Gain root privileges via su or sudo. apt install kde and
an x display manager.

You should be happy after that.

-dsr-

Macbook Post-Installation Issue

2019-12-16 Thread Dr. Jason Amerson

Hello,

Me again. Different computer with a different problem. I may ask about other 
computers later. I am in the process of migrating my laptops from Windows 10 to 
Debian. This computer is a Macbook Pro. I installed Debian without errors, not 
even network errors like my other computer. I rebooted the computer and I was 
taken to a grub screen where I can select “Debian GNU/Linux” or “Advanced 
Options for Debian GNU/Linux.” I chose the first option. Then I was taken to a 
tty1 prompt for me to login. I know how to login into the shell and issue 
commands, I just do not know what to do at this point. This is something that I 
have not had happen before. I just would like to login to my KDE desktop.

Jason

Re: apparent change in hostnames on LAN without admin intervention

On Mon 16 Dec 2019 at 10:53:02 (-0500), Jape Person wrote:
> On 12/16/19 12:42 AM, David Wright wrote:
> > On Sat 14 Dec 2019 at 13:49:25 (-0500), Jape Person wrote:
> > > On 12/14/19 1:24 AM, john doe wrote:
> ...
> > > > The file '/etc/resolv.conf' should let you know what TLD is sent from
> > > > the DHCP server.
> > > > 
> > > > Debian shouldn't modify your configuration files '/etc' without your 
> > > > nolage.
> > 
> > Depending on the packages chosen, /etc/resolv.conf is one file in /etc
> > that is modified by Debian. The resolvconf package lists 23 other
> > programs that it is designed to adjudicate between, for want of a
> > better term.
> > 
> ...
> 
> That has been my understanding, and it's why I never edit /etc/resolv.conf 
> myself.
> 
> > > > Note that the TLD '.lan' is sometime used.
> > 
> > That's another choice, like .local, that could always be issued as a
> > real TLD at some point in the future.
> > 
> > > > 1)  
> > > > https://www.xfinity.com/support/articles/list-of-approved-cable-modems
> > > 
> > > I'm using my own router behind the modem provided by the ISP. I've
> > > never used a router provided by an ISP for controlling my network.
> > > 
> > > I'm using a Luxul XWR-1750 which has been kept on the latest firmware
> > > available. Last upgrade was done early this year, long before the
> > > noted change in names.
> > > 
> > > The router is set to provide static IP addresses and has the names of
> > > each of the systems associated with their MAC Addresses and IP
> > > Addresses.
> > 
> > Can you just clarify this? My router provides static IP addresses on
> > the basis of the MAC addresses, all the information being typed in¹
> > by me. It also lists the names of the other hosts, but only because
> > those hosts told it their names. IOW the router (cheap, $35) doesn't
> > issue hostnames, nor provide a DNS service itself. It also neither
> > knows nor cares what the domain name of the network is.
> > 
> > How much of this is the same on the router in your network?
> > 
> > ¹ actually, of course, it deduces all but the last number in the
> > dotted quad.
> 
> Yes, it's my understanding that my router does provide DNS on the
> local network and will provide the 208.67.222.222, 208.67.220.220
> OpenDNS servers or whatever the ISP provides for DNS servers,
> depending upon entries made in its setup pages. I do not think that it
> actually issues the hostnames, but it does detect whatever hostnames
> the devices provide and shows them associated with the IP addresses
> its DHCP server issues in a table. Do you think that I'm
> misunderstanding the arrangement? Could well be. I have ASSumed that
> it worked this way from the appearance of the tables in the setup
> software.
> 
> The software running the router is licensed under Luxul Open Source Code for 
> Programmers (GPL).

Others will have to comment on the functionality provided by this
software as I'm not familiar with it.

But a table of names doesn't convince me that your router is providing
a DNS service (or a domain name). My router maintains a list of names,
but they're not strictly hostnames unless I edit them to be so. For
example, when we bought our last Roku¹, it told the router it was
called "ROKU PREMIEREPLUS - 964" which I edited to "rokupw²", the name
by which I can ping it if I want to know whether it's powered up.

Try typing
$ nslookup chip-nuc 192.168.1.1
where 192.168.1.1 is the IP address for *your* router.

¹ a TV streamer. ² and "rokupe" for its ethernet interface.

Cheers,
David.

Re: unstable: directory pulse in root directory : /pulse where from?

On Sat, Dec 14, 2019 at 10:04:34AM +0100, Jörg-Volker Peetz wrote:
> $ dpkg -S /pulse
> dpkg-query: no path found matching pattern /pulse
> 
> fails to give any clue.
> The directory is generated at boot-time. But I wasn't able to find any hint in
> systemd or udev conf-files.

Well, the first thing I would try would be "grep -r /pulse /etc".
And if that fails, "grep -r /pulse /lib/systemd".

If *those* both fail... well, I might be crazy enough to try removing
the offending directory, doing "chattr +i /", then rebooting, and seeing
who complains when they can't create the /pulse directory.  Only on a
system where I have local hardware access, of course -- not a remote.

Do not forget to remove the immutable bit after your test is complete.

And as a wise reader already said, it's probably pulseaudio.  Meaning,
you might be able to test without rebooting, by stopping pulseaudio,
removing the directory, and starting pulseaudio, to see if it gets
recreated.

Re: apparent change in hostnames on LAN without admin intervention

On Mon 16 Dec 2019 at 12:03:58 (+0530), tv.deb...@googlemail.com wrote:
> I am not the OP, but questions seems directed to me, see inline answers.

Yes, it's interesting to see what people's configurations are when
they make suggestions, because that affects whether they apply in
other cases (including mine).

> On 16/12/2019 11:12, David Wright wrote:
> > On Sun 15 Dec 2019 at 11:49:55 (+0530), tv.deb...@googlemail.com wrote:
> > > On 15/12/2019 00:35, Jape Person wrote:
> > > > On 12/14/19 3:56 AM, Andrei POPESCU wrote:
> > > > > On Vi, 13 dec 19, 19:33:51, Jape Person wrote:
> > > > > > Hi folks. Did I miss something?
> > > > > > 
> > > > > > I've had 3 Sid/testing systems running on the same LAN behind the 
> > > > > > same
> > > > > > router for just shy of 3 years. Their static IP addresses
> > > > > > have always been
> > > > > > issued by the DHCP server on the router. Everything has
> > > > > > been copacetic among
> > > > > > the systems, with local and outside name resolution
> > > > > > working with no issue.
> > > > > > 
> > > > > > A little over a week ago the systems stopped being able to
> > > > > > access each other
> > > > > > by name. No changes were made in the settings or firmware
> > > > > > of the router or
> > > > > > of the local network settings on the systems.
> > > > > > 
> > > > > > I discovered that all of the hostnames had changed from 
> > > > > > xx.local to
> > > > > > xx. I've tried to determine the cause of this alteration in the
> > > > > > hostnames on the LAN.
> > > > > 
> > > > > Please provide more info on this, specifically where / how are the
> > > > > hostnames configured and where / how did you discover they changed.
> > > > > 
> > > > > Do note that .local is typically used by mDNS and in my understanding 
> > > > > it
> > > > > should not be used with a DNS server.
> > > > > 
> > > > > https://en.wikipedia.org/wiki/.local
> > > > 
> > > > The hostnames and local domain name were used during installation.
> > > > 
> > > > The static DHCP addresses are issued by a Luxul XWR-1750 router
> > > > which associates the hostnames with the MAC and IP addresses.
> > > > 
> > > > Contents of /etc/resolv.conf:
> > > > 
> > > > search local
> > > > nameserver 208.67.220.220
> > > > 
> > > > I discovered the change a few days ago when I was doing my daily
> > > > check for updates by using SSH to connect to two of the systems. I
> > > > received the following response to the connection command:
> > > > 
> > > > ssh: Could not resolve hostname chip-nuc.local: Name or service not 
> > > > known
> > > > 
> > > > I checked to make sure I could connect to everything by IP
> > > > address, and I checked DNS on the outside world. Everything looked
> > > > okay.
> > > > 
> > > > On a hunch I tried omitting the .local from the connection
> > > > command, and it work on each client.
> > > > 
> > > > I figured any time the name of a client changes without deliberate
> > > > action on the part of the network admin (however incompetent he
> > > > may be), that could be a security issue. That's why I asked here.
> > > 
> > > Hi, I am running a very similar setup, also on Sid/Testing (updated
> > > daily), and didn't notice any change. My local domain is not ".local"
> > > or ".home", it is custom.
> > 
> > That might be a reason for no change to have occurred.
> > 
> > Just out of curiosity, is your custom name registered or just made up?
> 
> Made up, it exists only on my LAN.

OK. so that's the same as me.

> > > My resolv.conf looks like yours (modulo the domain name), I have an
> > > additional nameserver line for my router address. My router only
> > > resolves names for the local network, public DNS is resolved though a
> > > VPN.
> > > 
> > > My hosts file is just standard :
> > > 
> > >  
> > > 
> > > one line per host on the network, the router has the same hosts file,
> > > the IP are reserved by the router DHCP and associated with (static
> > > spoofed) MAC addresses. Routers are running on Asuswrt-Merlin and
> > > openWRT (one is AP mode only).
> > 
> > Again, curious, why do you maintain hosts files on each host? As you
> > resolve that other hosts on your network by DNS at the router, I
> > would have expected all your hosts files to look like:
> > 
> > 127.0.0.1   localhost
> > 127.0.1.1   foo.custom   foo
> > 
> > for host foo.
> > 
> 
> One of the PC is serving various services to the LAN, some bypassing
> the router for load/performances reason,

Fair enough. (I do that between hosts using IPv6 over Cat5, and have
been scolded here for it.)

> this PC is carrying an up to
> date version of the hosts file.

But does it need to? If your router runs a DNS server (you say it
does), it can provide that (DNS) service to the PC that's providing
the various other services.

> It's not one hosts file on every
> machines on the network, it's one hosts file with every machines on
> the LAN registered in it on one of the node on the LAN.

… which

Re: Debian 10.2 ne démarre pas



Le 16/12/2019 à 15:30, Jo Engo a écrit :
> Le Sun, 15 Dec 2019 10:20:01 +0100, didier.gaumet a Ã©critÂ :
>
>
>> - ça te dit de vérifier /var/log/Xorg.0.log pour plus de détails:
>> l'as-tu fait? peut-être y trouveras-tu d'autres indices...
> Quand il y a le curseur qui clignote que se passe-t-il quand tu (pardon 
> Didier, je m'adresse à g2pc) tapes Ctrl+Alt+Fn (1≤n≤6) as-tu accès alors 
> à un terminal virtuel (getty)) Tu peux partir de là, essayer en peone, 
> (pas en root) 'startx', ou en root 'X'.

Excellente question mais comme dit, j'ai finalement installé Linux Mint.

Ce que je peux dire pour le moment, c'est que j'ai aussi testé une
Debian Live et même soucis d'écran noir.

Maintenant que Linux Mint est installé sur le premier SSD, je me rend
compte qu'en faisant update grub, c'est l'ancienne Mint sur le disque
SATA qui a prit le relais pour le grub ( heu, oui, j'ai installé semble
t'il plusieurs grub. Aille. )

Autre chose, dans le bios, lors du choix des séquences de démarrage, je
trouve toujours encore 2 lignes mentionnant Debian pour le SSD. Hors, si
je les utilises, j'ai soit une erreur typique de UEFI et une alerte de
sécurité qui propose d'aller dans le BIOS pour désactiver UEFI, soit, je
tombe sur un écran grub, noir, avec un petit message et la ligne grub >

De ce fait, pour le moment, je suis " bloqué " dans une situation
fonctionnelle en utilisant le grub du disque SATA, mais, qui ne me
semble pas être optimisée correctement.

Re: looking for a replacement for debian since systemd

2019-12-16 Thread Alberto Luaces

"0...@caiway.net" writes:

> But I do like systemd-container very much.

What is that thing? Another name for systemd-nspawn?

-- 
Alberto

New Install Boots to Grub

2019-12-16 Thread Dr. Jason Amerson

Hello,

I installed Debian 10.2.0 from a USB drive and the installation finished 
without errors. The only thing that happened during install is that it was 
unable to setup the network. Anyways, I removed the USB drive and rebooted the 
computer. It then booted into grub. There was a message telling me I can press 
TAB to get a list of commands but I know nothing about grub and I do not know 
how to fix the computer so that it boots into Debian. Will someone please help 
me with this?


Thank you,

Jason

Re: apparent change in hostnames on LAN without admin intervention


On 12/16/19 12:42 AM, David Wright wrote:

On Sat 14 Dec 2019 at 13:49:25 (-0500), Jape Person wrote:

On 12/14/19 1:24 AM, john doe wrote:

...

The file '/etc/resolv.conf' should let you know what TLD is sent from
the DHCP server.

Debian shouldn't modify your configuration files '/etc' without your nolage.


Depending on the packages chosen, /etc/resolv.conf is one file in /etc
that is modified by Debian. The resolvconf package lists 23 other
programs that it is designed to adjudicate between, for want of a
better term.


...

That has been my understanding, and it's why I never edit /etc/resolv.conf 
myself.


Note that the TLD '.lan' is sometime used.


That's another choice, like .local, that could always be issued as a
real TLD at some point in the future.


1)  https://www.xfinity.com/support/articles/list-of-approved-cable-modems


I'm using my own router behind the modem provided by the ISP. I've
never used a router provided by an ISP for controlling my network.

I'm using a Luxul XWR-1750 which has been kept on the latest firmware
available. Last upgrade was done early this year, long before the
noted change in names.

The router is set to provide static IP addresses and has the names of
each of the systems associated with their MAC Addresses and IP
Addresses.


Can you just clarify this? My router provides static IP addresses on
the basis of the MAC addresses, all the information being typed in¹
by me. It also lists the names of the other hosts, but only because
those hosts told it their names. IOW the router (cheap, $35) doesn't
issue hostnames, nor provide a DNS service itself. It also neither
knows nor cares what the domain name of the network is.

How much of this is the same on the router in your network?

¹ actually, of course, it deduces all but the last number in the
dotted quad.

Cheers,
David.



Yes, it's my understanding that my router does provide DNS on the local network and will provide the 
208.67.222.222, 208.67.220.220 OpenDNS servers or whatever the ISP provides for DNS servers, 
depending upon entries made in its setup pages. I do not think that it actually issues the 
hostnames, but it does detect whatever hostnames the devices provide and shows them associated with 
the IP addresses its DHCP server issues in a table. Do you think that I'm misunderstanding the 
arrangement? Could well be. I have ASSumed that it worked this way from the appearance of the tables 
in the setup software.


The software running the router is licensed under Luxul Open Source Code for 
Programmers (GPL).

Thanks, David.

JP

Re: User Forgets Aliases

On Mon, Dec 16, 2019 at 09:30:08AM -0500, Stephen P. Molnar wrote:
> As a matter of fact, there was no .bash_profile.
> 
> I created on and transferred all of my alias statement to that and not is
> fine.

I believe you meant to say "now is fine".  But your typo is literally
correct: it is *NOT* fine.  That is not how you do it.

https://mywiki.wooledge.org/DotFiles
https://wiki.debian.org/DotFiles

You put aliases in ~/.bashrc so that they are read by NON-LOGIN SHELLS
such as the one you get when you open an xterm from a window manager,
and that xterm is NOT invoked with the -ls option.

You source .bashc from your profile so that you ALSO get your aliases
when you run a LOGIN SHELL, such as the one you get when you ssh into
the system, or login on a text console, or open an xterm from a window
manager with the -ls option.

On top of that, you probably already had a ~/.profile, and now that you've
created a ~/.bash_profile, your ~/.profile is no longer used.  This
will probably be a new, separate problem that you have just created for
yourself, and simply not noticed yet.

Remove your ~/.bash_profile.

Put all your LOGIN SHELL STUFF (environment variables and so on)
in ~/.profile.

Make sure ~/.profile dots in ~/.bashrc.

Put all your ALIASES, FUNCTIONS, SHOPTS AND SO FORTH in ~/.bashrc.

Read the two wiki pages.  Or at least one of them.  The Debian one is
older, so if you only read one of them, it should probably be the
first one.

Tell us HOW. YOU. LOG. IN.  This is no longer optional.  Stop fooling
around.  Stop being an obstinate blockhead.

Do you not understand the QUESTION?  Here are some possible answers to
it:

"I login on a text console, and then I run startx."

"I login with the GNOME graphical thingy.  It says it runs a Wayland."

"I login with the graphical thingy and the default is GNOME Wayland,
but I have problems with that, so I told it use to use GNOME X11."

"I installed XFCE and I login with the graphical thing, I think it's
called light something."

"It's a remote server.  I login with ssh."

And so on.

These things MATTER.

You don't have to be an EXPERT, but you do have to demonstrate a tiny
modicum of AWARENESS.

Re: Debian 10.2 ne démarre pas

2019-12-16 Thread Jo Engo

Le Sun, 15 Dec 2019 10:20:01 +0100, didier.gaumet a Ã©critÂ :


> - ça te dit de vérifier /var/log/Xorg.0.log pour plus de détails:
> l'as-tu fait? peut-être y trouveras-tu d'autres indices...

Quand il y a le curseur qui clignote que se passe-t-il quand tu (pardon 
Didier, je m'adresse à g2pc) tapes Ctrl+Alt+Fn (1≤n≤6) as-tu accès alors 
à un terminal virtuel (getty)) Tu peux partir de là, essayer en peone, 
(pas en root) 'startx', ou en root 'X'.

Re: User Forgets Aliases

2019-12-16 Thread Stephen P. Molnar





On 12/16/2019 08:30 AM, Greg Wooledge wrote:

On Sat, Dec 14, 2019 at 04:27:39AM -0500, Stephen P. Molnar wrote:

I find that I have to source the .bashrc use the aliases.

My guess is that you:
1) created a ~/.bash_profile and forgot to tell it to source ~/.bashrc; or
2) altered your ~/.profile in such a way that it no longer sources
~/.bashrc; or
3) somehow are no longer using bash as your shell when you launch a
terminal, or when you login to a shell session.

In any case, if your shell is bash, your PROFILE (which is one of the
three files ~/.bash_profile or ~/.bash_login or ~/.profile) must source
or dot in ~/.bashrc.

If none of these shotgun guesses match your problem, then please provide
details.  What version of Debian, how do you login, how do you get to an
interactive shell.




As a matter of fact, there was no .bash_profile.

I created on and transferred all of my alias statement to that and not 
is fine.


--
Stephen P. Molnar, Ph.D.
www.molecular-modeling.net
614.312.7528 (c)
Skype:  smolnar1

Re: how to have a common prompt in bash and guake so I can view date and time as part of prompt ?

On Fri, Dec 13, 2019 at 04:50:18PM -0600, David Wright wrote:
> > PS1='\u@\h $(date +"%d %b %Y %H:%M:%S") :\w\$ '
> 
> Could \D{format} not do that?

Oh, good catch.  I've... never used that before. ;-)  I scanned the
PROMPTING section of the man page too quickly and only saw
the \t \T \@ \A parts.

PS1='\u@\h \D{%d %b %Y %H:%M:%S} :\w\$ '

Re: apparent change in hostnames on LAN without admin intervention

2019-12-16 Thread John Hasler

John Doe writes:
> In the above example 'try' is the hostname while 'example.com' is the
> domainname. From other e-mail, it looks like your DHCP server was
> sending as 'local' as domainname.

Your MTA should be rewriting headers to use your external email domain.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: User Forgets Aliases

On Sat, Dec 14, 2019 at 04:27:39AM -0500, Stephen P. Molnar wrote:
> I find that I have to source the .bashrc use the aliases.

My guess is that you:
1) created a ~/.bash_profile and forgot to tell it to source ~/.bashrc; or
2) altered your ~/.profile in such a way that it no longer sources
   ~/.bashrc; or
3) somehow are no longer using bash as your shell when you launch a
   terminal, or when you login to a shell session.

In any case, if your shell is bash, your PROFILE (which is one of the
three files ~/.bash_profile or ~/.bash_login or ~/.profile) must source
or dot in ~/.bashrc.

If none of these shotgun guesses match your problem, then please provide
details.  What version of Debian, how do you login, how do you get to an
interactive shell.

Re: Re : Re: Erreur d'URL pour la liste debian user french