Re: Detect upgradable packages in shell script ran as a non-root user

[Tixy]

On Wed, 2016-11-30 at 17:09 +0200, Martin T wrote:
> I would like to run a cron job which periodically checks if I have
> upgradable packages. One way to do it is probably like this:

What do you want to do with the information once you got it? I ask
because Debian includes some packages to do various periodic things for
updates and you might be reinventing the wheel. E.g. I use apticron [1]
on all the machines I manage which periodically checks if there's
upgradable packages an emails me a summary of them if there are. I
believe there are also means on doing other things.

[1] 
https://debian-administration.org/article/491/Automatic_package_update_nagging_with_apticron

-- 
Tixy  

Re: Cómo activar placa de red (notebook)

[Rivera Valdez]

Acabo de bootear con la imagen live de Debian con el firmware non-free incluido.
Siguen sin funcionar ni la placa de red ni la wireless, y me topo con
lo siguiente:

root@debian:/home/user# iwconfig
lono wireless extensions.

wlan0 IEEE 802.11bgn  ESSID:off/any
  Mode:Managed  Access Point: Not-Associated   Tx-Power=off
  Retry short limit:7   RTS thr:off   Fragment thr:off
  Encryption key:off
  Power Management:off

eth0  no wireless extensions.

root@debian:/home/user# ifconfig wlan0 up
SIOCSIFFLAGS: Operation not possible due to RF-kill


Ahora voy a ver qué es RF-kill, pero si tienen alguna orientación al
respecto, bienvenida.

Saludos, y muchas gracias de nuevo.

Re: arm people distributing images with user 1000 already allocated, please stop that

[Gene Heskett]

On Thursday 01 December 2016 15:30:12 emetib wrote:

> gene i can understand your pain.  one of the reasons that i don't
> necessarily like sudo systems.
>
> one of the first things that i do when i have a sudo system, ubuntu,
> lmde, raspbian, is to 'sudo su' and then 'passwd' to actually set a
> root password.
>
> i have found that this has remedied the situation that you have
> described here.  with doing the above you wouldn't have to mount the
> sd somewhere else, you just make a new password for root.

The last time I tried that, some years ago, it demanded the old passwd 
first. I think that was about Red Hat 7.1's day. I'd been using it since 
1998 and 5.0.

> i hope that this helps some for future reference.
If no pw is needed, great.
> take care
> em

Well, I am behind a dd-wrt install, which has not been penetrated in over 
a decade of using it. I am the only user unless the Mrs wants to sit 
down and answer an email from her niece in noo yauwk.

That doesn't happen too often as she is getting awful close to dragging 
an oxygen bottle around, COPD, and because computer keyboards scare her 
with all those strange keys and a mouse may as well be a roulette wheel.  
So I'm it. She doesn't even have an account on this box.  So it doesn't 
bither me a bot that the root pw is a linefeed on that little SBC. If 
somehow, someone does root it, I'll always have lst night's amanda 
backup of it. Gotta run, I'm cooking.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Paket Quisk-Error

[Dan Ritter]

On Thu, Dec 01, 2016 at 09:29:31PM +0100, Peter Seifert wrote:
> root@raspberry:~# quisk
> 
> 
> 20:24:28: Warning: Mismatch between the program and library build versions 
> detected.
> The library used 3.0 (wchar_t,compiler with C++ ABI 1010,wx 
> containers,compatible with 2.8),
> and wxPython used 3.0 (wchar_t,compiler with C++ ABI 1009,wx 
> containers,compatible with 2.8).
> Unable to access the X Display, is $DISPLAY set properly?
> 
> (process:731): GLib-GObject-CRITICAL **: g_type_class_unref: assertion 
> 'g_class != NULL' failed
> 
> 
> ---
> what is this?
> 

It's an SDR program called quisk that wants an X11 display and
can't find one.

-dsr-

Re: Cómo activar placa de red (notebook)

[José María]

El 01/12/16 a las 17:31, Rivera Valdez escribió:

No hombre, no está bloqueado, solo es un cambio de "nombre".

¿Hay alguna manera de volver a poner el "nombre" anterior?


El comando "ifconfig" te dio "eth0" (que es la tarjeta de red)



Entiendo que el sistema instalado no encuentre la placa por tener el
"nombre" cambiado, pero ¿por qué no la encuentran los sistemas que
booteo en LiveUSB?
¿Puede ser que el firmware (non-free) de la placa wireless que instalé
y luego desinstalé (firmware-iwlwifi) haya modificado el firmware de
la placa de red?
En ese caso, ¿dónde/cómo se edita eso?



Creo que te estás liando, el firmware es para el wifi, no para el cable




Y he de suponer que ni en Trisquel ni en Parabola tendrías wifi porque son
proyectos de software libre y el firmware que vas a instalar (o has
instalado) no lo es.

Correcto. Pero los derivados de Debian (Trisquel) no se conectan a la
red cableada. Parabola/Arch en cambio usan la red cableada con este
"nombre" nuevo (enp6s0). ¿Se le puede indicar al sistema que use ese
otro "nombre" entonces?



Que Parabola o Arch usen ese nombre a tí te tiene que dar igual, usa los 
datos que te ofrece tu Debian, el que tienes INSTALADO.






El problema es no sabemos que has hecho para que no tengas conexión por
cable, o sea, como intestaste activar el wifi.

Instalé el paquete firmware-iwlwifi con gdebi (los mismos pasos que
reproduje en la salida de terminal que pegué antes), descargué y volví
a cargar el módulo indicado (modprobe -r iwlwifi ; modprobe iwlwifi),
y como la conexión wireless seguía sin aparecer, desinstalé iwlwifi
con apt-get.
Al reiniciar el sistema ya no se conectaba con la placa de red (que es
esta, según lshw):

Ethernet interface
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controler
Realtek Semiconductor Co., Ltd.


Así que deshaz todo lo que hayas hecho hasta que tenías conexión por cable y
después sigue los pasos para instalar el firmware como te pone en la wiki
[1].

Hecho. Pero deshechos todos los pasos, no vuelve a conectarse por
cable (eth0) ni de ningún otro modo.


Si no te acuerdas reinstala el sistema. No te compliques.

Preferiría evitar esto. El disco está encriptado y desde las distros
en modo Live no consiguen abrir el contenido, de modo que hacer un
backup está doblemente complicado (al margen de que reinstalar el
sistema me significaría una enorme pérdida de tiempo adicional, desde
ya).


Si lo ves muy complicado usa una imagen live con el firmware non-free
incluido [2].

Gracias por el link. Si eventualmente tengo que reinstalar todo el
sistema quizá me sirva, pero en rigor todo lo que necesito es que el
sistema se conecte por cable de red como lo venía haciendo antes.



