Re: [Stretch] Fix for not network after installing without desktop

[RavenLX]

On 06/26/2017 08:24 AM, Greg Wooledge wrote:
[snip]


If I had to guess, I would guess that the OP's system is a laptop, and
the OP is attempting to use a wireless network of some kind.  There may
be setups where n-m handles wireless stuff particularly well.


You guessed right. I am sorry I didn't think to add those details 
because I (probably wrongly) assumed it was something that just happens. 
I also had this issue with two laptops: A 10-yr. old Lenovo/IBM ThinkPad 
T61 and a newer (I think about 4 or 5 yrs - forgot how old) HP Pavilion 
g7 2010-nr laptop. Both installing via WiFi using the firmware 
(non-free) install DVD (and no other DVDs). I was installing off a USB 
drive on both.


When I wrote the post, I assumed that it would do that because I was 
installing without a Desktop. I hadn't realized that maybe other factors 
may have been the reason.

Re: [Stretch] Fix for not network after installing without desktop

[RavenLX]

On 06/24/2017 03:33 PM, Brian wrote:

On Sat 24 Jun 2017 at 11:07:13 +0200, Erwan David wrote:


Le 06/24/17 à 04:43, RavenLX a écrit :

I want to share with everyone a fix for not getting network / internet
if you're installing Debian without a desktop (ie. not selecting a
desktop AND Unchecking the Debian Desktop Environment option).

If you install as I mentioned above and reboot, you get the command
prompt to log into (which is what I wanted so I could install minimal
KDE as I mentioned in another post). However, you can NOT get on the
internet! Even though the installer used the internet and set it up, the
settings won't stick. That's because the installer doesn't install
network-manager into the system!


Do you mean that network-manager is compulsory in stretch ? Impossible
to use a fixed configuration in /etc/network/interfaces or another
connection manager like wicd ?


The OP is particularly drawing attention to a situation which could
possibly occur when *Debian is installed*. Unfortunately, although one
of the conditions under which the installation was done (no selection
of a DE) is stated, the complete situation is not described. This
reduces the usefulness of the suggested fix.



My Bad: I was installing no DE *and* via WiFi (not cable) connection on 
a 10 yr. old laptop.

Re: [Stretch] Fix for not network after installing without desktop

[RavenLX]

On 06/24/2017 06:44 AM, Brian wrote:

On Fri 23 Jun 2017 at 22:43:40 -0400, RavenLX wrote:


I want to share with everyone a fix for not getting network / internet if
you're installing Debian without a desktop (ie. not selecting a desktop AND
Unchecking the Debian Desktop Environment option).

If you install as I mentioned above and reboot, you get the command prompt
to log into (which is what I wanted so I could install minimal KDE as I
mentioned in another post). However, you can NOT get on the internet! Even
though the installer used the internet and set it up, the settings won't
stick. That's because the installer doesn't install network-manager into the
system!

So what I do to get around this and get the network settings to "stick" when
rebooting:

1. When installing, at the screen that says to remove media and reboot, DO
NOT do this yet! Do not press Continue either.

2. CTRL+ALT+F3 (or some function key) to get to a terminal. Press ENTER to
activate the terminal.

3. Execute this: apt-install network-manager


3. Backup the interfaces file in /target/etc/network

[Snip]


6. Click "Continue" in the GUI installer to finish up.


Log into the command prompt and restore the interfaces file and use
ifup.



I tried using ifup and also tried to edit the interfaces file and it 
didn't seem to work for me. I gave up and decided to do it within the 
installer terminal mode. Seemed a bit easier.

Re: [Stretch] Fix for not network after installing without desktop

[RavenLX]

On 06/24/2017 05:38 AM, Brian wrote:

On Fri 23 Jun 2017 at 22:43:40 -0400, RavenLX wrote:


I want to share with everyone a fix for not getting network / internet if
you're installing Debian without a desktop (ie. not selecting a desktop AND
Unchecking the Debian Desktop Environment option).

If you install as I mentioned above and reboot, you get the command prompt
to log into (which is what I wanted so I could install minimal KDE as I
mentioned in another post). However, you can NOT get on the internet! Even
though the installer used the internet and set it up, the settings won't
stick. That's because the installer doesn't install network-manager into the
system!


Installing over a cabled connection gives a stanza in /e/n/i which
sticks. It is a bug if it doesn't. It is possible you have not
mentioned a crucial aspect of the way you installed.


You're right. I didn't. I was installing using WiFi (too much 
trouble/bending, etc. to plug in a friggen cable! :D )

Re: [Stretch] Fix for not network after installing without desktop

[RavenLX]

On 06/24/2017 04:01 AM, Curt wrote:

On 2017-06-24, RavenLX  wrote:


3. Execute this: apt-install network-manager



