Re: text editors

[Teemu Likonen]

Ben Finney [2019-03-26 13:28:56+11] wrote:

> If by “protect” you mean “prevent editing these lines but not others”,
> no I think that's not a feature of any editor I know.

Emacs has that feature. See the "read-only" text property in the
following manual (info) page:

(elisp) Special Properties

https://www.gnu.org/software/emacs/manual/html_node/elisp/Special-Properties.html#Special-Properties

In my other message in this thread I showed quick example functions for
(1) making a buffer area read only and (2) removing read only
properties. If someone wants to the functions could be made fancier, for
example with a button that removes the read only status.

-- 
/// Teemu Likonen   - .-..    //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///


signature.asc
Description: PGP signature

need sources.list example for lan with approx-server

[rlharris]

Would someone kindly point me to (or email me) an example sources.list 
for machines running Debian-9 (Stretch) in a LAN with an approx server?


Following the installation of Stretch on a machine in the LAN, I used 
Synaptic to add packages, but pressing the RELOAD button of Synaptic 
produces the following error message:



http://192.168.1.40:/debian/dists/stretch-updates/InRelease: The 
key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is 
not readable by user '_apt' executing 
apt-key.http://deb.debian.org/debian-security/dists/stretch/updates/InRelease: 
The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file 
is not readable by user '_apt' executing 
apt-key.http://192.168.1.40:/debian/dists/stretch/Release.gpg: The 
key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is 
not readable by user '_apt' executing apt-key.Failed to fetch 
http://192.168.1.40:/debian/dists/stretch-updates/main/source/Sources.xz

Hash Sum mismatch



The approx server is running a recent installation of Stretch, and was 
used as a mirror for installation of the machine which now is generating 
the error message.  I then attempted to edit the sources.list created by 
the installer on the complaining machine, and in the process I overwrote 
the version left by the installer.

Re: text editors

[Ben Finney]

mick crane  writes:

> Is there any text editor, preferably in a terminal that has the
> facility to protect lines in the document, not the document itself ?

If by “protect” you mean “prevent editing these lines but not others”,
no I think that's not a feature of any editor I know.

You can achieve some protection by temporarily *hiding* lines you're not
wanting to edit.

Vim has “folding” (hiding a set of lines).

Emacs has “narrow&"9 to see nothing *but* a specific range of lines.

> I've got 2 blocks of "code" that look similar and I keep editing the
> wrong one and then it doesn't work.

I would use Emacs “narrow” commands for that; quickly narrow the focus
of the editor to only show me the area I'm meaning to edit, then easily
widen the range when I need to.