Es que tienes que deshacer todo lo que has hecho hasta este punto, hasta 
que tenías conexión de red.





Si hay alguna documentación técnica que leer donde se explique cómo
hacer esto a mano (por más que sea largo) agradecería que me la
indiquen.

Y gracias de nuevo por la ayuda, desde ya. Esto me está impidiendo
seguir trabajando y reinstalar todo el sistema sería la peor solución
(al menos en principio)...



Probaste desde consola configurar la placa de red con el nombre nuevo?:

ifconfig enp6s0 up
ifconfig enp6s0 192.168.1.10 netmask 255.255.255.0
route add default gateway 192.168.1.1

Obviamente cambiando las ips (y mascara de red) a las que correspondan
de tu maquina y del gateway.

Si eso te funciona, modifica el nombre en /etc/network/interfaces

Saludos,

Javier.



Se supone que tu tarjeta de red es "eth0", pero al usar un live de Arch 
éste lo nombra como "enp6s0"... ¿y que más dá? como si se llama pepito 
grillo!!!


Usa los datos que te proporciona el sistema que tienes instalado, el que 
no te funciona, el que quieres arreglar.


Si en un principio tenia conexión por red pero al intentar activar el 
wifi lo perdiste todo eso quiere decir:


a) Que la tarjeta de red funciona (o funcionaba)
b) Que has hecho algo mal (pero lo vas a arreglar, confío en tí)

Así que deja el pc en ese punto, en donde todo (o casi todo) funcionaba 
bien.


Y cuando lo tengas todo como antes le metes mano al wifi instalando el 
firmware como te pone en la wiki (porque se supone que ya tendrás 
internet), o sea, añadiendo el non-free al repositorio e instalando el 
paquete firmware-iwlwifi.


A ver si me das una alegría la próxima vez que escribas :-)

Saludos

Re: arm people distributing images with user 1000 already allocated, please stop that

[emetib]

gene i can understand your pain.  one of the reasons that i don't necessarily 
like sudo systems.

one of the first things that i do when i have a sudo system, ubuntu, lmde, 
raspbian, is to 'sudo su' and then 'passwd' to actually set a root password.

i have found that this has remedied the situation that you have described here. 
 with doing the above you wouldn't have to mount the sd somewhere else, you 
just make a new password for root.

i hope that this helps some for future reference.

take care
em

Re: Manually installed packages

[Brian]

On Thu 01 Dec 2016 at 18:38:45 +, Rodolfo Medina wrote:

> Curt  writes:
> 
> > I think in the OP's case having asked for the whole Gnome kit and
> > caboodle upon installation he's got lots of stuff he might not even be
> > aware of necessarily that doesn't fall into the auto category (or the
> > high priority required category either), but that he didn't expressly
> > install. I guess I'm just repeating what you already said though. I
> > suppose the confusion derives from the fact that the word manual
> > connotes "requiring human effort," and certain manual packages appear
> > on our systems effortlessly. 
> 
> 
> The present thread has collected many replies whose I thank all that kindly
> contributed.  But I unfortunately see no real solution to the general problem 
> I
> put to myself of which the uninstallation of Gnome is only an example.

But you never tried uninstalling GNOME as advised. Solving the general
proceeds from solvng the particular.

> Suppose that, during months and years, you have installed many packages in 
> your
> Debian system that you no more want and no more use, and that you want to free
> some space on disk because your machine is old with a small hard disk.  The
> problem is what packages you can be really sure and safe to remove.

You lay out the problem clearly. There is no silver bullet. You cannot
always be sure but you can imagine biting it. Trust the packaging system
and your own judgement.

-- 
Brian.

Paket Quisk-Error

[Peter Seifert]

root@raspberry:~# quisk


20:24:28: Warning: Mismatch between the program and library build versions 
detected.
The library used 3.0 (wchar_t,compiler with C++ ABI 1010,wx 
containers,compatible with 2.8),
and wxPython used 3.0 (wchar_t,compiler with C++ ABI 1009,wx 
containers,compatible with 2.8).
Unable to access the X Display, is $DISPLAY set properly?

(process:731): GLib-GObject-CRITICAL **: g_type_class_unref: assertion 'g_class 
!= NULL' failed


---
what is this?

greetings

peter

Berlin - Germany

Re: Cómo activar placa de red (notebook)

[Javier Marcon]

El 01/12/16 a las 17:31, Rivera Valdez escribió:
>> No hombre, no está bloqueado, solo es un cambio de "nombre".
> ¿Hay alguna manera de volver a poner el "nombre" anterior?
>
> Entiendo que el sistema instalado no encuentre la placa por tener el
> "nombre" cambiado, pero ¿por qué no la encuentran los sistemas que
> booteo en LiveUSB?
> ¿Puede ser que el firmware (non-free) de la placa wireless que instalé
> y luego desinstalé (firmware-iwlwifi) haya modificado el firmware de
> la placa de red?
> En ese caso, ¿dónde/cómo se edita eso?
>
>> Y he de suponer que ni en Trisquel ni en Parabola tendrías wifi porque son
>> proyectos de software libre y el firmware que vas a instalar (o has
>> instalado) no lo es.
> Correcto. Pero los derivados de Debian (Trisquel) no se conectan a la
> red cableada. Parabola/Arch en cambio usan la red cableada con este
> "nombre" nuevo (enp6s0). ¿Se le puede indicar al sistema que use ese
> otro "nombre" entonces?
>
>> El problema es no sabemos que has hecho para que no tengas conexión por
>> cable, o sea, como intestaste activar el wifi.
> Instalé el paquete firmware-iwlwifi con gdebi (los mismos pasos que
> reproduje en la salida de terminal que pegué antes), descargué y volví
> a cargar el módulo indicado (modprobe -r iwlwifi ; modprobe iwlwifi),
> y como la conexión wireless seguía sin aparecer, desinstalé iwlwifi
> con apt-get.
> Al reiniciar el sistema ya no se conectaba con la placa de red (que es
> esta, según lshw):
>
> Ethernet interface
> RTL8111/8168/8411 PCI Express Gigabit Ethernet Controler
> Realtek Semiconductor Co., Ltd.
>
>> Así que deshaz todo lo que hayas hecho hasta que tenías conexión por cable y
>> después sigue los pasos para instalar el firmware como te pone en la wiki
>> [1].
> Hecho. Pero deshechos todos los pasos, no vuelve a conectarse por
> cable (eth0) ni de ningún otro modo.
>
>> Si no te acuerdas reinstala el sistema. No te compliques.
> Preferiría evitar esto. El disco está encriptado y desde las distros
> en modo Live no consiguen abrir el contenido, de modo que hacer un
> backup está doblemente complicado (al margen de que reinstalar el
> sistema me significaría una enorme pérdida de tiempo adicional, desde
> ya).
>
>> Si lo ves muy complicado usa una imagen live con el firmware non-free
>> incluido [2].
> Gracias por el link. Si eventualmente tengo que reinstalar todo el
> sistema quizá me sirva, pero en rigor todo lo que necesito es que el
> sistema se conecte por cable de red como lo venía haciendo antes.
>
> Si hay alguna documentación técnica que leer donde se explique cómo
> hacer esto a mano (por más que sea largo) agradecería que me la
> indiquen.
>
> Y gracias de nuevo por la ayuda, desde ya. Esto me está impidiendo
> seguir trabajando y reinstalar todo el sistema sería la peor solución
> (al menos en principio)...
>
>
Probaste desde consola configurar la placa de red con el nombre nuevo?:

ifconfig enp6s0 up
ifconfig enp6s0 192.168.1.10 netmask 255.255.255.0
route add default gateway 192.168.1.1

Obviamente cambiando las ips (y mascara de red) a las que correspondan
de tu maquina y del gateway.

Si eso te funciona, modifica el nombre en /etc/network/interfaces

Saludos,

Javier.

-- 
Eco red Natural.
Veta de productos orgánicos y BPA.
Totalmente naturales.

Re: Is this really the way to get your name out?

[Nick Boyce]

On Wed, 30 Nov 2016 04:49:15 -0600
Doug  wrote:

> On 11/29/2016 03:23 PM, David Niklas wrote:
> > Every so often I see something very much like this on the debian
> > mailing list.
> > I want to know, do people really get a job this way?
> > Is this list really intended for these kinds of emails?
[...]
> > On Wed, 16 Nov 2016 15:37:37 + (UTC)
> > debian-user-digest-requ...@lists.debian.org wrote:  
[...]
> >> I am an entry level/junior/beginner Information Technology
(IT)
> >> Specialist/Systems Engineer/Linux Server Administrator/Helpdesk
> >> Support/Computer Technician available for hire anywhere in the
> >> world!!! Prospective employers, businesses and companies in any
> >> part of the world please feel free to contact me for my curriculum
> >> vitae/resume.
[...]
> There is always LinkedIn, but when you're looking for a job, all
> avenues are better than just a few. I wouldn't condemn him, altho I
> must say that I would not have thought of this path.

I'm afraid I would condemn him ... well 'condemn' is a bit harsh, but
I'd criticise him on behalf of myself and all the other overworked
sysadmins who get too much email as it is, especially from high-volume
lists such as debian-user (which is, after all, *not* a
recruitment/job-search mechanism).

I would say it's okay to include a .sig describing your employment
needs, but that's the limit of acceptability - max 3 lines.  Something
like "Experienced sysadmin/developer available for hire - 10 years
admin on all kinds of Un*x, and 5 years C++ programming.  Please email
me for more details".  And this .sig may *only* be attached to an email
on the list which discusses something relevant to the list charter -
otherwise it's spam.

Sorry.

Nick
-- 
Never FDISK after midnight

Re: Cómo activar placa de red (notebook)

[Rivera Valdez]

> No hombre, no está bloqueado, solo es un cambio de "nombre".

¿Hay alguna manera de volver a poner el "nombre" anterior?

Entiendo que el sistema instalado no encuentre la placa por tener el
"nombre" cambiado, pero ¿por qué no la encuentran los sistemas que
booteo en LiveUSB?
¿Puede ser que el firmware (non-free) de la placa wireless que instalé
y luego desinstalé (firmware-iwlwifi) haya modificado el firmware de
la placa de red?
En ese caso, ¿dónde/cómo se edita eso?

> Y he de suponer que ni en Trisquel ni en Parabola tendrías wifi porque son
> proyectos de software libre y el firmware que vas a instalar (o has
> instalado) no lo es.

Correcto. Pero los derivados de Debian (Trisquel) no se conectan a la
red cableada. Parabola/Arch en cambio usan la red cableada con este
"nombre" nuevo (enp6s0). ¿Se le puede indicar al sistema que use ese
otro "nombre" entonces?

> El problema es no sabemos que has hecho para que no tengas conexión por
> cable, o sea, como intestaste activar el wifi.

Instalé el paquete firmware-iwlwifi con gdebi (los mismos pasos que
reproduje en la salida de terminal que pegué antes), descargué y volví
a cargar el módulo indicado (modprobe -r iwlwifi ; modprobe iwlwifi),
y como la conexión wireless seguía sin aparecer, desinstalé iwlwifi
con apt-get.
Al reiniciar el sistema ya no se conectaba con la placa de red (que es
esta, según lshw):

Ethernet interface
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controler
Realtek Semiconductor Co., Ltd.

> Así que deshaz todo lo que hayas hecho hasta que tenías conexión por cable y
> después sigue los pasos para instalar el firmware como te pone en la wiki
> [1].

Hecho. Pero deshechos todos los pasos, no vuelve a conectarse por
cable (eth0) ni de ningún otro modo.

> Si no te acuerdas reinstala el sistema. No te compliques.

Preferiría evitar esto. El disco está encriptado y desde las distros
en modo Live no consiguen abrir el contenido, de modo que hacer un
backup está doblemente complicado (al margen de que reinstalar el
sistema me significaría una enorme pérdida de tiempo adicional, desde
ya).

> Si lo ves muy complicado usa una imagen live con el firmware non-free
> incluido [2].

Gracias por el link. Si eventualmente tengo que reinstalar todo el
sistema quizá me sirva, pero en rigor todo lo que necesito es que el
sistema se conecte por cable de red como lo venía haciendo antes.

Si hay alguna documentación técnica que leer donde se explique cómo
hacer esto a mano (por más que sea largo) agradecería que me la
indiquen.

Y gracias de nuevo por la ayuda, desde ya. Esto me está impidiendo
seguir trabajando y reinstalar todo el sistema sería la peor solución
(al menos en principio)...

Re: arm people distributing images with user 1000 already allocated, please stop that

[Joe]

On Thu, 1 Dec 2016 14:17:52 -0500
Gene Heskett  wrote:


> Only then could I load up the software I needed to do the job I
> bought 3 of these SBC's to do.  Not even the first user can "sudo apt
> install" anything that is not in the supplied repo list. So even he
> cannot actually put a raspberry pi 3b to work doing much but browsing
> the web or doing email.  

Don't forget that most of the midget computers are ARM-based, that the
ARM architecture bears no resemblance to that of the i386/amd64, and
that porting software isn't generally just a matter of setting a few
compiler switches. Many ARMs don't have a numeric coprocessor, the
original ARM2 being contemporary with the *real* i386, which needed an
i387.