Is that right? Or is it not rather "apt install" without the hyphen (I'm
still Wheezing so I'm unsure).


Yes. There's no 'apt-get' when you are going into the terminal from the 
installer. I looked in the usual 'bin' directories and this is what I 
found. 'apt-install' with hyphen is what works.

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

[Henrique de Moraes Holschuh]

(updates, hopefully the last ones...)

On Sun, 25 Jun 2017, Henrique de Moraes Holschuh wrote:
> Fast-forward a few months, and Mark Shinwell noticed the mention of a
> possible fix for a microcode defect with unknown hit-ratio in the
> intel-microcode package changelog.  He matched it to the issues the
> OCaml community were observing, verified that the microcode fix indeed
> solved the OCaml issue, and contacted the Debian maintainer about it.

There are a few factual incorrections in the advisory text, which were
entirely my fault, and for which I apologise.  The corrections are
below:

1. It was one of the OCaml bug reporters (by the handle of ygrek) who
   first noticed that the 20170511 microcode update could be relevant,
   and not Mark Shinwell.

2. Various other bug reporters and OCaml developers, some under request
   from Mark and some by their own volition, helped out and devoted
   substantial time to investigating the issue.

I apologise to those involved: to "ygrek" for misreading the bug report
and attributing to Mark Shinwell the correlation between the SKL150
erratum description and the OCaml compiler issue report; and to all
members of the OCaml community that worked on the issue both in the bug
report and behind the scenes, for not explicitly crediting their effort.

The original OCaml bug report is listed in the references section at the
end of the advisory (and also in this update).

> Related processor signatures and microcode revisions:
> Skylake   : 0x406e3, 0x506e3 (fixed in revision 0xb9/0xba and later,
>   public fix in linux microcode 20170511)
> Skylake   : 0x50654  (no information, erratum listed)
> Kaby Lake : 0x806e9, 0x906e9 (defect still exists in revision 0x48,
>   fix available as a BIOS/UEFI update)

The recently launched "Kaby Lake-X" processors (signature 0x906e9,
socket LGA2066) are documented by Intel as *NOT* being affected by the
KBL095 defect.  This information comes from table 16 of the latest
revision of the "7th gen. Core Family specification update" (which is
listed in the references section).

Please note that the "7th gen. Core i7 X-series processors" (Kaby
Lake-X) both support hyper-threading and share the processor signature
(family, model number and stepping) with "Kaby Lake-H/S" processors.
The tests in the advisory (and also the perl script) will *incorrectly*
report Kaby Lake-X processors as affected.

References:
https://caml.inria.fr/mantis/view.php?id=7452
http://metadata.ftp-master.debian.org/changelogs/non-free/i/intel-microcode/unstable_changelog
https://www.intel.com/content/www/us/en/processors/core/desktop-6th-gen-core-family-spec-update.html
https://www.intel.com/content/www/us/en/processors/core/7th-gen-core-family-spec-update.html
https://www.intel.com/content/www/us/en/processors/xeon/xeon-e3-1200v6-spec-update.html
https://www.intel.com/content/www/us/en/processors/xeon/xeon-e3-1200v5-spec-update.html
https://www.intel.com/content/www/us/en/products/processors/core/6th-gen-x-series-spec-update.html

-- 
  Henrique Holschuh

Re: debian8 y vlan en mikrotik

[Cristian Mitchell]

El 26 de junio de 2017, 20:17, Dixan Rivas escribió:

>
>
> El 26/06/17 a las 23:39, Cristian Mitchell escribió:
>
>
>
> El 26 de junio de 2017, 19:07, Dixan Rivas escribió:
>
>>
>>
>> El 26/06/17 a las 22:23, Cristian Mitchell escribió:
>>
>>
>>
>> El 26 de junio de 2017, 15:14, Ariel Alvarez
>> escribió:
>>
>>>
>>> El 26-06-17 12:33, Cristian Mitchell escribió:
>>>
>>>
>>>
>>> El 26 de junio de 2017, 12:25, JAP
>>> escribió:
>>>
 El 26/06/17 a las 11:08, Ariel Alvarez escribió:


> El 26-06-17 9:38, JAP escribió:
>
>> El 26/06/17 a las 09:51, Ariel Alvarez escribió:
>>
>>> no me da red
>>>
>>
>> ¿Cómo está configurado el swtich? ¿Como enrutador? ¿Como switch?
>> ¿Quién asigna dirección IP, por dhcp o estáticas?
>> ¿Qué dice tu /etc/network/interfaces?
>>
>> JAP
>>
>>
>> -
>> Consejo Nacional de Casas de Cultura
>> http://www.casasdecultura.cult.cu
>>
>
> gracias amigo por contestar:
>
> el switch actua como switch solo que en su gestion agrupa una x
> cantidad
> de puertos fisicos los cuales responden a una vlan creada por mikrotik
> entre esos puertos fisicos iria el punto de red perteneciente al
> servidor debian el cual no me funciona de esa forma.
>
> las direcciones ip se asignan de modo estatico no estamos usando dhcp
>
> pego lo que contiene /etc/network/interfaces referente a la interface
> en
> cuestion, aclaro ademas que no tengo mas ninguna interface solo figura
> en este archivo lo relacionado con (lo)
> auto eth0
> allow-hotplug eth0
> iface eth0 inet static
> address 10.20.48.2
> netmask 255.255.255.128
> network 10.20.48.129
> broadcast 10.20.48.255
> gateway 10.20.28.129  (esta es la ip del equipo que tiene
> mikrotik ademas)
>

>>> No estoy muy seguro de como expresarlo pero tendrías que leer sobre
>>> TCP/IP
>>> la configuración tiene errores de concepto
>>>
>>> netmask 255.255.255.128 te da un rango de 1 a 126
>>> o sea
>>> gateway 10.20.28.129 esta en otra red
>>> por ultimo el
>>> broadcast 10.20.48.255
>>> no es este es
>>> 10.20.48.127
>>>
>>> si tenes dudas usa la aplicación ipcalc
>>>
>>>
>>>

> como datos adicional todos los equipos pertenecientes a esa vlan se
> encuentran en el mismo segmento como es logico, otro dato curioso que
> olvide mencionar anteriormente, en mikrotik aparece reflejado el equipo
> con debian puesto como debe ir es decir en el punto de red
> perteneciente
> a la vlan del switch pero este aparece y se va es como intermitente,
> esto sucede poniendolo en cualquier punto del switch declarados para
> esa
> vlan. tengo ademas iptables en debian pero descarto la posibilidad que
> sea este el del problema pues ya he probado con un debian en limpio sin
> ningun iptables.
>
> una vez mas gracias por su acostumbrada ayuda.
>
>
> -
> Consejo Nacional de Casas de Cultura
> http://www.casasdecultura.cult.cu
>
>


 Realmente, no entiendo cómo está armada la red.
 No me cierran las direcciones del enmascaramiento y la red,
 considerando las correspondientes a la dirección de la máquina y la
 pasarela.
 Si yo tuviese que armarla, lo haría así:

 auto eth0
 allow-hotplug eth0
 iface eth0 inet static
 address 10.20.48.2
 netmask 255.255.0.0
 broadcast 10.20.48.255
 gateway 10.20.28.129

 La opción "network" está de más.

 Por otro lado, algo que SIEMPRE genera problemas cuando uno arma una
 red estática, es network-manager.

 Asegurate que NO esté instalado con
 # dpkg -l network-manager*

 Si lo está, elimina todo con
 # apt-get purge network-manager*

 Prueba con eso.

 Luego, manda la salida del comando
 # route

 JAP


>>>
>>>
>>> --
>>> MrIX
>>> Linux user number 412793.
>>> http://counter.li.org/
>>>
>>> las grandes obras,
>>> las sueñan los santos locos,
>>> las realizan los luchadores natos,
>>> las aprovechan los felices cuerdo,
>>> y las critican los inútiles crónicos,
>>>
>>> a ver disculpen es que la config la copie a mano y al parecer se me fue
>>> ese error en realidad seria 10.20.48.129, a ver aclaro una vez mas si ese
>>> fuera el caso que la configuracion tuviera algun error no pudiera verse al
>>> conectar el debian punto a punto con un windows, ni siquiera tampoco
>>> funcionara el puente como lo esta haciendo ahora, pido disculpas por el
>>> error.
>>>
>>> la config seria esta:
>>>
>>> auto eth0
>>> allow-hotplug eth0
>>> iface eth0 inet static
>>> 

Re: How did you update to stretch?

[Fungi4All]

> On 27/06/17 05:39, Brian wrote:
>> It was. I am a creature of habit. I still reboot between upgrade and
>> dist-upgrade when I eventually upgrade a machine from one distribution
>> to another.

When one uses synaptic there is reload (update) and upgrade, it does not 
distinguish
between dist and non-dist upgrade. I assume it is dist-upgrade. So if synaptic 
has a new
edition (which I assume its dependencies may have been updated) it sounds wise 
to
upgrade it alone (w/ dependencies) and then restart it and run the upgrade.
Would these be correct assumptions? In most cases I use apt, and synaptic when 
I am
searching for a useful package, due to descriptions, snapshots, etc.

Re: debian8 y vlan en mikrotik

[Dixan Rivas]

El 26/06/17 a las 23:39, Cristian Mitchell escribió:
>
>
> El 26 de junio de 2017, 19:07, Dixan Rivas > escribió:
>
>
>
> El 26/06/17 a las 22:23, Cristian Mitchell escribió:
>>
>>
>> El 26 de junio de 2017, 15:14, Ariel Alvarez> > escribió:
>>
>>
>> El 26-06-17 12:33, Cristian Mitchell escribió:
>>>
>>>
>>> El 26 de junio de 2017, 12:25,
>>> JAP>> > escribió:
>>>
>>> El 26/06/17 a las 11:08, Ariel Alvarez escribió:
>>>
>>>
>>> El 26-06-17 9:38, JAP escribió:
>>>
>>> El 26/06/17 a las 09:51, Ariel Alvarez escribió:
>>>
>>> no me da red
>>>
>>>
>>> ¿Cómo está configurado el swtich? ¿Como
>>> enrutador? ¿Como switch?
>>> ¿Quién asigna dirección IP, por dhcp o estáticas?
>>> ¿Qué dice tu /etc/network/interfaces?
>>>
>>> JAP
>>>
>>>
>>> 
>>> -
>>> Consejo Nacional de Casas de Cultura
>>> http://www.casasdecultura.cult.cu
>>> 
>>>
>>>
>>> gracias amigo por contestar:
>>>
>>> el switch actua como switch solo que en su gestion
>>> agrupa una x cantidad
>>> de puertos fisicos los cuales responden a una vlan
>>> creada por mikrotik
>>> entre esos puertos fisicos iria el punto de red
>>> perteneciente al
>>> servidor debian el cual no me funciona de esa forma.
>>>
>>> las direcciones ip se asignan de modo estatico no
>>> estamos usando dhcp
>>>
>>> pego lo que contiene /etc/network/interfaces
>>> referente a la interface en
>>> cuestion, aclaro ademas que no tengo mas ninguna
>>> interface solo figura
>>> en este archivo lo relacionado con (lo)
>>> auto eth0
>>> allow-hotplug eth0
>>> iface eth0 inet static
>>> address 10.20.48.2
>>> netmask 255.255.255.128
>>> network 10.20.48.129
>>> broadcast 10.20.48.255
>>> gateway 10.20.28.129  (esta es la ip del
>>> equipo que tiene
>>> mikrotik ademas)
>>>
>>>
>>> No estoy muy seguro de como expresarlo pero tendrías que
>>> leer sobre TCP/IP
>>> la configuración tiene errores de concepto
>>>  
>>> netmask 255.255.255.128 te da un rango de 1 a 126
>>> o sea
>>> gateway 10.20.28.129 esta en otra red
>>> por ultimo el
>>> broadcast 10.20.48.255
>>> no es este es
>>> 10.20.48.127
>>>
>>> si tenes dudas usa la aplicación ipcalc
>>>
>>>  
>>>
>>>
>>> como datos adicional todos los equipos
>>> pertenecientes a esa vlan se
>>> encuentran en el mismo segmento como es logico, otro
>>> dato curioso que
>>> olvide mencionar anteriormente, en mikrotik aparece
>>> reflejado el equipo
>>> con debian puesto como debe ir es decir en el punto
>>> de red perteneciente
>>> a la vlan del switch pero este aparece y se va es
>>> como intermitente,
>>> esto sucede poniendolo en cualquier punto del switch
>>> declarados para esa
>>> vlan. tengo ademas iptables en debian pero descarto
>>> la posibilidad que
>>> sea este el del problema pues ya he probado con un
>>> debian en limpio sin
>>> ningun iptables.
>>>
>>> una vez mas gracias por su acostumbrada ayuda.
>>>
>>>
>>> 
>>> -
>>> Consejo Nacional de Casas de Cultura
>>> http://www.casasdecultura.cult.cu
>>> 
>>>
>>>
>>>
>>>
>>> Realmente, no entiendo cómo está armada la red.
>>> No me cierran las direcciones del enmascaramiento y la
>>> red, considerando las correspondientes a la dirección de
>>> la máquina y la pasarela.
>>> Si yo tuviese que armarla, lo haría así:
>>>
>>> auto eth0
>>> allow-hotplug eth0
>>> iface eth0 inet static
>>> address 10.20.48.2
>>> netmask 255.255.0.0

Re: debian8 y vlan en mikrotik

[Cristian Mitchell]

El 26 de junio de 2017, 19:07, Dixan Rivas escribió:

>
>
> El 26/06/17 a las 22:23, Cristian Mitchell escribió:
>
>
>
> El 26 de junio de 2017, 15:14, Ariel Alvarez escribió:
>
>>
>> El 26-06-17 12:33, Cristian Mitchell escribió:
>>
>>
>>
>> El 26 de junio de 2017, 12:25, JAP
>> escribió:
>>
>>> El 26/06/17 a las 11:08, Ariel Alvarez escribió:
>>>
>>>
 El 26-06-17 9:38, JAP escribió:

> El 26/06/17 a las 09:51, Ariel Alvarez escribió:
>
>> no me da red
>>
>
> ¿Cómo está configurado el swtich? ¿Como enrutador? ¿Como switch?
> ¿Quién asigna dirección IP, por dhcp o estáticas?
> ¿Qué dice tu /etc/network/interfaces?
>
> JAP
>
>
> -
> Consejo Nacional de Casas de Cultura
> http://www.casasdecultura.cult.cu
>

 gracias amigo por contestar:

 el switch actua como switch solo que en su gestion agrupa una x cantidad
 de puertos fisicos los cuales responden a una vlan creada por mikrotik
 entre esos puertos fisicos iria el punto de red perteneciente al
 servidor debian el cual no me funciona de esa forma.

 las direcciones ip se asignan de modo estatico no estamos usando dhcp

 pego lo que contiene /etc/network/interfaces referente a la interface en
 cuestion, aclaro ademas que no tengo mas ninguna interface solo figura
 en este archivo lo relacionado con (lo)
 auto eth0
 allow-hotplug eth0
 iface eth0 inet static
 address 10.20.48.2
 netmask 255.255.255.128
 network 10.20.48.129
 broadcast 10.20.48.255
 gateway 10.20.28.129  (esta es la ip del equipo que tiene
 mikrotik ademas)

>>>
>> No estoy muy seguro de como expresarlo pero tendrías que leer sobre TCP/IP
>> la configuración tiene errores de concepto
>>
>> netmask 255.255.255.128 te da un rango de 1 a 126
>> o sea
>> gateway 10.20.28.129 esta en otra red
>> por ultimo el
>> broadcast 10.20.48.255
>> no es este es
>> 10.20.48.127
>>
>> si tenes dudas usa la aplicación ipcalc
>>
>>
>>
>>>
 como datos adicional todos los equipos pertenecientes a esa vlan se
 encuentran en el mismo segmento como es logico, otro dato curioso que
 olvide mencionar anteriormente, en mikrotik aparece reflejado el equipo
 con debian puesto como debe ir es decir en el punto de red perteneciente
 a la vlan del switch pero este aparece y se va es como intermitente,
 esto sucede poniendolo en cualquier punto del switch declarados para esa
 vlan. tengo ademas iptables en debian pero descarto la posibilidad que
 sea este el del problema pues ya he probado con un debian en limpio sin
 ningun iptables.

 una vez mas gracias por su acostumbrada ayuda.


 -
 Consejo Nacional de Casas de Cultura
 http://www.casasdecultura.cult.cu


>>>
>>>
>>> Realmente, no entiendo cómo está armada la red.
>>> No me cierran las direcciones del enmascaramiento y la red, considerando
>>> las correspondientes a la dirección de la máquina y la pasarela.
>>> Si yo tuviese que armarla, lo haría así:
>>>
>>> auto eth0
>>> allow-hotplug eth0
>>> iface eth0 inet static
>>> address 10.20.48.2
>>> netmask 255.255.0.0
>>> broadcast 10.20.48.255
>>> gateway 10.20.28.129
>>>
>>> La opción "network" está de más.
>>>
>>> Por otro lado, algo que SIEMPRE genera problemas cuando uno arma una red
>>> estática, es network-manager.
>>>
>>> Asegurate que NO esté instalado con
>>> # dpkg -l network-manager*
>>>
>>> Si lo está, elimina todo con
>>> # apt-get purge network-manager*
>>>
>>> Prueba con eso.
>>>
>>> Luego, manda la salida del comando
>>> # route
>>>
>>> JAP
>>>
>>>
>>
>>
>> --
>> MrIX
>> Linux user number 412793.
>> http://counter.li.org/
>>
>> las grandes obras,
>> las sueñan los santos locos,
>> las realizan los luchadores natos,
>> las aprovechan los felices cuerdo,
>> y las critican los inútiles crónicos,
>>
>> a ver disculpen es que la config la copie a mano y al parecer se me fue
>> ese error en realidad seria 10.20.48.129, a ver aclaro una vez mas si ese
>> fuera el caso que la configuracion tuviera algun error no pudiera verse al
>> conectar el debian punto a punto con un windows, ni siquiera tampoco
>> funcionara el puente como lo esta haciendo ahora, pido disculpas por el
>> error.
>>
>> la config seria esta:
>>
>> auto eth0
>> allow-hotplug eth0
>> iface eth0 inet static
>> address 10.20.48.2
>> netmask 255.255.255.128
>> network 10.20.48.129
>> broadcast 10.20.48.255
>> gateway 10.20.48.129
>> -
>> Consejo Nacional de Casas de Cultura http://www.casasdecultura.cult.cu
>>
>
> Insisto pertenecen a dos redes 

Re: debian8 y vlan en mikrotik

[Dixan Rivas]

El 26/06/17 a las 22:23, Cristian Mitchell escribió:
>
>
> El 26 de junio de 2017, 15:14, Ariel Alvarez > escribió:
>
>
> El 26-06-17 12:33, Cristian Mitchell escribió:
>>
>>
>> El 26 de junio de 2017, 12:25, JAP> > escribió:
>>
>> El 26/06/17 a las 11:08, Ariel Alvarez escribió:
>>
>>
>> El 26-06-17 9:38, JAP escribió:
>>
>> El 26/06/17 a las 09:51, Ariel Alvarez escribió:
>>
>> no me da red
>>
>>
>> ¿Cómo está configurado el swtich? ¿Como enrutador?
>> ¿Como switch?
>> ¿Quién asigna dirección IP, por dhcp o estáticas?
>> ¿Qué dice tu /etc/network/interfaces?
>>
>> JAP
>>
>>
>> 
>> -
>> Consejo Nacional de Casas de Cultura
>> http://www.casasdecultura.cult.cu
>> 
>>
>>
>> gracias amigo por contestar:
>>
>> el switch actua como switch solo que en su gestion agrupa
>> una x cantidad
>> de puertos fisicos los cuales responden a una vlan creada
>> por mikrotik
>> entre esos puertos fisicos iria el punto de red
>> perteneciente al
>> servidor debian el cual no me funciona de esa forma.
>>
>> las direcciones ip se asignan de modo estatico no estamos
>> usando dhcp
>>
>> pego lo que contiene /etc/network/interfaces referente a
>> la interface en
>> cuestion, aclaro ademas que no tengo mas ninguna
>> interface solo figura
>> en este archivo lo relacionado con (lo)
>> auto eth0
>> allow-hotplug eth0
>> iface eth0 inet static
>> address 10.20.48.2
>> netmask 255.255.255.128
>> network 10.20.48.129
>> broadcast 10.20.48.255
>> gateway 10.20.28.129  (esta es la ip del equipo
>> que tiene
>> mikrotik ademas)
>>
>>
>> No estoy muy seguro de como expresarlo pero tendrías que leer
>> sobre TCP/IP
>> la configuración tiene errores de concepto
>>  
>> netmask 255.255.255.128 te da un rango de 1 a 126
>> o sea
>> gateway 10.20.28.129 esta en otra red
>> por ultimo el
>> broadcast 10.20.48.255
>> no es este es
>> 10.20.48.127
>>
>> si tenes dudas usa la aplicación ipcalc
>>
>>  
>>
>>
>> como datos adicional todos los equipos pertenecientes a
>> esa vlan se
>> encuentran en el mismo segmento como es logico, otro dato
>> curioso que
>> olvide mencionar anteriormente, en mikrotik aparece
>> reflejado el equipo
>> con debian puesto como debe ir es decir en el punto de
>> red perteneciente
>> a la vlan del switch pero este aparece y se va es como
>> intermitente,
>> esto sucede poniendolo en cualquier punto del switch
>> declarados para esa
>> vlan. tengo ademas iptables en debian pero descarto la
>> posibilidad que
>> sea este el del problema pues ya he probado con un debian
>> en limpio sin
>> ningun iptables.
>>
>> una vez mas gracias por su acostumbrada ayuda.
>>
>>
>> -
>> Consejo Nacional de Casas de Cultura
>> http://www.casasdecultura.cult.cu
>> 
>>
>>
>>
>>
>> Realmente, no entiendo cómo está armada la red.
>> No me cierran las direcciones del enmascaramiento y la red,
>> considerando las correspondientes a la dirección de la
>> máquina y la pasarela.
>> Si yo tuviese que armarla, lo haría así:
>>
>> auto eth0
>> allow-hotplug eth0
>> iface eth0 inet static
>> address 10.20.48.2
>> netmask 255.255.0.0
>> broadcast 10.20.48.255
>> gateway 10.20.28.129
>>
>> La opción "network" está de más.
>>
>> Por otro lado, algo que SIEMPRE genera problemas cuando uno
>> arma una red estática, es network-manager.
>>
>> Asegurate que NO esté instalado con
>> # dpkg -l network-manager*
>>
>> Si lo está, elimina todo con
>> # apt-get purge network-manager*
>>
>> Prueba con eso.
>>
>> Luego, manda la salida del comando
>> # route
>>
>> JAP
>>
>>
>>
>>
>> -- 
>> MrIX
>> Linux user number 412793.
>> http://counter.li.org/
>>
>> las grandes 

[Mysql] Performance problem after database drop

[kc atgb]

Hi all,

I have a strange situation with one of our database servers. After a table purge
, we can see a performance degradation for the same jobs. 

What do the job do, write data to two tables. The first one is purged from
entries after 2 months. The second one, is never purged so we had do to it
manually and that was done some days ago. 

The table had a size approximatively of 350GB. The purge operatoin was done
without problem (show create table, drop table, create table). 

Some time after, 2 or maybe 3 days, a colleague reported me that some job that
was working with these datas, are taking longer to be executed. It's very very
strange because there was no configuration modification at all, just data purge.

The time needed for the job to terminate was from 45-60 minutes longer to 2h+
longer. 

Does any body have already been in a situation like this ? 

Any advice or feedback is welcome to help to troubleshoot this. 

Thanks,
K.

LibreOffice

[jordi]

Bones, al final he fet una instal·lació nova del Debian Stretch, en un
altre correu explicaré els problemes que han sortit durant aquesta.

Per ara, anem pel LibreOffice. Els primers dies de la instal·lació
funcionava, o al menys s'engegava i semblava que anava be. Després de
instal·lar una colla més de programes, i entre ells els controladors
privatius NVIDIA i la màquina virtual Java(TM) SE Runtime Environment
(build 1.8.0_131-b11), va deixar de funcionar, o es a dir no engega.
Amb el soffice --backtrace vaig veure que petava la maquina virtual
java que ve amb l'Stretch. Així que la vaig desinstal·lar i al menys
vaig poder canviarla a les opcions per la nova. Ara em trobo que
soffice em funciona amb sudo però no com a usuari.

He vist pel Google que això a passat amb altres versions de
LibreOffice, però no en trobo la solució. (El google no deixa de ser un
 hipermercat amb interesos només comercials).

Si algú em pot orientar ...

Moltes gracies.

Jordi

Re: debian8 y vlan en mikrotik

[Cristian Mitchell]

El 26 de junio de 2017, 15:14, Ariel Alvarez escribió:

>
> El 26-06-17 12:33, Cristian Mitchell escribió:
>
>
>
> El 26 de junio de 2017, 12:25, JAP
> escribió:
>
>> El 26/06/17 a las 11:08, Ariel Alvarez escribió:
>>
>>
>>> El 26-06-17 9:38, JAP escribió:
>>>
 El 26/06/17 a las 09:51, Ariel Alvarez escribió:

> no me da red
>

 ¿Cómo está configurado el swtich? ¿Como enrutador? ¿Como switch?
 ¿Quién asigna dirección IP, por dhcp o estáticas?
 ¿Qué dice tu /etc/network/interfaces?

 JAP


 -
 Consejo Nacional de Casas de Cultura
 http://www.casasdecultura.cult.cu

>>>
>>> gracias amigo por contestar:
>>>
>>> el switch actua como switch solo que en su gestion agrupa una x cantidad
>>> de puertos fisicos los cuales responden a una vlan creada por mikrotik
>>> entre esos puertos fisicos iria el punto de red perteneciente al
>>> servidor debian el cual no me funciona de esa forma.
>>>
>>> las direcciones ip se asignan de modo estatico no estamos usando dhcp
>>>
>>> pego lo que contiene /etc/network/interfaces referente a la interface en
>>> cuestion, aclaro ademas que no tengo mas ninguna interface solo figura
>>> en este archivo lo relacionado con (lo)
>>> auto eth0
>>> allow-hotplug eth0
>>> iface eth0 inet static
>>> address 10.20.48.2
>>> netmask 255.255.255.128
>>> network 10.20.48.129
>>> broadcast 10.20.48.255
>>> gateway 10.20.28.129  (esta es la ip del equipo que tiene
>>> mikrotik ademas)
>>>
>>
> No estoy muy seguro de como expresarlo pero tendrías que leer sobre TCP/IP
> la configuración tiene errores de concepto
>
> netmask 255.255.255.128 te da un rango de 1 a 126
> o sea
> gateway 10.20.28.129 esta en otra red
> por ultimo el
> broadcast 10.20.48.255
> no es este es
> 10.20.48.127
>
> si tenes dudas usa la aplicación ipcalc
>
>
>
>>
>>> como datos adicional todos los equipos pertenecientes a esa vlan se
>>> encuentran en el mismo segmento como es logico, otro dato curioso que
>>> olvide mencionar anteriormente, en mikrotik aparece reflejado el equipo
>>> con debian puesto como debe ir es decir en el punto de red perteneciente
>>> a la vlan del switch pero este aparece y se va es como intermitente,
>>> esto sucede poniendolo en cualquier punto del switch declarados para esa
>>> vlan. tengo ademas iptables en debian pero descarto la posibilidad que
>>> sea este el del problema pues ya he probado con un debian en limpio sin
>>> ningun iptables.
>>>
>>> una vez mas gracias por su acostumbrada ayuda.
>>>
>>>
>>> -
>>> Consejo Nacional de Casas de Cultura
>>> http://www.casasdecultura.cult.cu
>>>
>>>
>>
>>
>> Realmente, no entiendo cómo está armada la red.
>> No me cierran las direcciones del enmascaramiento y la red, considerando
>> las correspondientes a la dirección de la máquina y la pasarela.
>> Si yo tuviese que armarla, lo haría así:
>>
>> auto eth0
>> allow-hotplug eth0
>> iface eth0 inet static
>> address 10.20.48.2
>> netmask 255.255.0.0
>> broadcast 10.20.48.255
>> gateway 10.20.28.129
>>
>> La opción "network" está de más.
>>
>> Por otro lado, algo que SIEMPRE genera problemas cuando uno arma una red
>> estática, es network-manager.
>>
>> Asegurate que NO esté instalado con
>> # dpkg -l network-manager*
>>
>> Si lo está, elimina todo con
>> # apt-get purge network-manager*
>>
>> Prueba con eso.
>>
>> Luego, manda la salida del comando
>> # route
>>
>> JAP
>>
>>
>
>
> --
> MrIX
> Linux user number 412793.
> http://counter.li.org/
>
> las grandes obras,
> las sueñan los santos locos,
> las realizan los luchadores natos,
> las aprovechan los felices cuerdo,
> y las critican los inútiles crónicos,
>
> a ver disculpen es que la config la copie a mano y al parecer se me fue
> ese error en realidad seria 10.20.48.129, a ver aclaro una vez mas si ese
> fuera el caso que la configuracion tuviera algun error no pudiera verse al
> conectar el debian punto a punto con un windows, ni siquiera tampoco
> funcionara el puente como lo esta haciendo ahora, pido disculpas por el
> error.
>
> la config seria esta:
>
> auto eth0
> allow-hotplug eth0
> iface eth0 inet static
> address 10.20.48.2
> netmask 255.255.255.128
> network 10.20.48.129
> broadcast 10.20.48.255
> gateway 10.20.48.129
> - Consejo
> Nacional de Casas de Cultura http://www.casasdecultura.cult.cu
>

Insisto pertenecen a dos redes diferentes
usa el ipcalc para calcular las redes


-- 
MrIX
Linux user number 412793.
http://counter.li.org/

las grandes obras,
las sueñan los santos locos,
las realizan los luchadores natos,
las aprovechan los felices cuerdo,
y las critican los inútiles crónicos,

Re: pavucontrol fails to start

[Thomas George]

On 06/26/2017 05:01 PM, Ralph Katz wrote:

On 06/26/2017 02:29 PM, Thomas George wrote:

The command pavucontrol returns an error message:

error while loading shared libraries: libgtkmm-3.0.so-1: cannot open
object file: No such file or directory.

Where can I find this missing file?

I checked apt-get install libgtkmm-3.0-1 The response was latest version
installed.

I tried apt-cache search libgtkmm-3.0.so.1 Nothing was found.

Are you using debian stretch?  I have only these similar filenames, and
pavucontrol works fine in stretch:

/usr/lib/x86_64-linux-gnu/libgtkmm-3.0.so.1
/usr/lib/x86_64-linux-gnu/libgtkmm-3.0.so.1.1.0

 From package libgtkmm-3.0-1v5 which is a "depends" of  pavucontrol.

If you're on stretch, you can apt-get update, then apt-get install
--reinstall  libgtkmm-3.0-1v5

Good luck!
Thanks. I am trying to do this on a raspberry pi with rasbian, an debian 
based jessie system for arm cpu's..
I was not aware that apt-file existed. I have installed it and used it 
to find libgtkmm-3.0.so.1 in a directory /usr/lib/arm-linux-gnueabihf/
Other raspberry pi users have not reported a problem using pavucontrol 
so I'll have to figure out why I have this problem.

Re: debian8 y vlan en mikrotik

[Jorge A. Secreto]

hola

El día 26 de junio de 2017, 15:14, Ariel Alvarez  escribió:
>
> El 26-06-17 12:33, Cristian Mitchell escribió:
>
>.
> a ver disculpen es que la config la copie a mano y al parecer se me fue ese
> error en realidad seria 10.20.48.129, a ver aclaro una vez mas si ese fuera
> el caso que la configuracion tuviera algun error no pudiera verse al
> conectar el debian punto a punto con un windows, ni siquiera tampoco
> funcionara el puente como lo esta haciendo ahora, pido disculpas por el
> error.
>
> la config seria esta:
>
> auto eth0
> allow-hotplug eth0
> iface eth0 inet static
> address 10.20.48.2
> netmask 255.255.255.128
> network 10.20.48.129
> broadcast 10.20.48.255
> gateway 10.20.48.129
> - Consejo
> Nacional de Casas de Cultura http://www.casasdecultura.cult.cu

Pido disculpas si estoy tan dormido como para entender mal la
configuración,pero, me parece, que con máscara 128 las direcciones 2 y
129 están en diferente red.
129 no sirve como GW de 2, con esa máscara.
Abrazo

-- 
Jorge A Secreto
Analista de Sistemas
MP 361

Re: pavucontrol fails to start

[Ralph Katz]

On 06/26/2017 02:29 PM, Thomas George wrote:
> The command pavucontrol returns an error message:
> 
> error while loading shared libraries: libgtkmm-3.0.so-1: cannot open
> object file: No such file or directory.
> 
> Where can I find this missing file?
> 
> I checked apt-get install libgtkmm-3.0-1 The response was latest version
> installed.
> 
> I tried apt-cache search libgtkmm-3.0.so.1 Nothing was found.

Are you using debian stretch?  I have only these similar filenames, and
pavucontrol works fine in stretch:

/usr/lib/x86_64-linux-gnu/libgtkmm-3.0.so.1
/usr/lib/x86_64-linux-gnu/libgtkmm-3.0.so.1.1.0

From package libgtkmm-3.0-1v5 which is a "depends" of  pavucontrol.

If you're on stretch, you can apt-get update, then apt-get install
--reinstall  libgtkmm-3.0-1v5

Good luck!




signature.asc
Description: OpenPGP digital signature

Re: How did you update to stretch?

[Jonathan Dowland]

On Tue, Jun 27, 2017 at 03:04:30AM +1000, John Elliot V wrote:

Can I ask why you did the apt-get upgrade before the apt-get
dist-upgrade? Why not just go straight for apt-get dist-upgrade..?


Merely because that's what the release notes said to do.


--

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland

⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not CC me, I am subscribed to the list.

Re: stretch to buster

[Jean-Louis Giraud]

Bonsoir 
Voir mon post de ce matin pour le retour d'expérience. 
Ne pas oublier de commencer par une sauvegarde complète au cas où..
Et puis avant de modifier le source.list update et upgrade. 
Pour ma part après ton 2/ j'ai juste fait un upgrade et tout s'est passé nickel 
( précision : comme environnement de bureau j'utilise Xfce) 


Envoyé de mon iPhone

> Le 26 juin 2017 à 20:38, Cyrille  a écrit :
> 
> Bonsoir
> Pour passer de l'une à l'autre
> 1/ modifier le source liste en changeant le stretch par buster
> 2/ update
> 3/ full-upgrade
> 
> ça devrait le faire non ?
> 
> Des retours, des conseils ?
> 
> Thx !
> Cyrille
> 

Re: pavucontrol fails to start

[Dejan Jocic]

On 26-06-17, Thomas George wrote:
> The command pavucontrol returns an error message:
> 
> error while loading shared libraries: libgtkmm-3.0.so-1: cannot open object
> file: No such file or directory.
> 
> Where can I find this missing file?
> 
> I checked apt-get install libgtkmm-3.0-1 The response was latest version
> installed.
> 
> I tried apt-cache search libgtkmm-3.0.so.1 Nothing was found.
> 

It is more appropriate to use apt-file search libgtkmm-3.0.so.1. That
will return that it is part of package libgtkmm-3.0-1v5. And that
package replaces and conflicts libgtkmm-3.0-1. At least on Stretch, on
my laptop.

Re: pavucontrol fails to start

[Frank M]

On 06/26/2017 04:29 PM, Thomas George wrote:

The command pavucontrol returns an error message:

error while loading shared libraries: libgtkmm-3.0.so-1: cannot open 
object file: No such file or directory.


Where can I find this missing file?

I checked apt-get install libgtkmm-3.0-1 The response was latest 
version installed.


I tried apt-cache search libgtkmm-3.0.so.1 Nothing was found.




   This is available for 64 bit. libgtkmm-3.0-1v5
   sudo apt install libgtkmm-3.0-1v5

pavucontrol fails to start

[Thomas George]

The command pavucontrol returns an error message:

error while loading shared libraries: libgtkmm-3.0.so-1: cannot open 
object file: No such file or directory.


Where can I find this missing file?

I checked apt-get install libgtkmm-3.0-1 The response was latest version 
installed.


I tried apt-cache search libgtkmm-3.0.so.1 Nothing was found.

iputils-ping bug, please verify

[Stefan Helmert]

Hi,

I got this bug:

https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1700413

on Ubuntu. Please check, if it can be also triggered on debian.

Re: No live CD ISOs without GUI desktops?

[Fungi4All]

> From: j...@debian.org
> To: debian-user@lists.debian.org
> If your point is that context-free links are not very useful, I agree.
> On Fri, Jun 23, 2017 at 03:16:07PM +, Weaver wrote:
>>On 2017-06-24 00:56, Rene Engelhard wrote:
>>> http://grml.org/download/
> GRML is a derivative distribution based closely on Debian.
>>http://puppylinux.com/download.html
>>http://www.tinycorelinux.net/
> Not to suggest any criticism of these projects, which have fine goals (and 
> I"ve
> used tinycorelinux myself for some projects, and it has some very interesting
> ideas) but none of those are Debian derivatives, nor do they appear to be
> non-GUI live CDs, except maybe some of the tinyCore ones that offer a 
> boot-time
> choice to avoid GUIs, and have them on the image.

Since there is a gui-less installer for Jessie, one can use that live and after 
install
upgrade to stretch. Maybe a +20' dist-upgrade inconvenience, if hardware is
compatible.

Re: How did you update to stretch?

[John Elliot V]

On 27/06/17 05:39, Brian wrote:
> It was. I am a creature of habit. I still reboot between upgrade and
> dist-upgrade when I eventually upgrade a machine from one distribution
> to another.

Do you ever use configuration management tools like Salt Stack?

 https://saltstack.com/

I'm just starting out with Salt, and I haven't figured out what you do
if you want to put a reboot between various configuration steps...

-- 
E: j...@jj5.net
P: +61 4 3505 7839
W: https://www.jj5.net/
<>

Re: How to attach a fully encrypted drive to Stretch

[commentsabout]

Hello,

On 2017-06-26 19:36, Eduardo M KALINOWSKI wrote:
> On 26-06-2017 16:28, commentsab...@riseup.net wrote:
>> I have an adapter to connect my older Jessie (fully encrypted) SATA HDD
>> to a USB port. Simply plugin the older disk/adapter into the freshly
>> installed Stretch doesn't seem to work (I'm not being prompted for a
>> passphrase).
>>
>> What is the proper way to access the data on that drive when connected
>> to the host system via a USB adapter ?
>>
>> I found an answer on
>> 
>> but do not know if it is valid and am not keen on running undocumented
>> commands/commands that I do not understand.
> 
> Assuming the disk is a LUKS encrypted volume (the default since who
> knows when), the command is exactly the one in your link.

Thank you for your answer.

There are actually several answers on the Stack Exchange thread, which
one is the right one ?

This one ?

> cryptsetup luksOpen /dev/sdb1 disk2
> modprobe dm-mod
> vgchange -ay
> mount /dev/disk2/disk2 /disk2


CA

SOLVED xfce volume keys [was: Re: Stretch upgrade from Jessie -- several issues]

[Ralph Katz]

On 06/26/2017 12:54 PM, Dejan Jocic wrote:
> On 26-06-17, Ralph Katz wrote:
>>
>> I think the workaround of using the mouse on pavucontrol or
>> gkrellm-volume will have to do for sound control.  Thanks!
>>
> 
> Well, not exactly solution, but as a work around, you can assign some
> shortcuts to do your sound work in a same way volume keys would do. For
> example, in case of the pulse audio you can use these:
> 
> pactl set-sink-volume 0 -- +5% to increase volume by 5%
> 
> pactl set-sink-volume 0 -- -5% to decrease volume by 5%
> 
> pactl set-sink-mute 0 toggle to mute/unmute

Perfect!  In xfce desktop, settings, keyboard, application shortcuts,
add, (each command line below and choose key when prompted):

pactl set-sink-mute 0 toggle
pactl set-sink-volume 0 +5%
pactl set-sink-volume 0 -5%

This solves the adjust sound problem when using xfce.  Thanks Dejan!




signature.asc
Description: OpenPGP digital signature

Re: How did you update to stretch?

[Brian]

On Mon 26 Jun 2017 at 13:27:42 -0500, David Wright wrote:

> On Mon 26 Jun 2017 at 19:01:21 (+0100), Brian wrote:
> > On Mon 26 Jun 2017 at 13:06:29 -0400, Greg Wooledge wrote:
> > 
> > > On Tue, Jun 27, 2017 at 03:04:30AM +1000, John Elliot V wrote:
> > > > Can I ask why you did the apt-get upgrade before the apt-get
> > > > dist-upgrade? Why not just go straight for apt-get dist-upgrade..?
> > > 
> > > Probably because (s)he read the release notes:
> > > 
> > > 
> > 
> > The notes are clear but what is the point of following this procedure?
> > 
> > You do an upgrade, so an upgrade is done. No new packages. Fair enough.
> 
> I have a desktop that I don't use very frequently at the moment.
> Last time I booted it up, the apt-get upgrade downloaded over 70
> packages. There was probably a point-release involved.
> That contrasts with my regularly used machines that apt-get -d upgrade
> every three hours and email me if their cache contains any packages.
> 
> If you watch upgrades taking place, you can see that they're phased.
> Apt-ish and Dpkg-ish are setup before other packages are unpacked,
> and so on. It's not all just done in one heap.
> 
> By running upgrade before dist-upgrade, you reduce complexity by
> maximising the compatibility of packages with each other. When
> lenny was replaced by squeeze, even these two steps were
> insufficient; the kernel and udev needed replacing as a pair after
> the (lenny) upgrade and before the (squeeze) dist-upgrade.

Thank you for reminding us of Lenny -> Squeeze. It is not the same this
time but I have been scarred by it! 'apt-get upgrade' is such a simple
step to take first for the reason you give that it would be churlish not
to agree with it for the reason you give.
 
> > You are none the wiser about what would happen if a dist-upgrade is done
> > next, so it is still a dive into the unknown.
> > 
> > Then you dist-upgrade. Why not leave out the previous step, unless there
> > are packages you wish to keep? Perhaps an illustrative example of when
> > the single-step process dist-upgrade fails would be helpful. The advice
> > 
> >  This has the effect of upgrading those packages which can be
> >  upgraded without requiring any other packages to be removed
> >  or installed
> > 
> > simply repeats what apt-get(8) says without its detailed explanation.
> > 
> > (I upgrade, reboot, dist-upgrade, But I am into cargo-cult).
> 
> Oh, I forgot. It was necessary, of course, to reboot after replacing
> the kernel and udev in the lenny/squeeze process, in order for the
> newly installed kernel to be actually running as opposed to just
> spinning on the drive.

It was. I am a creature of habit. I still reboot between upgrade and
dist-upgrade when I eventually upgrade a machine from one distribution
to another.

-- 
Brian.
-- 
Brian.

Re: How to attach a fully encrypted drive to Stretch

[Eduardo M KALINOWSKI]

On 26-06-2017 16:28, commentsab...@riseup.net wrote:
> I have an adapter to connect my older Jessie (fully encrypted) SATA HDD
> to a USB port. Simply plugin the older disk/adapter into the freshly
> installed Stretch doesn't seem to work (I'm not being prompted for a
> passphrase).
>
> What is the proper way to access the data on that drive when connected
> to the host system via a USB adapter ?
>
> I found an answer on
> 
> but do not know if it is valid and am not keen on running undocumented
> commands/commands that I do not understand.