-- 
 \  “Ridicule is the only weapon which can be used against |
  `\   unintelligible propositions.” —Thomas Jefferson, 1816-07-30 |
_o__)  |
Ben Finney

Re: Q. about Tinkering with Debian Source Code

[Roberto C . Sánchez]

On Mon, Mar 25, 2019 at 04:49:15PM -0400, Stefan Monnier wrote:
> > When I use "apt source sl" (from sid, into its own directory) and compare
> > that tree (?) with what I get if I download via what that suggests (git
> > clone https://salsa.debian.org/debian/sl.git) (into its own directory), I
> > notice that the Makefile in the Debian version is slightly
> > more complex.
> 
> I believe the difference should be that "apt source sl" will have
> applied the patches that you can find in the `debian/patches`
> subdirectory of the https://salsa.debian.org/debian/sl.git version.
> 
Apart from that, depending on how active development on a given package
is, the code checked out by debcheckout may differ from what is
currently in Debian.

Some reasons for this might include:

- The maintainer has made new commits that have not yet been uploaded to
  unstable
- You are running stable and debcheckout gets an old repository URL that
  is no longer in use (in which case you get outdated code)

Regards,

-Roberto

-- 
Roberto C. Sánchez

Instalador 'Network install' não consegue se reconectar

[Robson]

Olá,

Gostaria de sugerir uma melhoria para o futuro instalador da imagem
"minimal CD", e reportar um pequeno problema:

Sugestão:
Seria interessante adicionar um botão 'Pause' para a tela de download dos
arquivos (Tela de título 'Selecionar e Instalar software'), pois se o
usuário precisar acessar a internet, o download feito pelo instalador pode
prejudicar o acesso do usuário, usando outro dispositivo qualquer, como
smartphone.

Problema:
Quando o instalador está sendo executado em um portátil (Netbook) e o
usuário desativar a placa de rede wifi (por exemplo com as teclas Fn+F3)
para interromper o uso de dados, seja pelo motivo que for, depois de o
usuário ativar novamente a placa de rede wifi, o instalador não consegue
recomeçar de onde parou, é necessário voltar na etapa de configuração de
rede, mesmo que todos os dados (como senha do roteador wifi) já estejam
armazenados no instalador. Ao que parece o buffer de downloads é mantido,
mas o usuário precisa repassar as etapas anteriores.

Obrigado.


Livre
de vírus. www.avast.com
.
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Re: Command DD

[Stefan Monnier]

> No tengo idea de como hacerlo.
>
> seria algo asi como:
>
> dd if=/dev/sda | pv | dd of=/home/knoppix/disco/imgwindows7x.img 
> count=43010047

Al parecer sí tenés idea: me parece correcto.
En cualquier caso, podés probarlo, no le va hacer mal a nada.


Stefan

Command DD

[Eriel Perez]

Hola amigos.

Tengo un disco duro de 120 GB.

El comando fdisk -l /dev/sda me da como resultado:

fdisk -l /dev/sda
Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x9639c36a

Device Boot  Start  End  Sectors  Size Id Type
/dev/sda1  *  2048   206847   204800  100M  7 HPFS/NTFS/exFAT
/dev/sda2   206848 43010047 42803200 20.4G  7 HPFS/NTFS/exFAT

Hasta aqui tengo dos particiones. Por cierto en el disco esta instalado
windows 7. Y ahi las dos particiones la del boot de windos mas 1 de 20 GB.
Por supuesto que hay una parte que esta como espacio libre. No
particionado. Esa no la quiero.

Ahora con el comando DD quiero extraer las particiones de boot mas esa de
20.

No tengo idea de como hacerlo.

seria algo asi como:

dd if=/dev/sda | pv | dd of=/home/knoppix/disco/imgwindows7x.img
count=43010047

?

Espero me puedan ayudar.

Gracias.

Comando DD

[Eriel Perez]

Hola amigos.

Tengo un disco duro de 120 GB.

El comando fdisk -l /dev/sda me da como resultado:

fdisk -l /dev/sda
Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x9639c36a

Device Boot  Start  End  Sectors  Size Id Type
/dev/sda1  *  2048   206847   204800  100M  7 HPFS/NTFS/exFAT
/dev/sda2   206848 43010047 42803200 20.4G  7 HPFS/NTFS/exFAT

Hasta aqui tengo dos particiones. Por cierto en el disco esta instalado
windows 7. Y ahi las dos particiones la del boot de windos mas 1 de 20 GB.
Por supuesto que hay una parte que esta como espacio libre. No
particionado. Esa no la quiero.

Ahora con el comando DD quiero extraer las particiones de boot mas esa de
20.

No tengo idea de como hacerlo.

seria algo asi como:

dd if=/dev/sda | pv | dd of=/home/knoppix/disco/imgwindows7x.img
count=43010047

?

Espero me puedan ayudar.

Gracias.

Re: relocation error: /lib/x86_64-linux-gnu/libnss_files.so.2: symbol __libc_readline_unlocked version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

[stupidate]

I had the same issue, mariadb will actually start if you do so manually, what 
fails is the command `install` from coreutils, try to upgrade that package.

On Monday, December 3, 2018 at 1:20:04 AM UTC-8, Office onFocus wrote:
> Hi!
> 
> 
> How can I correctly report the following error?
> 
> 
> "relocation error: /lib/x86_64-linux-gnu/libnss_files.so.2: symbol 
> __libc_readline_unlocked version GLIBC_PRIVATE not defined in file libc.so.6 
> with link time reference"
> 
> 
> 
> 
> After the libc6:amd64 (2.27-8, 2.28-1) update, I can no longer start 
> databases on different servers. 
> 
> .. I neet libc6 >= 2.27 for apache2, ...
> 
> 
> For testing you can install stretch with mariadb 10-1 and then upgrade libc6 
> to 2.28-1 == sid 
> 
> 
> 
> 
> 
> root@rs33073:~# dpkg -l | grep mariadb-server
> ii  mariadb-server-10.1                                10.1.37-0+deb9u1       
>         amd64        MariaDB database server binaries
> ii  mariadb-server-core-10.1                           10.1.37-0+deb9u1       
>         amd64        MariaDB database core server files
> 
> 
> 
> root@rs33073:~# /etc/init.d/mysql restart
> [] Restarting mysql (via systemctl): mysql.serviceJob for mariadb.service 
> failed because the control process exited with error code.
> See "systemctl status mariadb.service" and "journalctl -xe" for details.
>  failed!
> 
> 
> 
> 
> Dec  3 09:24:26 rs33073 systemd[9747]: (systemd): relocation error: 
> /lib/x86_64-linux-gnu/libnss_files.so.2: symbol __libc_readline_unlocked 
> version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
> 
> 
> 
> root@rs33073:~# /lib/x86_64-linux-gnu/libc.so.6
> GNU C Library (Debian GLIBC 2.28-1) stable release version 2.28.
> Copyright (C) 2018 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.
> There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
> PARTICULAR PURPOSE.
> Compiled by GNU CC version 8.2.0.
> libc ABIs: UNIQUE IFUNC ABSOLUTE
> For bug reporting instructions, please see:
> .
> 
> 
> 
> 
> 
> 
> 
> 
> root@mysql57a:~# dpkg -l | grep mysql-server
> ii  mysql-server                                       5.7.24-1debian8        
>             amd64        MySQL Server meta package depending on latest version
> 
> 
> E not defined in file libc.so.6 with link time reference
> Nov 30 09:10:44 mysql57a mysql-systemd-start[12394]: (md-start): relocation 
> error: /lib/x86_64-linux-gnu/libnss_files.so.2: symbol 
> __libc_readline_unlocked version GLIBC_PRIVATE not defined in file libc.so.6 
> with link time reference
> 
> 
> 
> 
> 
> root@mysql57a:~# cat /etc/apt/preferences
> 
> Package: *
> Pin: release a=old-stable
> Pin-Priority: 500
> 
> 
> Package: *
> Pin: release a=testing
> Pin-Priority: 50
> 
> 
> Package: *
> Pin: release a=unstable
> Pin-Priority: 50
> 
> 
> Package: *
> Pin: release a=stable
> Pin-Priority: 50
> 
> 
> Package: apache2 apache2-bin apache2-data apache2-utils curl 
> fontconfig-config libapache2-mod-php7.2 libapache2-mod-php7.3 libapr1 
> libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap libargon2-0 libargon2-1 
> libbrotli1 libc-bin libc-l10n libc6 libcom-err2 libcomerr2 libcurl4 
> libfontconfig1 libgcrypt20 libgd3 libgdbm5 libgdbm6 libgpg-error0 
> libgssapi-krb5-2 libidn2-0 libjansson4 libk5crypto3 libkrb5-3 libkrb5support0 
> libncurses6 libnghttp2-14 libpcre2-8-0 libpng16-16 libpsl5 libsodium23 
> libssh2-1 libssl1.1 libtinfo6 libunistring2 libwebp6 libzip4 linux-base 
> locales os-prober php php-bz2 php-common php-curl php-gd php-mbstring 
> php-mysql php-phpseclib php-xml php-zip php7.2 php7.2-bz2 php7.2-cli 
> php7.2-common php7.2-curl php7.2-gd php7.2-json php7.2-mbstring php7.2-mysql 
> php7.2-opcache php7.2-readline php7.2-xml php7.2-zip php7.3 php7.3-bz2 
> php7.3-cli php7.3-common php7.3-curl php7.3-gd php7.3-json php7.3-mbstring 
> php7.3-mysql php7.3-opcache php7.3-readline php7.3-xml php7.3-zip phpmyadmin 
> publicsuffix zlib1g libgpg-error-l10n libncurses5 libncursesw5 libtinfo5
> Pin: release a=unstable
> Pin-Priority: 600
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> best,
> 
> Daniel
> 
> -- 
> onFocus.at e.U. 
> 
> off...@onfocus.at

Re: text editors

[deloptes]

Étienne Mollier wrote:

> If I need some configuration, or a sort of shell functions
> library, this is something I would consider.

+1

Re: xorg opengl / intel integrated graphics problem

[tim]

So, apparently
apt remove --purge nvidia*
is not enough to clean the opengl mess nvidias drivers left. Manually removing
the files nvidia replaced and reinstalling xorg and mesa as described in
this answer did:
https://unix.stackexchange.com/a/339652

Thanks for your help

24. März 2019 23:34, t...@t8w.de schrieb:

> Hey,
> 
> due to a graphics card change in a few days, which will allow me to properly 
> use
> virtualization, I wanted to check a few things. First check, starting the pc 
> without
> the current dedicated graphics card, failed really unexpectedly, because the
> integrated graphics card of my intel processor was not able to load my desktop
> environment. I did not use this integrated card since I assembled my pc, got
> everything running and installed a dedicated graphics card - maybe the Nvidia
> drivers broke something in the meanwhile.
> 
> Anyway, trying to fix this, I've found no used drivers for the card and a 
> opengl
> error message in xorg.
> 
> lspci output and xorg logs: https://t8w.de/log.txt
> (my private server, plain text, no logging, tracking nor anything else ;) )
> 
> Installing, uninstalling, reinstalling several driver / mesa related packages
> did not help and neither did the handful of threads about the same or similar 
> issues,
> so I'd really appreciate any help.
> 
> Thanks

Re: Q. about Tinkering with Debian Source Code

[Stefan Monnier]

> When I use "apt source sl" (from sid, into its own directory) and compare
> that tree (?) with what I get if I download via what that suggests (git
> clone https://salsa.debian.org/debian/sl.git) (into its own directory), I
> notice that the Makefile in the Debian version is slightly
> more complex.

I believe the difference should be that "apt source sl" will have
applied the patches that you can find in the `debian/patches`
subdirectory of the https://salsa.debian.org/debian/sl.git version.


Stefan

Fwd: Upcoming stable point release (9.9)

[Juan Lavieri]

Para la información de la comunidad.


 Mensaje reenviado 
Asunto: Upcoming stable point release (9.9)
Resent-Date: Mon, 25 Mar 2019 20:21:15 + (UTC)
Resent-From: debian-secur...@lists.debian.org
Fecha: Mon, 25 Mar 2019 20:20:31 +
De: Adam D. Barratt 
Para: debian-rele...@lists.debian.org

Hi,

The next point release for "stretch" (9.9) is scheduled for Saturday,
April 27th. Processing of new uploads into stretch-proposed-updates
will be frozen during the preceding weekend.

Regards,

Adam


--
Errar es de humanos, pero es mas humano culpar a los demás

Re: mdadm started before disks are detected

[John Hasler]

> Please update your system, Debian 6.0 Squeeze is severely out of date
> and should NOT be used for any production systems and even less when
> connected to the public Internet.

It certainly should not be connected to the Internet but there is no
reason not to keep using it for off-line systems where it still works.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: text editors

[Étienne Mollier]

On 3/25/19 12:47 PM, rhkra...@gmail.com wrote:
> There are equivalent approaches in bash, but I forget them (in bash, it might
> be a little more convoluted, like an external / 3rd file that assembles a new
> file from the read-only and read / write files.

Good Day rhkramer,

Perhaps I missed some points, but wouldn't `.`, or `source`,
command do the trick, instead of building a script dynamically?

readonly.sh:
# Don't touch that!
PATH="/opt/thirparty/bin:$PATH"
CPATH="/opt/thirparty/include:$CPATH"
LD_LIBRARY_PATH="/opt/thirparty/lib:$LD_LIBRARY_PATH"
export PATH CPATH LD_LIBRARY_PATH

main.sh:
#! /bin/bash
set -e
# Loading environment from read only file
. readonly.sh
printf 'Using libraries in %s\n' "$LD_LIBRARY_PATH"
do_stuff_with_thirdparty_program

If I need some configuration, or a sort of shell functions
library, this is something I would consider.

Kind Regards,
-- 
Étienne Mollier 

All opinions are my own.

Re: XFCE probleem

[Paul van der Vlis]

Hallo Henk, en anderen,

Op 25-03-19 om 19:53 schreef henk van ballegooijen:
> 
> Op 25-03-19 om 14:12 schreef Paul van der Vlis:
>> Hallo,
>>
>> Ik probeer XFCE te installeren op een bestaande computer, maar er
>> verschijnt geen menubalk. Ook bij een nieuw aangemaakte user met lege
>> homedir verschijnt er geen menubalk (panel).
>>
>> Wel kan ik met mijn rechtermuisknop klikken op het bureaublad, dan zie
>> ik daar als onderste optie wel een menu.
>>
>> Iemand een idee wat er aan de hand is, of hoe dat panel te herstarten?
>> Het pakket purgen en weer opnieuw installeren helpt ook al niet.
>>
>> Wat me opvalt als ik "pstree" draai, is dat xfce4-panel draait als
>> subproces van systemd, niet van LightDM (dat is normaal).
>>
>> Groeten,
>> Paul
>>
> Dus het proces xfce4-panel draait en toch is er geen werkbalk te zien?

Ja. Op de "foute machine":
--
paul@laptopp:~/Bureaublad$ ps aux | grep xfce4-panel
paul  1783  0.0  0.2 190116 18084 ?S20:36   0:00 xfce4-panel
--

En op een andere machine waar XFCE goed draait (Debian testing):
-
root@server:~# ps aux | grep xfce4-panel
paul  6173  0.0  0.1 285640 32808 ?Sl   mrt21   0:05
xfce4-panel --display :0.0 --sm-client-id
2e6f45401-9361-4e58-97d9-eb200a5e81d1
--

> xfce4-panel herstarten doe je met "xfce4-panel -r"

Dit heeft geen effect, het proces houdt hetzelfde PID en er verschijnt
geen menu.

> "xfce4-panel -p" geeft het werkbalkvoorkeuren scherm.
> Misschien kun je van hier uit een extra werkbalk maken en kijken of die
> zichtbaar is.

Ik kan het voorkeurenscherm wel starten, een extra balk maken heeft
echter geen effect.

> Bij: "Instellingen > Sessie en Opstart > Sessie" moet xfce4-panel
> aanwezig zijn. Herstart-stijl: "meteen"

Dat staat er.

> Ik zou de opgeslagen sessies wissen en de lopende sessie (met werkbalk)
> opslaan.

Huidige lopende sessie heeft geen werkbalk...

> Hopelijk werkt het dan.

Nog niet...

> Wel vreemd is dat in "pstree" xfce4-panel als subproces van systemd
> draait en niet van lightdm.

Inderdaad, er is iets raars aan de hand.

Groeten,
Paul



-- 
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

Re: mdadm started before disks are detected

[Sven Hartge]

Mimiko  wrote:

> Linux 2.6.32-5-amd64 #1 SMP Tue May 13 16:34:35 UTC 2014 x86_64 GNU/Linux

Please update your system, Debian 6.0 Squeeze is severely out of date
and should NOT be used for any production systems and even less when
connected to the public Internet.

Grüße,
Sven

-- 
Sigmentation fault. Core dumped.

Re: XFCE probleem

[henk van ballegooijen]

Op 25-03-19 om 14:12 schreef Paul van der Vlis:

Hallo,

Ik probeer XFCE te installeren op een bestaande computer, maar er
verschijnt geen menubalk. Ook bij een nieuw aangemaakte user met lege
homedir verschijnt er geen menubalk (panel).

Wel kan ik met mijn rechtermuisknop klikken op het bureaublad, dan zie
ik daar als onderste optie wel een menu.

Iemand een idee wat er aan de hand is, of hoe dat panel te herstarten?
Het pakket purgen en weer opnieuw installeren helpt ook al niet.

Wat me opvalt als ik "pstree" draai, is dat xfce4-panel draait als
subproces van systemd, niet van LightDM (dat is normaal).

Groeten,
Paul


Dus het proces xfce4-panel draait en toch is er geen werkbalk te zien?

xfce4-panel herstarten doe je met "xfce4-panel -r"

"xfce4-panel -p" geeft het werkbalkvoorkeuren scherm.
Misschien kun je van hier uit een extra werkbalk maken en kijken of die 
zichtbaar is.


Bij: "Instellingen > Sessie en Opstart > Sessie" moet xfce4-panel 
aanwezig zijn. Herstart-stijl: "meteen"
Ik zou de opgeslagen sessies wissen en de lopende sessie (met werkbalk) 
opslaan.

Hopelijk werkt het dan.

Wel vreemd is dat in "pstree" xfce4-panel als subproces van systemd 
draait en niet van lightdm.


Groeten,

Henk.

Re: Error en Exim

[Fernando Romero]

El lun., 25 mar. 2019 a las 15:43, Matias Mucciolo ()
escribió:

> On Monday, March 25, 2019 2:59:45 PM -03 Fernando Romero wrote:
> > Ahora me tira otro error:
> >
> >  socket bind() to port 993 for address (any IPv6) failed: Address already
> > in use: daemon abandoned
> >
> > No estoy usando ipv6
> >
> >
> > El dom., 24 mar. 2019 a las 10:59, Gerardo Diez (<
> >
> > gerardo.diez.gar...@gmail.com>) escribió:
> > > El dom., 24 mar. 2019 14:53, Fernando Romero 
> > >
> > > escribió:
> > >> Hola como están.
> > >> Estoy corriendo debian 9 como servidor de correo con exim, funcionaba
> > >> perfecto hasta que quise habilitar ssl.
> > >> Ahí ya me dejo de autentificar, tanto por smtp como por ssl, este es
> el
> > >> error que me aparece en el log
> > >>
> > >> 2019-03-22 14:16:09 TLS error on connection from [xxx.xxx.xx.xx]:49888
> > >> (SSL_accept): error:140760FC:SSL
> routines:SSL23_GET_CLIENT_HELLO:unknown
> > >> protocol
> > >> 2019-03-22 14:16:09 TLS client disconnected cleanly (rejected our
> > >> certificate?)
> > >>
> > >> Busque en la web y hay distintas opciones que no me funcionaron
> ninguna,
> > >> desde error de permisos en el directorio de los certificados hasta
> > >> errores
> > >> de librería.
> > >> No entiendo por que me dejo de funcionar la autentificación por el
> puerto
> > >> 25 si en eso no toque nada.
> > >>
> > >> Alguien tuvo este problema con exim?.
> > >>
> > >> Saludos y gracias
> > >
> > > Hola,
> > >
> > > Sin más datos de tu configuración ¿seguro que es ese el puerto a
> emplear
> > > con TLS habilitado?
> > >
> > > Saludos
>
> NO top posting...
>
> Acerca del error el puerto 993 no lo deberia usar exim
> me parece que ese error es de algun servidor de IMAP.
> Ahora si es de exim no deberia escuchar en ese puerto.
> Hasta donde tengo entendido exim es solo un demonio "SMTP".
>
> Igualmente ademas de esto...te recomiendo postfix
> si vas a montar un servidor de correo.
>
> saludos
> Matias
>

Gracias Matias por tu respuesta, voy a mirar porque lo tengo con WHM y no
me aparece como opción postfix

Re: Error en Exim

[Matias Mucciolo]

On Monday, March 25, 2019 2:59:45 PM -03 Fernando Romero wrote:
> Ahora me tira otro error:
> 
>  socket bind() to port 993 for address (any IPv6) failed: Address already
> in use: daemon abandoned
> 
> No estoy usando ipv6
> 
> 
> El dom., 24 mar. 2019 a las 10:59, Gerardo Diez (<
> 
> gerardo.diez.gar...@gmail.com>) escribió:
> > El dom., 24 mar. 2019 14:53, Fernando Romero 
> > 
> > escribió:
> >> Hola como están.
> >> Estoy corriendo debian 9 como servidor de correo con exim, funcionaba
> >> perfecto hasta que quise habilitar ssl.
> >> Ahí ya me dejo de autentificar, tanto por smtp como por ssl, este es el
> >> error que me aparece en el log
> >> 
> >> 2019-03-22 14:16:09 TLS error on connection from [xxx.xxx.xx.xx]:49888
> >> (SSL_accept): error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown
> >> protocol
> >> 2019-03-22 14:16:09 TLS client disconnected cleanly (rejected our
> >> certificate?)
> >> 
> >> Busque en la web y hay distintas opciones que no me funcionaron ninguna,
> >> desde error de permisos en el directorio de los certificados hasta
> >> errores
> >> de librería.
> >> No entiendo por que me dejo de funcionar la autentificación por el puerto
> >> 25 si en eso no toque nada.
> >> 
> >> Alguien tuvo este problema con exim?.
> >> 
> >> Saludos y gracias
> > 
> > Hola,
> > 
> > Sin más datos de tu configuración ¿seguro que es ese el puerto a emplear
> > con TLS habilitado?
> > 
> > Saludos

NO top posting...

Acerca del error el puerto 993 no lo deberia usar exim
me parece que ese error es de algun servidor de IMAP.
Ahora si es de exim no deberia escuchar en ese puerto.
Hasta donde tengo entendido exim es solo un demonio "SMTP".

Igualmente ademas de esto...te recomiendo postfix
si vas a montar un servidor de correo.

saludos
Matias

Q. about Tinkering with Debian Source Code

[Kent West]

Hi!

I'm trying to dip my toe in the waters of editing the source code of Debian
packages, and I've started with the simplest, most innocuous program I
could think of - sl (the ASCII train that goes by on the screen when you
mistype "ls" as "sl).

When I use "apt source sl" (from sid, into its own directory) and compare
that tree (?) with what I get if I download via what that suggests (git
clone https://salsa.debian.org/debian/sl.git) (into its own directory), I
notice that the Makefile in the Debian version is slightly more complex. I
also notice some extra code in the Debian's "sl.c" file which is not in the
Git version's, which indicates to me that the Debian version has updates
that are not in the "newest" version on the Git repository.

Should I consider the Debian download as the official source, of the Git
version? If I were to make changes to feed back to the project, would I
want to make the changes to the Debian version or the Git version? Has the
Debian version essentially forked, making the Git version irrelevant? If I
start with the Git version, and it were to get accepting back into Debian,
wouldn't that erase all the extra stuff that has been added to the Debian
version that is not in the Git version (unless I find it all and re-include
it)? If I start in the Debian version and it gets accepted back into
Debian, wouldn't that make the Git version just that much more irrelevant?

I'm not even sure my questions make sense; I'm just trying to wrap my brain
around the basic process.

Thanks!


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

Re: Error en Exim

[Fernando Romero]

Ahora me tira otro error:

 socket bind() to port 993 for address (any IPv6) failed: Address already
in use: daemon abandoned

No estoy usando ipv6


El dom., 24 mar. 2019 a las 10:59, Gerardo Diez (<
gerardo.diez.gar...@gmail.com>) escribió:

>
>
> El dom., 24 mar. 2019 14:53, Fernando Romero 
> escribió:
>
>> Hola como están.
>> Estoy corriendo debian 9 como servidor de correo con exim, funcionaba
>> perfecto hasta que quise habilitar ssl.
>> Ahí ya me dejo de autentificar, tanto por smtp como por ssl, este es el
>> error que me aparece en el log
>>
>> 2019-03-22 14:16:09 TLS error on connection from [xxx.xxx.xx.xx]:49888
>> (SSL_accept): error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown
>> protocol
>> 2019-03-22 14:16:09 TLS client disconnected cleanly (rejected our
>> certificate?)
>>
>> Busque en la web y hay distintas opciones que no me funcionaron ninguna,
>> desde error de permisos en el directorio de los certificados hasta errores
>> de librería.
>> No entiendo por que me dejo de funcionar la autentificación por el puerto
>> 25 si en eso no toque nada.
>>
>> Alguien tuvo este problema con exim?.
>>
>> Saludos y gracias
>>
>
> Hola,
>
> Sin más datos de tu configuración ¿seguro que es ese el puerto a emplear
> con TLS habilitado?
>
> Saludos
>
>>

Re: Re : Backuppc et caractères accentués

[Migrec]

Le 25/03/2019 à 18:13, nicolas.patr...@gmail.com a écrit :

Bonjour,

Je ne sais pas ce que contient ce message quand je clique dessus, Balsa me le 
montre tout blanc.
Je dois y répondre pour voir son contenu.

nicolas patrois : pts noir asocial


Bonjour,

Désolé, il devait être en HTML. Celui-ci devrait être en texte.
Voici l'original :

Directement dans le fichier de configuration /etc/backuppc/machine.pl ?

Est-ce que dans l'interface de configuration, on ne peut pas passer 
outre pour cette histoire d'accent ? J'ai tenté de mettre "utf8" dans 
ClientCharsetLegacy 
 
sans succès.


--
Migrec

Re: mdadm started before disks are detected

[Mimiko]

On 24.03.2019 22:46, Sven Hartge wrote:

I came across a problem when booting. In the server is installed 4
disks connected to raid controller and 2 disks connected to
motherboard sata interfaces. During booting disks connected to raid
controller are detected before md raid assembling process, while the 2
disks connected to motherboard sata interfaces are detected after md
raid assembly, so the raid made of this 2 disks are not detected and
assembled during boot.

Add "rootdelay=10" to your Linux cmdline via /etc/default/grub. This
normally solves the problem.


This didn't help.

Linux 2.6.32-5-amd64 #1 SMP Tue May 13 16:34:35 UTC 2014 x86_64 GNU/Linux

Re : Backuppc et caractères accentués

[nicolas . patrois]

Bonjour,

Je ne sais pas ce que contient ce message quand je clique dessus, Balsa me le 
montre tout blanc.
Je dois y répondre pour voir son contenu.

nicolas patrois : pts noir asocial
-- 
RÉALISME

M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des humains ? 
Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...

Re: [Debian 8] - Paquet indisponible

[hamster]

Le 25/03/2019 à 16:59, pierre bourget a écrit :
> Re bonjour,
>
> je vois que plusieurs paquets ne sont plus dispo dans les
> jessie-backports en fait : gpsd notamment.
> C’est définitif ? Si oui pourquoi les avoir retiré ? Sinon, où puis-je
> les trouver svp ?

comme déjà dit : Les paquets de jessie ont récamment été retirés des
dépots. Ils sont maintenant disponibles dans les archives :

https://lists.debian.org/debian-devel-announce/2019/03/msg6.html

les archives, c'est http://archive.debian.org/

Re: Backuppc et caractères accentués

[Migrec]

  
  
Le 25/03/2019 à 09:06, Jacques a écrit :

  Je ne sais plu comment j'en suis arrivé là, mais en pratique et ça tombe en marche dans ma configuration backuppc, je remplace le caractère é par le caractère hexadecimal E9


Directement dans le fichier de configuration
/etc/backuppc/machine.pl ?

Est-ce que dans l'interface de configuration, on ne peut pas passer
outre pour cette histoire d'accent ? J'ai tenté de mettre "utf8"
dans ClientCharsetLegacy
sans succès.

--
Migrec
  

Re: [Debian 8] - Paquet indisponible

[pierre bourget]

Re bonjour,

je vois que plusieurs paquets ne sont plus dispo dans les jessie-backports en 
fait : gpsd notamment.
C’est définitif ? Si oui pourquoi les avoir retiré ? Sinon, où puis-je les 
trouver svp ?

Merci et bonne fin de journée,

Pierre BOURGET
Administrateur systèmes et réseaux

9 rue des Tuiliers - 69003 Lyon




> Le 25 mars 2019 à 12:25, Alban Vidal  a écrit :
> 
> Bonjour Pierre,
> 
> La présente liste de diffusion est à destination de l'équipe française
> de traduction.
> 
> Pour des question plus généralistes sur Debian, merci de bien vouloir
> utiliser l'adresse suivante (que j'ai mis en copie) :
> debian-user-french@lists.debian.org
> 
> Le 25/03/2019 à 11:56, pierre bourget a écrit :
>> Bonjour,
>> 
>> le paquet «  openjdk-8-jre-headless » est indisponible pour debian
>> Jessie, alors qu’il l’était récemment…
>> J’ai une erreur sur cette page
>> : https://packages.debian.org/fr/jessie-backports/openjdk-8-jre-headless
>> 
>> J’oublie quelque chose ? 
>> 
>> Merci pour votre aide, 
>> 
>> Pierre
> 
> Sinon pour quand même répondre à la question :
> Le paquet « openjdk-8-jre-headless » n'existe pas sous Debian Jessie, il
> s'agirait de la version « openjdk-7-jre-headless ».
> 
> Paquets openjdk dans Jessie :
> https://packages.debian.org/search?keywords=openjdk=names=oldstable=all
> 
> Paquets openjdk dans Stretch :
> https://packages.debian.org/search?keywords=openjdk=names=stable=all
> 
> 
> Il n'y a pas d'openjdk dans les dépôts jessie-backports ou
> jessie-backports-sloppy.
> 
> Cordialement,
> 
> Alban
> 
> 

Re: apt-cacher errors

[Greg Wooledge]

On Mon, Mar 25, 2019 at 02:24:22PM +, Adam Weremczuk wrote:
> Any practical difference between \*wheezy\* and '*wheezy*' in this case?

Both forms of quoting yield identical results.  As does "*wheezy*".

Re: apt-cacher errors

[Adam Weremczuk]

Hi Greg,

Thank you for taking the time to point out all the shortcomings.


On 25/03/19 13:21, Greg Wooledge wrote:

On Mon, Mar 25, 2019 at 12:11:21PM +, Adam Weremczuk wrote:

I've found 30 entries referencing wheezy and removed them all:

sudo find /var/cache/apt-cacher/ -type f -name *wheezy* | xargs rm

sudo find /var/cache/apt-cacher -type f -name '*wheezy*' -delete

There are three mistakes in your command:

1) The glob must be quoted, or the shell will expand it based on the files
in the current working directory, wherever that happens to be.
I would normally use \*wheezy\* but I new that wouldn't make any 
difference as I saw the list earlier.

Any practical difference between \*wheezy\* and '*wheezy*' in this case?

2) xargs without -0 is unsafe to use for filenames, because they may contain
whitespace or single quotes or double quotes, all of which are special
to xargs.
Again, I saw the list so didn't bother but a fair point indeed, it could 
easily fail or even turn disastrous.

3) You ran find with sudo privileges (probably not necessary), and failed
to run the rm with sudo privileges.  All of the removals are therefore
going to fail.
TBH I run it as root and added single sudo in front after pasting not to 
promote bad practices :)


You might argue that "apt-cacher never has any files with spaces!"
That may be true.  But it's still a good habit to develop.  Also, -delete
is more efficient than | xargs rm, albeit not portable to POSIX scripts.

Never used it with find, good to know.


If you want it to be portable as well as safe, then:

sudo find /var/cache/apt-cacher -type f -name '*wheezy*' -exec rm {} +

That's less efficient than -delete, but it's the best you can do if
POSIX portability is required.

Agree.

Thanks again,
Adam

Re: apt-cacher errors

[deb]

On 3/25/19 9:21 AM, Greg Wooledge wrote:

On Mon, Mar 25, 2019 at 12:11:21PM +, Adam Weremczuk wrote:

I've found 30 entries referencing wheezy and removed them all:

sudo find /var/cache/apt-cacher/ -type f -name *wheezy* | xargs rm

sudo find /var/cache/apt-cacher -type f -name '*wheezy*' -delete

There are three mistakes in your command:

1) The glob must be quoted, or the shell will expand it based on the files
in the current working directory, wherever that happens to be.

2) xargs without -0 is unsafe to use for filenames, because they may contain
whitespace or single quotes or double quotes, all of which are special
to xargs.

3) You ran find with sudo privileges (probably not necessary), and failed
to run the rm with sudo privileges.  All of the removals are therefore
going to fail.

You might argue that "apt-cacher never has any files with spaces!"
That may be true.  But it's still a good habit to develop.  Also, -delete
is more efficient than | xargs rm, albeit not portable to POSIX scripts.

If you want it to be portable as well as safe, then:

sudo find /var/cache/apt-cacher -type f -name '*wheezy*' -exec rm {} +

That's less efficient than -delete, but it's the best you can do if
POSIX portability is required.




Great thoughts Greg.

Helped me too.

Re: apt-cacher errors

[Greg Wooledge]

On Mon, Mar 25, 2019 at 12:11:21PM +, Adam Weremczuk wrote:
> I've found 30 entries referencing wheezy and removed them all:
> 
> sudo find /var/cache/apt-cacher/ -type f -name *wheezy* | xargs rm

sudo find /var/cache/apt-cacher -type f -name '*wheezy*' -delete

There are three mistakes in your command:

1) The glob must be quoted, or the shell will expand it based on the files
   in the current working directory, wherever that happens to be.

2) xargs without -0 is unsafe to use for filenames, because they may contain
   whitespace or single quotes or double quotes, all of which are special
   to xargs.

3) You ran find with sudo privileges (probably not necessary), and failed
   to run the rm with sudo privileges.  All of the removals are therefore
   going to fail.

You might argue that "apt-cacher never has any files with spaces!"
That may be true.  But it's still a good habit to develop.  Also, -delete
is more efficient than | xargs rm, albeit not portable to POSIX scripts.

If you want it to be portable as well as safe, then:

sudo find /var/cache/apt-cacher -type f -name '*wheezy*' -exec rm {} +

That's less efficient than -delete, but it's the best you can do if
POSIX portability is required.

XFCE probleem

[Paul van der Vlis]

Hallo,

Ik probeer XFCE te installeren op een bestaande computer, maar er
verschijnt geen menubalk. Ook bij een nieuw aangemaakte user met lege
homedir verschijnt er geen menubalk (panel).

Wel kan ik met mijn rechtermuisknop klikken op het bureaublad, dan zie
ik daar als onderste optie wel een menu.

Iemand een idee wat er aan de hand is, of hoe dat panel te herstarten?
Het pakket purgen en weer opnieuw installeren helpt ook al niet.

Wat me opvalt als ik "pstree" draai, is dat xfce4-panel draait als
subproces van systemd, niet van LightDM (dat is normaal).

Groeten,
Paul

-- 
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

Re: Conseils sur l'administration de MySQL/MariaDB sur Buster ? [RESOLU]

[BERTRAND Joël]

Olivier a écrit :
> 
> 
> Le lun. 25 mars 2019 à 12:19, BERTRAND Joël  > a écrit :
> 
> 
> 
>         Pas chez moi :
> 
> 
> @Joel:
> Que donne 'SELECT host, user, password, plugin FROM mysql.user;' sur ta
> machine ?
> Sur la mienne, j'ai bien le plugin unix_socket qu'Alexandre mentionne
> dans son message.

Je vire toujours la socket Unix.

MariaDB [(none)]> select host,user,password,plugin from mysql.user where
user='root';
+---+--+---++
| host  | user | password  | plugin |
+---+--+---++
| localhost | root | *8DD098CAB69587D2A67BE8E8A66010A99DF39A75 ||
| rayleigh  | root | *8DD098CAB69587D2A67BE8E8A66010A99DF39A75 ||
+---+--+---++
2 rows in set (0.000 sec)

Je considère que ce n'est pas un trou de sécurité, mais une faille
délirante. root doit se connecter avec un mot de passe.

JKB

Re: Conseils sur l'administration de MySQL/MariaDB sur Buster ? [RESOLU]

[Olivier]

Le lun. 25 mars 2019 à 12:19, BERTRAND Joël  a
écrit :

>
>
> Pas chez moi :
>
>
> @Joel:
Que donne 'SELECT host, user, password, plugin FROM mysql.user;' sur ta
machine ?
Sur la mienne, j'ai bien le plugin unix_socket qu'Alexandre mentionne dans
son message.

@Alexandre:
Merci pour ton lien: il explique bien le nouveau paramétrage.
Le lien [1] le détaille aussi.
Pour l'instant, je conserve ce nouveau fonctionnement en l'état.
Je marque néanmoins ce fil de discussion comme RESOLU car je pense qu'il
pourra être utile à d'autres.

Merci à vous

[1] https://mariadb.com/kb/en/library/authentication-plugin-unix-socket/

Re: text editors

[Teemu Likonen]

mick crane [2019-03-25 04:38:31Z] wrote:

> Is there any text editor, preferably in a terminal that has the facility
> to protect lines in the document, not the document itself ?
> I've got 2 blocks of "code" that look similar and I keep editing the
> wrong one and then it doesn't work.

GNU Emacs has text properties which can be added to any piece of text.
One of the properties is named "read-only". I made two functions to
handle the situation you described.

Put these function to you Emacs's init file (~/.emacs or
~/.emacs.d/init.el):


(defun read-only-region (beg end)
  "Makes a region in the current buffer read only, from buffer
position BEG to END. If this function is called interactively use
the current hightlighted region."
  (interactive "r")
  (add-text-properties beg end '(read-only t)))

(defun remove-read-only ()
  "Remove all read only text properties from the current buffer."
  (interactive)
  (let ((inhibit-read-only t))
(remove-text-properties (point-min) (point-max)
'(read-only t


Select some text in a buffer and execute command "Alt+x
read-only-region". That area becomes read only. To remove all read only
text areas from the current buffer execute command "Alt+x
remove-read-only".

-- 
/// Teemu Likonen   - .-..    //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///


signature.asc
Description: PGP signature

Re: apt-cacher errors

[Adam Weremczuk]

I've found 30 entries referencing wheezy and removed them all:

sudo find /var/cache/apt-cacher/ -type f -name *wheezy* | xargs rm

which appears to have fixed the issue.

Thanks,
Adam


On 25/03/19 11:43, Roberto C. Sánchez wrote:

On Mon, Mar 25, 2019 at 07:05:11AM -0400, Roberto C. Sánchez wrote:

On Mon, Mar 25, 2019 at 08:59:40AM +, Adam Weremczuk wrote:

Hi all,

On 24th March (last Sunday) I received the following (for the first time):

Subject: Cron test -x /usr/share/apt-cacher/apt-cacher-cleanup.pl && 
/usr/share/apt-cacher/apt-cacher-cleanup.pl

Error: cannot open ../headers/debian_dists_wheezy_Release for locking: No such 
file or directory
Failed to open filehandles for debian_dists_wheezy_Release. Resolve this 
manually.
Exiting to prevent deletion of cache contents.

The above all came from systems originally running wheezy which were upgraded 
to stretch about 2 years ago.

Questions:

1. How to get rid of these errors? I would prefer to avoid spending half a day 
deciphering a chain of Perl scripts which I'm not familiar with.
2. What specifically happened last week to trigger this behavior? Was it e.g. a 
permanent removal of all wheezy repos and references?


https://lists.debian.org/debian-devel-announce/2019/03/msg6.html

You will need to change your sources.list.

http://archive.debian.org/debian/README


Perhaps I spoke too soon.  I encountered this error in my apt-cacher-ng
log after replying to your message.

Checking/Updating debrep/dists/wheezy/Release...
Attempting to download the alternative version... Checking/Updating
debrep/dists/wheezy/InRelease...
404 Not Found

After seeing that I re-read your message and noticed that the system had
been initially installed as wheezy but now runs stretch.

It has been some years since I moved to apt-cacher-ng, so I've forgotten
how it differs from apt-cacher, but in my case I had to remove the
directories /var/cache/apt-cacher-ng/debrep/dists/wheezy* and then
re-run the expiration task.

You may need to do something similar.

Regards,

-Roberto

Re: [Debian 8] - Paquet indisponible

[hamster]

Le 25/03/2019 à 11:56, pierre bourget a écrit :
>> le paquet «  openjdk-8-jre-headless » est indisponible pour debian
>> Jessie, alors qu’il l’était récemment…

Les paquets de jessie ont récamment été retirés des dépots. Ils sont
maintenant disponibles dans les archives :
https://lists.debian.org/debian-devel-announce/2019/03/msg6.html

Re: text editors

[rhkramer]

On Monday, March 25, 2019 07:47:31 AM rhkra...@gmail.com wrote:
> I even have a vague recollection that there is / was an "include a file"
> facility in (Microsoft) Word.  And, if so, because LIbre Office seems to
> make a point of providing a feature complete "clone" (mcow) of Word, I
> suspect there is an include facility there as well.

Ahh, yes, after a little bit of googling, I found (and remember) that Word had 
(and presumably still has) a master document concept -- which is essentially 
the same as the include file concept.

Then, looking at ODF (Open Document Format), which is either the default or at 
least one of the formats supported by Libre Office, also supports a master 
document format.

Re: [Debian 8] - Paquet indisponible

[Alban Vidal]

Bonjour Pierre,

La présente liste de diffusion est à destination de l'équipe française
de traduction.

Pour des question plus généralistes sur Debian, merci de bien vouloir
utiliser l'adresse suivante (que j'ai mis en copie) :
debian-user-french@lists.debian.org

Le 25/03/2019 à 11:56, pierre bourget a écrit :
> Bonjour,
>
> le paquet «  openjdk-8-jre-headless » est indisponible pour debian
> Jessie, alors qu’il l’était récemment…
> J’ai une erreur sur cette page
> : https://packages.debian.org/fr/jessie-backports/openjdk-8-jre-headless
>
> J’oublie quelque chose ? 
>
> Merci pour votre aide, 
>
> Pierre

Sinon pour quand même répondre à la question :
Le paquet « openjdk-8-jre-headless » n'existe pas sous Debian Jessie, il
s'agirait de la version « openjdk-7-jre-headless ».

Paquets openjdk dans Jessie :
https://packages.debian.org/search?keywords=openjdk=names=oldstable=all

Paquets openjdk dans Stretch :
https://packages.debian.org/search?keywords=openjdk=names=stable=all


Il n'y a pas d'openjdk dans les dépôts jessie-backports ou
jessie-backports-sloppy.

Cordialement,

Alban




signature.asc
Description: OpenPGP digital signature

Re: text editors

[rhkramer]

On Monday, March 25, 2019 07:05:14 AM to...@tuxteam.de wrote:
> On Mon, Mar 25, 2019 at 04:38:31AM +, mick crane wrote:
> > Is there any text editor, preferably in a terminal that has the
> > facility to protect lines in the document, not the document itself ?
> > I've got 2 blocks of "code" that look similar and I keep editing the
> > wrong one and then it doesn't work.
> > mick
> 
> What is "the document"? And what format is it in?
> 
> I have the strong suspicion that the answer to the first would be
> "a configuration file of some sort" and to the second, it might
> be "plain text".

Because there have been some interesting ideas in this thread, I'll add one 
more (which might not be interesting). ;-)

I share the thought that the file / document might be  "a configuration file of 
some sort" and have a suggestion that might be useful in that case, or if the 
document is a program, and maybe even if it is just a text (not necessarily 
plain) file that you open with a word processor.

The thought: put the part of the document that should not be modified in a read 
only file, then "include" that file in another file that you allow to be edited 
(read / write).

There are various ways to do this, depending on the computer language under 
considereration (for example, #include in C / C++).  

There are equivalent approaches in bash, but I forget them (in bash, it might 
be a little more convoluted, like an external / 3rd file that assembles a new 
file from the read-only and read / write files.

I even have a vague recollection that there is / was an "include a file" 
facility in (Microsoft) Word.  And, if so, because LIbre Office seems to make a 
point of providing a feature complete "clone" (mcow) of Word, I suspect there 
is an include facility there as well.

Re: apt-cacher errors

[Roberto C . Sánchez]

On Mon, Mar 25, 2019 at 07:05:11AM -0400, Roberto C. Sánchez wrote:
> On Mon, Mar 25, 2019 at 08:59:40AM +, Adam Weremczuk wrote:
> > Hi all,
> > 
> > On 24th March (last Sunday) I received the following (for the first time):
> > 
> > Subject: Cron test -x /usr/share/apt-cacher/apt-cacher-cleanup.pl && 
> > /usr/share/apt-cacher/apt-cacher-cleanup.pl
> > 
> > Error: cannot open ../headers/debian_dists_wheezy_Release for locking: No 
> > such file or directory
> > Failed to open filehandles for debian_dists_wheezy_Release. Resolve this 
> > manually.
> > Exiting to prevent deletion of cache contents.
> > 
> > The above all came from systems originally running wheezy which were 
> > upgraded to stretch about 2 years ago.
> > 
> > Questions:
> > 
> > 1. How to get rid of these errors? I would prefer to avoid spending half a 
> > day deciphering a chain of Perl scripts which I'm not familiar with.
> > 2. What specifically happened last week to trigger this behavior? Was it 
> > e.g. a permanent removal of all wheezy repos and references?
> > 
> https://lists.debian.org/debian-devel-announce/2019/03/msg6.html
> 
> You will need to change your sources.list.
> 
> http://archive.debian.org/debian/README
> 
Perhaps I spoke too soon.  I encountered this error in my apt-cacher-ng
log after replying to your message.

Checking/Updating debrep/dists/wheezy/Release...
Attempting to download the alternative version... Checking/Updating
debrep/dists/wheezy/InRelease...
404 Not Found

After seeing that I re-read your message and noticed that the system had
been initially installed as wheezy but now runs stretch.

It has been some years since I moved to apt-cacher-ng, so I've forgotten
how it differs from apt-cacher, but in my case I had to remove the
directories /var/cache/apt-cacher-ng/debrep/dists/wheezy* and then
re-run the expiration task.

You may need to do something similar.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: Conseils sur l'administration de MySQL/MariaDB sur Buster ?

[Alexandre Goethals]

Bonjour,

pour la connexion au compte root sans mot de passe (en local), c'est
parce que ce compte utilise le plugin unix socket:

|SELECThost,user,password,plugin FROMmysql.user; devrait donner quelque
chose comme: 
||+---+--+--+-+|host
|user|password |plugin
|+---+--+--+-+|localhost
|root ||unix_socket
|+---+--+--+-+ Donc il
faut faire: ||UPDATEmysql.userSETplugin =''WHEREuser='root'ANDhost 
='localhost';FLUSH
PRIVILEGES; redémarrer mariadb source:
https://stackoverflow.com/questions/7179894/how-to-disable-mysql-root-logins-when-no-password-is-supplied
|

Le 25/03/2019 à 12:19, BERTRAND Joël a écrit :
> Olivier a écrit :
>> Bonjour,
>   Bonjour,
>
>> Je travaille sur une configuration de Freeradius avec une base de
>> données pour Debian Buster.
>>
>> Comme la documentation de Freeradius avec base de données se réfère
>> massivement à MySQL, j'ai installé sur une VM, MySQL/MariaDB avec la
>> commande apt-get install default-mysql-server suivie de
>> mysql_secure_installation.
>>
>> J'ai volontairement installé default-mysql-servercar dans mon cas, je
>> suis indifférent au choix MySQL/MariaDB: je souhaite juste mettre au
>> point une configuration qui fonctionnera quand Buster sera la version
>> stable de Debian.
>>
>> Ce faisant, j'ai été surpris de constater qu'après ces 2 commandes, la
>> méthode d'accès à MySQL/MariaDB avait changé:
>>
>> - l'utilisateur root peut se connecter sans mot de passe ou avec un mot
>> de passe erroné
>   Pas chez moi :
>
> Root rayleigh:[~] > mysql -uroot -p
> Enter password:
> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
> password: YES)
> Root rayleigh:[~] >
>
>   Naturellement, si je fournis le bon mot de passe, ça fonctionne comme
> attendu.
>
>> - un utilisateur lambda ne peut plus se connecter en tant qu'utilisateur
>> MySQL/MariaDB root même en fournissant le bon mot de passe.
>   Pas chez moi :
>
> rayleigh:[~] > mysql -uroot -p
> Enter password:
> Welcome to the MariaDB monitor.  Commands end with ; or \g.
> Your MariaDB connection id is 10044
> Server version: 10.3.13-MariaDB-1-log Debian buildd-unstable
>
> Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
>
> Type 'help;' or '\h' for help. Type '\c' to clear the current input
> statement.
>
> MariaDB [(none)]> quit
> Bye
> rayleigh:[~] > whoami
> bertrand
>
>   À mon avis, le problème est ailleurs ;-)
>
>   Je commencerais pas jeter un oeil à la configuration de mariadb.
>
>   Bien cordialement,
>
>   JKB
>

Re: text editors

[tomas]

On Mon, Mar 25, 2019 at 04:38:31AM +, mick crane wrote:
> Is there any text editor, preferably in a terminal that has the
> facility to protect lines in the document, not the document itself ?
> I've got 2 blocks of "code" that look similar and I keep editing the
> wrong one and then it doesn't work.
> mick

What is "the document"? And what format is it in?

I have the strong suspicion that the answer to the first would be
"a configuration file of some sort" and to the second, it might
be "plain text".

In that case, I guess the straight answer to your question above
is "no".

And with the possibility that, perhaps, this (hypothetical) editor
won't be the only interface to your file, it might be wise to
consider another angle from which to attack the problem. A version
control system which allows you to easily revert to a previous
version of your file should anything go wrong. Or a post-commit
script charged of ensuring certain constraints before "activating"
your new version of the file (cf. visudo for inspiration). Just
two examples to perhaps get you started.

You can nevertheless get every civilised editor to do the trick
(vim, Emacs will easily comply) -- but perhaps you won't be
solving your problem...

Cheers
-- t


signature.asc
Description: Digital signature

Re: Conseils sur l'administration de MySQL/MariaDB sur Buster ?

[BERTRAND Joël]

Olivier a écrit :
> Bonjour,

Bonjour,

> Je travaille sur une configuration de Freeradius avec une base de
> données pour Debian Buster.
> 
> Comme la documentation de Freeradius avec base de données se réfère
> massivement à MySQL, j'ai installé sur une VM, MySQL/MariaDB avec la
> commande apt-get install default-mysql-server suivie de
> mysql_secure_installation.
> 
> J'ai volontairement installé default-mysql-servercar dans mon cas, je
> suis indifférent au choix MySQL/MariaDB: je souhaite juste mettre au
> point une configuration qui fonctionnera quand Buster sera la version
> stable de Debian.
> 
> Ce faisant, j'ai été surpris de constater qu'après ces 2 commandes, la
> méthode d'accès à MySQL/MariaDB avait changé:
> 
> - l'utilisateur root peut se connecter sans mot de passe ou avec un mot
> de passe erroné

Pas chez moi :

Root rayleigh:[~] > mysql -uroot -p
Enter password:
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
password: YES)
Root rayleigh:[~] >

Naturellement, si je fournis le bon mot de passe, ça fonctionne comme
attendu.

> - un utilisateur lambda ne peut plus se connecter en tant qu'utilisateur
> MySQL/MariaDB root même en fournissant le bon mot de passe.

Pas chez moi :

rayleigh:[~] > mysql -uroot -p
Enter password:
Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 10044
Server version: 10.3.13-MariaDB-1-log Debian buildd-unstable

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input
statement.

MariaDB [(none)]> quit
Bye
rayleigh:[~] > whoami
bertrand

À mon avis, le problème est ailleurs ;-)

Je commencerais pas jeter un oeil à la configuration de mariadb.

Bien cordialement,

JKB

Re: apt-cacher errors

[Roberto C . Sánchez]

On Mon, Mar 25, 2019 at 08:59:40AM +, Adam Weremczuk wrote:
> Hi all,
> 
> On 24th March (last Sunday) I received the following (for the first time):
> 
> Subject: Cron test -x /usr/share/apt-cacher/apt-cacher-cleanup.pl && 
> /usr/share/apt-cacher/apt-cacher-cleanup.pl
> 
> Error: cannot open ../headers/debian_dists_wheezy_Release for locking: No 
> such file or directory
> Failed to open filehandles for debian_dists_wheezy_Release. Resolve this 
> manually.
> Exiting to prevent deletion of cache contents.
> 
> The above all came from systems originally running wheezy which were upgraded 
> to stretch about 2 years ago.
> 
> Questions:
> 
> 1. How to get rid of these errors? I would prefer to avoid spending half a 
> day deciphering a chain of Perl scripts which I'm not familiar with.
> 2. What specifically happened last week to trigger this behavior? Was it e.g. 
> a permanent removal of all wheezy repos and references?
> 
https://lists.debian.org/debian-devel-announce/2019/03/msg6.html

You will need to change your sources.list.

http://archive.debian.org/debian/README

Regards,

-Roberto

-- 
Roberto C. Sánchez

Conseils sur l'administration de MySQL/MariaDB sur Buster ?

[Olivier]

Bonjour,

Je travaille sur une configuration de Freeradius avec une base de données
pour Debian Buster.

Comme la documentation de Freeradius avec base de données se réfère
massivement à MySQL, j'ai installé sur une VM, MySQL/MariaDB avec la
commande apt-get install default-mysql-server suivie de
mysql_secure_installation.

J'ai volontairement installé default-mysql-servercar dans mon cas, je suis
indifférent au choix MySQL/MariaDB: je souhaite juste mettre au point une
configuration qui fonctionnera quand Buster sera la version stable de
Debian.

Ce faisant, j'ai été surpris de constater qu'après ces 2 commandes, la
méthode d'accès à MySQL/MariaDB avait changé:

- l'utilisateur root peut se connecter sans mot de passe ou avec un mot de
passe erroné
- un utilisateur lambda ne peut plus se connecter en tant qu'utilisateur
MySQL/MariaDB root même en fournissant le bon mot de passe.

J'ai trouvé sur Internet vraiment très peu de doc sur l'administration de
MySQL/MariaDBsous Buster.

Avez-vous des conseils sur ceci dans le cas où on a besoin d'exécuter des
scripts de création-configuration de base de données MySQL ?

Faut-il installer MySQL plutôt que MariaDB ? Le contraire ?
Y-a-t-il une autre commande que mysql_secure_installation à exécuter ?
Peut-on sans état d'âme ignorer cette différence avec les versions de MySQL
sous Jessie ou autre ?
Documentation ?

Slts

Re: text editors

[mick crane]

On 2019-03-25 10:12, Erik Christiansen wrote:

On 25.03.19 07:53, mick crane wrote:

not heard about folding.


It can be very handy. I have around 420 pages of notes in one file. 
They

present as a one-page contents table with section page counts. While
cursoring down and then across opens a chosen fold, there are several
folding levels to the bottom. Hierarchical groping and digging is an
inefficient constraint suffered by GUIs; it is much quicker to just use
vim's '/' to search for a keyword. Given capitalised headings and
keywords, suffixed with a ':' for the major section on that topic, the
right line in 28532 lines is quickly found, and the required folds
opened automatically.


I'm not very good at this.


Give it 30 years. Experience creeps up on you.


kind of related I'm having difficulty copy and pasting.
If on windows [sorry] and in putty session for Debian no gui vi, if


Commiserations. I'd be sorry too if I had to use windows. (Avoided it
entirely during 30 years in IT - took a fat redundancy package when
windows finally caught up, and retired.


highlight text with mouse then it is automatically saved to windows
clipboard for pasting but then in putty cannot scroll past bottom of 
screen.


Sounds like a putty limitation? I'll admit to only ever having copied 
to

an X11 clipboard, so can't offer relevant experience. I've never used
gvim - plain vim in an xterm works fine with the X11 clipboard, so long
as I remember to turn off autoindent before pasting, to avoid a
stairstep paste. (I have the F12 key mapped to toggle vim's "paste"
attribute, so a single key handles both on and off.)


If set marks and then yank to other mark text is yanked but is not in
windows clipboard buffer for pasting.


Have you checked whether the yank goes into the "* (clipboard) 
register?

Check also the "+ register, in case the windows clipboard is looking
there instead. A post on the vim-use ML might elicit more info related
to your environment. Back in 2011, Gary Johnson had a "Copy and paste
problem" which was fixed for windows with "set clipboard^=unnamed".)

:help 'clipboard'
:help :set^=

I tend to just use a mouse drag to grab text to the X11 clipboard for
pasting into something GUI.

In visual mode I can highlight all text with go to mark but that is 
not in

windows buffer either.
I tried all different commands to try to get text into windows buffer 
but

nothing seems to work.


Check   " :set clipboard ? "

IIUC, it should include unnamed and unnamedplus for problem-free
communication with the windows clipboard - inferring from a couple of
archive posts from 2011,12. Including unnamedplus isn't good for the
linux clipboard, though.

If all else fails, the vim-use mailing list is a darned sight more
knowledgeable on vim/windows stuff.

Erik


tried "set clipboard=unnamed" and that.
":%y *" is supposed to copy to buffer and ":%y +" also says unrecognized 
register or something"

": reg" shows
""
"0
":
"%
so I don't know.
obviously buffers are on different machines and maybe putty just buffers 
what's on the screen.

Just wondered why it didn't work.

mick






--
Key ID4BFEBB31

Re: installation Debian avec home sur disque dur usb

[hamster]

Le 25/03/2019 à 10:08, Erwann Le Bras a écrit :
> Le 24/03/2019 à 20:29, hamster a écrit :
>> Le 24/03/2019 à 20:14, alex.pad...@laposte.net a écrit :
>>>
>>> Bonsoir à tous,
>>>
>>>
>>> Je souhaiterai faire une installation Debian sur un mini-pc avec un
>>> disque dur SSD, Debian sera installé sur le disque SSD tandis que mon
>>> home devra être installer impérativement sur un disque dur usb externe.
>>>
>>> Je souhaiterai que mon home soit crypté ou chiffré.
>>>
>>> Comment faire tout cela à l'installation du système.
>>>
>> Tout cela est prévu dans l'installeur. Autant le fait de chiffrer que de
>> séparer le /home sur une partition de ton choix.
>>
>
> Tout à fait : faire une install classique avec le disque externe en
> place pour préciser, au moment du partitionnement (choisir
> "personnalisé") la cible et l'état des partitions.

J'ajoute que chiffrer le /home ne suffit pas. Quand tu va utiliser ton
ordi, tu va taper ta phrase de passe pour acceder a tes données. Cette
phrase va etre stockée en mémoire vive. Si a ce moment la tu hiberne, le
contenu de la mémoire vive (avec ta phrase de passe) sera copié dans la
swap. Il faut donc chiffrer aussi la swap. Et tant que t'y est, si tu
chiffre aussi la partition système c'est pas plus mal.

Re: text editors

[Erik Christiansen]

On 25.03.19 07:53, mick crane wrote:
> not heard about folding.

It can be very handy. I have around 420 pages of notes in one file. They
present as a one-page contents table with section page counts. While
cursoring down and then across opens a chosen fold, there are several
folding levels to the bottom. Hierarchical groping and digging is an
inefficient constraint suffered by GUIs; it is much quicker to just use
vim's '/' to search for a keyword. Given capitalised headings and
keywords, suffixed with a ':' for the major section on that topic, the
right line in 28532 lines is quickly found, and the required folds
opened automatically.

> I'm not very good at this.

Give it 30 years. Experience creeps up on you.

> kind of related I'm having difficulty copy and pasting.
> If on windows [sorry] and in putty session for Debian no gui vi, if

Commiserations. I'd be sorry too if I had to use windows. (Avoided it
entirely during 30 years in IT - took a fat redundancy package when
windows finally caught up, and retired.

> highlight text with mouse then it is automatically saved to windows
> clipboard for pasting but then in putty cannot scroll past bottom of screen.

Sounds like a putty limitation? I'll admit to only ever having copied to
an X11 clipboard, so can't offer relevant experience. I've never used
gvim - plain vim in an xterm works fine with the X11 clipboard, so long
as I remember to turn off autoindent before pasting, to avoid a
stairstep paste. (I have the F12 key mapped to toggle vim's "paste"
attribute, so a single key handles both on and off.)

> If set marks and then yank to other mark text is yanked but is not in
> windows clipboard buffer for pasting.

Have you checked whether the yank goes into the "* (clipboard) register?
Check also the "+ register, in case the windows clipboard is looking
there instead. A post on the vim-use ML might elicit more info related
to your environment. Back in 2011, Gary Johnson had a "Copy and paste
problem" which was fixed for windows with "set clipboard^=unnamed".)

:help 'clipboard'
:help :set^=

I tend to just use a mouse drag to grab text to the X11 clipboard for
pasting into something GUI.

> In visual mode I can highlight all text with go to mark but that is not in
> windows buffer either.
> I tried all different commands to try to get text into windows buffer but
> nothing seems to work.

Check   " :set clipboard ? "

IIUC, it should include unnamed and unnamedplus for problem-free
communication with the windows clipboard - inferring from a couple of
archive posts from 2011,12. Including unnamedplus isn't good for the
linux clipboard, though.

If all else fails, the vim-use mailing list is a darned sight more
knowledgeable on vim/windows stuff.

Erik

Re: Flushing all Buffers Before Exiting

[tomas]

On Sun, Mar 24, 2019 at 11:17:54AM -0500, David Wright wrote:
> On Sat 23 Mar 2019 at 18:23:47 (+0100), to...@tuxteam.de wrote:
> > On Sat, Mar 23, 2019 at 10:27:01AM -0500, David Wright wrote:
> > > On Fri 22 Mar 2019 at 17:45:50 (+0100), to...@tuxteam.de wrote:
> > 
> > > Reading the OP's problem, I wonder how you're meant to detect
> > > "any whiff of a problem" [...]
> > 
> > Torture tests.
> 
> Like, multiply the number of sources by stealing a few more radio
> scanners to connect up, which then all burst into life as the
> police scour the neighbourhood for thieves?

Tests require some modeling and phantasy. And some knowledge of
the environment. Otherwise I'd call it "futzing around" -- still
important, but at an earlier stage.

We don't know OP's data sources; for modeling, one should have
a couple of parameters, like expected average bandwidth, expected
peak bandwith wrt interval and so on. For example, if data is
coming in via serial 115kb/s or, say USB (which one?), we'd have
the input bandwith. Knowing something about the process's digestion
would tell us how much output it will produce for a given input.
And so on.

I've been doing some industrial data acquisition stuff. You end
up doing this kind of estimations all the time: you don't want
exceptional conditions to throw your systems into confusion --
you want to have an idea on "how they fail". And then test, test
and test, to know where you made bad assumptions.

"Stealing radio scanners" would be definitely one possibility.
I'd rather try to simulate them in software -- better for the
nerves :-)

For that, you'd have to have an idea about the interface the
radio scanner has to your computer. Serial? (I strongly guess,
but can't know ;-)

We know a bit about the output: "20 to 30 lines per second".
Assuming roughly 60 - 80 chars per line, that'd make 1200 to
2400 char/s, so roughly 12 - 14 kb/s. That's way below of
what a serial interface handles. Pentium 90s did that under
Linux back then, even a bunch of interfaces at a time.

You had to put a bit of care into it, though.

> When dealing with realtime real information coming in, over which you
> have no control, it can be non-trivial to set up such scenarios.
> That's why I thought it best to devise a method that's more
> efficient than line buffering. After all, that's why buffering
> was invented, wasn't it.

Buffering is no magic: it's the tradeoff you have to make between
bandwith, latency and loss granularity (i.e. how much you're willing
to lose, should your "buffering process" fail to work properly).

Also, just saying "buffering" here is confusing, since there are
usually several levels of buffering at work: in the present case
there is

 - in-process buffering (provided by the libraries (here Perl,
   the one you control with $| resp. ->autoflush()) which goes
   the way of the do-do if your process loses control: signal,
   memory corruption, whatnot)

 - OS level buffering (the one controlled with sync and friends),
   which offers somewhat stronger guarantees (because your OS
   kernel --ahem!-- never loses control [1]).

It comes down to understanding what's going on, more or less.
Given the few data points we have, I'm pretty confident in
saying "write away, trust your hardware/OS, but watch out for
possible problems. Make your back-of-the-envelope calculations
and run a few tests to validate them".

Your proposed "catching of signals" sounds elegant, but know that
it'll only protect you during fair weather. For a SIGHUP or
SIGUSR1 it'll be fine, for a SIGSEGV or a SIGILL (which is telling
you that your process might be highly confused: perhaps the
pointer to the buffer you're trying to flush points to something
completely different!) it might be... not that fine. It's a bit
like doing backups: you'd better done that earlier :-D

Cheers

[1] Database folks are a bit more restrictive than that and
   want to perform well even when the OS loses control. One
   can learn quite a bit from them.

-- tomás


signature.asc
Description: Digital signature

apt-cacher errors

[Adam Weremczuk]

Hi all,

On 24th March (last Sunday) I received the following (for the first time):

Subject: Cron test -x /usr/share/apt-cacher/apt-cacher-cleanup.pl && 
/usr/share/apt-cacher/apt-cacher-cleanup.pl

Error: cannot open ../headers/debian_dists_wheezy_Release for locking: No such 
file or directory
Failed to open filehandles for debian_dists_wheezy_Release. Resolve this 
manually.
Exiting to prevent deletion of cache contents.

The above all came from systems originally running wheezy which were upgraded 
to stretch about 2 years ago.

Questions:

1. How to get rid of these errors? I would prefer to avoid spending half a day 
deciphering a chain of Perl scripts which I'm not familiar with.
2. What specifically happened last week to trigger this behavior? Was it e.g. a 
permanent removal of all wheezy repos and references?

Regards,
Adam

Re: installation Debian avec home sur disque dur usb

[Erwann Le Bras]

Le 24/03/2019 à 20:29, hamster a écrit :

Le 24/03/2019 à 20:14, alex.pad...@laposte.net a écrit :


Bonsoir à tous,


Je souhaiterai faire une installation Debian sur un mini-pc avec un
disque dur SSD, Debian sera installé sur le disque SSD tandis que mon
home devra être installer impérativement sur un disque dur usb externe.

Je souhaiterai que mon home soit crypté ou chiffré.

Comment faire tout cela à l'installation du système.


Tout cela est prévu dans l'installeur. Autant le fait de chiffrer que de
séparer le /home sur une partition de ton choix.



Tout à fait : faire une install classique avec le disque externe en 
place pour préciser, au moment du partitionnement (choisir 
"personnalisé) la cible et l'état des partitions.


Bien réfléchir avant car selon le point de montage et la protection mise 
sur le disque externe, le système pourrait ne pas démarrer sans le 
disque externe ou le disque externe pas pouvoir être lu sur un autre 
système.


Erwann

Re: Backuppc et caractères accentués

[Jacques]

Le 25/03/2019 à 09:06, Jacques a écrit :
> 
> ...> Une des façons de procéder avec vi:
> pour passer en mode edition hexadecimal: :%!xxd (en mode commande)
> pour revenir en mode normal: :%!xxd -r
> 
> N'oublie pas de sauvegarder ton fichier de configuration si jamais le remède 
> est pire que le mal
> 
> Bonne journée
> 

Encore plus simple sous vi, charger le fichier et effectuer la conversion 
utf8/iso-8859-1 par:
:set fileencoding=latin1

Re: Backuppc et caractères accentués

[Jacques]

Le 24/03/2019 à 22:36, Migrec a écrit :
> Bonjour,
> 
> Je rencontre un problème avec l'argument BackupFilesExclude 
> 
>  de backuppc.
> Je ne souhaite pas sauvegarder le répertoire Téléchargements mais il est tout 
> de même inclut dans les sauvegardes. Je soupçonne un problème avec les 
> accents.
> 
> Voici le log de backuppc
> 
> incr backup started back to 2019-03-22 15:00:11 (backup #146) for directory 
> /home
> Running: /usr/bin/ssh -q -x -l root skeleton /usr/bin/rsync --server --sender 
> --numeric-ids --perms --owner --group -D --links --hard-links --times 
> --block-size=2048 --recursive . /home/
> Xfer PIDs are now 26881
> Got remote protocol 31
> Negotiated protocol version 28
> Sent exclude: */.local/share/Trash
> Sent exclude: */tmp
> Sent exclude: */T�l�chargements
> Sent exclude: michel/VirtualBox VMs
> Xfer PIDs are now 26881,26882
> 
> J'ai tenté de rajouter  |--iconv=utf8,iso88591 |mais sans succès.
> 
> Une idée ?
> --
> Migrec
> 
> ||

Bonjour,

Je ne sais plu comment j'en suis arrivé là, mais en pratique et ça tombe en 
marche dans ma configuration backuppc, je remplace le caractère é par le 
caractère hexadecimal E9

Une des façons de procéder avec vi:
pour passer en mode edition hexadecimal: :%!xxd (en mode commande)
pour revenir en mode normal: :%!xxd -r

N'oublie pas de sauvegarder ton fichier de configuration si jamais le remède 
est pire que le mal

Bonne journée

Re: text editors

[mick crane]

On 2019-03-25 05:29, Erik Christiansen wrote:

On 25.03.19 04:38, mick crane wrote:
Is there any text editor, preferably in a terminal that has the 
facility to

protect lines in the document, not the document itself ?
I've got 2 blocks of "code" that look similar and I keep editing the 
wrong

one and then it doesn't work.


The only thing I can think of, using vim (haven't used anything else 
for

30 years), is to turn on folding, and include a warning in a comment on
the first line of the block. Whether folding is on blank lines (simple
paragraph/block folding), or foldmethod=marker, the first line line is
displayed while folded.

Having to unfold the block, with only the warning and a short initial
line of code or block identifier visible, ought to be sufficiently
alerting if the blood level in the caffeine stream is not too high.

Putting the warning in "foldtext" wouldn't work, because then it'd
appear on all folded paragraphs - unless you used foldmethod=manual, 
and

only folded the troublesome blocks.

In extremis, you could write a vimscript function to do all sorts of
weird stuff on folding, but I think it would be a bit of work to put a
password on unfolding.

:help folding

Erik

not heard about folding.
I'm not very good at this.
kind of related I'm having difficulty copy and pasting.
If on windows [sorry] and in putty session for Debian no gui vi, if 
highlight text with mouse then it is automatically saved to windows 
clipboard for pasting but then in putty cannot scroll past bottom of 
screen.
If set marks and then yank to other mark text is yanked but is not in 
windows clipboard buffer for pasting.
In visual mode I can highlight all text with go to mark but that is not 
in windows buffer either.
I tried all different commands to try to get text into windows buffer 
but nothing seems to work.

mick
--
Key ID4BFEBB31

Re: amd64 stable netinstall failing repeatedly 'scanning the mirror'

[Sven Hartge]

Rory Campbell-Lange  wrote:
> On 24/03/19, Rory Campbell-Lange (r...@campbell-lange.net) wrote:

>> Hi. I'm stuck in the DC and it's getting cold!
>> 
>> I'm trying to install debian-9.8.0-amd64-netinst.iso using the
>> non-graphical installer. All is fine till I hit the 'configure apt'
>> stage, when it simply hangs at 'scanning the mirror'.
>> 
>> I can still ping the network. I've tried three different mirrors.

> I've found a subtle layer 7 routing problem upstream which seems to be
> the problem.


You mean, you are in the wrong data center, trying to install Debian on
the wrong server?

S!


-- 
Sigmentation fault. Core dumped.

Re: Smokeping et ce de systemd

[Lucas Nussbaum]

On 25/03/19 at 07:24 +0100, BERTRAND Joël wrote:
> Lucas Nussbaum a écrit :
> > 
> > Et quand tu lances smokeping à la main avec /usr/sbin/smokeping
> > --pid-dir=/run/smokeping, où crée-t-il smokeping.pid ?
> > 
> > est-ce que tu peux faire 'systemctl cat smokeping.service' pour vérifier
> > que tu as bien le même contenu que ci-dessus (cad que tu n'as pas
> > d'overrides dans /etc) ?
> 
> Root rayleigh:[/lib/systemd/system] > systemctl cat smokeping.service
> # /lib/systemd/system/smokeping.service
> [Unit]
> Description=Latency Logging and Graphing System
> Documentation=man:smokeping(1)
> file:/usr/share/doc/smokeping/examples/systemd/slave_mode.conf
> After=network.target
> 
> [Service]
> # It would in theory be simpler to run smokeping with the --nodaemon
> option and
> # Type=simple, but smokeping does not work properly when in "slave" mode
> with
> # --nodaemon set.
> Type=forking
> RuntimeDirectory=smokeping
> PIDFile=/run/smokeping/smokeping.pid
> User=smokeping
> Group=smokeping
> StandardError=syslog
> 
> # If you need to run smokeping in slave/master mode, see the example unit
> # override in /usr/share/doc/smokeping/examples/systemd/slave_mode.conf
> ExecStart=/usr/sbin/smokeping --pid-dir=/run/smokeping
> 
> ExecReload=/bin/kill -HUP $MAINPID
> 
> [Install]
> WantedBy=multi-user.target
> Root rayleigh:[/lib/systemd/system] >
> 
>   Ça semble bien être la même chose (petite remarque en passant, le truc
> qui intercepte les scripts SysV me semble lui aussi être une connerie
> sans nom au fonctionnement aléatoire dans le machin systemd, on est bien
> loin du KISS du monde Unix...).
> 
>   Si je lance le daemon à la main :
> Root rayleigh:[/lib/systemd/system] > /usr/sbin/smokeping
> --pid-dir=/run/smokeping
> 
> je récupère un pid dans /run :
> Root rayleigh:[/lib/systemd/system] > ls /run/
> ...
> smokeping.pid
> ...
> 
>   Je pensais naïvement qu'il devait être dans 
> /run/smokeping/smokeping.pid...
> 
>   Même si je crée avant de lancer smokeping un répertoire /run/smokeping,
> je me retrouve avec le pid dans /run/smokeping.pid.

Voila, donc à la fin, c'est un probleme coté smokeping qui ne semble pas
respecter l'option --pid-dir. Rien à voir avec systemd. Je t'invite à
ouvrir un bug sur le paquet smokeping.

Lucas

Re: Smokeping et ce de systemd

[BERTRAND Joël]

Lucas Nussbaum a écrit :
> 
> Et quand tu lances smokeping à la main avec /usr/sbin/smokeping
> --pid-dir=/run/smokeping, où crée-t-il smokeping.pid ?
> 
> est-ce que tu peux faire 'systemctl cat smokeping.service' pour vérifier
> que tu as bien le même contenu que ci-dessus (cad que tu n'as pas
> d'overrides dans /etc) ?

Root rayleigh:[/lib/systemd/system] > systemctl cat smokeping.service
# /lib/systemd/system/smokeping.service
[Unit]
Description=Latency Logging and Graphing System
Documentation=man:smokeping(1)
file:/usr/share/doc/smokeping/examples/systemd/slave_mode.conf
After=network.target

[Service]
# It would in theory be simpler to run smokeping with the --nodaemon
option and
# Type=simple, but smokeping does not work properly when in "slave" mode
with
# --nodaemon set.
Type=forking
RuntimeDirectory=smokeping
PIDFile=/run/smokeping/smokeping.pid
User=smokeping
Group=smokeping
StandardError=syslog

# If you need to run smokeping in slave/master mode, see the example unit
# override in /usr/share/doc/smokeping/examples/systemd/slave_mode.conf
ExecStart=/usr/sbin/smokeping --pid-dir=/run/smokeping

ExecReload=/bin/kill -HUP $MAINPID

[Install]
WantedBy=multi-user.target
Root rayleigh:[/lib/systemd/system] >

Ça semble bien être la même chose (petite remarque en passant, le truc
qui intercepte les scripts SysV me semble lui aussi être une connerie
sans nom au fonctionnement aléatoire dans le machin systemd, on est bien
loin du KISS du monde Unix...).

Si je lance le daemon à la main :
Root rayleigh:[/lib/systemd/system] > /usr/sbin/smokeping
--pid-dir=/run/smokeping

je récupère un pid dans /run :
Root rayleigh:[/lib/systemd/system] > ls /run/
...
smokeping.pid
...

Je pensais naïvement qu'il devait être dans 
/run/smokeping/smokeping.pid...

Même si je crée avant de lancer smokeping un répertoire /run/smokeping,
je me retrouve avec le pid dans /run/smokeping.pid.

Bien cordialement,

JB

Re: text editors

[john doe]

On 3/25/2019 5:38 AM, mick crane wrote:
> Is there any text editor, preferably in a terminal that has the facility
> to protect lines in the document, not the document itself ?
> I've got 2 blocks of "code" that look similar and I keep editing the
> wrong one and then it doesn't work.

Not strictly an answer but I would track the good file for example in Git.
That way, you can always return back to a working state.

$ git checkout -- .

--
John Doe

Re: Flushing all Buffers Before Exiting

[deloptes]

Martin McCormick wrote:

> deloptes  writes:
>> I just wonder why one would do that, but it is again your business.
> 
> In all but a very small handful of countries around the
> world, the hobby of amateur radio exists and it's justification
> for existence is to allow people to self-train as to how
> electronic communication, especially radio, works.  The vast
> majority of radio amateurs do not do destructive things with the
> knowledge they gain but listening to non-amateur communications
> systems and understanding how they work is part of the hobby.
> So, we do things that may seem really strange to those who don't
> look at technology that way.
> 
> Computers fit right in to this hobby also as they are
> part of modern life.
> 
>> Nowdays
>> all of this communication is encrypted and you have virtually no chance
>> listening to this.
> 
> When the day comes in which all radio communications are
> encrypted except for amateur radio where encryption is illegal,
> we will probably stop listening to signals other than amateur
> radio and broadcasting.
> 
> Right now, much is still in the clear.  It may be
> digitally encoded but the coding standards are either to
> improve reception, compress bandwidth or both.  If they are to
> obscure the conversation from eaves-droppers, then the landscape
> gets more complicated regarding the law.
> 

I was thinking it is forbidden for amateur radio, because theywant to listen
to you.

>> In most of the countries it is even illegal, but ok,
>> one
>> can do things for fun anyway - braking the encryption though is close to
>> impossible.
> 
> That is quite true.  some of the encoding schemes involve
> more than one layer of encryption and use 1024-bit keys or
> something similar so a person who doesn't know the key or keys
> involved probably doesn't have enough seconds in his or her
> natural life to break even 1 set of keys much less deal with the
> key-holders changing the keys every hour or so.  There are far
> better ways to spend one's life.
> 

Look at the wikipedia link I shared - it talks about the keys

>> The communication follows well defined protocol, so knowing it, you might
>> be
>> able to read the frames, but the content will remain hidden.
> 
> Quite true.
> 
> In the case of what I am doing, a web site for scanner
> radio enthusiasts published the frequencies and the logical order in
> which they should be entered in to a receiver but the index
> numbers turned out to be wrong due to changes made to the site
> after the information was published.  The control data includes
> the index number for the channel to which a conversation or part
> of one is assigned so one can learn the list by reading the index
> numbers and observing which channels come to life.  This allows
> one to fix the list correctly.  It's like solving a partly
> assembled puzzle.
> 
> Sorry for getting far afield of the original topic.
> 
> Martin  WB5AGZ

Why don't you get the documentation or at least what is publicly available
and solve it?

regards

Re: xorg opengl / intel integrated graphics problem

[deloptes]

t...@t8w.de wrote:

> due to a graphics card change in a few days, which will allow me to
> properly use virtualization, I wanted to check a few things. First check,
> starting the pc without the current dedicated graphics card, failed really
> unexpectedly, because the integrated graphics card of my intel processor
> was not able to load my desktop environment. I did not use this integrated
> card since I assembled my pc, got everything running and installed a
> dedicated graphics card - maybe the Nvidia drivers broke something in the
> meanwhile.
> 

I had similar issue once - I had to remove the nvidia drivers - AFAIR they
come with own OpenGL stuff

> Anyway, trying to fix this, I've found no used drivers for the card and a
> opengl error message in xorg.
> 
> lspci output and xorg logs: https://t8w.de/log.txt
> (my private server, plain text, no logging, tracking nor anything else ;)
> )
> 
> Installing, uninstalling, reinstalling several driver / mesa related
> packages did not help and neither did the handful of threads about the
> same or similar issues, so I'd really appreciate any help.

put together you problems are summerized in following

[ 4.905] (EE) open /dev/dri/card0: No such file or directory
[ 4.905] (WW) Falling back to old probe method for modesetting
[ 4.905] (EE) open /dev/dri/card0: No such file or directory
[ 4.905] (II) Loading sub module "fbdevhw"
[ 4.905] (II) LoadModule: "fbdevhw"
[ 4.905] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 4.906] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 4.906]compiled for 1.19.2, module version = 0.0.2
[ 4.906]ABI class: X.Org Video Driver, version 23.0
[ 4.906] (**) FBDEV(1): claimed PCI slot 0@0:2:0
[ 4.906] (II) FBDEV(1): using default device
[ 4.906] (WW) Falling back to old probe method for vesa
[ 4.906] (EE) Screen 0 deleted because of no matching config section.

[ 4.910] (II) AIGLX: Screen 0 is not DRI2 capable
[ 4.910] (EE) AIGLX: reverting to software rendering
[ 4.935] (EE) AIGLX error: dlopen
of /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so failed
(/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: undefined symbol:
_glapi_tls_Dispatch)
[ 4.935] (EE) GLX: could not load software renderer
[ 4.935] (II) GLX: no usable GL providers found for screen 0

First of all if you have a xorg.conf file - need to remove it (put aside)
dri.so is perhaps from the Nvidia - need to fix it - this is the AIGLX
(OpenGL) or Mesa that comes with NVidia.

I am writing from memory as I do not use NVidia or AMD cards anymore.

regards