How to make dhclient reread its config? (Debian 10)

2020-08-25 Thread Victor Sudakov
Dear Colleagues,

I've made some changes to /etc/dhcp/dhclient.conf, now I need to make
dhclient reread it (and apply the changes to /etc/resolv.conf).

There seems to be no dhclient service in systemd, and I don't find
any info about signalling dhclient with "kill -HUP" etc.

"dhclient -x" or "dhclient -r" bring the network down (I've actually
confirmed that on a test host), and I loathe to risk it on a remote box.
A reboot seems too radical.

Any ideas please?

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
2:5005/49@fidonet http://vas.tomsk.ru/


signature.asc
Description: PGP signature


Re: Get an error when i use new kernel

2020-08-25 Thread stan clay
 I'm sorry, I haven't finished. I sent it by mistake,
 the error log is:

[  26.367633] nvme :01:00.0: AER: PCIe Bus Error:
severity=Corrected, type=Data Link Layer, (Transmitter ID)
[  26.367633] nvme :01:00.0: AER:   device [1e0f:0009] error
status/mask=1000/6000
[  26.367633] nvme :01: AER:  [12]Timeout

i use lspci to search this device(1e0f:0009),and i got the error device is

➜  ~ lspci -nn |grep 0009
01:00.0 Non-Volatile memory controller [0108]: KIOXIA Corporation
Device [1e0f:0009] (rev 01)

the device is my ssd

I searched the Internet for this error and found some similar errors
and solutions, such as in the grub.cfg Riga PCI = ***, etc., but it
doesn't work here. I found that their error reporting devices are
different from mine



stan clay  于2020年8月26日周三 上午10:26写道:

> Yesterday, I upgraded unstable from stable and installed a new kernel, but
> I couldn't get into the system with the new kernel. I got an error
>
>
> [  26.367633] nvme :01:00.0: AER: PCIe Bus Error:
> severity=Corrected, type=Data Link Layer, (Transmitter ID)
> [  26.367633] nvme :01:00.0: AER:   device [1e0f:0009] error
> status/mask=1000/6000
>
>


Get an error when i use new kernel

2020-08-25 Thread stan clay
Yesterday, I upgraded unstable from stable and installed a new kernel, but
I couldn't get into the system with the new kernel. I got an error


[  26.367633] nvme :01:00.0: AER: PCIe Bus Error:
severity=Corrected, type=Data Link Layer, (Transmitter ID)
[  26.367633] nvme :01:00.0: AER:   device [1e0f:0009] error
status/mask=1000/6000


Re: Cannot see a process listening on 127.0.0.1

2020-08-25 Thread Victor Sudakov
Anssi Saari wrote:
> Victor Sudakov  writes:
> 
> > It's different in *BSD which got me confused. In *BSD, even if you bind
> > to INADDR_ANY, you'll see something like this in sockstat output:
> >
> > root dovecot39601 21 tcp4   *:110 *:*
> > root dovecot39601 22 tcp6   *:110 *:*
> > root dovecot39601 23 tcp4   *:995 *:*
> > root dovecot39601 24 tcp6   *:995 *:*
> 
> Well, what about using ss instead of netstat on Linux? I don't seem to
> have any daemon running that would show different with netstat or ss so
> can't check.

Basically the same:

root@test4:~# netstat -lpn | grep 8081
tcp6   0  0 :::8081 :::*LISTEN  
10872/node /home/ad 
root@test4:~# ss -ln | grep 8081
tcpLISTEN 0  128  :::8081 :::*
root@test4:~# 


-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
2:5005/49@fidonet http://vas.tomsk.ru/


signature.asc
Description: PGP signature


Fwd: Updated the Wiki Page to reflect Coronavirus and Events