The result is that ARM software lags behind that for the popular PC
architectures, and that there are many fewer packages in the ARM
repositories than for the traditional architectures.

-- 
Joe

Re: Manually installed packages

[Jörg-Volker Peetz]

Speaking of aptitude, it does remove automatically installed package if no other
package depends on it, or recommends it. This behavior can be changed by
configuration entries in /etc/apt/apt.conf, /etc/apt/apt.conf.d/*, etc.

To show any installed packages that aren't "auto" and which are dependencies or
recommendations of other packages, in short, packages that aren't marked "auto"
but could (should?) be, order

  aptitude search '~i!~M(~R~i|~Rrecommends:~i)'

Go through this list and, as root, mark the ones you don't need with

  aptitude markauto PACKAGE

When done,

  aptitude search '~g'

shows what can be purged from the system.

Regards,
jvp.

Re: Cómo activar placa de red (notebook)

[José María]

2016-11-29 18:45 GMT+00:00 José María :

El 29/11/16 a las 18:52, Rivera Valdez escribió:


Qué tal,

se trata de la placa Realtek (eth0) de una Dell XPS 15 L502X, que
funcionaba perfectamente hasta que traté de hacer andar la placa wifi
(Intel Centrino Wireless-N 1030) y no sólo no logré esto último sino
que ahora tampoco me reconoce el administrador de redes la conexión
cableada que antes funcionaba sin problemas.

Si boote (LiveUSB) Debian o Trisquel, el administrador (ícono de abajo
a la derecha) simplemente no encuentra ninguna conexión disponible
(por más que las placas aparecen correctamente en lshw), pero en
cambio, si booteo un Parabola (variante Libre de Arch), sí encuentra
la conexión cableada (y se conecta automáticamente) pero bajo otro
nombre.

Ahora no estoy en casa y no tengo los datos técnicos para pasarlos,
pero por si me pueden ir orientando sobre dónde leer o fijarme para
comenzar, lo voy mencionando.

Básicamente necesito, para empezar, que el sistema vuelva a encontrar
y activar normalmente la placa de red eth0 como lo hacía antes.
Cualquier lectura que me permita manejar esto, será ampliamente
bienvenida.

Gracias, !!



Tienes que instalarle el firmware. Sigue estos pasos:

https://wiki.debian.org/iwlwifi

Saludos



Gracias, José, ya lo había intentado. De hecho, el problema comenzó
ahí: No sólo no se activa la conexión wireless sino que dejó de
funcionar la conexión por cable de red normal (que antes funcionaba
perfecto).


Vale.



Lo extraño es que si booteo Debian Jessie (LiveUSB) no consigo
conectarme, en cambio, con Parabola (Arch derivative) configura la
conexión cableada (no como eth0, sino como enp6s0). Es como si eth0
hubiera quedado ¿bloqueado? ...



No hombre, no está bloqueado, solo es un cambio de "nombre".

Debian Stretch seguramente traerá ese cambio... ya nos acostumbraremos.

Y he de suponer que ni en Trisquel ni en Parabola tendrías wifi porque 
son proyectos de software libre y el firmware que vas a instalar (o has 
instalado) no lo es.





A continuación pego la secuencia de comandos con que instalé el
firmware (iwlwifi) en Debian, y el hardware y conexiones que me
muestra el sistema antes y después (en ningún momento wicd encuentra
ninguna de las redes disponibles, ni cableada ni wireless).

¿Hay alguna manera de activar la conexión cableada manualmente?
Agradezco cualquier ayuda, desde ya.



El problema es no sabemos que has hecho para que no tengas conexión por 
cable, o sea, como intestaste activar el wifi.


Como puedes observar al instalar el firmware-iwlwifi (el que te has 
descargado), ya te lo reconoce (wlan0)... te pone que está desactivado, 
pero te lo reconoce.


Así que deshaz todo lo que hayas hecho hasta que tenías conexión por 
cable y después sigue los pasos para instalar el firmware como te pone 
en la wiki [1].


Si no te acuerdas reinstala el sistema. No te compliques.

Si lo ves muy complicado usa una imagen live con el firmware non-free 
incluido [2].


Suerte.


[1] https://wiki.debian.org/iwlwifi

[2] 
http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/8.6.0-live+nonfree/amd64/iso-hybrid/





user@debian:~$ sudo su
root@debian:/home/user# ifconfig && iwconfig && lspci && lsmod

eth0  Link encap:Ethernet  HWaddr 14:fe:b5:b8:11:13
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:43 errors:0 dropped:0 overruns:0 frame:0
  TX packets:43 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:4133 (4.0 KiB)  TX bytes:4133 (4.0 KiB)

lono wireless extensions.

eth0  no wireless extensions.

00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor
Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core
Processor Family PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200
Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset
Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset
Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
Family PCI Express Root Port 1 (rev b5)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
Family PCI Express Root Port 2 (rev b5)
00:1c.3 PCI bridge: Intel 

Re: arm people distributing images with user 1000 already allocated, please stop that

[Gene Heskett]

On Thursday 01 December 2016 12:58:59 Alexandre GRIVEAUX wrote:

> Le 01/12/2016 à 18:45, Gene Heskett a écrit :
> > Greetings;
>
> Hello,
>
> > The arm folks, like unbuntu and raspian, are distribution for
> > installation usually on an micro-sd card, install images with the
> > first user pre-configured.  He is in the sudoers file, but the
> > ability to install other software to actually DO something is
> > restricted to a root pw only, and that is unknown/unpublished.
>
> You talk about HAL ?
No. from raspian, the first user is raspi, root is something else I've 
already forgotten.

The distribution I actually installed was the full jessie, which appears 
to be a fully rebuilt, made into an iso then compressed with pk7z and 
downloadable as the 7z file, updated frequently.  And this image has a 
first user=1000, named pi and already sudo configured, but only halfway. 
No gui based real package managers can be used by user pi because 
something in the /etc/pam tree insists on a root pw to run it.  And that 
pw is unknown so the only thing I could do was edit the passwd file by 
mounting the sd card on another machine and remove the root pw entirely.

Only then could I load up the software I needed to do the job I bought 3 
of these SBC's to do.  Not even the first user can "sudo apt install" 
anything that is not in the supplied repo list. So even he cannot 
actually put a raspberry pi 3b to work doing much but browsing the web 
or doing email.  I have a 1500 lb lathe, made in about 1950, which I 
have rebuilt where needed, and modified with more accurate ball screws 
to run, and as it turned out, there is not a fast way to forward the x 
stuff to another sbc. But once I got a good install, it turns out the 
raspi has more than enough power to do the job. I am getting screen 
updates at about 20 a second, quite adequate for this use.

> > I just spent 2 days (and I still have one more item to fix, probably
> > no biggie, but it won't let ME run raspi.config, has a hissy because
> > it can't even find pi's home directory)  with the sd card mounted
> > intermittently in a reader, removing the user pi from the
> > debian-jessie-full image, making it so that I was user 1000 and
> > COULD install what I needed onto an raspberry pi 3b. That SW was
> > linuxcnc, last nights bleeding edge version, supplied in a deb from
> > the buildbot.linuxcnc.org. I expected the raspi to have problems
> > with that SW because of its heavy, and time critical IRQ response
> > requirements. But not a single instance of an out of range delay was
> > recorded while it ran a virtual lathe to make half a dozen chess
> > pawns on that lathe.  So we have a new, in-expensive machine
> > controller lashup.
> >
> > This existing situation is very discouraging to potential new users
> > who expect to be able to do these things from his own account.  And
> > finds out quickly that there are many things that even user 1000
> > still cannot do on the raspi, or an odroid64-c2, an even more
> > powerfull SBC thats still stuck in kernel 3.14 days. And that
> > kernel, while running on it, has NO support for its 4 gpu's, nor
> > working support for spi, which would appear to be the future
> > interface to a machine controller of choice as it gives 72 gpio
> > lines, quite some number of which can become useful functions like a
> > PWM generator to control things that need an analog voltage control,
> > or a stepper motor pulse generator, even a quadrature encoder
> > receiver capable of tracking spindle position to a 1.5 degree
> > accuracy at 12,000 rpms in the encoder I've built.  All that in an
> > fpga card that sells for $53 and can be field re-programmed with one
> > of many supplied fpga bit files.
>
> If the maker of the board and/or SoC doesn't help the board can be
> forever on old kernel with unknown source.

Lets just say that while their forums are helpfull, they've also been 
drinking the koolaid and don't seem to want to understand questions 
about this. Replies always just change the subject.

> > Thats the bragging. But the pre-allocation of user 1000 in the
> > distributed image, instead of that being part of the normal first
> > login procedure is a PAIN IN THE A$$ to fix so that the first user
> > can actually install what he needs to get his job done while logging
> > in as himself, using his normal pw.
> >
> > Please exert what ever influence you may have to make the first user
> > a first login function again for the arm distributions that port
> > your
>
> Like you write it's distributed image he as nothing to do with the
> source, the distro maker choose to use that, you should talk to them.

I have tried thru their forums and have been either ignored, or the 
content of the replies wasn't at all about what I was asking for help 
with.  Hence my plea to you, the source of the code that is being built 
for the raspi's.

> > source.
> >
> > Thank you Debian for a great, stable (I'm still on wheezy with this
> > old, 

Re: Manually installed packages

[Greg Wooledge]

On Thu, Dec 01, 2016 at 06:38:45PM +, Rodolfo Medina wrote:
> Suppose that, during months and years, you have installed many packages in 
> your
> Debian system that you no more want and no more use, and that you want to free
> some space on disk because your machine is old with a small hard disk.  The
> problem is what packages you can be really sure and safe to remove.

At some point you actually have to *know* what a package does.  Go through
the list sorted by size and skip everything you know is useful.  When you
get to one that you think is not useful, or which you don't recognize
*at all*, dig into it and find out what it does.  Then consider removing
it, but be prepared to put it back if you break something.

This is how you learn.

P.S. http://wooledge.org/~greg/ds will sort the installed packages by
size for you.  As you can see, many of us have been there, done that.

P.P.S. do this learning on your desktop box, not a server.

Re: Manually installed packages

[Rodolfo Medina]

Curt  writes:

> I think in the OP's case having asked for the whole Gnome kit and
> caboodle upon installation he's got lots of stuff he might not even be
> aware of necessarily that doesn't fall into the auto category (or the
> high priority required category either), but that he didn't expressly
> install. I guess I'm just repeating what you already said though. I
> suppose the confusion derives from the fact that the word manual
> connotes "requiring human effort," and certain manual packages appear
> on our systems effortlessly. 


The present thread has collected many replies whose I thank all that kindly
contributed.  But I unfortunately see no real solution to the general problem I
put to myself of which the uninstallation of Gnome is only an example.

Suppose that, during months and years, you have installed many packages in your
Debian system that you no more want and no more use, and that you want to free
some space on disk because your machine is old with a small hard disk.  The
problem is what packages you can be really sure and safe to remove.

First, you need knowing what actually you have installed with your hands
because you don't remember them all.  This information is not provided by
apt-mark because its meaning of `manual' is not yours.  That information is
stored here and there, in pieces and chunks, within /var/log inside apt-get,
aptitude an dpkg log files that is not so simple to grep.  Besides, those files
seem to go back in the past not further 12 months or so.  So the best way is to
take note, in future, with pencil and paper, of what you installed during time;
and, for the present, erase the disk and reinstall everything.

Now, suppose you know - thanks to pencil and paper - what packages you've been
installed on your system since its creation.  And suppose that you decide to
remove, say, package1 bcause you don't need it any more.  You do: `aptitude
purge package1' or equivalent command but here comes another problem: only
package1 is removed but not all those packages that were installed at its time
along with package1.  Then you use for this purpose deborphans.  But this
morning I did a little experiment (see thread `deborphan') and it came out that
neither deborphan seems to actually remove those orphans packages.  The
solution seems so to be that pencil and paper should take note *also* of those
children or configuration files and not only of the main packages - in future.
In the present, erase and reinstall.

It seems to me not very enthusiastical all this.  To you?

Thanks,

Rodolfo

Re: Programa para diseño de DER y DFD

[Paynalton]

Lo que pasa es que pasó el idioma a ukraniano y no sabe como escribir
la pregunta porque no sirve ninguna de las vocales.


-- 

 __
< Brilla por su ausencia.  >
 --
\   ^__^
 \  (oo)\___
(__)\   )\/\
||w |
|| ||

On jue, 2016-12-01 at 15:17 -0300, walter wrote:
> algo anda mail en un iPhone?.. o es algo codificado?
> 
> que los mortales no entendemos
> 
> 
> Elvira Ramirez:
> > Dsskkmmssdklñlkkslfkdffsdsd
> > 
> > Enviado desde mi iPhone
> > 
> 

Re: Programa para diseño de DER y DFD

[walter]

algo anda mail en un iPhone?.. o es algo codificado?

que los mortales no entendemos


Elvira Ramirez:
> Dsskkmmssdklñlkkslfkdffsdsd
>
> Enviado desde mi iPhone
>

Re: arm people distributing images with user 1000 already allocated, please stop that

[Alexandre GRIVEAUX]

Le 01/12/2016 à 18:45, Gene Heskett a écrit :
> Greetings;
Hello,
>
> The arm folks, like unbuntu and raspian, are distribution for 
> installation usually on an micro-sd card, install images with the first 
> user pre-configured.  He is in the sudoers file, but the ability to 
> install other software to actually DO something is restricted to a root 
> pw only, and that is unknown/unpublished.
You talk about HAL ?
>
> I just spent 2 days (and I still have one more item to fix, probably no 
> biggie, but it won't let ME run raspi.config, has a hissy because it 
> can't even find pi's home directory)  with the sd card mounted 
> intermittently in a reader, removing the user pi from the 
> debian-jessie-full image, making it so that I was user 1000 and COULD 
> install what I needed onto an raspberry pi 3b. That SW was linuxcnc, 
> last nights bleeding edge version, supplied in a deb from the 
> buildbot.linuxcnc.org. I expected the raspi to have problems with that 
> SW because of its heavy, and time critical IRQ response requirements. 
> But not a single instance of an out of range delay was recorded while it 
> ran a virtual lathe to make half a dozen chess pawns on that lathe.  So 
> we have a new, in-expensive machine controller lashup.
>
> This existing situation is very discouraging to potential new users who 
> expect to be able to do these things from his own account.  And finds 
> out quickly that there are many things that even user 1000 still cannot 
> do on the raspi, or an odroid64-c2, an even more powerfull SBC thats 
> still stuck in kernel 3.14 days. And that kernel, while running on it, 
> has NO support for its 4 gpu's, nor working support for spi, which would 
> appear to be the future interface to a machine controller of choice as 
> it gives 72 gpio lines, quite some number of which can become useful 
> functions like a PWM generator to control things that need an analog 
> voltage control, or a stepper motor pulse generator, even a quadrature 
> encoder receiver capable of tracking spindle position to a 1.5 degree 
> accuracy at 12,000 rpms in the encoder I've built.  All that in an fpga 
> card that sells for $53 and can be field re-programmed with one of many 
> supplied fpga bit files.
If the maker of the board and/or SoC doesn't help the board can be
forever on old kernel with unknown source.
>
> Thats the bragging. But the pre-allocation of user 1000 in the 
> distributed image, instead of that being part of the normal first login 
> procedure is a PAIN IN THE A$$ to fix so that the first user can 
> actually install what he needs to get his job done while logging in as 
> himself, using his normal pw.
>
> Please exert what ever influence you may have to make the first user a 
> first login function again for the arm distributions that port your 
Like you write it's distributed image he as nothing to do with the
source, the distro maker choose to use that, you should talk to them.
> source.
>
> Thank you Debian for a great, stable (I'm still on wheezy with this old, 
> slow, Phenom powered machine) os.  Its a place of familiarity that Just 
> Works(TM) if one doesn't want to be a lab rat.
>
> Cheers, Gene Heskett
Thanks.

arm people distributing images with user 1000 already allocated, please stop that

[Gene Heskett]

Greetings;

The arm folks, like unbuntu and raspian, are distribution for 
installation usually on an micro-sd card, install images with the first 
user pre-configured.  He is in the sudoers file, but the ability to 
install other software to actually DO something is restricted to a root 
pw only, and that is unknown/unpublished.

I just spent 2 days (and I still have one more item to fix, probably no 
biggie, but it won't let ME run raspi.config, has a hissy because it 
can't even find pi's home directory)  with the sd card mounted 
intermittently in a reader, removing the user pi from the 
debian-jessie-full image, making it so that I was user 1000 and COULD 
install what I needed onto an raspberry pi 3b. That SW was linuxcnc, 
last nights bleeding edge version, supplied in a deb from the 
buildbot.linuxcnc.org. I expected the raspi to have problems with that 
SW because of its heavy, and time critical IRQ response requirements. 
But not a single instance of an out of range delay was recorded while it 
ran a virtual lathe to make half a dozen chess pawns on that lathe.  So 
we have a new, in-expensive machine controller lashup.

This existing situation is very discouraging to potential new users who 
expect to be able to do these things from his own account.  And finds 
out quickly that there are many things that even user 1000 still cannot 
do on the raspi, or an odroid64-c2, an even more powerfull SBC thats 
still stuck in kernel 3.14 days. And that kernel, while running on it, 
has NO support for its 4 gpu's, nor working support for spi, which would 
appear to be the future interface to a machine controller of choice as 
it gives 72 gpio lines, quite some number of which can become useful 
functions like a PWM generator to control things that need an analog 
voltage control, or a stepper motor pulse generator, even a quadrature 
encoder receiver capable of tracking spindle position to a 1.5 degree 
accuracy at 12,000 rpms in the encoder I've built.  All that in an fpga 
card that sells for $53 and can be field re-programmed with one of many 
supplied fpga bit files.

Thats the bragging. But the pre-allocation of user 1000 in the 
distributed image, instead of that being part of the normal first login 
procedure is a PAIN IN THE A$$ to fix so that the first user can 
actually install what he needs to get his job done while logging in as 
himself, using his normal pw.

Please exert what ever influence you may have to make the first user a 
first login function again for the arm distributions that port your 
source.

Thank you Debian for a great, stable (I'm still on wheezy with this old, 
slow, Phenom powered machine) os.  Its a place of familiarity that Just 
Works(TM) if one doesn't want to be a lab rat.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Desktop freeze

[Gianluca Guidi]

Hello,
I would like to report a bug I experienced in sid but I have no idea 
about what package could be involved.


I use Xfce, including its window manager, and Compton to add some effects.

Every few seconds everything on the screen freezes except for the mouse 
pointer, which can still be moved. Clicking and typing actually works,

however the effects of these actions are not displayed.
The screen can be unfrozen by switching to a login console then
switching back to X.

Any idea on where to look at to find out why this happens?
--
Gianluca

postfix-cluebringer problem

[Gokan Atmaca]

Hello

I'm getting a table error. I got the database files from the site.
Can you help with this ?

Error:

postfix-cluebringer[32765]: [2016/12/01-20:04:28 - 306] [CORE] ERROR:
Database query failed: cbp::dblayer::DBSelect(107): Error executing
select: Table 'policyd.access_control' doesn't exist

Thanks.

Re: Manually installed packages

[Curt]

On 2016-12-01, David Wright  wrote:
> On Wed 30 Nov 2016 at 08:47:21 (-0500), Stefan Monnier wrote:
>> > apt-mark showmanual   gives you the complement of   apt-mark showauto.
>> > The second paragraph of apt-mark's description explains what's meant
>> > by "auto". So "manual" doesn't mean what you appear to assume it does,
>> > that you were involved in manually selecting it for installation. It
>> > just means "not auto".
>> 
>> To me "auto" means "not manually",
>
> Yes, auto and manual are anotnyms.
>
>> so I'm just as confused as Rodolfo
>> and I think for good reasons.
>
> I don't know whether Rodolfo is still confused after the explanation
> I gave. AFAICT once you realise that manual means "not marked as auto"
> rather than "I installed this by typing apt* ", then it's
> fairly obvious that "manual" is a bucket term that includes, for
> example, packages installed by the debian-installer because they're
> essential, with Priority: required.

I think in the OP's case having asked for the whole Gnome kit and
caboodle upon installation he's got lots of stuff he might not even be
aware of necessarily that doesn't fall into the auto category (or the
high priority required category either), but that he didn't expressly
install. I guess I'm just repeating what you already said though. I
suppose the confusion derives from the fact that the word manual
connotes "requiring human effort," and certain manual packages appear
on our systems effortlessly. 

> I can't remember installing bash or grep, but they're certainly not
> auto, so they're going to be "unmarked auto", or "marked non-auto",
> or "marked manual". I think I'll stick to the last. What would
> you prefer?

>> There might be technical reasons behind
>> the way it currently works, but I think this qualifies as a bug (maybe
>> a UI bug, maybe a coding bug, maybe a doc bug).
>
> *What* qualifies as a bug...that you're confused?
>
> Cheers,
> David.
>
>


-- 
“It is enough that the arrows fit exactly in the wounds that they have made.”
Franz Kafka

Re: Cómo activar placa de red (notebook)

[Rivera Valdez]

2016-11-29 18:45 GMT+00:00 José María :
> El 29/11/16 a las 18:52, Rivera Valdez escribió:
>
>> Qué tal,
>>
>> se trata de la placa Realtek (eth0) de una Dell XPS 15 L502X, que
>> funcionaba perfectamente hasta que traté de hacer andar la placa wifi
>> (Intel Centrino Wireless-N 1030) y no sólo no logré esto último sino
>> que ahora tampoco me reconoce el administrador de redes la conexión
>> cableada que antes funcionaba sin problemas.
>>
>> Si boote (LiveUSB) Debian o Trisquel, el administrador (ícono de abajo
>> a la derecha) simplemente no encuentra ninguna conexión disponible
>> (por más que las placas aparecen correctamente en lshw), pero en
>> cambio, si booteo un Parabola (variante Libre de Arch), sí encuentra
>> la conexión cableada (y se conecta automáticamente) pero bajo otro
>> nombre.
>>
>> Ahora no estoy en casa y no tengo los datos técnicos para pasarlos,
>> pero por si me pueden ir orientando sobre dónde leer o fijarme para
>> comenzar, lo voy mencionando.
>>
>> Básicamente necesito, para empezar, que el sistema vuelva a encontrar
>> y activar normalmente la placa de red eth0 como lo hacía antes.
>> Cualquier lectura que me permita manejar esto, será ampliamente
>> bienvenida.
>>
>> Gracias, !!
>>
>
> Tienes que instalarle el firmware. Sigue estos pasos:
>
> https://wiki.debian.org/iwlwifi
>
> Saludos
>

Gracias, José, ya lo había intentado. De hecho, el problema comenzó
ahí: No sólo no se activa la conexión wireless sino que dejó de
funcionar la conexión por cable de red normal (que antes funcionaba
perfecto).

Lo extraño es que si booteo Debian Jessie (LiveUSB) no consigo
conectarme, en cambio, con Parabola (Arch derivative) configura la
conexión cableada (no como eth0, sino como enp6s0). Es como si eth0
hubiera quedado ¿bloqueado? ...

A continuación pego la secuencia de comandos con que instalé el
firmware (iwlwifi) en Debian, y el hardware y conexiones que me
muestra el sistema antes y después (en ningún momento wicd encuentra
ninguna de las redes disponibles, ni cableada ni wireless).

¿Hay alguna manera de activar la conexión cableada manualmente?
Agradezco cualquier ayuda, desde ya.

user@debian:~$ sudo su
root@debian:/home/user# ifconfig && iwconfig && lspci && lsmod

eth0  Link encap:Ethernet  HWaddr 14:fe:b5:b8:11:13
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:43 errors:0 dropped:0 overruns:0 frame:0
  TX packets:43 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:4133 (4.0 KiB)  TX bytes:4133 (4.0 KiB)

lono wireless extensions.

eth0  no wireless extensions.

00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor
Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core
Processor Family PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200
Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset
Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset
Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
Family PCI Express Root Port 1 (rev b5)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
Family PCI Express Root Port 2 (rev b5)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
Family PCI Express Root Port 4 (rev b5)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
Family PCI Express Root Port 5 (rev b5)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
Family PCI Express Root Port 6 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset
Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation HM67 Express Chipset Family LPC
Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series
Chipset Family 6 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family
SMBus Controller (rev 05)
01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce
GT 525M] (rev a1)
03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1030
[Rainbow Peak] (rev 34)
04:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host
Controller (rev 04)
06:00.0 Ethernet controller: 

Re: C.

[German Velazquez]

solo falta el area code

El 1 de diciembre de 2016, 9:54, Amid Ale  escribió:

> será una emergencia y quieren que la llame por teléfono??
>
> El 1 de diciembre de 2016, 12:43, fernando sainz <
> fernandojose.sa...@gmail.com> escribió:
>
>> Ahora ya tenemos todos tu teléfono :-) , pero tienes algún problema con
>> Debian
>>
>>
>> 2016-12-01 14:46 GMT+01:00 Alicia Gutiérrez :
>> >
>> >
>> > Alicia Gutiérrrez
>> > 651 889 691
>> >
>>
>>
>

Re: Manually installed packages

[David Wright]

On Wed 30 Nov 2016 at 08:47:21 (-0500), Stefan Monnier wrote:
> > apt-mark showmanual   gives you the complement of   apt-mark showauto.
> > The second paragraph of apt-mark's description explains what's meant
> > by "auto". So "manual" doesn't mean what you appear to assume it does,
> > that you were involved in manually selecting it for installation. It
> > just means "not auto".
> 
> To me "auto" means "not manually",

Yes, auto and manual are anotnyms.

> so I'm just as confused as Rodolfo
> and I think for good reasons.

I don't know whether Rodolfo is still confused after the explanation
I gave. AFAICT once you realise that manual means "not marked as auto"
rather than "I installed this by typing apt* ", then it's
fairly obvious that "manual" is a bucket term that includes, for
example, packages installed by the debian-installer because they're
essential, with Priority: required.

I can't remember installing bash or grep, but they're certainly not
auto, so they're going to be "unmarked auto", or "marked non-auto",
or "marked manual". I think I'll stick to the last. What would
you prefer?

> There might be technical reasons behind
> the way it currently works, but I think this qualifies as a bug (maybe
> a UI bug, maybe a coding bug, maybe a doc bug).

*What* qualifies as a bug...that you're confused?

Cheers,
David.

Re: C.

[Amid Ale]

será una emergencia y quieren que la llame por teléfono??

El 1 de diciembre de 2016, 12:43, fernando sainz <
fernandojose.sa...@gmail.com> escribió:

> Ahora ya tenemos todos tu teléfono :-) , pero tienes algún problema con
> Debian
>
>
> 2016-12-01 14:46 GMT+01:00 Alicia Gutiérrez :
> >
> >
> > Alicia Gutiérrrez
> > 651 889 691
> >
>
>

Re: C.

[fernando sainz]

Ahora ya tenemos todos tu teléfono :-) , pero tienes algún problema con Debian


2016-12-01 14:46 GMT+01:00 Alicia Gutiérrez :
>
>
> Alicia Gutiérrrez
> 651 889 691
>

C.

[Alicia Gutiérrez]

Alicia Gutiérrrez 
651 889 691

[HS] : Offre d'emploi

[Grégoire COUTANT]

Bonjour à tous,
C'est un semi HS car nous administrons tous nos serveurs sous Debian, 
alors si vous connaissez qqun qui cherche un job d'admin sys varié dans 
une équipe très sympa avec beaucoup d'autonomie, n'hésitez pas :


http://emploi.alsacreations.com/offre-571081-Administrateur-systeme-reseau---serveur.html

Grégoire

Re: deborphan

[Hans]

> By default it does remove automatically installed packages (but not their
> configurations), see the manual page and [1]. So it's quite possible that
> it did just that on your system.
> 
> Next time you do an experiment like that, make sure to set up a suitable
> control group[2] :-)
> 
> [1] http://aptitude.alioth.debian.org/doc/en/ch02s02s06.html
> [2] e.g. by doing a dpkg --get-selections > before and another
> 
> > after and diffing the sorted results, or similar.
> 
> Regards
> -- t

Configurations can be purges with 

aptitude purge ~c

Hans

Re: deborphan

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Dec 01, 2016 at 12:06:03PM +, Rodolfo Medina wrote:
> Peter Ludikovsky  writes:
> 
> > What was the output from aptitude purge? The reason I'm asking is that
> > aptitude usually auto-removes packages where the one removed was the
> > only one with dependencies.
> >
> > Regards.
> > /peter
> 
> aptitude said it was just removing , not those packages that were
> installed along with .

By default it does remove automatically installed packages (but not their
configurations), see the manual page and [1]. So it's quite possible that
it did just that on your system.

Next time you do an experiment like that, make sure to set up a suitable
control group[2] :-)

[1] http://aptitude.alioth.debian.org/doc/en/ch02s02s06.html
[2] e.g. by doing a dpkg --get-selections > before and another
> after and diffing the sorted results, or similar.

Regards
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlhAFaMACgkQBcgs9XrR2kaDQgCfaOptjSHslFhKFTxYe9FpL5da
o9UAn1QY2dXL1c1oGm9SUOmL9IqdHdH3
=TWpu
-END PGP SIGNATURE-

Re: deborphan

[Rodolfo Medina]

Peter Ludikovsky  writes:

> What was the output from aptitude purge? The reason I'm asking is that
> aptitude usually auto-removes packages where the one removed was the
> only one with dependencies.
>
> Regards.
> /peter

aptitude said it was just removing , not those packages that were
installed along with .

Rodolfo

>
> On 12/01/2016 12:26 PM, Rodolfo Medina wrote:
>> I did a little experiment with deborphan: first I did: `aptitude install
>> ', and along with it a certain number of other packages were
>> installed.  Then I did: `aptitude purge ' followed by `deborphan'
>> but in the output of `deborphan' none of those packages that were installed
>> along with  was present.  Is that normal?
>> 
>> Thanks for any help,
>> 
>> Rodolfo
>> 

Re: deborphan

[Peter Ludikovsky]

What was the output from aptitude purge? The reason I'm asking is that
aptitude usually auto-removes packages where the one removed was the
only one with dependencies.

Regards.
/peter

On 12/01/2016 12:26 PM, Rodolfo Medina wrote:
> I did a little experiment with deborphan: first I did: `aptitude install
> ', and along with it a certain number of other packages were
> installed.  Then I did: `aptitude purge ' followed by `deborphan' but
> in the output of `deborphan' none of those packages that were installed along
> with  was present.  Is that normal?
> 
> Thanks for any help,
> 
> Rodolfo
> 



signature.asc
Description: OpenPGP digital signature

Re: deborphan

[Hans]

Am Donnerstag, 1. Dezember 2016, 11:49:20 CET schrieb Rodolfo Medina:
> Nicolas George  writes:
> > Le primidi 11 frimaire, an CCXXV, Rodolfo Medina a écrit :

> Same result: none of them.
> 
> Rodolfo

Try 

aptitude purge `deborphan --guess-all`

But look, what is going to be deinstalled. In rare cases it might uninstall a 
needed lib. If so, just reinstall that again. But as I said: it will appear in 
very rare cases. On my system I only needed to reinstall a lib only one time 
in the last 12 months.

Good luck!

Hans

Re: deborphan

[Rodolfo Medina]

Nicolas George  writes:

> Le primidi 11 frimaire, an CCXXV, Rodolfo Medina a écrit :
>> I did a little experiment with deborphan: first I did: `aptitude install
>> ', and along with it a certain number of other packages were
>> installed.  Then I did: `aptitude purge ' followed by `deborphan'
>> but in the output of `deborphan' none of those packages that were installed
>> along with  was present.  Is that normal?
>
> By default, deborphan shows only packages that it finds unlikely to be
> installed for themselves: libraries, transitional packages, etc. Use
> option -a to get them all.

Same result: none of them.

Rodolfo

Re: deborphan

[Nicolas George]

Le primidi 11 frimaire, an CCXXV, Rodolfo Medina a écrit :
> I did a little experiment with deborphan: first I did: `aptitude install
> ', and along with it a certain number of other packages were
> installed.  Then I did: `aptitude purge ' followed by `deborphan' but
> in the output of `deborphan' none of those packages that were installed along
> with  was present.  Is that normal?

By default, deborphan shows only packages that it finds unlikely to be
installed for themselves: libraries, transitional packages, etc. Use
option -a to get them all.


signature.asc
Description: Digital signature

deborphan

[Rodolfo Medina]

I did a little experiment with deborphan: first I did: `aptitude install
', and along with it a certain number of other packages were
installed.  Then I did: `aptitude purge ' followed by `deborphan' but
in the output of `deborphan' none of those packages that were installed along
with  was present.  Is that normal?

Thanks for any help,

Rodolfo