Assuming the disk is a LUKS encrypted volume (the default since who
knows when), the command is exactly the one in your link.

If you don't know what the command does, try 'man cryptsetup', which
will explain what it does and list the other commands and options you
can use.

-- 
It's easier to take it apart than to put it back together.
-- Washlesky

Eduardo M KALINOWSKI
edua...@kalinowski.com.br

How to attach a fully encrypted drive to Stretch

[commentsabout]

Hello,

Rather than upgrading my Jessie system, I decided to go with a fresh
install of Stretch on a new SSD.

I have an adapter to connect my older Jessie (fully encrypted) SATA HDD
to a USB port. Simply plugin the older disk/adapter into the freshly
installed Stretch doesn't seem to work (I'm not being prompted for a
passphrase).

The encryption on Jessie was done at install time following the guided
install ("use entire disk and setup encrypted LVM").

What is the proper way to access the data on that drive when connected
to the host system via a USB adapter ?

I found an answer on

but do not know if it is valid and am not keen on running undocumented
commands/commands that I do not understand.

Thank you in advance for your help :)

CA

Sound issue WAS: Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

[John Elliot V]

On 27/06/17 03:16, John Elliot V wrote:
> Hmm. I re-enabled hyper-threading (to test) and sound didn't come back.

After a number of false starts I was able to restore audio by:

 KDE -> System Settings -> Multimedia (Hardware) -> Audio and Video ->
  Audio Hardware Setup

Then in the Hardware section changing Profile from:

 Digital Stereo (IEC958) Output + Analog Stereo Input

To:

 Digital Stereo (HDMI2) Output + Analog Stereo Input

I'm not sure what changed that required me to make this change. Anyway,
happy that sound is working again for me.

Regards,
John Elliot V
-- 
E: j...@jj5.net
P: +61 4 3505 7839
W: https://www.jj5.net/
<>

stretch to buster

[Cyrille]

Bonsoir
Pour passer de l'une à l'autre
1/ modifier le source liste en changeant le stretch par buster
2/ update
3/ full-upgrade

ça devrait le faire non ?

Des retours, des conseils ?

Thx !
Cyrille

Re: How did you update to stretch?

[Brian]

On Mon 26 Jun 2017 at 14:16:57 -0400, The Wanderer wrote:

> On 2017-06-26 at 14:01, Brian wrote:
> 
> > On Mon 26 Jun 2017 at 13:06:29 -0400, Greg Wooledge wrote:
> > 
> >> On Tue, Jun 27, 2017 at 03:04:30AM +1000, John Elliot V wrote:
> >> 
> >>> Can I ask why you did the apt-get upgrade before the apt-get
> >>> dist-upgrade? Why not just go straight for apt-get
> >>> dist-upgrade..?
> >> 
> >> Probably because (s)he read the release notes:
> >> 
> >> 
> >
> > The notes are clear but what is the point of following this
> > procedure?
> > 
> > You do an upgrade, so an upgrade is done. No new packages. Fair
> > enough. You are none the wiser about what would happen if a
> > dist-upgrade is done next, so it is still a dive into the unknown.
> > 
> > Then you dist-upgrade. Why not leave out the previous step, unless
> > there are packages you wish to keep? Perhaps an illustrative example
> > of when the single-step process dist-upgrade fails would be helpful.
> 
> For one thing, this way any new code from e.g. apt/dpkg/etc. themselves
> will be in place before you run the more-complex portion of the upgrade
> process, and you'll be able to take advantages of any fixes or
> improvements which may result from that.

This is the sort of advice which should be in the Release Notes rather
than the anodyne reason which is given at present. It makes sense to
target one of the most fundamental aspects of Debian before moving on
to other things,

-- 
Brian.

Re: Stretch upgrade from Jessie -- several issues

[Dejan Jocic]

On 26-06-17, Ralph Katz wrote:
> 
> I think the workaround of using the mouse on pavucontrol or
> gkrellm-volume will have to do for sound control.  Thanks!
> 

Well, not exactly solution, but as a work around, you can assign some
shortcuts to do your sound work in a same way volume keys would do. For
example, in case of the pulse audio you can use these:

pactl set-sink-volume 0 -- +5% to increase volume by 5%

pactl set-sink-volume 0 -- -5% to decrease volume by 5%

pactl set-sink-mute 0 toggle to mute/unmute

In case of ALSA, should be something like:

amixer set Master 5%+ to increase

amixer set Master 5%- to decrease

amixer set Master toggle to mute/unmute

Re: How did you update to stretch?

[The Wanderer]

On 2017-06-26 at 14:27, David Wright wrote:

> On Mon 26 Jun 2017 at 19:01:21 (+0100), Brian wrote:
> 
>> On Mon 26 Jun 2017 at 13:06:29 -0400, Greg Wooledge wrote:

>>> Probably because (s)he read the release notes:
>>> 
>>> 
>>
>> The notes are clear but what is the point of following this
>> procedure?
>> 
>> You do an upgrade, so an upgrade is done. No new packages. Fair
>> enough.
> 
> I have a desktop that I don't use very frequently at the moment. Last
> time I booted it up, the apt-get upgrade downloaded over 70 packages.
> There was probably a point-release involved. That contrasts with my
> regularly used machines that apt-get -d upgrade every three hours and
> email me if their cache contains any packages.

I understood "No new packages." to mean "no not-previously-installed
packages get installed", not "no new versions of existing packages get
installed".

> If you watch upgrades taking place, you can see that they're phased.
> Apt-ish and Dpkg-ish are setup before other packages are unpacked,
> and so on. It's not all just done in one heap.
> 
> By running upgrade before dist-upgrade, you reduce complexity by 
> maximising the compatibility of packages with each other. When lenny
> was replaced by squeeze, even these two steps were insufficient; the
> kernel and udev needed replacing as a pair after the (lenny) upgrade
> and before the (squeeze) dist-upgrade.

This is my interpretation of (one major reason for) the recommendation,
as well.

-- 
   The Wanderer

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



signature.asc
Description: OpenPGP digital signature

Re: How did you update to stretch?

[David Wright]

On Mon 26 Jun 2017 at 19:01:21 (+0100), Brian wrote:
> On Mon 26 Jun 2017 at 13:06:29 -0400, Greg Wooledge wrote:
> 
> > On Tue, Jun 27, 2017 at 03:04:30AM +1000, John Elliot V wrote:
> > > Can I ask why you did the apt-get upgrade before the apt-get
> > > dist-upgrade? Why not just go straight for apt-get dist-upgrade..?
> > 
> > Probably because (s)he read the release notes:
> > 
> > 
> 
> The notes are clear but what is the point of following this procedure?
> 
> You do an upgrade, so an upgrade is done. No new packages. Fair enough.

I have a desktop that I don't use very frequently at the moment.
Last time I booted it up, the apt-get upgrade downloaded over 70
packages. There was probably a point-release involved.
That contrasts with my regularly used machines that apt-get -d upgrade
every three hours and email me if their cache contains any packages.

If you watch upgrades taking place, you can see that they're phased.
Apt-ish and Dpkg-ish are setup before other packages are unpacked,
and so on. It's not all just done in one heap.

By running upgrade before dist-upgrade, you reduce complexity by
maximising the compatibility of packages with each other. When
lenny was replaced by squeeze, even these two steps were
insufficient; the kernel and udev needed replacing as a pair after
the (lenny) upgrade and before the (squeeze) dist-upgrade.

> You are none the wiser about what would happen if a dist-upgrade is done
> next, so it is still a dive into the unknown.
> 
> Then you dist-upgrade. Why not leave out the previous step, unless there
> are packages you wish to keep? Perhaps an illustrative example of when
> the single-step process dist-upgrade fails would be helpful. The advice
> 
>  This has the effect of upgrading those packages which can be
>  upgraded without requiring any other packages to be removed
>  or installed
> 
> simply repeats what apt-get(8) says without its detailed explanation.
> 
> (I upgrade, reboot, dist-upgrade, But I am into cargo-cult).

Oh, I forgot. It was necessary, of course, to reboot after replacing
the kernel and udev in the lenny/squeeze process, in order for the
newly installed kernel to be actually running as opposed to just
spinning on the drive.

Cheers,
David.

Re: How did you update to stretch?

[The Wanderer]

On 2017-06-26 at 14:01, Brian wrote:

> On Mon 26 Jun 2017 at 13:06:29 -0400, Greg Wooledge wrote:
> 
>> On Tue, Jun 27, 2017 at 03:04:30AM +1000, John Elliot V wrote:
>> 
>>> Can I ask why you did the apt-get upgrade before the apt-get
>>> dist-upgrade? Why not just go straight for apt-get
>>> dist-upgrade..?
>> 
>> Probably because (s)he read the release notes:
>> 
>> 
>
> The notes are clear but what is the point of following this
> procedure?
> 
> You do an upgrade, so an upgrade is done. No new packages. Fair
> enough. You are none the wiser about what would happen if a
> dist-upgrade is done next, so it is still a dive into the unknown.
> 
> Then you dist-upgrade. Why not leave out the previous step, unless
> there are packages you wish to keep? Perhaps an illustrative example
> of when the single-step process dist-upgrade fails would be helpful.

For one thing, this way any new code from e.g. apt/dpkg/etc. themselves
will be in place before you run the more-complex portion of the upgrade
process, and you'll be able to take advantages of any fixes or
improvements which may result from that.

> (I upgrade, reboot, dist-upgrade, But I am into cargo-cult).

I update, dist-upgrade, autoremove, remove $(deborphan), and then run
'update-flashplugin-nonfree --install', manually as root, about once a
day - not quite every day, but on average multiple times a week over the
gap between major releases.

Since I also track testing (by that name, not by release name) in
sources.list, that means that by the time the freeze ends and the
release officially occurs, I'm essentially already upgraded.

-- 
   The Wanderer

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



signature.asc
Description: OpenPGP digital signature

Re: How did you update to stretch?

[Brian]

On Mon 26 Jun 2017 at 18:27:28 +0100, Joe wrote:

> On Tue, 27 Jun 2017 03:04:30 +1000
> John Elliot V  wrote:
> 
> > On 26/06/17 23:12, Jonathan Dowland wrote:
> > >> So, how are your experiences? Did you end in the same issues as I
> > >> ended?  
> > > 
> > > Nope, I read the release notes and simply did
> > > 
> > > (correct sources.list)
> > > apt-get update
> > > apt-get upgrade
> > > apt-get dist-upgrade
> > > (pending reboot)  
> > 
> > Can I ask why you did the apt-get upgrade before the apt-get
> > dist-upgrade? Why not just go straight for apt-get dist-upgrade..?
> > 
> 
> As far as I remember, that's been advised, not mandatory, in all the
> upgrade sections of release notes that I have ever seen. Presumably,
> serious problems in an upgrade are potentially less difficult to
> recover from than those during a dist-upgrade, as only new software and
> version changes have been installed.

Some time round about Etch or Potato there was a problem with udev and
the two-step process was obligatory and also involved a reboot. My
recollection might be incorrect but, to some extent, the procedure has
passed into folklore.

> Package architecture changes and other alterations which only a
> dist-upgrade can achieve would seem to me to be likely to be harder to
> roll back. Of course, there's no reason why a small number of problems
> in only the dist-upgrade changes should not occur, making no
> difference to the methods.

Indeed.

> Maybe it's also for the psychological effect of dividing the task into
> two parts, with time for a break and a sigh of relief when the first
> part goes without difficulty...

I really like that as an explanation. Following the two-step procedure
does no harm; it lowers the blood pressure!

-- 
Brian.

Re: debian8 y vlan en mikrotik

[Ariel Alvarez]

El 26-06-17 12:33, Cristian Mitchell escribió:



El 26 de junio de 2017, 12:25, JAP> escribió:


El 26/06/17 a las 11:08, Ariel Alvarez escribió:


El 26-06-17 9:38, JAP escribió:

El 26/06/17 a las 09:51, Ariel Alvarez escribió:

no me da red


¿Cómo está configurado el swtich? ¿Como enrutador? ¿Como
switch?
¿Quién asigna dirección IP, por dhcp o estáticas?
¿Qué dice tu /etc/network/interfaces?

JAP


-
Consejo Nacional de Casas de Cultura
http://www.casasdecultura.cult.cu



gracias amigo por contestar:

el switch actua como switch solo que en su gestion agrupa una
x cantidad
de puertos fisicos los cuales responden a una vlan creada por
mikrotik
entre esos puertos fisicos iria el punto de red perteneciente al
servidor debian el cual no me funciona de esa forma.

las direcciones ip se asignan de modo estatico no estamos
usando dhcp

pego lo que contiene /etc/network/interfaces referente a la
interface en
cuestion, aclaro ademas que no tengo mas ninguna interface
solo figura
en este archivo lo relacionado con (lo)
auto eth0
allow-hotplug eth0
iface eth0 inet static
address 10.20.48.2
netmask 255.255.255.128
network 10.20.48.129
broadcast 10.20.48.255
gateway 10.20.28.129  (esta es la ip del equipo que tiene
mikrotik ademas)


No estoy muy seguro de como expresarlo pero tendrías que leer sobre TCP/IP
la configuración tiene errores de concepto

netmask 255.255.255.128 te da un rango de 1 a 126
o sea
gateway 10.20.28.129 esta en otra red
por ultimo el
broadcast 10.20.48.255
no es este es
10.20.48.127

si tenes dudas usa la aplicación ipcalc


como datos adicional todos los equipos pertenecientes a esa
vlan se
encuentran en el mismo segmento como es logico, otro dato
curioso que
olvide mencionar anteriormente, en mikrotik aparece reflejado
el equipo
con debian puesto como debe ir es decir en el punto de red
perteneciente
a la vlan del switch pero este aparece y se va es como
intermitente,
esto sucede poniendolo en cualquier punto del switch
declarados para esa
vlan. tengo ademas iptables en debian pero descarto la
posibilidad que
sea este el del problema pues ya he probado con un debian en
limpio sin
ningun iptables.

una vez mas gracias por su acostumbrada ayuda.


-
Consejo Nacional de Casas de Cultura
http://www.casasdecultura.cult.cu





Realmente, no entiendo cómo está armada la red.
No me cierran las direcciones del enmascaramiento y la red,
considerando las correspondientes a la dirección de la máquina y
la pasarela.
Si yo tuviese que armarla, lo haría así:

auto eth0
allow-hotplug eth0
iface eth0 inet static
address 10.20.48.2
netmask 255.255.0.0
broadcast 10.20.48.255
gateway 10.20.28.129

La opción "network" está de más.

Por otro lado, algo que SIEMPRE genera problemas cuando uno arma
una red estática, es network-manager.

Asegurate que NO esté instalado con
# dpkg -l network-manager*

Si lo está, elimina todo con
# apt-get purge network-manager*

Prueba con eso.

Luego, manda la salida del comando
# route

JAP




--
MrIX
Linux user number 412793.
http://counter.li.org/

las grandes obras,
las sueñan los santos locos,
las realizan los luchadores natos,
las aprovechan los felices cuerdo,
y las critican los inútiles crónicos,

a ver disculpen es que la config la copie a mano y al parecer se me fue 
ese error en realidad seria 10.20.48.129, a ver aclaro una vez mas si 
ese fuera el caso que la configuracion tuviera algun error no pudiera 
verse al conectar el debian punto a punto con un windows, ni siquiera 
tampoco funcionara el puente como lo esta haciendo ahora, pido disculpas 
por el error.


la config seria esta:

auto eth0
allow-hotplug eth0
iface eth0 inet static
address 10.20.48.2
netmask 255.255.255.128
network 10.20.48.129
broadcast 10.20.48.255
gateway 10.20.48.129


-
Consejo Nacional de Casas de Cultura
http://www.casasdecultura.cult.cu

Re: How did you update to stretch?

[Brian]

On Mon 26 Jun 2017 at 13:06:29 -0400, Greg Wooledge wrote:

> On Tue, Jun 27, 2017 at 03:04:30AM +1000, John Elliot V wrote:
> > Can I ask why you did the apt-get upgrade before the apt-get
> > dist-upgrade? Why not just go straight for apt-get dist-upgrade..?
> 
> Probably because (s)he read the release notes:
> 
> 

The notes are clear but what is the point of following this procedure?

You do an upgrade, so an upgrade is done. No new packages. Fair enough.
You are none the wiser about what would happen if a dist-upgrade is done
next, so it is still a dive into the unknown.

Then you dist-upgrade. Why not leave out the previous step, unless there
are packages you wish to keep? Perhaps an illustrative example of when
the single-step process dist-upgrade fails would be helpful. The advice

 This has the effect of upgrading those packages which can be
 upgraded without requiring any other packages to be removed
 or installed

simply repeats what apt-get(8) says without its detailed explanation.

(I upgrade, reboot, dist-upgrade, But I am into cargo-cult).

-- 
Brian.

Re: Stretch upgrade from Jessie -- several issues

[Ralph Katz]

On 06/26/2017 12:50 AM, Floris wrote:
> Op Mon, 26 Jun 2017 03:23:32 +0200 schreef Ralph Katz
> :
> 
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>>
>> On 06/25/2017 04:22 PM, Floris wrote:
>>>
>>> Op Sun, 25 Jun 2017 19:10:40 +0200 schreef Ralph Katz
>>> :

> 3) The sound volume up/down function keys [Fn up/down arrow] no
> longer respond (xfce4).  However the screen brightness keys
> function normally [Fn left/right arrow].  The mute sound
> function key is also ignored [Fn F8].  I can control volume
> with the mouse using pavucontrol or gkrellm-volume.

 No progress.
>>>
>>> if the keys are recognized by the kernel, then you can remap them
>>> with an udev hwdb rule.
>>>
>>> Test with evtest if the keys get a scancode and a keycode.
>>> Something like: type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0
>>> type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1 In this case I
>>> pressed the Left Ctrl key, which has a value of 700e0
>>>
>>> Create a new rule in /etc/udev/hwdb.d with something like:
>>>
>>> evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*
>>> KEYBOARD_KEY_ed=volumeup KEYBOARD_KEY_ee=volumedown etc...
>>>
>>> use evemu-describe to find your evdev:... line
>>>
>>> also read:
>>> https://wiki.archlinux.org/index.php/Map_scancodes_to_keycodes
>>> https://wiki.archlinux.org/index.php/Extra_keyboard_keys
>>> /lib/udev/hwdb.d/60-keyboard.hwdb for more information and
>>> examples
>>>
>>> Floris
>>
>> Thanks Floris!  I will look into this, but I am confounded as to why
>> on jessie and previous versions, recognizing these sound keys was
>> automatic.
>>
>> Ralph
>>
> 
> Maybe the switch from "the old" xserver-xorg-input-evdev to "the
> Wayland" xserver-xorg-input-libinput has something to do with it. But I
> don't know if you have the libinput version installed.
> 
> https://packages.debian.org/stretch/xserver-xorg-input-libinput
> ...
> X.Org X server -- libinput input driver
> 
> This package provides the driver for input devices using libinput
> library. It can handle keyboards, mice and touchpads, and essentially
> replaces the separate -evdev and -synaptics drivers.
> ...
> 
> Floris

Yes, the libinput packages were pulled in by the dist-upgrade.  Nothing
in /usr/share/doc/xserver-xorg-input-libinput/ gives any clue on how to
use it.  There is no man page I can find.  There is
/usr/share/X11/xorg.conf.d/40-libinput.conf but again no clue on usage.

I think the workaround of using the mouse on pavucontrol or
gkrellm-volume will have to do for sound control.  Thanks!




signature.asc
Description: OpenPGP digital signature

Re: light-locker (was Stretch upgrade from Jessie -- several issues)

[Ralph Katz]

On 06/26/2017 06:09 AM, Greg Wooledge wrote:
> On Sun, Jun 25, 2017 at 07:23:10PM -0600, Ralph Katz wrote:
>> While purging xscreensaver removed 2 or 3 packages, installing now would
>> bring in a host of packages, for whatever reason.  I don't need a
>> screensaver as much as I need the lock.
> 
> I use i3lock, from a terminal, exactly as I used to use "xlock" when
> Debian still had that.  (I don't use any other part of i3.)
> 

light-locker works fine until the kernel errors make it hard to re-enter
my open session.  This morning I had to restart lightdm because of the
errors:

> ralph@spike2 ~$ grep ERROR /var/log/syslog 
> grep: warning: GREP_OPTIONS is deprecated; please use an alias or script
> Jun 26 06:00:19 spike2 kernel: [49759.456083] 
> [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* 
> [CRTC:26:pipe A] flip_done timed out
> Jun 26 06:01:59 spike2 kernel: [49859.296184] 
> [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* 
> [CRTC:26:pipe A] flip_done timed out
> Jun 26 06:07:08 spike2 kernel: [50168.544120] 
> [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* 
> [CRTC:26:pipe A] flip_done timed out
> Jun 26 06:10:02 spike2 kernel: [50342.624077] 
> [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* 
> [CRTC:26:pipe A] flip_done timed out
...
> ralph@spike2 ~$ grep ERROR /var/log/syslog |wc -l
> grep: warning: GREP_OPTIONS is deprecated; please use an alias or script
> 24
> ralph@spike2 ~$ 

The workaround is don't blank or sleep. ;-)




signature.asc
Description: OpenPGP digital signature

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

[Larry Fletcher]

On 06/25/2017 05:19 AM, Henrique de Moraes Holschuh wrote:

This warning advisory is relevant for users of systems with the Intel
processors code-named "Skylake" and "Kaby Lake".  These are: the 6th and
7th generation Intel Core processors (desktop, embedded, mobile and
HEDT), their related server processors (such as Xeon v5 and Xeon v6), as
well as select Intel Pentium processor models.

TL;DR: unfixed Skylake and Kaby Lake processors could, in some
situations, dangerously misbehave when hyper-threading is enabled.
Disable hyper-threading immediately in BIOS/UEFI to work around the
problem.  Read this advisory for instructions about an Intel-provided
fix.


Hyper-threading was enabled in the BIOS and the Skylake processor looks 
good.


lscpu:
Thread(s) per core:2
Model: 94
Stepping:  3

But both of the "intel-microcode" and "amd64-microcode" packages were 
installed, so I removed amd64-microcode.


apt-cache depends amd64-microcode:
amd64-microcode
  Breaks: intel-microcode

Thanks!

Re: quasi-SOLVED: Re: no network after jessie -> stretch

[Joe]

On Mon, 26 Jun 2017 11:02:10 -0600
"D. R. Evans"  wrote:

> David Wright wrote on 06/24/2017 06:42 PM:
> 
> > Do you need the network before your
> > login prompt appears or not? If not, it looks like systemd needs
> > telling that. I think this just came up in a contemporaneous thread
> > here, but in a disk-mounting context rather than networking.
> >   
> 
> Well, some remote disk filesystems get mounted at boot time -- so that
> obviously needs a functioning network -- but I have no idea whether
> that happens before the login prompt appears. It is definitely true
> that by the time I am logged in (which is very fast, since I use i3),
> the network is up and running.
> 
> I'll go look at the disk-mounting thread and see if there's something
> useful there.
> 
>

If you don't actually need the remote file systems for the boot process
itself, then systemd has an option to automount fstab entries when
first needed. This can cut down boot time. Include:
noauto
and
x-systemd.automount
among the options. I have my workstation's cifs mounts set up that way,
and there's no perceptible delay in opening one for the first time.
They stay mounted then until shutdown. It works for local drives as
well, but they're less of a problem.

-- 
Joe

Re: How did you update to stretch?

[Joe]

On Tue, 27 Jun 2017 03:04:30 +1000
John Elliot V  wrote:

> On 26/06/17 23:12, Jonathan Dowland wrote:
> >> So, how are your experiences? Did you end in the same issues as I
> >> ended?  
> > 
> > Nope, I read the release notes and simply did
> > 
> > (correct sources.list)
> > apt-get update
> > apt-get upgrade
> > apt-get dist-upgrade
> > (pending reboot)  
> 
> Can I ask why you did the apt-get upgrade before the apt-get
> dist-upgrade? Why not just go straight for apt-get dist-upgrade..?
> 

As far as I remember, that's been advised, not mandatory, in all the
upgrade sections of release notes that I have ever seen. Presumably,
serious problems in an upgrade are potentially less difficult to
recover from than those during a dist-upgrade, as only new software and
version changes have been installed.

Package architecture changes and other alterations which only a
dist-upgrade can achieve would seem to me to be likely to be harder to
roll back. Of course, there's no reason why a small number of problems
in only the dist-upgrade changes should not occur, making no
difference to the methods.

Maybe it's also for the psychological effect of dividing the task into
two parts, with time for a break and a sigh of relief when the first
part goes without difficulty...

-- 
Joe 

Re: Paquetes retenidos y aplicaciones rotas tras actualizar a Debian 9

[hector rodriguez]

El 26/6/17, JAP  escribió:
> El 26/06/17 a las 05:57, Iván Hernández Cazorla escribió:
>> Buenas,
>> Creo que no es la primera vez que me suscribo a esta lista de correo,
>> pero nunca está de más agradecer a todos aquellos que atienden los
>> correos de antemano. Gracias. Bueno, les comento mi problema.
>>
>> Últimamente ando un poco desactualizado de las novedades de todo,
>> inclusive de Debian. Fue ayer cuando me enteré de que el 17 de junio de
>> 2017 se lanzó Debian 9 Stretch
>> . Con la emoción fui un poco
>> a la desesperada y busqué rápidamente "how to upgrade debian 8 to 9" y
>> me encontré con este tutorial
>> .
>>
>> Lo seguí al pie de la letra. Pero, cuando el ordenador se reinició tras
>> ejecutar *shutdown -r now*, comprobé que algo no había ido bien por dos
>> razones:
>>
>>  1. Al ejecutar *lsb_release -a *me mostraba (y sigue mostrando este
>> mensaje):
>> No LSB modules are available.
>> Distributor ID:Debian
>> Description:Debian GNU/Linux 9.0 (n/a)
>> Release:9.0
>> Codename:n/a
>> Donde debería indicar el codename "Stretch", no indica nada, solo
>> n/a.
>>  2. Hay programas que se han roto. Por ej. el navegador de archivos
>> "nemo" y VLC.
>>
>> Como no atinaba con que podía ser la razón de este fallo, ejecuté un
>> *apt-get update *y luego un *upgrade* para comprobar que todos los
>> paquetes se habían actualizado. Sin embargo, para mi sorpresa, a estas
>> horas de la mañana que he vuelto a intentarlo, me dice que:
>>
>> 1 actualizados, 0 nuevos se instalarán, 0 para eliminar y 748 no
>> actualizados.
>>
>> Al revisar los 748 paquetes no actualizados por encima, me encuentro con
>> la sorpresa de que VLC y sus dependencias, de la misma manera que muchos
>> otros, no se han actualizado, razón por la que creo que en estos
>> momentos no funciona.
>>
>> Quitando esto, creo además que el comportamiento del cargador ha
>> comenzado a hacer cosas extrañas, pero esto ya es otra cuestión que iré
>> analizando con el tiempo de uso de Stretch.
>>
>> Les adjunto una imagen con la información del sistema por si fuese de
>> alguna utilidad.
>>
>> Muchas gracias de antemano.
>>
>> Saludos, Iván
>
>
> El cambio de nombre en cada equipo, siempre es algo que a veces, tarda.
> Por ejemplo, yo estoy en "testing", y aún sigue como Debian 9 Stretch.
>
> Recomendación: luego de
>
> # apt-get upgrade
>
> haz un
>
> # apt-get dist-upgrade
>
> Probablemente tengas paquetes que se estén reteniendo.
>
> Esto va a hacer una actualización más completa y va a solucionar cosas
> que una actualización normal no hace, por tema de seguridad del sistema.
>
> dist-upgrade in addition to performing the function of upgrade, also
> intelligently handles changing dependencies with new versions of
> packages; apt-get has a "smart" conflict resolution system, and it will
> attempt to upgrade the most important packages at the expense of less
> important ones if necessary. The dist-upgrade command may therefore
> remove some packages. The /etc/apt/sources.list file contains a list of
> locations from which to retrieve desired package files. See also
> apt_preferences(5) for a mechanism for overriding the general settings
> for individual packages.
>
> JAP
>
>


-- 
Cuando hables, procura que tus palabras sean mejores que tu silencio.

Re: How did you update to stretch?

[John Elliot V]

On 27/06/17 03:06, Greg Wooledge wrote:
> On Tue, Jun 27, 2017 at 03:04:30AM +1000, John Elliot V wrote:
>> Can I ask why you did the apt-get upgrade before the apt-get
>> dist-upgrade? Why not just go straight for apt-get dist-upgrade..?
>
> Probably because (s)he read the release notes

Oh. Right. Thanks. :)

-- 
E: j...@jj5.net
P: +61 4 3505 7839
W: https://www.jj5.net/
<>

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

[John Elliot V]

On 27/06/17 02:47, John Elliot V wrote:
> I disabled hyper-threading in my BIOS in response to this advisory (I
> have an i7-7700K). Now I get weird graphical artifacts in drop-down
> lists in KDE (they flash between black and white background) and sound
> has stopped working on my system. Can anyone guess why that might be
> happening? I might try re-enabling hyper-threading to see if things go
> back to normal...

Hmm. I re-enabled hyper-threading (to test) and sound didn't come back.
So I disabled hyper-threading again.

Before I disabled hyper-threading the first time I tried updating my
BIOS, and in order to do that my BIOS reconfigured itself to enable some
networking features so it could update the BIOS over the Internet.
Turned out my BIOS was already at the latest version (details are here [1]).

I'm not sure how to diagnose a "no sound" issue. I've checked all the
volume controls I know about, and nothing is mute and/or low volume.
Sound was working this morning, and now, after I changed my
hyper-threading settings, it's not.

Dunno what happened or why. Totally stumped.

Regards,
John Elliot V

[1] https://www.progclub.org/pipermail/programming/2017-June/002892.html

-- 
E: j...@jj5.net
P: +61 4 3505 7839
W: https://www.jj5.net/
<>

Re: How did you update to stretch?

[Greg Wooledge]

On Tue, Jun 27, 2017 at 03:04:30AM +1000, John Elliot V wrote:
> Can I ask why you did the apt-get upgrade before the apt-get
> dist-upgrade? Why not just go straight for apt-get dist-upgrade..?

Probably because (s)he read the release notes:

Re: How did you update to stretch?

[John Elliot V]

On 26/06/17 23:12, Jonathan Dowland wrote:
>> So, how are your experiences? Did you end in the same issues as I ended?
> 
> Nope, I read the release notes and simply did
> 
> (correct sources.list)
> apt-get update
> apt-get upgrade
> apt-get dist-upgrade
> (pending reboot)

Can I ask why you did the apt-get upgrade before the apt-get
dist-upgrade? Why not just go straight for apt-get dist-upgrade..?

-- 
E: j...@jj5.net
P: +61 4 3505 7839
W: https://www.jj5.net/
<>

Re: quasi-SOLVED: Re: no network after jessie -> stretch

[D. R. Evans]

David Wright wrote on 06/24/2017 06:42 PM:

> 
>>> The error message above indicates, that you have network-manager
>>> installed and since stretch NetworkManager-wait-online.service is
>>> enabled by default (it wasn't in jessie).
> 
> this would suggest a cause. Do you need the network before your login
> prompt appears or not? If not, it looks like systemd needs telling that.
> I think this just came up in a contemporaneous thread here, but in a
> disk-mounting context rather than networking.
> 

Well, some remote disk filesystems get mounted at boot time -- so that
obviously needs a functioning network -- but I have no idea whether that
happens before the login prompt appears. It is definitely true that by the
time I am logged in (which is very fast, since I use i3), the network is up
and running.

I'll go look at the disk-mounting thread and see if there's something useful
there.

>>> Now, if you don't actually manage your interfaces with NetworkManager,
>>> NetworkManager-wait-online.service might run into a timeout (of 30s).
> 
> You originally wrote "about 30 useless seconds". It is worth stating
> whether that is a counted-down timeout period or just an estimate of
> a period you have wait. (I'm assuming you've done nothing to increase
> the flow of console messages when you boot.)

This is a counted-up period. I forget precisely what appears on the screen,
but it's a counter that counts upwards; and, strangely, it doesn't suggest
that there's a 30-second timeout (it's of the form "s / No timeout", or
something like that, where the  increments each second). But when it hits
30 seconds, it does time out and the rest of the boot sequence occurs.

> 
> I have no idea whether the status of eth1 could have any bearing
> because I don't know where one makes ones wishes known to NM,
> not having used it.

Ditto. (At least, "not having used it knowingly".)

Nothing is plugged into eth1, and I have never told the system to configure
that interface, so one would hope that it would be completely ignored. But I
have no idea if that's actually what happens. The error message from NM is
singularly unhelpful :-(

  Doc

-- 
Web:  http://enginehousebooks.com/drevans



signature.asc
Description: OpenPGP digital signature

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

[John Elliot V]

I disabled hyper-threading in my BIOS in response to this advisory (I
have an i7-7700K). Now I get weird graphical artifacts in drop-down
lists in KDE (they flash between black and white background) and sound
has stopped working on my system. Can anyone guess why that might be
happening? I might try re-enabling hyper-threading to see if things go
back to normal...

Regards,
John Elliot V
-- 
E: j...@jj5.net
P: +61 4 3505 7839
W: https://www.jj5.net/
<>

Re: off topic! What is the error in this script

[David Wright]

On Mon 26 Jun 2017 at 09:24:40 (-0400), Greg Wooledge wrote:
> On Sun, Jun 25, 2017 at 06:30:18PM +0300, Teemu Likonen wrote:
> > Dominic Knight [2017-06-25 15:35:46+01] wrote:
> > 
> > > To convert a series of .flac files to .mp3 files I attempted to use the
> > > following line;
> > >
> > >> $ find -name "*.flac" -exec bash -c 'ffmpeg -i "{}" -y -acodec
> > > libmp3lame -ab 320k "${0/.flac}.mp3"' {} \;
> 
> Teemu has highlighted one of the bugs here:
> 
> > The arguments for "bash -c" go like this:
> > 
> > bash -c '...' name one two three
> 
> The other bug is that you are have {} inside of a larger argument to
> find -exec.  This is "allowed" by GNU find (a horrible misfeature of
> the GNU implementation), but is not allowed by other implementations
> of find, because it leads directly to a code injection vulnerability.
> 
> (You are also using the implicit "." starting path for find, which is
> another GNU extension.  This one is not a security problem, just a
> portability problem.)
> 
> > And in '...' the arguments are in variables $0 (=name), $1 (=one), $2
> > (=two), $3 (=three) etc. So:
> > 
> > find -name "*.flac" -exec \
> > bash -c 'ffmpeg -i file:"$1" -c:a libmp3lame -ab 320k -y 
> > file:"${1%.flac}.mp3"' \
> > foo {} \;
> > 
> > Note the "foo": it is saved to $0 ("shell's name") and and then the
> > actual filename is in usual first positional parameter $1. We also want
> > to have explicitl "file:" protocol with ffmpeg so that any "something:"
> > prerix in filename is not interpreted as a protocol name. (See "man
> > ffmpeg-protocols".)
> > 
> > But here's another way without double quoting:
> > 
> > while read -r -d $'\0' input; do
> > ffmpeg -i file:"$input" -c:a libmp3lame -ab 320k \
> > -y file:"${input%.flac}.mp3"
> > done < <(find . -name '*.flac' -print0)
> 
> $'\0' is just the same as ''.  Also, you need to set IFS to the empty
> string for this read, to suppress trimming of leading/trailing IFS
> whitespace characters in filenames.
> 
> while IFS= read -r -d '' input; do ...
> 
> I'd probably add -type f to the find command.
> 
> Finally, ffmpeg is known to have an issue inside loops that read
> from stdin.  Specifically, ffmpeg is one of those programs that reads
> all available stdin, which means the loop will only run once, with the
> other filenames being slurped up by ffmpeg with unpredictable results.
> ssh is another such program.
> 
> There are two workarounds for that:
> 
> 1) Add  
> 2) Use a file descriptor other than stdin for the outer while loop.
>For example,
> 
>  while IFS= read -r -d '' input <&3; do
>  ffmpeg -i file:"$input" -c:a libmp3lame -ab 320k \
>  -y file:"${input%.flac}.mp3"
>  done 3< <(find . -type f -name '*.flac' -print0)

While it's laudable to write command lines such as these, I can't help
being reminded of perl obfuscation contests.

I've been recording radio/TV programmes/vinyl discs/whatever for years,
and generating mp3 files from them (and from MIDI/youtube-type files).
I have bash functions for handling the different sources, targets
("faithful", or compressed for noisy backgrounds, or wav for further
processing), and processes (gapless concatenation or individual
tracks). They're named [s]2mp3[x] where s is for concatenating
the inputs, and x with compression.

This means you haven't got to remember how to apply your preferred
bitrates, compression parameters and so on, and the functions can look
after output directory creation, preservation of timestamps, and any
other housekeeping tasks.

Just a suggestion…

Cheers,
David.

Re: debian8 y vlan en mikrotik

[Cristian Mitchell]

El 26 de junio de 2017, 12:25, JAP escribió:

> El 26/06/17 a las 11:08, Ariel Alvarez escribió:
>
>
>> El 26-06-17 9:38, JAP escribió:
>>
>>> El 26/06/17 a las 09:51, Ariel Alvarez escribió:
>>>
 no me da red

>>>
>>> ¿Cómo está configurado el swtich? ¿Como enrutador? ¿Como switch?
>>> ¿Quién asigna dirección IP, por dhcp o estáticas?
>>> ¿Qué dice tu /etc/network/interfaces?
>>>
>>> JAP
>>>
>>>
>>> -
>>> Consejo Nacional de Casas de Cultura
>>> http://www.casasdecultura.cult.cu
>>>
>>
>> gracias amigo por contestar:
>>
>> el switch actua como switch solo que en su gestion agrupa una x cantidad
>> de puertos fisicos los cuales responden a una vlan creada por mikrotik
>> entre esos puertos fisicos iria el punto de red perteneciente al
>> servidor debian el cual no me funciona de esa forma.
>>
>> las direcciones ip se asignan de modo estatico no estamos usando dhcp
>>
>> pego lo que contiene /etc/network/interfaces referente a la interface en
>> cuestion, aclaro ademas que no tengo mas ninguna interface solo figura
>> en este archivo lo relacionado con (lo)
>> auto eth0
>> allow-hotplug eth0
>> iface eth0 inet static
>> address 10.20.48.2
>> netmask 255.255.255.128
>> network 10.20.48.129
>> broadcast 10.20.48.255
>> gateway 10.20.28.129  (esta es la ip del equipo que tiene
>> mikrotik ademas)
>>
>
No estoy muy seguro de como expresarlo pero tendrías que leer sobre TCP/IP
la configuración tiene errores de concepto

netmask 255.255.255.128 te da un rango de 1 a 126
o sea
gateway 10.20.28.129 esta en otra red
por ultimo el
broadcast 10.20.48.255
no es este es
10.20.48.127

si tenes dudas usa la aplicación ipcalc



>
>> como datos adicional todos los equipos pertenecientes a esa vlan se
>> encuentran en el mismo segmento como es logico, otro dato curioso que
>> olvide mencionar anteriormente, en mikrotik aparece reflejado el equipo
>> con debian puesto como debe ir es decir en el punto de red perteneciente
>> a la vlan del switch pero este aparece y se va es como intermitente,
>> esto sucede poniendolo en cualquier punto del switch declarados para esa
>> vlan. tengo ademas iptables en debian pero descarto la posibilidad que
>> sea este el del problema pues ya he probado con un debian en limpio sin
>> ningun iptables.
>>
>> una vez mas gracias por su acostumbrada ayuda.
>>
>>
>> -
>> Consejo Nacional de Casas de Cultura
>> http://www.casasdecultura.cult.cu
>>
>>
>
>
> Realmente, no entiendo cómo está armada la red.
> No me cierran las direcciones del enmascaramiento y la red, considerando
> las correspondientes a la dirección de la máquina y la pasarela.
> Si yo tuviese que armarla, lo haría así:
>
> auto eth0
> allow-hotplug eth0
> iface eth0 inet static
> address 10.20.48.2
> netmask 255.255.0.0
> broadcast 10.20.48.255
> gateway 10.20.28.129
>
> La opción "network" está de más.
>
> Por otro lado, algo que SIEMPRE genera problemas cuando uno arma una red
> estática, es network-manager.
>
> Asegurate que NO esté instalado con
> # dpkg -l network-manager*
>
> Si lo está, elimina todo con
> # apt-get purge network-manager*
>
> Prueba con eso.
>
> Luego, manda la salida del comando
> # route
>
> JAP
>
>


-- 
MrIX
Linux user number 412793.
http://counter.li.org/

las grandes obras,
las sueñan los santos locos,
las realizan los luchadores natos,
las aprovechan los felices cuerdo,
y las critican los inútiles crónicos,

Re: flash in stretch again

[Patrick Bartek]

On Sun, 25 Jun 2017 18:03:22 -0400 Maureen L Thomas
 wrote:

> 
> 
> On 06/25/2017 05:18 PM, Dan Norton wrote:
> >
> >
> > On 06/25/2017 03:42 PM, Patrick Bartek wrote:
> >> On Sat, 24 Jun 2017 22:17:13 -0400 Maureen L Thomas
> >>  wrote:
> >>
> >>>
> >>> On 06/24/2017 07:29 PM, The Wanderer wrote:
>  On 2017-06-24 at 18:56, Maureen L Thomas wrote:
> 
> > As a last desperate attempt I completely removed firefox-esr and
> > reinstalled it.  I opened it up and the first game actually came
> > up. But the next two games again stated that I needed flash.
> > So I shut down thinking that firefox had a problem and
> > restarted it and none of the games will run.  I am at a
> > complete loss. What the hell could be going on?
>  What does about:plugins report for Flash?
> 
>  I also have a niggling idea related to the Firefox
>  click-to-activate model and the sometimes-missable "doorhanger"
>  drop-down prompt related to that model, but I'm not sure how to
>  express the question about that much less how to recommend
>  checking into it.
> 
> >>> The plugin says it is not there.  All the others are there except
> >>> for flash.  It has to be something with where libflashplayer.so
> >>> is but I have no idea where to start?  I am seriously considering
> >>> going to a different distro.  I really hate that idea but this is
> >>> just to damn much for me to figure out.  At 67 I just want to
> >>> browse and play my damn games.
> >> Just install the flash plugin manually.  That's what I do and have
> >> done so since I started using Linux 15+ years ago.
> >>
> >> In firefox-esr, go to www.adobe.com.  Make sure that's all that's
> >> in the URL.  (It may take you to the Adobe Cloud app page.)
> >> Toward the bottom of the page, right hand side, you should see
> >> listed Adobe Reader, Flash Player, etc.  Click Flash Player and
> >> you should be taken to the Download Page. The OS should say Linux,
> >> if not change it to.  The player version should be 26.something.
> >> Using the Type dropdown menu, select tar.gz. NOT .DEB! Click
> >> Download.  Don't do any of the following "install" steps. This is
> >> a manaul install, remember.  Plus, the auto-install never worked
> >> for me.  Check if the download suceeded. Depending on how you've
> >> got firefox-esr configured, the file should be in Downloads in
> >> your home directory or possibly on your Desktop.  Using a file
> >> manager, exact the tar.gz file to the same place it was
> >> downloaded. The only file you need be concerned with is
> >> libflashplayer.so  As root, using a terminal (or if your
> >> filemanager is able to switch to root priviledge), copy
> >> libflashplayer.so to /usr/lib/mozilla/plugins/
> >>
> >> Restart firefox-esr, do the about:plugin thing and see if
> >> FlashPlayer is there and enabled.  Also, by entering about: in the
> >> URL line, see if firefox-esr version is 52.2.something.  That's
> >> the lastest version of esr.
> >>
> >>
> >> Test if it works with your game sites, etc.
> > Thank you, Patrick! You would not believe how much time I have
> > wasted trying to install this thing (hmm... maybe you would).
> > Manual installation rocks and it works for Jessie and FF 45.9.0.
> >
> >  - Dan
> >> FWIW, you said you were "upgraded" to Stretch automatically.  From
> >> Jessie, I assume.  This was most likely caused by your Debian
> >> Repositories being set to "Stable."  I had this happen 10+ years
> >> ago when I first tried Debian (Sarge).  I was "upgraded" to Etch,
> >> IIRC, and it caused problems since it was a improper upgrade with
> >> a bastard system mix of Sarge and Etch.  To make a long story
> >> short, the fix was a clean install.  You may have to do that
> >> (clean install of either Jessie or Stretch), too, to get things
> >> working properly.  If everything was working with Jessie, I
> >> suggest you install that.  With Debian's Long Term Support, Jessie
> >> will be supported for another 3 years or so.
> >>
> >> Good Luck.
> >>
> >> B
> >>
> >
> >
> So I was playing around trying to figure this crap out and I
> installed Opera and my games work in that browser.  They still do NOT
> work in Firefox ESR.  I would use Opera but none of the movie things
> will play. So how is that for screwed up.  I am going to download
> Stretch and do a clean install and then see how that goes. Thanks
> everyone for all the help.

Sorry, you've had problems.  Like I said, I think a lot of it is due to
that improper (and unwanted) upgrade to Stretch.

It's not unusual to have some sites work with one browser and not
another even if all are up-to-date with all the necessary plugins,
extensions, etc.  I came across one site that parts would only work
properly with Windows and Internet Explorer.  And that was a few months
ago!

Goo luck on your clean install of Stretch.  Just read the Release Notes
and Install Instructions first.

B

Re: flash in stretch again

[Patrick Bartek]

On Sun, 25 Jun 2017 17:18:50 -0400 Dan Norton 
wrote:

> 
> 
> On 06/25/2017 03:42 PM, Patrick Bartek wrote:
> > On Sat, 24 Jun 2017 22:17:13 -0400 Maureen L Thomas
> >  wrote:
> >
> >>
> >> On 06/24/2017 07:29 PM, The Wanderer wrote:
> >>> On 2017-06-24 at 18:56, Maureen L Thomas wrote:
> >>>
>  As a last desperate attempt I completely removed firefox-esr and
>  reinstalled it.  I opened it up and the first game actually came
>  up. But the next two games again stated that I needed flash.  So
>  I shut down thinking that firefox had a problem and restarted it
>  and none of the games will run.  I am at a complete loss.  What
>  the hell could be going on?
> >>> What does about:plugins report for Flash?
> >>>
> >>> I also have a niggling idea related to the Firefox
> >>> click-to-activate model and the sometimes-missable "doorhanger"
> >>> drop-down prompt related to that model, but I'm not sure how to
> >>> express the question about that much less how to recommend
> >>> checking into it.
> >>>
> >> The plugin says it is not there.  All the others are there except
> >> for flash.  It has to be something with where libflashplayer.so is
> >> but I have no idea where to start?  I am seriously considering
> >> going to a different distro.  I really hate that idea but this is
> >> just to damn much for me to figure out.  At 67 I just want to
> >> browse and play my damn games.
> > Just install the flash plugin manually.  That's what I do and have
> > done so since I started using Linux 15+ years ago.
> >
> > In firefox-esr, go to www.adobe.com.  Make sure that's all that's in
> > the URL.  (It may take you to the Adobe Cloud app page.)  Toward the
> > bottom of the page, right hand side, you should see listed Adobe
> > Reader, Flash Player, etc.  Click Flash Player and you should be
> > taken to the Download Page. The OS should say Linux, if not change
> > it to.  The player version should be 26.something.  Using the Type
> > dropdown menu, select tar.gz. NOT .DEB! Click Download.  Don't do
> > any of the following "install" steps. This is a manaul install,
> > remember.  Plus, the auto-install never worked for me.  Check if
> > the download suceeded. Depending on how you've got firefox-esr
> > configured, the file should be in Downloads in your home directory
> > or possibly on your Desktop.  Using a file manager, exact the
> > tar.gz file to the same place it was downloaded. The only file you
> > need be concerned with is libflashplayer.so  As root, using a
> > terminal (or if your filemanager is able to switch to root
> > priviledge), copy libflashplayer.so to /usr/lib/mozilla/plugins/
> >
> > Restart firefox-esr, do the about:plugin thing and see if
> > FlashPlayer is there and enabled.  Also, by entering about: in the
> > URL line, see if firefox-esr version is 52.2.something.  That's the
> > lastest version of esr.
> >
> >
> > Test if it works with your game sites, etc.
> Thank you, Patrick! You would not believe how much time I have wasted 
> trying to install this thing (hmm... maybe you would). Manual 
> installation rocks and it works for Jessie and FF 45.9.0.

You're welcome. 

The manual install method was originally the only way to get the Flash
plugin installed in Linux.  Later when some distros offered auto
install, they were problematical (or didn't work at all), created new
directories, symlinks all over the place, etc.  Even when Adobe
created the install page on their web site, I was never able to get
it to work.  I'll stick with manual than you very much.

FYI: just manually installed in both Wheezy and Stretch the latest Flash
Player plugin (26.0.0.131) to run in Firefox-esr 52.2.0, the most
current version.  All working just fine.

B

Re: debian8 y vlan en mikrotik

[Ariel Alvarez]

El 26-06-17 11:25, JAP escribió:

El 26/06/17 a las 11:08, Ariel Alvarez escribió:


El 26-06-17 9:38, JAP escribió:

El 26/06/17 a las 09:51, Ariel Alvarez escribió:

no me da red


¿Cómo está configurado el swtich? ¿Como enrutador? ¿Como switch?
¿Quién asigna dirección IP, por dhcp o estáticas?
¿Qué dice tu /etc/network/interfaces?

JAP


-
Consejo Nacional de Casas de Cultura
http://www.casasdecultura.cult.cu


gracias amigo por contestar:

el switch actua como switch solo que en su gestion agrupa una x cantidad
de puertos fisicos los cuales responden a una vlan creada por mikrotik
entre esos puertos fisicos iria el punto de red perteneciente al
servidor debian el cual no me funciona de esa forma.

las direcciones ip se asignan de modo estatico no estamos usando dhcp

pego lo que contiene /etc/network/interfaces referente a la interface en
cuestion, aclaro ademas que no tengo mas ninguna interface solo figura
en este archivo lo relacionado con (lo)
auto eth0
allow-hotplug eth0
iface eth0 inet static
address 10.20.48.2
netmask 255.255.255.128
network 10.20.48.129
broadcast 10.20.48.255
gateway 10.20.28.129  (esta es la ip del equipo que tiene
mikrotik ademas)

como datos adicional todos los equipos pertenecientes a esa vlan se
encuentran en el mismo segmento como es logico, otro dato curioso que
olvide mencionar anteriormente, en mikrotik aparece reflejado el equipo
con debian puesto como debe ir es decir en el punto de red perteneciente
a la vlan del switch pero este aparece y se va es como intermitente,
esto sucede poniendolo en cualquier punto del switch declarados para esa
vlan. tengo ademas iptables en debian pero descarto la posibilidad que
sea este el del problema pues ya he probado con un debian en limpio sin
ningun iptables.

una vez mas gracias por su acostumbrada ayuda.


-
Consejo Nacional de Casas de Cultura
http://www.casasdecultura.cult.cu





Realmente, no entiendo cómo está armada la red.
No me cierran las direcciones del enmascaramiento y la red, 
considerando las correspondientes a la dirección de la máquina y la 
pasarela.

Si yo tuviese que armarla, lo haría así:

auto eth0
allow-hotplug eth0
iface eth0 inet static
address 10.20.48.2
netmask 255.255.0.0
broadcast 10.20.48.255
gateway 10.20.28.129

La opción "network" está de más.

Por otro lado, algo que SIEMPRE genera problemas cuando uno arma una 
red estática, es network-manager.


Asegurate que NO esté instalado con
# dpkg -l network-manager*

Si lo está, elimina todo con
# apt-get purge network-manager*

Prueba con eso.

Luego, manda la salida del comando
# route

JAP


-
Consejo Nacional de Casas de Cultura
http://www.casasdecultura.cult.cu
gracias por tus aclaraciones amigo, a  ver el server debian esta en modo 
texto por lo que asumo que en administrador de red grafico no debe estar 
presente o interponerse, en otro orden tambien probe la solucion que me 
dices sin usar el parametro network, lo que si no probe abrir la mascara 
como me lo recomiendas.

en cuanto tenga acceso al equipo debian probare esta solucion y te comento.
un abrazo.

-
Consejo Nacional de Casas de Cultura
http://www.casasdecultura.cult.cu

Email problems

[Phil Dobbin]

please ignore & excuse the noise



0x17F9F9B7.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: debian8 y vlan en mikrotik

[JAP]

El 26/06/17 a las 11:08, Ariel Alvarez escribió:


El 26-06-17 9:38, JAP escribió:

El 26/06/17 a las 09:51, Ariel Alvarez escribió:

no me da red


¿Cómo está configurado el swtich? ¿Como enrutador? ¿Como switch?
¿Quién asigna dirección IP, por dhcp o estáticas?
¿Qué dice tu /etc/network/interfaces?

JAP


-
Consejo Nacional de Casas de Cultura
http://www.casasdecultura.cult.cu


gracias amigo por contestar:

el switch actua como switch solo que en su gestion agrupa una x cantidad
de puertos fisicos los cuales responden a una vlan creada por mikrotik
entre esos puertos fisicos iria el punto de red perteneciente al
servidor debian el cual no me funciona de esa forma.

las direcciones ip se asignan de modo estatico no estamos usando dhcp

pego lo que contiene /etc/network/interfaces referente a la interface en
cuestion, aclaro ademas que no tengo mas ninguna interface solo figura
en este archivo lo relacionado con (lo)
auto eth0
allow-hotplug eth0
iface eth0 inet static
address 10.20.48.2
netmask 255.255.255.128
network 10.20.48.129
broadcast 10.20.48.255
gateway 10.20.28.129  (esta es la ip del equipo que tiene
mikrotik ademas)

como datos adicional todos los equipos pertenecientes a esa vlan se
encuentran en el mismo segmento como es logico, otro dato curioso que
olvide mencionar anteriormente, en mikrotik aparece reflejado el equipo
con debian puesto como debe ir es decir en el punto de red perteneciente
a la vlan del switch pero este aparece y se va es como intermitente,
esto sucede poniendolo en cualquier punto del switch declarados para esa
vlan. tengo ademas iptables en debian pero descarto la posibilidad que
sea este el del problema pues ya he probado con un debian en limpio sin
ningun iptables.

una vez mas gracias por su acostumbrada ayuda.


-
Consejo Nacional de Casas de Cultura
http://www.casasdecultura.cult.cu





Realmente, no entiendo cómo está armada la red.
No me cierran las direcciones del enmascaramiento y la red, considerando 
las correspondientes a la dirección de la máquina y la pasarela.

Si yo tuviese que armarla, lo haría así:

auto eth0
allow-hotplug eth0
iface eth0 inet static
address 10.20.48.2
netmask 255.255.0.0
broadcast 10.20.48.255
gateway 10.20.28.129

La opción "network" está de más.

Por otro lado, algo que SIEMPRE genera problemas cuando uno arma una red 
estática, es network-manager.


Asegurate que NO esté instalado con
# dpkg -l network-manager*

Si lo está, elimina todo con
# apt-get purge network-manager*

Prueba con eso.

Luego, manda la salida del comando
# route

JAP

Re: How did you update to stretch?

[Jörg-Volker Peetz]

For every release the Debian developers take the trouble to write down an
upgrade guide
https://www.debian.org/releases/stretch/amd64/release-notes/ch-upgrading.en.html#upgradingpackages
.
Did you take a look at it?
In my opinion it's written very clear and easy to read. Many thanks from me for
all this work.
I think it answers all your questions.

Regards,
jvp.

Re: How did you update to stretch?

[Joe]

On Mon, 26 Jun 2017 15:46:00 +0200
Hans  wrote:

> Am Montag, 26. Juni 2017, 08:26:38 CEST schrieb John Hasler:
> > Hans writes:  
> Interesting! I did not notice apt, just used apt-get, apt-cache and
> so on. Just read the manual of apt. However, aptitude has also its
> worth, as for me it is faster to see, which dependencies are existent
> for the packages. I like ncurses-guis. 
> 

Aptitude does a better job of resolving dependencies than apt-get.
Unfortunately, the other side of that coin is that it takes longer to
do a particular job, and large numbers of simultaneous upgrades cause
it to run very slowly. It therefore doesn't handle version upgrades
very well, and may break. Some versions ago, aptitude was the
recommended tool for the upgrade, but that has not been the case for
the last two or three.

I have two mobile installations of sid, which may go for months
without getting upgraded. This means that when the time comes, there may
well be hundreds of upgrades, and I gave up long ago using aptitude for
that job. If it's a short time since the last upgrade, I'll use
aptitude, but not otherwise.

-- 
Joe

Re: apt-get upgrade problem

[Curt]

On 2017-06-26, Greg Wooledge  wrote:
> On Sun, Jun 25, 2017 at 09:01:30AM +, Curt wrote:
>> Because of the pedagogical interest of the thing, for those who come
>> after us, for posterity's sake, I wanted the OP to give us a complete
>> description of what occurred, rather than a misleading one (for we are
>> left wondering why FF was held back in the first place, if an 'apt-get
>> install' simply "went ahead and installed it."
>
> In stretch, the upgrade from firefox-esr 45.x to 52.x requires a
> new Depends: package, named libjsoncpp1.

Right. Same here on Wheezy. The name of the package escaped me. Actually
it was rhetorical wondering I was doing up there. Sorry if that was
unclear.



-- 
“Yeah yeah.” --Sidney Morgenbesser's retort to a speaker who said that although
there are many cases in which two negatives make a positive, he knew of no case
in which two positives made a negative.

Re: How did you update to stretch?

[Eduardo M KALINOWSKI]

On Seg, 26 Jun 2017, Hans wrote:

But it would be nice, if we could agree to ONE tool, which is to be
used for dist-upgrades.

And this should be well documented! At the moment IMO there are too  
many tools and that makes it very confusing, doesn't it?


For the specific case of upgrading to stretch, there is one  
recommended tool, and it's documented in the release notes (as are  
other things one should be aware when upgrading).


Spoiler: It's apt-get.

--
Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: No live CD ISOs without GUI desktops?

[Jonathan Dowland]

If your point is that context-free links are not very useful, I agree.

On Fri, Jun 23, 2017 at 03:16:07PM +, Weaver wrote:

On 2017-06-24 00:56, Rene Engelhard wrote:

http://grml.org/download/


GRML is a derivative distribution based closely on Debian.


http://puppylinux.com/download.html
http://www.tinycorelinux.net/


Not to suggest any criticism of these projects, which have fine goals (and I've 
used tinycorelinux myself for some projects, and it has some very interesting 
ideas) but none of those are Debian derivatives, nor do they appear to be 
non-GUI live CDs, except maybe some of the tinyCore ones that offer a boot-time

choice to avoid GUIs, and have them on the image.


--

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland

⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not CC me, I am subscribed to the list.

Re: debian8 y vlan en mikrotik

[Ariel Alvarez]

El 26-06-17 9:38, JAP escribió:

El 26/06/17 a las 09:51, Ariel Alvarez escribió:

no me da red


¿Cómo está configurado el swtich? ¿Como enrutador? ¿Como switch?
¿Quién asigna dirección IP, por dhcp o estáticas?
¿Qué dice tu /etc/network/interfaces?

JAP


-
Consejo Nacional de Casas de Cultura
http://www.casasdecultura.cult.cu


gracias amigo por contestar:

el switch actua como switch solo que en su gestion agrupa una x cantidad 
de puertos fisicos los cuales responden a una vlan creada por mikrotik 
entre esos puertos fisicos iria el punto de red perteneciente al 
servidor debian el cual no me funciona de esa forma.


las direcciones ip se asignan de modo estatico no estamos usando dhcp

pego lo que contiene /etc/network/interfaces referente a la interface en 
cuestion, aclaro ademas que no tengo mas ninguna interface solo figura 
en este archivo lo relacionado con (lo)

auto eth0
allow-hotplug eth0
iface eth0 inet static
address 10.20.48.2
netmask 255.255.255.128
network 10.20.48.129
broadcast 10.20.48.255
gateway 10.20.28.129  (esta es la ip del equipo que tiene 
mikrotik ademas)


como datos adicional todos los equipos pertenecientes a esa vlan se 
encuentran en el mismo segmento como es logico, otro dato curioso que 
olvide mencionar anteriormente, en mikrotik aparece reflejado el equipo 
con debian puesto como debe ir es decir en el punto de red perteneciente 
a la vlan del switch pero este aparece y se va es como intermitente, 
esto sucede poniendolo en cualquier punto del switch declarados para esa 
vlan. tengo ademas iptables en debian pero descarto la posibilidad que 
sea este el del problema pues ya he probado con un debian en limpio sin 
ningun iptables.


una vez mas gracias por su acostumbrada ayuda.


-
Consejo Nacional de Casas de Cultura
http://www.casasdecultura.cult.cu

Re: [Stretch] Fix for not network after installing without desktop

[Brian]

On Mon 26 Jun 2017 at 08:24:10 -0400, Greg Wooledge wrote:

> On Sat, Jun 24, 2017 at 11:07:13AM +0200, Erwan David wrote:
> > Do you mean that network-manager is compulsory in stretch ? Impossible
> > to use a fixed configuration in /etc/network/interfaces or another
> > connection manager like wicd ?
> 
> No, this is not the case.  I've got two stretch desktop systems that
> use /e/n/i and not network-manager.  I have *never* used n-m.
> 
> > It would surprise me.
> 
> The OP is well intentioned, but is only presenting anecdotal experience
> from one system, without sufficient detail to understand where things
> went wrong.

It is very, very likely nothing went wrong and d-i did exactly what it
is designed to do, but the lack of detail on the installation conditions
makes it difficult to be be 100% certain. Please see later.

> On Sat, Jun 24, 2017 at 08:33:00PM +0100, Brian wrote:
> > The OP is particularly drawing attention to a situation which could
> > possibly occur when *Debian is installed*. Unfortunately, although one
> > of the conditions under which the installation was done (no selection
> > of a DE) is stated, the complete situation is not described. This
> > reduces the usefulness of the suggested fix.
> 
> "No DE selected" is not the underlying cause either.  I've installed
> Debian without selecting a DE, many times, on many computers, and I've
> never needed n-m.

"No DE selected" *is* one of the underlying causes. It is not really a
matter of *needing* n-m but of being given it by the installer when a
DE is selected. Please see later.

> Granted, I have never directly installed Stretch yet.  Only Jessie and
> earlier.  My two Stretch systems are upgrades.

If the OP's observations are not due to a bug you would find the Jessie
installer behaving in the same way as described below.

> If I had to guess, I would guess that the OP's system is a laptop, and
> the OP is attempting to use a wireless network of some kind.  There may
> be setups where n-m handles wireless stuff particularly well.

I dislike guessing, myself, especially when extra information is so easy
to supply, but your guess is a good one.

netcfg sets up the network during installation and writes a temporary
/e/n/i stanza. If a user installs a DE and n-m is installed the stanza
is not copied to /target, the assumption being, I suppose, that the user
would want n-m to handle the network. This happens when either a wired
or wireless connection is used to install.

If the user uses a cabled connection but does not select a DE the stanza
is copied to /target.

If a user has a wireless connection but does not select a DE the stanza
is not copied to /target but rewritten to contain loopback only and then
copied over. On first boot there is no external connectivity. Your guess
is as good as mine why a wireless installation is treated differently
from a cabled one. I have never seen any adequate justification for
denying external connectivity in this circumstance.

Sources: netcfg's 55netcfg-copy-config script and its bug record.

-- 
Brian.

Re: How did you update to stretch?

[Hans]

Am Montag, 26. Juni 2017, 15:46:00 CEST schrieb Hans:
I am responsing to myself. Just checked aptitude wiki. It is already well 
documented (what I did not know, yet), so there is no further agreement 
necessary.
On the other hand, it is good to see, that my experiences are made by other 
people, too. So I can exclude my own dumbness. :)

All this does not inhibit one thing: making debian better and better (although 
it might be already the best operating system on earth).

Best regards and happy hacking

Hans
> > Hans writes:
> Interesting! I did not notice apt, just used apt-get, apt-cache and so on.
> Just read the manual of apt. However, aptitude has also its worth, as for me
> it is faster to see, which dependencies are existent for the packages. I
> like ncurses-guis.
> 
> Same is related to synaptic, which is good to fix dependency problems.
> However, as far as I know, synaptic is just a frontend for aptitude and
> apt.
> 
> I do not want to blame any of these tools, as they might all have their
> goods and bads. But it would be nice, if we could agree to ONE tool, which
> is to be used for dist-upgrades.
> 
> And this should be well documented! At the moment IMO there are too many
> tools and that makes it very confusing, doesn't it?
> 
> Ok,. now we have about 2 years, to find the best way till the next "stable".
> 
> Best
> 
> Hans

Re: How did you update to stretch?

[Alberto Luaces]

Jonathan Dowland writes:

> That's not going to happen. I'm not even sure aptitude is maintained anymore.

Yes, it is.  And I am glad because it is my favourite tool for dealing
with updating and conflict resolving:

https://packages.qa.debian.org/a/aptitude.html

-- 
Alberto

Re: How did you update to stretch?

[Hans]

Am Montag, 26. Juni 2017, 08:26:38 CEST schrieb John Hasler:
> Hans writes:
Interesting! I did not notice apt, just used apt-get, apt-cache and so on. 
Just read the manual of apt. However, aptitude has also its worth, as for me 
it is faster to see, which dependencies are existent for the packages. I like 
ncurses-guis. 

Same is related to synaptic, which is good to fix dependency problems. However, 
as far as I know, synaptic is just a frontend for aptitude and apt. 
 
I do not want to blame any of these tools, as they might all have their goods 
and bads. But it would be nice, if we could agree to ONE tool, which is to be 
used for dist-upgrades. 

And this should be well documented! At the moment IMO there are too many tools 
and that makes it very confusing, doesn't it?

Ok,. now we have about 2 years, to find the best way till the next "stable".

Best

Hans  
> Use apt.  It is intended as an end-user interface and does everything
> apt-get does.  Apt-get is actually intended as a "back-end" tool.

Re: debian8 y vlan en mikrotik

[JAP]

El 26/06/17 a las 09:51, Ariel Alvarez escribió:

no me da red


¿Cómo está configurado el swtich? ¿Como enrutador? ¿Como switch?
¿Quién asigna dirección IP, por dhcp o estáticas?
¿Qué dice tu /etc/network/interfaces?

JAP

Re: How did you update to stretch?

[John Hasler]

Hans writes:
> As I read, aptitude is the tool for the future, so I fear, apt-get will
> disappear some day. Please don't! Aptitude does not do the job (full-upgrade)
> very well at the moment.

Use apt.  It is intended as an end-user interface and does everything
apt-get does.  Apt-get is actually intended as a "back-end" tool.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: off topic! What is the error in this script

[Greg Wooledge]

On Sun, Jun 25, 2017 at 06:30:18PM +0300, Teemu Likonen wrote:
> Dominic Knight [2017-06-25 15:35:46+01] wrote:
> 
> > To convert a series of .flac files to .mp3 files I attempted to use the
> > following line;
> >
> >> $ find -name "*.flac" -exec bash -c 'ffmpeg -i "{}" -y -acodec
> > libmp3lame -ab 320k "${0/.flac}.mp3"' {} \;

Teemu has highlighted one of the bugs here:

> The arguments for "bash -c" go like this:
> 
> bash -c '...' name one two three

The other bug is that you are have {} inside of a larger argument to
find -exec.  This is "allowed" by GNU find (a horrible misfeature of
the GNU implementation), but is not allowed by other implementations
of find, because it leads directly to a code injection vulnerability.

(You are also using the implicit "." starting path for find, which is
another GNU extension.  This one is not a security problem, just a
portability problem.)

> And in '...' the arguments are in variables $0 (=name), $1 (=one), $2
> (=two), $3 (=three) etc. So:
> 
> find -name "*.flac" -exec \
> bash -c 'ffmpeg -i file:"$1" -c:a libmp3lame -ab 320k -y 
> file:"${1%.flac}.mp3"' \
> foo {} \;
> 
> Note the "foo": it is saved to $0 ("shell's name") and and then the
> actual filename is in usual first positional parameter $1. We also want
> to have explicitl "file:" protocol with ffmpeg so that any "something:"
> prerix in filename is not interpreted as a protocol name. (See "man
> ffmpeg-protocols".)
> 
> But here's another way without double quoting:
> 
> while read -r -d $'\0' input; do
> ffmpeg -i file:"$input" -c:a libmp3lame -ab 320k \
> -y file:"${input%.flac}.mp3"
> done < <(find . -name '*.flac' -print0)

$'\0' is just the same as ''.  Also, you need to set IFS to the empty
string for this read, to suppress trimming of leading/trailing IFS
whitespace characters in filenames.

while IFS= read -r -d '' input; do ...

I'd probably add -type f to the find command.

Finally, ffmpeg is known to have an issue inside loops that read
from stdin.  Specifically, ffmpeg is one of those programs that reads
all available stdin, which means the loop will only run once, with the
other filenames being slurped up by ffmpeg with unpredictable results.
ssh is another such program.

There are two workarounds for that:

1) Add 

Re: How did you update to stretch?

[Jonathan Dowland]

On Mon, Jun 26, 2017 at 02:50:38PM +0200, Hans wrote:

I am running debian now since "potatoe", which is a rather loong time. And
in all this time I never got into any bad problems. Impressiv!


Nice. Potato was when I got started too, but I do not have any continually 
updated systems from that time. I guess if I had kept my potato machines, I'd 
still be running a Pentium Pro P200 with 32M of RAM. Still useful for something

I'm sure :)


I always remarked at every update to the next stable version is, that aptitude
might  not be the best choice for that. At every update, aptitude is ending in
a loop with trying to solve dependency conflicts.


The release notes explicitly say not to use aptitude for this. You are right,
it does not work as well.


So, how are your experiences? Did you end in the same issues as I ended?


Nope, I read the release notes and simply did

(correct sources.list)
apt-get update
apt-get upgrade
apt-get dist-upgrade
(pending reboot)


As I read, aptitude is the tool for the future, so I fear, apt-get will
disappear some day. Please don't! Aptitude does not do the job (full-upgrade)
very well at the moment.


That's not going to happen. I'm not even sure aptitude is maintained anymore.

--

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland

⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not CC me, I am subscribed to the list.

Re: apt-get upgrade problem

[Greg Wooledge]

On Sun, Jun 25, 2017 at 09:01:30AM +, Curt wrote:
> Because of the pedagogical interest of the thing, for those who come
> after us, for posterity's sake, I wanted the OP to give us a complete
> description of what occurred, rather than a misleading one (for we are
> left wondering why FF was held back in the first place, if an 'apt-get
> install' simply "went ahead and installed it."

In stretch, the upgrade from firefox-esr 45.x to 52.x requires a
new Depends: package, named libjsoncpp1.

If you are on stretch with firefox-esr 45.x and you do "apt-get upgrade"
(or the aptitude or apt or synaptics equivalent), you'll be told that
firefox-esr is held back, but you may not understand *why*, unless you
have some experience with Debian.

If you do "apt-get dist-upgrade" or "apt-get install firefox-esr", the
libjsoncpp1 package will be installed (after you confirm that it's OK),
and the firefox-esr package will be upgraded.

>From /var/log/apt/history.log:

Start-Date: 2017-06-16  14:15:04
Commandline: apt-get install firefox-esr
Requested-By: wooledg (1000)
Install: libjsoncpp1:amd64 (1.7.4-3, automatic)
Upgrade: firefox-esr:amd64 (45.9.0esr-1, 52.2.0esr-1~deb9u1)
End-Date: 2017-06-16  14:15:07

This sort of thing happens once in a while on stable, with some of the
security upgrades.  Web browsers are likely to see it, as well as
packages derived from the bind9 source package (dnsutils and so on).
This is because web browsers and bind9 are so completely full of
security holes that patching isn't even possible.  They have to roll
out new upstream versions instead.

debian8 y vlan en mikrotik

[Ariel Alvarez]

Hola lista, acudo a ustedes por que la verdad no tengo mucha experiencia 
en lo que les voy a exponer.
tengo un debian8 correctamente funcionando con algunos que otros 
servicios los cuales no vienen al tema (supongo), sucede que dicho 
debian debe estar conectado de su interface de red fisica a una 
interface de un switch gestionable tplink el cual tiene varios puertos 
dedicados a una vlan por mikrotik, el problema consiste que ya he 
probado con dos servidores distintos y misma instalacion de debian8 y al 
conectarlo a la interface del switch no me da red, sin embargo añadido a 
esto existen conectados a los demas puertos de esa misma vlan otros 
equipos windows que sin problema tienen red, como es logico la primera 
prueba que hice fue conectar el servidor debian a uno de esos puertos de 
la vlan donde se encontraban funcionando los servidores windows, sin 
ningun resultado positivo, otra prueba que hice fue poner un cable punto 
a punto entre un servidor windows y el servidor debian, en este caso sin 
problema tiene red, de hecho actualmente lo que tuve que hacer es 
ponerle una interface fisica a uno de los servidores windows y hacer un 
puente y a este conectar punto a punto el servidor debian para poder 
acceder a los servicios de este, el cual se encuentra actualmente 
funcionando asi, alguien tiene alguna experiencia similar, cualquier 
idea o sugerencia bienvenida sea.


gracias de antemano por su acostumbrada ayuda

-
Consejo Nacional de Casas de Cultura
http://www.casasdecultura.cult.cu

How did you update to stretch?

[Hans]

Hi folks,

I am running debian now since "potatoe", which is a rather loong time. And 
in all this time I never got into any bad problems. Impressiv! 

But I think, there is a little think worth to be noticed, and maybe, 
discussed.

I always remarked at every update to the next stable version is, that aptitude 
might  not be the best choice for that. At every update, aptitude is ending in 
a loop with trying to solve dependency conflicts. 

This is strange, as aptitude is running fine when using for regularly upgrades. 

So, how are your experiences? Did you end in the same issues as I ended?

The solution for me is using "apt-get dist-upgrade" and afterwards "aptitude 
full-upgrade". Doing so is working like a charme.

As I read, aptitude is the tool for the future, so I fear, apt-get will 
disappear some day. Please don't! Aptitude does not do the job (full-upgrade) 
very well at the moment. 

I believe, this is not a bug, I more believe. this is a problem for the 
algorithm to solve the complexity of the dependencies due to the complicated 
ruleset aptitude is using. As far as I know, apt-get is using a more simple 
ruleset, so it can resolve dependencies better.

What are your experiences? What are you prefer at distribution upgrades?

If this discussion is interesting for you, I will be happy, if not, sorry for 
the noise. 

Best regards and thanks for debian!

Hans 

Re: [Stretch] Fix for not network after installing without desktop

[Greg Wooledge]

On Sat, Jun 24, 2017 at 11:07:13AM +0200, Erwan David wrote:
> Do you mean that network-manager is compulsory in stretch ? Impossible
> to use a fixed configuration in /etc/network/interfaces or another
> connection manager like wicd ?

No, this is not the case.  I've got two stretch desktop systems that
use /e/n/i and not network-manager.  I have *never* used n-m.

> It would surprise me.

The OP is well intentioned, but is only presenting anecdotal experience
from one system, without sufficient detail to understand where things
went wrong.

On Sat, Jun 24, 2017 at 08:33:00PM +0100, Brian wrote:
> The OP is particularly drawing attention to a situation which could
> possibly occur when *Debian is installed*. Unfortunately, although one
> of the conditions under which the installation was done (no selection
> of a DE) is stated, the complete situation is not described. This
> reduces the usefulness of the suggested fix.

"No DE selected" is not the underlying cause either.  I've installed
Debian without selecting a DE, many times, on many computers, and I've
never needed n-m.

Granted, I have never directly installed Stretch yet.  Only Jessie and
earlier.  My two Stretch systems are upgrades.

If I had to guess, I would guess that the OP's system is a laptop, and
the OP is attempting to use a wireless network of some kind.  There may
be setups where n-m handles wireless stuff particularly well.

Re: light-locker (was Stretch upgrade from Jessie -- several issues)

[Greg Wooledge]

On Sun, Jun 25, 2017 at 07:23:10PM -0600, Ralph Katz wrote:
> While purging xscreensaver removed 2 or 3 packages, installing now would
> bring in a host of packages, for whatever reason.  I don't need a
> screensaver as much as I need the lock.

I use i3lock, from a terminal, exactly as I used to use "xlock" when
Debian still had that.  (I don't use any other part of i3.)

Stretch : nfs-common service on nfs server

[Prunk Dump]

Hello Debian Team !

I have three NFSv4 server on my network, all Debian Jessie recently
upgraded to Stretch.

Usually on Jessie, two services are running on NFS servers :
-> nfs-common that is used for both nfs clients and server
-> nfs-kernel-server that is used only by the server

But since the upgrade the nfs-common service is masked on servers. So
to restart all the nfs "common" services I need to restart
individually each the rpc.* services.

Is this normal that the nfs-common service become masked ? Is there
some documentation about this change ?

Can I unmask It to manage all the nfs "common" services ?

If someone can help me.

Thanks !

Baptiste.

Re: Actualización del repositorio trajo errores

[JAP]

El 25/06/17 a las 22:45, Miguel Matos escribió:

Muy buenas, quise aprovechar en realizar el update masivo luego de que
ya salió la nueva versión de Debian. Y al hacerlo me arrojó tamaños
errores, ¡más de uno!
Acá el resultado por terminal:
Err:72 http://ftp.cl.debian.org/debian testing/main Sources
  Writing more data than expected (6984840 > 6984328)
  Hashes of expected file:
   - Filesize:6984328 [weak]
   - SHA256:a8777e22b39c4cebcc2155e92960e9fda36695653a2237067dbdfb58dbb3d1bf
   - MD5Sum:73a8a9e421b1c8adb04ea76c892561a3 [weak]
  Release file created at: Sun, 25 Jun 2017 08:28:51 +
Descargados 286 kB en 1min 43s (2.774 B/s)
Leyendo lista de paquetes... Hecho
W: El repositorio «https://dl.winehq.org/wine-builds/debian stable
Release» no tiene un fichero de Publicación.
N: Los datos de un repositorio como este no se pueden autenticar y por
tanto su uso es potencialmente peligroso.
N: Vea la página de manual apt-secure(8) para los detalles sobre la
creación de repositorios y la configuración de usuarios.
E: Fallo al obtener
https://dl.winehq.org/wine-builds/debian/dists/stable/main/binary-i386/Packages
 403  Forbidden
E: Fallo al obtener
http://ftp.cl.debian.org/debian/dists/testing/main/source/Sources.xz
Writing more data than expected (6984840 > 6984328)
   Hashes of expected file:
- Filesize:6984328 [weak]
- SHA256:a8777e22b39c4cebcc2155e92960e9fda36695653a2237067dbdfb58dbb3d1bf
- MD5Sum:73a8a9e421b1c8adb04ea76c892561a3 [weak]
   Release file created at: Sun, 25 Jun 2017 08:28:51 +
E: Fallo al obtener
http://ftp.cl.debian.org/debian/dists/testing/main/binary-i386/Packages.xz
 404  Not Found
E: No se han podido descargar algunos archivos de índice, se han
omitido, o se han utilizado unos antiguos en su lugar.

Mi distribución la he etiquetado como "testing", y acá mi sources.list
en la actualidad:
## Repositorio Oficial
deb http://ftp.cl.debian.org/debian/ testing main contrib non-free
deb-src http://ftp.cl.debian.org/debian/ testing main contrib non-free

deb http://security.debian.org/ testing/updates main contrib non-free
deb-src http://security.debian.org/ testing/updates main contrib non-free

# testing-updates, previously known as 'testing', and previously known
as 'volatile'
deb http://ftp.cl.debian.org/debian/ testing-updates main contrib non-free
deb-src http://ftp.cl.debian.org/debian/ testing-updates main contrib non-free

# testing-actualizaciones-sistema
deb http://mirrors.kernel.org/debian/ testing-updates main contrib non-free
deb-src http://mirrors.kernel.org/debian/ testing-updates main contrib non-free

# testing-backports
# deb http://mirrors.kernel.org/debian/ testing-backports main contrib non-free
# deb-src http://mirrors.kernel.org/debian/ testing-backports main
contrib non-free

#
# Aquí se agregan los repositorios de aplicaciones externas a los de Debian
#

# deb-multimedia
# apt-get install deb-multimedia-keyring
deb http://www.deb-multimedia.org/ testing main non-free
deb-src http://www.deb-multimedia.org/ testing main non-free

# Wine Repository
deb https://dl.winehq.org/wine-builds/debian/ stable main

¿Debo continuar con el apt-get dist-upgrade sin problemas? Aunque
capaz surgirán problemas por dependencias sin cumplir que estén atadas
a estos repositorios... ¿O será conveniente primero solucionar esto?
Voy a indagar con google la primera de las fallas, pero igual les
escribo para saber si pasaron por lo mismo que yo.




Te recomiendo hacer una actualización un tanto más conservadora.

Cuando existe un cambio de versión, fíate sólo de
ftp.debian.org/debian/ testing main contrib non-free

A veces, los espejos de otros países no están todo lo actualizado que 
debieran, sobre todo, los primeros días.


Lo segundo, yo primero actualizaría la línea principal, o sea
ftp.debian.org/debian/ testing main contrib non-free


Luego, a medida que las cosas funcionas, iría agregando
ftp.debian.org/debian/ testing-updates main contrib non-free
ftp.debian.org/debian/ testing-proposed-updates main contrib non-free

Ahora la pregunta:
¿De dónde sacaste

> deb http://security.debian.org/ testing/updates main contrib non-free
> deb-src http://security.debian.org/ testing/updates main contrib non-free

Los "security" son para "stable"


Además, hasta que tengas TODO tu sistema corriendo sin problemas, no 
agregues "multimedia" o "wine-hq"


JAP

Re: Paquetes retenidos y aplicaciones rotas tras actualizar a Debian 9

[JAP]

El 26/06/17 a las 05:57, Iván Hernández Cazorla escribió:

Buenas,
Creo que no es la primera vez que me suscribo a esta lista de correo,
pero nunca está de más agradecer a todos aquellos que atienden los
correos de antemano. Gracias. Bueno, les comento mi problema.

Últimamente ando un poco desactualizado de las novedades de todo,
inclusive de Debian. Fue ayer cuando me enteré de que el 17 de junio de
2017 se lanzó Debian 9 Stretch
. Con la emoción fui un poco
a la desesperada y busqué rápidamente "how to upgrade debian 8 to 9" y
me encontré con este tutorial
.

Lo seguí al pie de la letra. Pero, cuando el ordenador se reinició tras
ejecutar *shutdown -r now*, comprobé que algo no había ido bien por dos
razones:

 1. Al ejecutar *lsb_release -a *me mostraba (y sigue mostrando este
mensaje):
No LSB modules are available.
Distributor ID:Debian
Description:Debian GNU/Linux 9.0 (n/a)
Release:9.0
Codename:n/a
Donde debería indicar el codename "Stretch", no indica nada, solo n/a.
 2. Hay programas que se han roto. Por ej. el navegador de archivos
"nemo" y VLC.

Como no atinaba con que podía ser la razón de este fallo, ejecuté un
*apt-get update *y luego un *upgrade* para comprobar que todos los
paquetes se habían actualizado. Sin embargo, para mi sorpresa, a estas
horas de la mañana que he vuelto a intentarlo, me dice que:

1 actualizados, 0 nuevos se instalarán, 0 para eliminar y 748 no
actualizados.

Al revisar los 748 paquetes no actualizados por encima, me encuentro con
la sorpresa de que VLC y sus dependencias, de la misma manera que muchos
otros, no se han actualizado, razón por la que creo que en estos
momentos no funciona.

Quitando esto, creo además que el comportamiento del cargador ha
comenzado a hacer cosas extrañas, pero esto ya es otra cuestión que iré
analizando con el tiempo de uso de Stretch.

Les adjunto una imagen con la información del sistema por si fuese de
alguna utilidad.

Muchas gracias de antemano.

Saludos, Iván



El cambio de nombre en cada equipo, siempre es algo que a veces, tarda.
Por ejemplo, yo estoy en "testing", y aún sigue como Debian 9 Stretch.

Recomendación: luego de

# apt-get upgrade

haz un

# apt-get dist-upgrade

Probablemente tengas paquetes que se estén reteniendo.

Esto va a hacer una actualización más completa y va a solucionar cosas 
que una actualización normal no hace, por tema de seguridad del sistema.


dist-upgrade in addition to performing the function of upgrade, also 
intelligently handles changing dependencies with new versions of 
packages; apt-get has a "smart" conflict resolution system, and it will 
attempt to upgrade the most important packages at the expense of less 
important ones if necessary. The dist-upgrade command may therefore 
remove some packages. The /etc/apt/sources.list file contains a list of 
locations from which to retrieve desired package files. See also 
apt_preferences(5) for a mechanism for overriding the general settings 
for individual packages.


JAP

[Resolu] Re: [Stetch] Pas de connexion WIFI : aborting authentication ... by local choice (Reason: 3=DEAUTH_LEAVING)

[Yann Cohen]

Bonjour,

Hier j'ai reçu un mail de Maurico dans lequel il est fait référence à
un bug lié aux noms long des interfaces (le nom avec l'adresse MAC).

Le contournement est d'inhiber l'utilisation des noms longs avec la
command suivante 
ln -s /dev/null /etc/systemd/network/99-default.link

au redémarrage suivant (un peu plus long pour perte d'interface), les
noms "courts" sont de retour et la connexion WIFI fonctionne bien.

Bonne journée.

Yann.

Le jeudi 25 mai 2017 à 11:19 +0200, Yann Cohen a écrit :
> Bonjour,
> 
> J'ai réinstallé mon portable lenovo Yoga 13 sous stretch et je
> rencontre des problèmes lors de la connexion WIFI
> 
> De base j'ai sous usb une puce RTL8723AU (Wifi+BT) qui est reconnue
> via
> lsusb et dans les messages de démarrage
> 
> Bus 001 Device 004: ID 0bda:1724 Realtek Semiconductor Corp.
> RTL8723AU
> 802.11n WLAN Adapter
> 
> May 21 23:38:57 yogayan kernel: [   19.262374] usb 1-1.4: rtl8xxxu:
> Loading firmware rtlwifi/rtl8723aufw_B_NoBT.bin
> May 21 23:38:57 yogayan kernel: [   19.267786] usb 1-1.4: firmware:
> direct-loading firmware rtlwifi/rtl8723aufw_B_NoBT.bin
> May 21 23:38:57 yogayan kernel: [   19.267813] usb 1-1.4: Firmware
> revision 31.0 (signature 0x2302)
> 
> en plus j'ai une clé DLink
> Bus 001 Device 010: ID 07d1:3c07 D-Link System DWA-110 Wireless G
> Adapter(rev.A1) [Ralink RT2571W]
> 
> 
> Dans les deux cas j'ai le même symptôme lors de la tentative de
> connexion en WIFI sur tous les ssid disponibles dans mon
> environnement
> :
> aborting authentication with 9a:a1:d7:52:c2:71 by local choice
> (Reason:
> 3=DEAUTH_LEAVING)
> 
> Bien entendu "avant" le passage sous stretch, ce portable en Jessie
> fonctionnait en wifi sans problème...
> 
> Mon ami google ne m'a pas été d'une grande aide sur ce point ou bien
> je
> n'ai pas su lui poser la question correctement...
> 
> Merci d'avance pour vos remarques et suggestions...
> 
> 
> Yann.
> 
> 
> Trace dans /var/log/syslog lors de la connexion à un ssid WIFI ouvert
> 8>---
> -
> May 25 10:58:05 yogayan NetworkManager[572]:
>   [1495702685.2214]
> device (wlxa4db30024657): set-hw-addr: set MAC address to
> 66:2B:4E:B9:A6:EA (scanning)
> May 25 10:58:05 yogayan kernel: [ 1285.548176] IPv6:
> ADDRCONF(NETDEV_UP): wlxa4db30024657: link is not ready
> May 25 10:58:08 yogayan NetworkManager[572]:
>   [1495702688.6778]
> device (wlxa4db30024657): Activation: starting connection 'SFR WiFi
> FON' (b8e934d1-75ff-46a7-a6d2-dbca8ec880d8)
> May 25 10:58:08 yogayan NetworkManager[572]:
>   [1495702688.6786]
> audit: op="connection-activate" uuid="b8e934d1-75ff-46a7-a6d2-
> dbca8ec880d8" name="SFR WiFi FON" pid=11829 uid=1000 result="success"
> May 25 10:58:08 yogayan NetworkManager[572]:
>   [1495702688.6794]
> device (wlxa4db30024657): state change: disconnected -> prepare
> (reason
> 'none') [30 40 0]
> May 25 10:58:08 yogayan NetworkManager[572]:
>   [1495702688.7746]
> device (wlxa4db30024657): set-hw-addr: reset MAC address to
> A4:DB:30:02:46:57 (preserve)
> May 25 10:58:08 yogayan kernel: [ 1289.101900] IPv6:
> ADDRCONF(NETDEV_UP): wlxa4db30024657: link is not ready
> May 25 10:58:08 yogayan NetworkManager[572]:
>   [1495702688.8085]
> device (wlxa4db30024657): state change: prepare -> config (reason
> 'none') [40 50 0]
> May 25 10:58:08 yogayan NetworkManager[572]:
>   [1495702688.8121]
> device (wlxa4db30024657): Activation: (wifi) connection 'SFR WiFi
> FON'
> requires no security.  No secrets needed.
> May 25 10:58:08 yogayan NetworkManager[572]:
>   [1495702688.8129]
> Config: added 'ssid' value 'SFR WiFi FON'
> May 25 10:58:08 yogayan NetworkManager[572]:
>   [1495702688.8133]
> Config: added 'scan_ssid' value '1'
> May 25 10:58:08 yogayan NetworkManager[572]:
>   [1495702688.8138]
> Config: added 'key_mgmt' value 'NONE'
> May 25 10:58:08 yogayan wpa_supplicant[660]: wlxa4db30024657: SME:
> Trying to authenticate with 9a:a1:d7:52:c2:71 (SSID='SFR WiFi FON'
> freq=2437 MHz)
> May 25 10:58:08 yogayan kernel: [ 1289.150740] wlxa4db30024657:
> authenticate with 9a:a1:d7:52:c2:71
> May 25 10:58:08 yogayan kernel: [ 1289.160992] wlxa4db30024657: send
> auth to 9a:a1:d7:52:c2:71 (try 1/3)
> May 25 10:58:08 yogayan kernel: [ 1289.162624] wlxa4db30024657:
> authenticated
> May 25 10:58:08 yogayan NetworkManager[572]:
>   [1495702688.8572]
> device (wlxa4db30024657): supplicant interface state: inactive ->
> authenticating
> May 25 10:58:13 yogayan kernel: [ 1294.166593] wlxa4db30024657: 
> May 25 10:58:13 yogayan wpa_supplicant[660]: wlxa4db30024657: CTRL-
> EVENT-SSID-TEMP-DISABLED id=0 ssid="SFR WiFi FON" auth_failures=1
> duration=10 reason=CONN_FAILED
> May 25 10:58:13 yogayan NetworkManager[572]:
>   [1495702693.8652]
> device (wlxa4db30024657): supplicant interface state: authenticating
> ->
> disconnected
> May 25 10:58:23 yogayan NetworkManager[572]:
>   [1495702703.8721]
> device (wlxa4db30024657): supplicant interface state: disconnected ->
> scanning

[Solved] Re: Stretch, WIFI connection failed with aborting authentication with ... by local choice (Reason: 3=DEAUTH_LEAVING)

[Yann Cohen]

Hi,

Yesterday I received a mail from Maurico in which there is reference to
a bug related to long names interfaces (the name with the MAC address).

The workaround is to inhibit the use of long names with the following
command
Ln -s / dev / null /etc/systemd/network/99-default.link

At the next restart (a little longer for interface loss), the short
names are back and the WIFI connection works.

Thanks.

Cheers,

Yann.
Le lundi 19 juin 2017 à 19:59 +0200, Yann Cohen a écrit :
> Hello,
> 
> Le samedi 10 juin 2017 à 10:21 -0500, Richard Owlett a écrit :
> > On 06/10/2017 08:04 AM, Yann Cohen wrote:
> > > Hello,
> > > 
> 
> [...]
> > 
> > > Last week, I reinstalled my laptop (lenovo YOGA 13) with Debian
> > > Stretch  and network-manager.
> > > 
> > > Linux yogayan 4.9.0-3-amd64 #1 SMP Debian 4.9.30-1 (2017-06-04)
> > > x86_64
> > > GNU/Linux
> > > 
> > > Bus 001 Device 004: ID 0bda:1724 Realtek Semiconductor Corp.
> > > RTL8723AU
> > > 802.11n WLAN Adapter
> > 
> > That is likely your problem.
> > See thread beginning at
> > .
> > Cindy-Sue Causey pointed to
> > 
> > 
> > See also comment by Pascal Hambourg at
> > 
> > 
> > HTH
> > 
> 
> Well,
> 
> I summarize the situation :
>  * the WIFI interface embedded on my laptop has been working fine for
>    three with debian jessie
>  * on stretch, I installed realtek non-free firmware 
>  * at boot time, in dmesg, I can see the successful loading of the
>    firmware
> [   11.811782] usb 1-1.4: firmware: direct-loading firmware
> rtlwifi/rtl8723aufw_B_NoBT.bin
> [   11.811794] usb 1-1.4: Firmware revision 31.0 (signature
> 0x2302)
>  * the connection failed "by local choice (Reason: 3=DEAUTH_LEAVING)"
>  * I got 2 usb WIFI dongle (which work fine on my raspberry pi
>    -raspbian jessie-). For each the same message appears in the
> log...
>  * I tried to use this dongles on too other stretch workstation with
>    the same negative result.
>  * I have an other laptop with an PCI WIFI (Qualcomm Atheros QCA9565
> /
>    AR9565) interface which works fine with debian stretch...
> 
> 
> > From my point of view, I did everything right, at least like the
> > Jessie
> 
> configuration.
> But obviously it seems not !
> and I can't find where !
> I look more and more like a dog trying to catch his tail !
> 
> So, with the publication of Stretch as stable few days ago, maybe  I
> would no be the only to have this issue...
> 
> --- Begin Message ---
Correction, the source is this
https://www.reddit.com/r/debian/comments/5tdp8q/stretch_wifi_error/ (I had
a lot of tabs open, sorry)

On Sun, Jun 25, 2017 at 7:23 AM, Mauricio  wrote:

> Hello Yann,
>
> I found your mail on the web and I think I have a solution (it has worked
> for me!).
>
> As root, run:
>
> ln -s /dev/null /etc/systemd/network/99-default.link
>
> This will prevent systemd to create the long network interfaces names. It
> seems some firmwares don't play well with them. You must unplug-plug the
> USB dongle (or restart of it is internal).
>
> This has worked for me. I'm using a TL-WN821N (atheros firmware) Wifi USB
> dongle.
>
> My source:
> https://www.reddit.com/r/debian/comments/5leii8/unable_
> to_connect_to_wifi_with_usb_adapter_via/
>
> I hope this helps you. Happy hacking!
>

--- End Message ---

Re: firewall rules for NAT

[Dan Purgert]

Lucio Crusca wrote:
>[...]
> It works like a charm, but there is one problem: my mail server receives 
> all the connections from the router, which has its own private IP 
> address (10.7.33.100), so the mail server can't enforce SPF policies nor 
> DNS RBL rules on incoming mail connections.

That shouldn't be happening -- you may have an errant rule you didn't
show from one of the hosts in there that's doing this to you (perhaps
NAT Hairpin).

-- 
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

Re: Présence par défaut d'Aptitude sur Stretch

[G2PC]

Le 26/06/2017 à 11:09, maderios a écrit :
> On 06/26/2017 09:47 AM, Daniel Caillibaud wrote:
>> Le 24/06/17 à 15:36, maderios  a écrit :
>> M> C'est quand même gênant cette manie d'aptitude qui consiste à
>> supprimer
>> M> automatiquement des paquets qu'il considère comme inutiles. Un
>> exemple,
>> M> celui de certains paquets *.dev.
>>
>> Dans ce cas, c'est qu'ils ont été installés comme dépendances d'un
>> truc qui a disparu, et ça
>> parait logique de les enlever (les autres gestionnaires doivent faire
>> la même chose).
>
> La logique, c'est de respecter la volonté de l'utilisateur. C'est ce
> que font apt, apt-get et synaptic
>>
>> Si tu as installé manuellement de paquet *dev, aptitude ne le virera
>> pas.
> Ce n'est pas le cas
>>
>> M> Si quelqu'un connaît une solution pour améliorer le qI d'aptitude, je
>> M> suis preneur :)
>>
>> Je dis pas qu'aptitude est plus malin, mais faudrait un exemple
>> concret de cas où il ne prend
>> pas la bonne décision.
>>
> aptitude n'a pas à prendre de décision à la place de l'utilisateur
> concernant la suppression de paquets. Il devrait se comporter comme
> apt, apt-get et synaptic: indiquer que certains paquets ne sont plus
> nécessaires et non les supprimer.
>
+1 car sinon, comment gérer les configurations ? Est ce le comportement
normal de aptitude ?
Je ne vais pas oser l'utiliser alors. Comment me rassurer pour sa bone
utilisation ?

Re: Présence par défaut d'Aptitude sur Stretch

[maderios]

On 06/26/2017 09:47 AM, Daniel Caillibaud wrote:

Le 24/06/17 à 15:36, maderios  a écrit :
M> C'est quand même gênant cette manie d'aptitude qui consiste à supprimer
M> automatiquement des paquets qu'il considère comme inutiles. Un exemple,
M> celui de certains paquets *.dev.

Dans ce cas, c'est qu'ils ont été installés comme dépendances d'un truc qui a 
disparu, et ça
parait logique de les enlever (les autres gestionnaires doivent faire la même 
chose).


La logique, c'est de respecter la volonté de l'utilisateur. C'est ce que 
font apt, apt-get et synaptic


Si tu as installé manuellement de paquet *dev, aptitude ne le virera pas.

Ce n'est pas le cas


M> Si quelqu'un connaît une solution pour améliorer le qI d'aptitude, je
M> suis preneur :)

Je dis pas qu'aptitude est plus malin, mais faudrait un exemple concret de cas 
où il ne prend
pas la bonne décision.

aptitude n'a pas à prendre de décision à la place de l'utilisateur 
concernant la suppression de paquets. Il devrait se comporter comme apt, 
apt-get et synaptic: indiquer que certains paquets ne sont plus 
nécessaires et non les supprimer.


--
Maderios

Paquetes retenidos y aplicaciones rotas tras actualizar a Debian 9

[Iván Hernández Cazorla]

Buenas,
Creo que no es la primera vez que me suscribo a esta lista de correo, pero
nunca está de más agradecer a todos aquellos que atienden los correos de
antemano. Gracias. Bueno, les comento mi problema.

Últimamente ando un poco desactualizado de las novedades de todo, inclusive
de Debian. Fue ayer cuando me enteré de que el 17 de junio de 2017 se lanzó
Debian 9 Stretch . Con la
emoción fui un poco a la desesperada y busqué rápidamente "how to upgrade
debian 8 to 9" y me encontré con este tutorial

.

Lo seguí al pie de la letra. Pero, cuando el ordenador se reinició tras
ejecutar *shutdown -r now*, comprobé que algo no había ido bien por dos
razones:

   1. Al ejecutar *lsb_release -a *me mostraba (y sigue mostrando este
   mensaje):
   No LSB modules are available.
   Distributor ID:Debian
   Description:Debian GNU/Linux 9.0 (n/a)
   Release:9.0
   Codename:n/a
   Donde debería indicar el codename "Stretch", no indica nada, solo n/a.
   2. Hay programas que se han roto. Por ej. el navegador de archivos
   "nemo" y VLC.

Como no atinaba con que podía ser la razón de este fallo, ejecuté un *apt-get
update *y luego un *upgrade* para comprobar que todos los paquetes se
habían actualizado. Sin embargo, para mi sorpresa, a estas horas de la
mañana que he vuelto a intentarlo, me dice que:

> 1 actualizados, 0 nuevos se instalarán, 0 para eliminar y 748 no
> actualizados.
>
Al revisar los 748 paquetes no actualizados por encima, me encuentro con la
sorpresa de que VLC y sus dependencias, de la misma manera que muchos
otros, no se han actualizado, razón por la que creo que en estos momentos
no funciona.

Quitando esto, creo además que el comportamiento del cargador ha comenzado
a hacer cosas extrañas, pero esto ya es otra cuestión que iré analizando
con el tiempo de uso de Stretch.

Les adjunto una imagen con la información del sistema por si fuese de
alguna utilidad.

Muchas gracias de antemano.

Saludos, Iván

Re: Présence par défaut d'Aptitude sur Stretch

[Daniel Caillibaud]

Le 24/06/17 à 15:36, maderios  a écrit :
M> C'est quand même gênant cette manie d'aptitude qui consiste à supprimer 
M> automatiquement des paquets qu'il considère comme inutiles. Un exemple, 
M> celui de certains paquets *.dev.

Dans ce cas, c'est qu'ils ont été installés comme dépendances d'un truc qui a 
disparu, et ça
parait logique de les enlever (les autres gestionnaires doivent faire la même 
chose).

Si tu as installé manuellement de paquet *dev, aptitude ne le virera pas.

M> Si quelqu'un connaît une solution pour améliorer le qI d'aptitude, je 
M> suis preneur :)

Je dis pas qu'aptitude est plus malin, mais faudrait un exemple concret de cas 
où il ne prend
pas la bonne décision.

-- 
Daniel

Une belle idée qui n'aboutit pas vaut mieux qu'une
mauvaise qui voit le jour.
Pierre Dac

Re: Upgrade de Jessie

[G2PC]

Le 26/06/2017 à 09:37, maderios a écrit :
> On 06/25/2017 05:48 PM, Pierre L. wrote:
>> Voilà qui devrait apaiser quelques esprits ;)
>>
>> Peace!
>>
>> Le 24/06/2017 à 21:01, andre_deb...@numericable.fr a écrit :
>>> "Laisser le soin aux cobayes" étaient à prendre au second
>>> degré, étant conscient et admiratif du formidable travail accompli
>>> durant toutes ces années par l'équipe technique de Debian pour
>>> chaque nouvelle version.
>>>
> Une déclaration qui peut concerner tous les domaines, y compris celui
> du logiciel libre:
>
> "Ne vous demandez pas ce que votre pays peut faire pour vous,
> demandez-vous ce que vous pouvez faire pour votre pays"
>
> (John Fitzgerald KENNEDY)
>
Le cobaye, avec vin rouge et champignons, ça doit être très bon.
Merci à tous les collaborateurs Debian qui participent à la stabilité du
projet.
Bonne semaine à tous.

Re: Upgrade de Jessie

[maderios]

On 06/25/2017 05:48 PM, Pierre L. wrote:

Voilà qui devrait apaiser quelques esprits ;)

Peace!

Le 24/06/2017 à 21:01, andre_deb...@numericable.fr a écrit :

"Laisser le soin aux cobayes" étaient à prendre au second
degré, étant conscient et admiratif du formidable travail accompli
durant toutes ces années par l'équipe technique de Debian pour
chaque nouvelle version.

Une déclaration qui peut concerner tous les domaines, y compris celui du 
logiciel libre:


"Ne vous demandez pas ce que votre pays peut faire pour vous, 
demandez-vous ce que vous pouvez faire pour votre pays"


(John Fitzgerald KENNEDY)

--
Maderios

Re: Stretch upgrade from Jessie -- several issues

[Floris]

Op Mon, 26 Jun 2017 03:23:32 +0200 schreef Ralph Katz  
:



-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 06/25/2017 04:22 PM, Floris wrote:


Op Sun, 25 Jun 2017 19:10:40 +0200 schreef Ralph Katz
:



3) The sound volume up/down function keys [Fn up/down arrow] no
longer respond (xfce4).  However the screen brightness keys
function normally [Fn left/right arrow].  The mute sound
function key is also ignored [Fn F8].  I can control volume
with the mouse using pavucontrol or gkrellm-volume.


No progress.


if the keys are recognized by the kernel, then you can remap them
with an udev hwdb rule.

Test with evtest if the keys get a scancode and a keycode.
Something like: type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0
type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1 In this case I
pressed the Left Ctrl key, which has a value of 700e0

Create a new rule in /etc/udev/hwdb.d with something like:

evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*
KEYBOARD_KEY_ed=volumeup KEYBOARD_KEY_ee=volumedown etc...

use evemu-describe to find your evdev:... line

also read:
https://wiki.archlinux.org/index.php/Map_scancodes_to_keycodes
https://wiki.archlinux.org/index.php/Extra_keyboard_keys
/lib/udev/hwdb.d/60-keyboard.hwdb for more information and
examples

Floris


Thanks Floris!  I will look into this, but I am confounded as to why
on jessie and previous versions, recognizing these sound keys was
automatic.

Ralph



Maybe the switch from "the old" xserver-xorg-input-evdev to "the Wayland"  
xserver-xorg-input-libinput has something to do with it. But I don't know  
if you have the libinput version installed.


https://packages.debian.org/stretch/xserver-xorg-input-libinput
...
X.Org X server -- libinput input driver

This package provides the driver for input devices using libinput library.  
It can handle keyboards, mice and touchpads, and essentially replaces the  
separate -evdev and -synaptics drivers.

...

Floris

migration de stretch à buster

[Jean Louis Giraud Desrondiers]

Bonjour, 
migration effectuée à l'instant en 30 mn montre en main (incluant les
sauvegardes préalables) et me voilà avec un buster tout beau tout
neuf ! Un grand merci aux développeurs et à leur super boulot ! 

-- 
Cordialement, 

Jean Louis Giraud Desrondiers