2020-08-25 Thread Luna Jernberg
-- Forwarded message -
From: Luna Jernberg 
Date: Tue, Aug 25, 2020 at 11:28 PM
Subject: Updated the Wiki Page to reflect Coronavirus and Events
To: droidbittin , debian-nordic <
debian-nor...@lists.debian.org>, SmartList <
debian-security-announce-requ...@lists.debian.org>, debian-dug-nordic <
debian-dug-nor...@lists.debian.org>, , Debian
SE , debian-user-danish <
debian-user-dan...@lists.debian.org>, , <
debian-user-finn...@lists.debian.org>


Hello!

I got tasked with updating the Wiki page during todays meeting during
Debconf20 Online so i did it: https://wiki.debian.org/DebianEvents/Nordic
if something thinks it should say something else feel free to let me know
via email


Updated the Wiki Page to reflect Coronavirus and Events

2020-08-25 Thread Luna Jernberg
Hello!

I got tasked with updating the Wiki page during todays meeting during
Debconf20 Online so i did it: https://wiki.debian.org/DebianEvents/Nordic
if something thinks it should say something else feel free to let me know
via email


Updated the Wiki Page to reflect Coronavirus and Events

2020-08-25 Thread Luna Jernberg
Hello!

I got tasked with updating the Wiki page during todays meeting during
Debconf20 Online so i did it: https://wiki.debian.org/DebianEvents/Nordic
if something thinks it should say something else feel free to let me know
via email


Signal [Was:] Re: Encrypt files on Linux, decrypt on Windows

2020-08-25 Thread Celejar
On Sun, 23 Aug 2020 14:03:21 +0300
Andrei POPESCU  wrote:

> On Vi, 21 aug 20, 13:07:56, Charles Curley wrote:
> > On Fri, 21 Aug 2020 13:31:00 -0500
> > Paul Johnson  wrote:
> > 
> > > GnuPG.  It's in Debian, there's Windows versions on its website, and
> > > it's not some mystery box like Signal.
> > 
> > ++
> > 
> > It also has the advantage that the cryptext will stay encrypted on any
> > intermediate servers. WhatsApp and Signal claim their traffic is, but
> > one must take their word for it.
> 
> Signal is free and open source software.
> 
> Please do feel free to inspect the source code for potential back doors 
> or vulnerabilities.

I do use Signal on mobile, and I want to like it, but there are a few
things about it that just really bother me (these may not be relevant
to the OPs situation):

1) The requirement of associating accounts with (real, working) phone
numbers.

2) The (current) refusal [1] to provide an option to export messages
into a format easily accessible by the user. (I know, I can read and
try to understand Signal's code, and then write my own decryptor -
thanks, Signal).

3) The strong encouragement of the use of Google's Play Store to install
the mobile app, and the strong discouragement of other, FLOSS
compatible, methods of installation. [2]

Discussion of these and many other issues with Signal: [3]

I'm just a user, and not a very advanced one at that, but I can't get
away from the feeling that Signal is somewhat user-hostile, with an
attitude of "Trust us - Moxie is a legend, our code is great (and
FLOSS), and we really care." All true, to be sure, but still.

[1] https://github.com/signalapp/Signal-Android/issues/7586
[2] https://signal.org/android/apk/
[3] https://github.com/privacytools/privacytools.io/issues/779

Celejar



Re: Homebuilt NAS: System Drive Filesystem?

2020-08-25 Thread Patrick Bartek
On Tue, 25 Aug 2020 09:37:20 +0300
Andrei POPESCU  wrote:

> On Lu, 24 aug 20, 09:26:57, Patrick Bartek wrote:
> > 
> > Since F2FS is not supported directly for an install, one would have to
> > convert to it after or configure the flash drive with another computer
> > before the install. I don't know if it is worth the time to do so.
> > EXT4 without journaling would be easier.  
> 
> The journal is written to only if the filesystem is written to as well.  

Yes, and every time a log is written to, too.  On my main system,
normal usage, journaling on, I'm getting hard drive activity about 2 to
3 times a minute 24/7/365. And currently, I have firewall logging off
which was writing to log every 2 seconds or so.  The two Roku devices I
have, for some reason, were trying to access this computer, but no
others.  Don't know why.

Some have suggested to remount / read-only, but since my plan is not to
have a separate /home partition, that would cause problems. Probably
will cause problems even if I do.

However, the NAS software I plan to use (OpenMediaVault) has a
specific plugin if you're using solid state devices for the system
and/or DATA drives.  Don't know exactly what it does, or whether it's a
binary or an executable script.  Guess I'll have to wait until I get to
the point of installing it to see what it does.  No details are given
in OMV's docs.
 
> Without having any other data than my own, admittedly limited, 
> experience[1] it doesn't seem worth disabling the journal, it is only 
> written when the filesystem is written to as well anyway.

At least the flash drive I'm using has wear leveling.  And I'm going to
leave about 15% of it unpartitioned to be safe. Plus, clone it, so if
it goes down, I just plug in the clone and I'm up and running.

> [1] all my current systems are running from SD cards, with the only 
> optimisation being to not configure any swap.

Thanks for your input.

B



Re: Comment interdire certains sites web à un utilisateur donné ou limiter le temps d'utilisation ?

2020-08-25 Thread Michel Memeteau - EKIMIA
Le lun. 24 août 2020 à 16:22, Olivier  a écrit :

>
> Le lun. 24 août 2020 à 14:51, Michel Memeteau - EKIMIA  a
> écrit :
>
>> Pour le temps d'utilisation : https://doc.ubuntu-fr.org/timekpr  (
>> version next )
>>
>
> timekpr-next n'est empaqueté que pour Bullseyes
> Ses dépendances telles qu'elles sont listées dans Bulleyes, existent dans
> des versions "très proches" dans Buster.
>

La version pour Focal fonctionnera très bien sur buster
https://launchpad.net/~mjasnik/+archive/ubuntu/ppa?field.series_filter=focal


Re: AMD Radeon(TM) R2 en Jessie

2020-08-25 Thread Julián Daich




El 23/8/20 a las 17:13, Camaleón escribió:

Para que DKMS haga su trabajo, necesitas el controlador Catalyst y el
kernel que hay disponible en los repos de Debian. Es decir, que si no
hay paquete .deb de Catalyst en los repos para tu versión de Debian,
aunque tengas DKMS y el kernel de Debian no va a funcionar si instalas
el controladors de AMD-ATI desde otra fuente (p. ej., el controladora
que ofrece el fabricante desde su web.



Hola,

Tengo que ver si hay forma de instalar el controlador de Jessie en 
Strecht. Solo sería posible si en Strecht hay un núcleo compatible.



De hecho, DKMS no es necesario para esto. Recuerdo que en su momento
tenía instalado el controlador propetario de nvidia (que estaba
disponible en los repos de Debian non-oss), y el kernel de Debian, sin
más, y esta combinación funcionaba sin problemas y son tener instalado
el paquete DKMS.



Seguramente porque lo hiciste a través de m-a




https://packages.debian.org/jessie/fglrx-driver

Lo que ya no tienes es el driver para versiones superiores (9 y
posteriores).



Dicen hay que lo probaron hasta el núcleo 4.2. Siguiendo lo de más 
arriba hay que ver lo que se puede llegar a hacer en Strecht.




Mucha gente desconoce que una LiveCD te permite instalar paquetes. Eso
sí, no puedes reiniciar el sistema o perderás todo lo que hayas hecho,
paquetes instalados incluído. Con una LiveUSB sí podrás instalar
paquetes en la llave USB y reiniciar manteniendo los cambios, sin
problemas. 


Hay que convertir a la llave USB en persistente solo, asegurarse de que 
hay un GB libre e instalar los componentes privativos antes. Ya bajé la 
imagen. Es tarea para el fin de semana.



Es una forma de probar cosas sin tocar el sistema instalado,
yo siempre cargo una LiveCD en mis equipos antes de instalar una nueva
versión de Debian, y así anticipo posibles problemas con los componentes
que tengo instalados.



Ojalá funcionara siempre eso. De momento el plan de pruebas es el 
siguiente. Instalar en la imagen el núcleo más bajo posible.


1. deb de los repsoitorios Jessie
2. deb de ATI
3. probar si se puede con m-a
4. compilar el binario de ATI
5. Compilar por mi mismo un núcleo y probar lo de arriba.

Saludos,

Julián
--
Julian Daich 



Re: Modification user 1000

2020-08-25 Thread Alain Vaugham
Le Mon, 24 Aug 2020 14:07:10 +0200,
Patrick ZAJDA  a écrit :

> Donc c'est certain, c'est toujours plus confortable de le faire juste 
> après sa création ; sauf que c'est rarement juste après la création d'un 
> utilisateur qu'on a besoin de modifier son nom d'utilisateur ou son 
> home, ça ne serait pas aussi amusant sinon.
[...]
> Dans le même genre, récemment j'ai eu à modifier l'UID et le GID d'un 
> utilisateur, et le GID du groupe du coup histoire de m'éviter quelques 
> tracas avec NFS.


Le user 1000 est le premier compte installé. Je ne déplace jamais ce
user ni ne l'utilise.
Je créé les users à la demande.

Si je dois modifier/déplacer les UID/GID d'un user ce n'est jamais le user 1000
et c'est toujours à la main.
Pour les montages NFS j'ai l'impression de mieux maîtriser les UID.

Pour l'instant je n'ai rencontré aucun soucis après de telles
modifications. 

-- 
Alain Vaugham
Clef GPG : 0xDB77E054673ECFD2



Re: Cannot see a process listening on 127.0.0.1

2020-08-25 Thread Anssi Saari
Victor Sudakov  writes:

> It's different in *BSD which got me confused. In *BSD, even if you bind
> to INADDR_ANY, you'll see something like this in sockstat output:
>
> root dovecot39601 21 tcp4   *:110 *:*
> root dovecot39601 22 tcp6   *:110 *:*
> root dovecot39601 23 tcp4   *:995 *:*
> root dovecot39601 24 tcp6   *:995 *:*

Well, what about using ss instead of netstat on Linux? I don't seem to
have any daemon running that would show different with netstat or ss so
can't check.




Re: Comment interdire certains sites web à un utilisateur donné ou limiter le temps d'utilisation ?

2020-08-25 Thread Olivier
Le lun. 24 août 2020 à 20:46, Klaus Becker  a écrit :

>
> Salut,
>
> CTparental, facile à trouver avec une recherche sur le web
>
> Klaus
>
> En effet, CTparental a l'air pas mal du tout et dispo sur Debian Buster.
Merci beaucoup pour l'info !


Re: Comment interdire certains sites web à un utilisateur donné ou limiter le temps d'utilisation ?

2020-08-25 Thread Olivier
Le lun. 24 août 2020 à 18:32, Erwann Le Bras  a
écrit :

> bonsoir
>
> Attention, vu pendant le confinement, certaines ressources pédagogiques
> sont sur Youtube, tout n'est pas sur Lumni.  ..
>
C'est bien le problème: si lesdites ressources étaient "importées" sur les
sites web pédagogiques, ceux-ci agissant comme une sorte de proxy, il
suffirait de n'autoriser que ces sites web pédagogiques ce qui me paraît
infiniment plus simple à gérer
("entre 8h et 18h, du lundi au vendredi, seul le site web du collège est
autorisé").

Mais bon, ça n'est malheureusement pas le cas ...


Re: Homebuilt NAS: System Drive Filesystem?

2020-08-25 Thread Andrei POPESCU
On Lu, 24 aug 20, 09:26:57, Patrick Bartek wrote:
> 
> Since F2FS is not supported directly for an install, one would have to
> convert to it after or configure the flash drive with another computer
> before the install. I don't know if it is worth the time to do so.
> EXT4 without journaling would be easier.

The journal is written to only if the filesystem is written to as well.  

Without having any other data than my own, admittedly limited, 
experience[1] it doesn't seem worth disabling the journal, it is only 
written when the filesystem is written to as well anyway.

[1] all my current systems are running from SD cards, with the only 
optimisation being to not configure any swap.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature