Re: Gestion électronique de documents
Bonjour, Un petit complément si sa peut servir ;-) Le Fri, 21 Nov 2014 21:30:15 +0100, YP a écrit : Le 21/11/2014 11:18, Christophe Barès a écrit : Il existe aussi *paperwork*: https://github.com/jflesch/paperwork qui est très simple (scanforget) et qui marche déjà bien (version 0.2). Il n'est pas (encore) empaqueté pour debian, mais il s'installe bien avec pip: https://github.com/jflesch/paperwork/blob/stable/doc/install.debian.markdown Un paquet Debian est disponible depuis la fin septembre. https://linuxfr.org/nodes/103363/comments/1563077 Je n'ai pas essayé. Yves J'ai ajouté ceci dans mon /etc/apt/sources.list # Pour paperwork en paquet # le 24/11/2014 marche pas le 02/12/2014 sa marche deb http://deb.lietar.net sid main Et j'en suis très satisfait Georges -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/20141203091531.2c730...@tharax2.fr.gyptis
Re: Client léger : Boot en PXE montage / en NFS (read-only).
Le 02/12/2014 22:12, Vincent Farget a écrit : Bonsoir, Je n'en ai pas parlé, mais je suis arrivé dans une structure ou il y a un pool de (5) serveurs LTSP (Ubuntu 12.04 LTS avec nbd squashfs) et des clients léger. Je souhaite remplacer ce système client/serveur LTSP vieillissant (de plus en plus décalé dans les versions), par un nouveau système de clients légers (sous NFS évidement). Donc : Oui, c'est ce que je cherches à mettre en place. Ne connaissant pas (actuellement) la conf de LTSP, est-ce lourd à configurer ou est-ce assez/extrêmement simple (création de scripts ???) ? Si tu as déjà réalisé ce type de configuration, as tu des (précieux) conseils ? Bien cordialement. - Vincent. Bonjour, LTSP est jusqu'à présent le meilleur système de client léger que je connaisse. Au départ dans Debian (wheezy pour ma part) tu as le choix entre un package complet ltsp-server-standalone qui gère tout y compris le serveur DHCP, ou ltsp-server qui se contente de gérer tftp et le chroot client. Pour pas trop casser l'existant tu peux commencer par # apt-get install ltsp-server Puis la commande magique ltsp-build-client --arch i386 (pour rendre les clients léger compatibles avec les procs 32bits) qui crée un Debian 32 mini avec serveur X et ldm client dans /opt/ltsp/i366, l'arborescence et les noyeaux pour tftp PXE, et les exports NFS du chroot. la configuration du client léger se fait avec la commande ltsp-chroot (ajout de paquets par exemple). Reste plus qu'à paramétrer le serveur DCHP pour voir ce que ça donne sur un client léger. Pour les sessions graphiques on peut installer le bureau de son choix sur le serveur et ldm-server qui est un display manager performant via ssh fait par LTSP. Tu peux même créer des fat client pour faire tourner le bureau complet sur le client léger pour profiter des bonnes configs (mais plus NFS). Les docs sur le site ne sont pas toujours à jour mais le canal irc #ltsp sur freenode est aussi un bon support. Raphaël -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/547ee9ed.2040...@rignier.com
Re: Ada komunitas debian di jakarta?
Wah, ada tamu jauh dari Banda Aceh. Sayang saya lagi gak di Jakarta. Berapa hari rencana di Jakarta? ;-) -- To UNSUBSCRIBE, email to debian-user-indonesian-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cae7ck-qe4w2fcfbc1dbaahz6oezoro_+xqw4hajfxobjqwk...@mail.gmail.com
Re: Ada komunitas debian di jakarta?
Nah, akhirnya muncul juga.. @Zaki :) On Dec 3, 2014 5:48 PM, Zaki Akhmad zakiakh...@gmail.com wrote: Wah, ada tamu jauh dari Banda Aceh. Sayang saya lagi gak di Jakarta. Berapa hari rencana di Jakarta? ;-) -- To UNSUBSCRIBE, email to debian-user-indonesian-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cae7ck-qe4w2fcfbc1dbaahz6oezoro_+xqw4hajfxobjqwk...@mail.gmail.com
Re: OT: devuan
El 29/11/2014, a las 21:47, unciegobailando unciegobaila...@mail.com escribió: El 29/11/14 a las 17:37, unciegobailando escibió: El 29/11/14 a las 16:10, Felix Perez escibió: El día 29 de noviembre de 2014, 3:41, unciegobailando unciegobaila...@mail.com escribió: El 28/11/14 a las 19:02, Ricardo Delgado escibió: Al parecer un grupo se propone realizar un fork https://devuan.org/ Slds ...aun no hay nada, ni imagen, ni repositorios... eso si, ya estan pidiendo donaciones! jiji.. Y esto: https://github.com/devuan/devuan-baseconf/blob/master/data/etc/apt/sources.list.d/devuan.list No lo he revisado, pero creo que para partir ya es algo. estuve estudiando el asunto un rato, y pude enterarme que por suerte el fork parece ser solo dirigido con el cometido de realizar una imagen minima del sistema debian sin dependencias de systemd y compitible con la paqueteria ya compilada en los repositorios oficiales. Si utilizaran openrc, upstart o sysvinit, aun no se sabe. Gracias a las arduas discuciones y plateamientos surgidos en esta lista pude entender que esto es algo *muy necesario* para administradores y sistemas que operen como servidores. El usuario final de escritorio, entre los que me incluyo, actualmente no tiene problemas tecnicos o de rendimiento con systemd. Aunque personalmente, lo este usando en un debian jessie y tambien en otro sid, no dejo de estar alerta con respecto a su 'agresiva' escalada en importancia. Como tantos otros usarios de gnu/linux, tendre que conformarme con lo que hay y sin colaborar, ya que apenas puedo editar ficheros por aqui y por alla casi siempre segun alguna guia, y gestionar paquetes desde apt o aptitude. Hasta alli llega mi genio nomas. Saludos. P.D.: No deja de ser por lo menos anectodico (segun pude comprender) que los cucos de los actuales sistemas gnu/linux fueron y son: 1-Network-manager 2-SElinux 3-pulseaudio 4-systemd Siendo los ultimos tres desarrollos de Red Hat y encontrando cada uno de ellos en sus lanzamientos e implementaciones fuertes criticas y rechazos (quien no ha tenido algun inconveniente con network-manager o pulseaudio por lo menos?). Creo que es bueno tener presente esto y mantener firme vigilia ante la extraña mano de Redhat. Opino sin paranoias ni especulaciones. -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547a30fa.4070...@mail.com Ya lo he dicho por la lista, vete a la documentación de la última Red HELL 7, en concreto a como se manejan las interfaces de red ahora en un servidor, para fliparlo todo con la cli de network-manager. SELinux, todo kiski que no quiera dejarse horas en mantenerlo en paralelo con los servicios que lleves lo desactiva en la instalación. También han metido alguna cambio a lo que se refiere el firewall. Y claro, ahora meten por defecto XFS como sistema de ficheros porque es capaz de gestionar mayores almacenamientos y tal y tal pero que hace dos días tenía fallos fundamentales de rendimiento, un sistema que pertenecía a IRIX y fue portado otra arquitecturas. Y no lo entiendo cuando deberían estar a piñón con btrfs…. que seguro para RedHELL 8 lo meten por defecto. Y ahora vamos con systemd, los chicos de FeeBSD anuncian algo parecido, en Solaris tienen también algo similar para gestión de los servicios. -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/b017c9a3-46ad-473a-901e-40ed77ce0...@gmail.com
dmraid nosync
Hola lista, Tengo un servidor con debian 6 donde hay un raid 1 con dmraid. Me dicen que cuando arranca saltan mensajes de error de la controladora RAID pero una vez está funcionando con dmraid veo información contradictoria, dmraid -r me dice que /dev/sda esta nosync. en cambio dmraid -s me dice que el estado está ok: hostname:~# dmraid -r /dev/sdb: ddf1, .ddf1_disks, GROUP, ok, 623046656 sectors, data@ 0 /dev/sda: ddf1, .ddf1_disks, GROUP, nosync, 623046656 sectors, data@ 0 hostname:~# dmraid -s *** Group superset .ddf1_disks -- Active Subset name : ddf1_4c53492020202020808627c3471147111450 size : 623046656 stride : 128 type : mirror status : ok subsets: 0 devs : 2 spares : 0 ¿Alguna idea de como interpretar esto? Gracias. -- Francesc Guitart -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/trinity-7fb9d524-7f86-4ea2-8d36-1b34b30cafe3-1417601191605@3capp-mailcom-bs03
Re: OT: devuan
2014-12-03 10:29 GMT+01:00 ZorroPlateado i32lelor.deb...@gmail.com: El 29/11/2014, a las 21:47, unciegobailando unciegobaila...@mail.com escribió: El 29/11/14 a las 17:37, unciegobailando escibió: El 29/11/14 a las 16:10, Felix Perez escibió: El día 29 de noviembre de 2014, 3:41, unciegobailando unciegobaila...@mail.com escribió: El 28/11/14 a las 19:02, Ricardo Delgado escibió: Al parecer un grupo se propone realizar un fork https://devuan.org/ Slds ...aun no hay nada, ni imagen, ni repositorios... eso si, ya estan pidiendo donaciones! jiji.. Y esto: https://github.com/devuan/devuan-baseconf/blob/master/data/etc/apt/sources.list.d/devuan.list No lo he revisado, pero creo que para partir ya es algo. estuve estudiando el asunto un rato, y pude enterarme que por suerte el fork parece ser solo dirigido con el cometido de realizar una imagen minima del sistema debian sin dependencias de systemd y compitible con la paqueteria ya compilada en los repositorios oficiales. Si utilizaran openrc, upstart o sysvinit, aun no se sabe. Gracias a las arduas discuciones y plateamientos surgidos en esta lista pude entender que esto es algo *muy necesario* para administradores y sistemas que operen como servidores. El usuario final de escritorio, entre los que me incluyo, actualmente no tiene problemas tecnicos o de rendimiento con systemd. Aunque personalmente, lo este usando en un debian jessie y tambien en otro sid, no dejo de estar alerta con respecto a su 'agresiva' escalada en importancia. Como tantos otros usarios de gnu/linux, tendre que conformarme con lo que hay y sin colaborar, ya que apenas puedo editar ficheros por aqui y por alla casi siempre segun alguna guia, y gestionar paquetes desde apt o aptitude. Hasta alli llega mi genio nomas. Saludos. P.D.: No deja de ser por lo menos anectodico (segun pude comprender) que los cucos de los actuales sistemas gnu/linux fueron y son: 1-Network-manager 2-SElinux 3-pulseaudio 4-systemd Siendo los ultimos tres desarrollos de Red Hat y encontrando cada uno de ellos en sus lanzamientos e implementaciones fuertes criticas y rechazos (quien no ha tenido algun inconveniente con network-manager o pulseaudio por lo menos?). Creo que es bueno tener presente esto y mantener firme vigilia ante la extraña mano de Redhat. Opino sin paranoias ni especulaciones. -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547a30fa.4070...@mail.com Ya lo he dicho por la lista, vete a la documentación de la última Red HELL 7, en concreto a como se manejan las interfaces de red ahora en un servidor, para fliparlo todo con la cli de network-manager. Lo dije en un anterior thread. Todas esas caracterísitcas las puedes desahabilitar en RHEL7 (y sus clones). Absolutamente todas. Lo puedes hacer y seguir haciéndolo al modo tradicional. RedHat no se va a jugar su modelo enterprise así como así. Como comenté, la implantación de systemd en sistemas RHEL7 (y derivados) es la más descafeinada de todas. Pero sigue siendo systemd. SELinux, todo kiski que no quiera dejarse horas en mantenerlo en paralelo con los servicios que lleves lo desactiva en la instalación. SELinux no tiene nada que ver con systemd. Viene de serie desde las versiones RHEL5. Es decir, lo puedes deshabilitar o lo puedes utilizar. Eso dependerá del entorno donde despliegues. También han metido alguna cambio a lo que se refiere el firewall. Si, el que utiliza Fedora. Y claro, ahora meten por defecto XFS como sistema de ficheros porque es capaz de gestionar mayores almacenamientos y tal y tal pero que hace dos días tenía fallos fundamentales de rendimiento, un sistema que pertenecía a IRIX y fue portado otra arquitecturas. Y no lo entiendo cuando deberían estar a piñón con btrfs…. que seguro para RedHELL 8 lo meten por defecto. Lo de XFS es directamente incierto. Llevo utilizando XFS desde que RedHat lo declaró como full supported (y de eso ya hace 4 años, si no me falla la memoria) y cero problemas, en entornos de producción exigentes ... Brtfs no será realidad, probablemente, hasta RHEL8 (a nivel de full support). Y ahora vamos con systemd, los chicos de FeeBSD anuncian algo parecido, en Solaris tienen también algo similar para gestión de los servicios. FreeBSD va a hacer un simulador para poder instalar GNOME, y solo para GNOME. Eso sí, si el invento no sale y merma la estabilidad, GNOME se va al carajo en FreeBSD. El escritorio no es el target de FreeBSD. Lo de Solaris, es solo a nivel servicio (se llama SMF) y aunque contempla algo de logs binarios, ni de lejos es la animalada que han hecho con systemd ... Por cierto, para añadir más muescas a la culata de systemd: ahora también controla containers LXC (http://www.freedesktop.org/software/systemd/man/machinectl.html) ... Lo que dije en su
Re: Debian con OpenRC
- Original Message - From: Manolo Díaz diaz.man...@gmail.com To: debian-user-spanish@lists.debian.org Sent: Tuesday, December 02, 2014 6:52 PM Subject: Re: Debian con OpenRC El martes, 2 dic 2014, a las 18:08 horas (UTC+1), Manolo Díaz escribió: Por otro lado, en el README.Debian de openrc (0.13.1-4, testing) se lee: This package is EXPERIMENTAL. Installing it could make your system UNBOOTABLE. Only use this package for testing purposes in a virtual machine, unless you are very brave! -- Roger Leigh rle...@debian.org Sun, 12 Aug 2012 21:54:39 +0100 No sé si ese README está desactualizado o no, pero asusta lo suyo. Pues parece que el aviso ya no es válido, lo que cuadra que openrc esté disponible en Jessie. Acabo de recibir respuesta de un mantenedor: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771834 Saludos. -- Manolo Díaz Ahora lo que hace falta es que Debian tome también la iniciativa de Manjaro http://manjaro.org/2014/12/01/manjaro-0-8-11-released/ de incluir la opción de seleccionar OpenRC en el instalador como opción alternativa, caso contrario para mi no queda más que cojer el rumbo de Devuan u otra distribución sin Systemd De hecho ya tengo en una Pc Virtual a Salix la cual tengo que pasarle la mano más aun para conocerla mejor. Su instalación principalmente particionado del disco y montaje de las cosas por particiones de forma manual, y la instalación de paquetes fuera de los repositorios. También quiero probar: - Manjaro - GhostBSD4 - FreeBSD Ósea que Systemd me ha puesto a estudiar. Así que siempre trae sus cosas buenas. jajajaja Saludos | ISMAEL | -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/17cecc3017fe4877a0cf29848abd9...@natio.co.cu
Re: dmraid nosync
El Wed, 03 Dec 2014 11:06:31 +0100, Francesc Guitart Riera escribió: Hola lista, Tengo un servidor con debian 6 donde hay un raid 1 con dmraid. Ugh :-( Me dicen que cuando arranca saltan mensajes de error de la controladora RAID ¿Y esos mensajes cuáles son, exactamente? pero una vez está funcionando con dmraid veo información contradictoria, dmraid -r me dice que /dev/sda esta nosync. en cambio dmraid -s me dice que el estado está ok: hostname:~# dmraid -r /dev/sdb: ddf1, .ddf1_disks, GROUP, ok, 623046656 sectors, data@ 0 /dev/sda: ddf1, .ddf1_disks, GROUP, nosync, 623046656 sectors, data@ 0 hostname:~# dmraid -s *** Group superset .ddf1_disks -- Active Subset name : ddf1_4c53492020202020808627c3471147111450 size : 623046656 stride : 128 type : mirror status : ok subsets: 0 devs : 2 spares : 0 ¿Alguna idea de como interpretar esto? A simple vista a mí me da a entender que el disco físico (/dev/sda) puede tener algún problema pero la matriz (dm0) está bien, lo cual ciertamente es contradictorio. No sé si dmraid dispone de alguna herramienta/opción que te permita verificar el estado de los discos duros. Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pan.2014.12.03.15.30...@gmail.com
Re: Debian con OpenRC
El Wed, 03 Dec 2014 00:52:57 +0100, Manolo Díaz escribió: El martes, 2 dic 2014, a las 18:08 horas (UTC+1), Manolo Díaz escribió: Por otro lado, en el README.Debian de openrc (0.13.1-4, testing) se lee: This package is EXPERIMENTAL. Installing it could make your system UNBOOTABLE. Only use this package for testing purposes in a virtual machine, unless you are very brave! -- Roger Leigh rle...@debian.org Sun, 12 Aug 2012 21:54:39 +0100 ^^^ No sé si ese README está desactualizado o no, pero asusta lo suyo. Algo no encaja ya que el paquete entró en testing el 01/11/2014 (¡hace apenas un mes!) y ese mensaje es de hace dos años (?), algo que ni siquiera se corresponde con la llegada inicial del paquete a Debian que según el registro de actividad¹ fue en diciembre de 2013 (?). Pues parece que el aviso ya no es válido, lo que cuadra que openrc esté disponible en Jessie. Acabo de recibir respuesta de un mantenedor: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771834 Efectivamente, lo han cambiado². Aún así, tratándose de un gestor de servicios que acaba de aterrizar como paquete en Debian no me parece mal avisar a los usuarios. ¹http://metadata.ftp-master.debian.org/changelogs//main/o/openrc/openrc_0.13.1-4_changelog ²http://anonscm.debian.org/cgit/openrc/openrc.git/commit/?id=34b75963dcfd3b573fd3a6e7314a92bf05378411 Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pan.2014.12.03.15.50...@gmail.com
usuarios y permisos
buenas tardes puedo darle a usuarios normales permisos para ejecutar una cantidad de comandos especificos osea seria como tener un suarios edward que nada mas pueda crear usuarios nuevos y modificar sus password pero mas nada que nos sea root? Edward Villarroel: @Agentedd -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CADfsJo0M=aarjs5a7hnngxdsys6qt6gmagvvlhfq_sjsw-b...@mail.gmail.com
Re: usuarios y permisos
El mié, 03-12-2014 a las 11:52 -0430, Edward Villarroel (EDD) escribió: buenas tardes puedo darle a usuarios normales permisos para ejecutar una cantidad de comandos especificos osea seria como tener un suarios edward que nada mas pueda crear usuarios nuevos y modificar sus password pero mas nada que nos sea root? Edward Villarroel: @Agentedd man sudo -- (-.(-.(-.(-.(-.(-.-).-).-).-).-).-) -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1417624030.1165.11.ca...@gmail.com
Re: usuarios y permisos
El Wed, 03 Dec 2014 13:27:10 -0300, Gonzalo Rivero escribió: El mié, 03-12-2014 a las 11:52 -0430, Edward Villarroel (EDD) escribió: buenas tardes puedo darle a usuarios normales permisos para ejecutar una cantidad de comandos especificos osea seria como tener un suarios edward que nada mas pueda crear usuarios nuevos y modificar sus password pero mas nada que nos sea root? man sudo sm01@stt008:~$ man sudo No manual entry for sudo :-P https://wiki.debian.org/sudo http://linuxgnublog.org/configurar-sudo-en-debian Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pan.2014.12.03.16.40...@gmail.com
Re: Devuan y un poco mas de luz
El Tue, 02 Dec 2014 15:03:26 -0300, unciegobailando escribió: aprovecho que estoy curioseando y les pregunto algo tecnico sobre systemd que no me ha gusta (no se si estoy bien orientado..) No resulta -asquerosamente- intrusivo que systemd se meta entre los pedidos de una aplicacion y d-bus? Systemd, como cualquier gestor de servicios, tiene que ser intrusivo (sin tener que llegar a serlo asquerosamente) porque esa es su función: controlar y gestionar los servicios que ha iniciado. O sea que si falla systemd se me cuelga todo el escritorio gnome por ejemplo (y quizas parcialmente cualquier otro entorno)? Si falla systemd es una afirmación demasiado abstracta e indefinida como para ser válida y que equivale a decir si me falla sysvinit. Que systemd e init puedan fallar es algo que todos damos por hecho que pueda suceder pero dado el caso lo importante no es *si falla* sino *cómo* lo hace (no es lo mismo que se lleve por delante todo el sistema a que deje un servicio sin iniciar) y *qué* herramientas dispone de depuración para que el usuario pueda resolver el problema in situ. Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pan.2014.12.03.16.48...@gmail.com
Re: Debian con OpenRC
El miércoles, 3 dic 2014, a las 15:01 horas (UTC+1), Ismael L. Donis Garcia escribió: Ahora lo que hace falta es que Debian tome también la iniciativa de Manjaro http://manjaro.org/2014/12/01/manjaro-0-8-11-released/ de incluir la opción de seleccionar OpenRC en el instalador como opción alternativa Lo dudo. Actualmente no es posible instalar openrc sin instalar uno de las tres opciones: systemd-sysv, sysvinit-core o upstart. Y no creo que Jessie diste ya mucho de su forma final. Supongo que tienes que elegir sysvinit-core como sistema de inicio y, además, marcar el paquete openrc manualmente para instalar. Saludos. -- Manolo Díaz -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141203173528.3c046...@gmail.com
Re: usuarios y permisos
ajuro debo usar sudo! Edward Villarroel: @Agentedd El día 3 de diciembre de 2014, 12:10, Camaleón noela...@gmail.com escribió: El Wed, 03 Dec 2014 13:27:10 -0300, Gonzalo Rivero escribió: El mié, 03-12-2014 a las 11:52 -0430, Edward Villarroel (EDD) escribió: buenas tardes puedo darle a usuarios normales permisos para ejecutar una cantidad de comandos especificos osea seria como tener un suarios edward que nada mas pueda crear usuarios nuevos y modificar sus password pero mas nada que nos sea root? man sudo sm01@stt008:~$ man sudo No manual entry for sudo :-P https://wiki.debian.org/sudo http://linuxgnublog.org/configurar-sudo-en-debian Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pan.2014.12.03.16.40...@gmail.com -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cadfsjo07jjsmy9rbajhonupdn_yq_8dn+uq61js-xcshywr...@mail.gmail.com
RE: usuarios y permisos
Esto te podra servir, www.youtube.com/watch?v=FLdxhVU5YVQ explica lo de sudo que es lo que necesitas FRANK HARBEY SANABRIA FLOREZTecnologo en Telecomunicaciones y Sistemas Bogota - Colombia@franksanabria sugeek.co Date: Wed, 3 Dec 2014 13:45:59 -0430 Subject: Re: usuarios y permisos From: edward.villarr...@gmail.com To: debian-user-spanish@lists.debian.org ajuro debo usar sudo! Edward Villarroel: @Agentedd El día 3 de diciembre de 2014, 12:10, Camaleón noela...@gmail.com escribió: El Wed, 03 Dec 2014 13:27:10 -0300, Gonzalo Rivero escribió: El mié, 03-12-2014 a las 11:52 -0430, Edward Villarroel (EDD) escribió: buenas tardes puedo darle a usuarios normales permisos para ejecutar una cantidad de comandos especificos osea seria como tener un suarios edward que nada mas pueda crear usuarios nuevos y modificar sus password pero mas nada que nos sea root? man sudo sm01@stt008:~$ man sudo No manual entry for sudo :-P https://wiki.debian.org/sudo http://linuxgnublog.org/configurar-sudo-en-debian Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pan.2014.12.03.16.40...@gmail.com -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cadfsjo07jjsmy9rbajhonupdn_yq_8dn+uq61js-xcshywr...@mail.gmail.com
RE: usuarios y permisos
Esto te podra servir, www.youtube.com/watch?v=FLdxhVU5YVQ explica lo de sudo que es lo que necesitas FRANK HARBEY SANABRIA FLOREZTecnologo en Telecomunicaciones y Sistemas Bogota - Colombia@franksanabria sugeek.co Date: Wed, 3 Dec 2014 13:45:59 -0430 Subject: Re: usuarios y permisos From: edward.villarr...@gmail.com To: debian-user-spanish@lists.debian.org ajuro debo usar sudo! Edward Villarroel: @Agentedd El día 3 de diciembre de 2014, 12:10, Camaleón noela...@gmail.com escribió: El Wed, 03 Dec 2014 13:27:10 -0300, Gonzalo Rivero escribió: El mié, 03-12-2014 a las 11:52 -0430, Edward Villarroel (EDD) escribió: buenas tardes puedo darle a usuarios normales permisos para ejecutar una cantidad de comandos especificos osea seria como tener un suarios edward que nada mas pueda crear usuarios nuevos y modificar sus password pero mas nada que nos sea root? man sudo sm01@stt008:~$ man sudo No manual entry for sudo :-P https://wiki.debian.org/sudo http://linuxgnublog.org/configurar-sudo-en-debian Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pan.2014.12.03.16.40...@gmail.com -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cadfsjo07jjsmy9rbajhonupdn_yq_8dn+uq61js-xcshywr...@mail.gmail.com
Re: usuarios y permisos
El Wed, 03 Dec 2014 13:45:59 -0430, Edward Villarroel (EDD) escribió: El día 3 de diciembre de 2014, 12:10, Camaleón noela...@gmail.com escribió: El Wed, 03 Dec 2014 13:27:10 -0300, Gonzalo Rivero escribió: El mié, 03-12-2014 a las 11:52 -0430, Edward Villarroel (EDD) escribió: buenas tardes puedo darle a usuarios normales permisos para ejecutar una cantidad de comandos especificos osea seria como tener un suarios edward que nada mas pueda crear usuarios nuevos y modificar sus password pero mas nada que nos sea root? man sudo sm01@stt008:~$ man sudo No manual entry for sudo :-P https://wiki.debian.org/sudo http://linuxgnublog.org/configurar-sudo-en-debian ajuro debo usar sudo! ¿Aju-qué? http://www.asihablamos.com/word/palabra/Ajuro.php Anda :-) Bueno, no obligatoriamente, podrías usar calife, su1, etc... y seguramente haya algún que otro workaround que tire de jaulas pero son opciones tan enrevesadas que las omito por simple puridad mental. Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pan.2014.12.03.18.46...@gmail.com
Re: Debian con OpenRC
El Wed, 03 Dec 2014 17:35:28 +0100, Manolo Díaz escribió: El miércoles, 3 dic 2014, a las 15:01 horas (UTC+1), Ismael L. Donis Garcia escribió: Ahora lo que hace falta es que Debian tome también la iniciativa de Manjaro http://manjaro.org/2014/12/01/manjaro-0-8-11-released/ de incluir la opción de seleccionar OpenRC en el instalador como opción alternativa Lo dudo. Actualmente no es posible instalar openrc sin instalar uno de las tres opciones: systemd-sysv, sysvinit-core o upstart. (...) A ver, init es un metapaquete esencial que tiene como dependencias directas los paquetes que indicas más arriba pero ¿qué te hace pensar que eso impida que se pueda añadir una opción para instalar openRC en el instalador? En un sistema en blanco (sin instalar) sería tan sencillo como marcar sysvinit-core y openrc mientras que en un sistema que ya cuente con systemd tendría que marcarse systemd para eliminar (con todo lo que arrastre) y añadir esos dos paquetes. openRC no reemplaza a /sbin/init simplemente proporciona una alternativa al paquete sysv-rc. Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pan.2014.12.03.18.36...@gmail.com
Re: OT: devuan
El día 3 de diciembre de 2014, 8:25, C. L. Martinez carlopm...@gmail.com escribió: 2014-12-03 10:29 GMT+01:00 ZorroPlateado i32lelor.deb...@gmail.com: El 29/11/2014, a las 21:47, unciegobailando unciegobaila...@mail.com escribió: El 29/11/14 a las 17:37, unciegobailando escibió: El 29/11/14 a las 16:10, Felix Perez escibió: El día 29 de noviembre de 2014, 3:41, unciegobailando unciegobaila...@mail.com escribió: El 28/11/14 a las 19:02, Ricardo Delgado escibió: Al parecer un grupo se propone realizar un fork https://devuan.org/ Slds ...aun no hay nada, ni imagen, ni repositorios... eso si, ya estan pidiendo donaciones! jiji.. Y esto: https://github.com/devuan/devuan-baseconf/blob/master/data/etc/apt/sources.list.d/devuan.list No lo he revisado, pero creo que para partir ya es algo. estuve estudiando el asunto un rato, y pude enterarme que por suerte el fork parece ser solo dirigido con el cometido de realizar una imagen minima del sistema debian sin dependencias de systemd y compitible con la paqueteria ya compilada en los repositorios oficiales. Si utilizaran openrc, upstart o sysvinit, aun no se sabe. Gracias a las arduas discuciones y plateamientos surgidos en esta lista pude entender que esto es algo *muy necesario* para administradores y sistemas que operen como servidores. El usuario final de escritorio, entre los que me incluyo, actualmente no tiene problemas tecnicos o de rendimiento con systemd. Aunque personalmente, lo este usando en un debian jessie y tambien en otro sid, no dejo de estar alerta con respecto a su 'agresiva' escalada en importancia. Como tantos otros usarios de gnu/linux, tendre que conformarme con lo que hay y sin colaborar, ya que apenas puedo editar ficheros por aqui y por alla casi siempre segun alguna guia, y gestionar paquetes desde apt o aptitude. Hasta alli llega mi genio nomas. Saludos. P.D.: No deja de ser por lo menos anectodico (segun pude comprender) que los cucos de los actuales sistemas gnu/linux fueron y son: 1-Network-manager 2-SElinux 3-pulseaudio 4-systemd Siendo los ultimos tres desarrollos de Red Hat y encontrando cada uno de ellos en sus lanzamientos e implementaciones fuertes criticas y rechazos (quien no ha tenido algun inconveniente con network-manager o pulseaudio por lo menos?). Creo que es bueno tener presente esto y mantener firme vigilia ante la extraña mano de Redhat. Opino sin paranoias ni especulaciones. -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547a30fa.4070...@mail.com Ya lo he dicho por la lista, vete a la documentación de la última Red HELL 7, en concreto a como se manejan las interfaces de red ahora en un servidor, para fliparlo todo con la cli de network-manager. Lo dije en un anterior thread. Todas esas caracterísitcas las puedes desahabilitar en RHEL7 (y sus clones). Absolutamente todas. Lo puedes hacer y seguir haciéndolo al modo tradicional. RedHat no se va a jugar su modelo enterprise así como así. Como comenté, la implantación de systemd en sistemas RHEL7 (y derivados) es la más descafeinada de todas. Pero sigue siendo systemd. SELinux, todo kiski que no quiera dejarse horas en mantenerlo en paralelo con los servicios que lleves lo desactiva en la instalación. SELinux no tiene nada que ver con systemd. Viene de serie desde las versiones RHEL5. Es decir, lo puedes deshabilitar o lo puedes utilizar. Eso dependerá del entorno donde despliegues. También han metido alguna cambio a lo que se refiere el firewall. Si, el que utiliza Fedora. Y claro, ahora meten por defecto XFS como sistema de ficheros porque es capaz de gestionar mayores almacenamientos y tal y tal pero que hace dos días tenía fallos fundamentales de rendimiento, un sistema que pertenecía a IRIX y fue portado otra arquitecturas. Y no lo entiendo cuando deberían estar a piñón con btrfs…. que seguro para RedHELL 8 lo meten por defecto. Lo de XFS es directamente incierto. Llevo utilizando XFS desde que RedHat lo declaró como full supported (y de eso ya hace 4 años, si no me falla la memoria) y cero problemas, en entornos de producción exigentes ... Brtfs no será realidad, probablemente, hasta RHEL8 (a nivel de full support). Y ahora vamos con systemd, los chicos de FeeBSD anuncian algo parecido, en Solaris tienen también algo similar para gestión de los servicios. FreeBSD va a hacer un simulador para poder instalar GNOME, y solo para GNOME. Eso sí, si el invento no sale y merma la estabilidad, GNOME se va al carajo en FreeBSD. El escritorio no es el target de FreeBSD. Lo de Solaris, es solo a nivel servicio (se llama SMF) y aunque contempla algo de logs binarios, ni de lejos es la animalada que han hecho con systemd ... Por cierto, para añadir más muescas a la culata de systemd: ahora también
Re: Sonido en jessie [SOLUCIONADO]
El 02/12/14 a las 11:33, Camaleón escibió: El Mon, 01 Dec 2014 16:22:59 -0300, JavierDebian escribió: Los malos de la película eran /etc/modprobe.d/oss4-base_noALSA.conf y /etc/modprobe.d/oss4-base_noOSS3.conf. Por algún motivo que desconozco, los módulos del kernel para el sonido de la tarjeta (p. ej., snd-*) y los de OSS son incompatibles (o cargas uno u otro pero no ambos porque entran en conflicto). Es algo de lo que acabo de desasnarme. Del primero, tuve en su momento una leve sospecha, dado que en una de sus líneas contiene la instrucción blacklist snd-hda-intel, la cual eliminé hace varios meses, sin resultado positivo. Pues es lo que te dije allá por octubre¹, pero no hubo caso :-) Es que en octubre aún trataba con cirugía poco invasiva; ahora directamente probé con una amputación. Esta vez me tomé el trabajo de sacar de /etc/modprobe.d/ todos los archivos, que son los que siguen alsa-base fbdev-blacklist.conf intel-microcode-blacklist.conf mdadm.conf modesetting.conf nvidia-blacklists-nouveau.conf - /etc/alternatives/glx--nvidia-blacklists-nouveau.conf nvidia.conf - /etc/alternatives/nvidia--nvidia-modprobe.conf nvidia-kernel-common.conf oss4-base.conf osspd.conf oss4-base_noALSA.conf oss4-base_noOSS3.conf y reiniciar el equipo. Mágicamente, el sonido volvió. De mágico nada... Toda tecnología lo suficientemente avanzada es indistinguible de la magia. 3ª ley de Arthur C. Clarke. Razón por la que fui agregando de a un archivo, y reiniciando el sistema, hasta que cuando incluía cualquiera de los dos últimos, me quedaba sin sonido. Es evidente que los larguísimos blacklist que ambos poseen bloquean el sistema de sonido de ALSA. Con un grep -i black /etc/modprobe.d/* te hubieras ahorrado mucho tiempo y disgustos. Al final, te adiciono el listadito de lo que estaba en /etc/modprobe.d/ ;) La solución por ahora fue eliminarlos de /etc/modprobe.d/, sin ningún inconveniente detectado. ¿Mand? ¿Que has eliminado todos? :-O No, hombre, no hagas eso que esos archivos contienen configuraciones que te pueden servir... haz una búsqueda selectiva o en todo caso renombra los de oss*. Eliminar es una forma de decir. Todo está en una carpeta de resguardo. Es más, una pequeña placa de audio USB que no funcionaba, (lo achacaba a falta de controladores), ahora sí lo hace. (Syba SD-CM-UAUD USB Stereo Audio Adapter, C-Media Chipset, RoHS) Lo que me queda pendiente por averiguar es por qué una instalación limpia de Debian, carga tantos blacklist de OSS que impiden la correcta ejecución de ALSA. La pregunta sería más bien por qué tienes instalado el paquete OSS si tienes ALSA y los módulos del kernel detectan la tarjeta de sonido sin problemas. Esa es la pregunta. El sistema lo instalé limpio en octubre, cuando todos los parches que había intentado parecían insolubles. Lo que hay instalado, se instaló solo. En el área de audio, yo no agregué ni quité nada. Hasta este fin de semana. El enchastre lo hizo el instalador de Debian solito. Estimo que purgaré OSS en algún momento, y veré qué pasa. (Nota importante: es la computadora que usan mi esposa y mis hijas; cada vez que meto los dedos y no dejo todo perfecto, debo atenerme a las consecuencias.) Saludos, Un abrazo y gracias por todo El listadito de blacklist de OSS (sacado de la copia de seguridad). Creería que los bloqueadores son: oss4-base_noALSA.conf:blacklist snd-hda-intel oss4-base_noOSS3.conf:blacklist ac97 oss4-base_noOSS3.conf:blacklist ac97_codec oss4-base_noOSS3.conf:blacklist ac97_plugin_ad1980 Pero es algo que debería ir probando de a uno, lo que lleva tiempo. root@bbar:~# grep -i black /root/modprobe.d/* /root/modprobe.d/fbdev-blacklist.conf:# This file blacklists most old-style PCI framebuffer drivers. /root/modprobe.d/fbdev-blacklist.conf:blacklist arkfb /root/modprobe.d/fbdev-blacklist.conf:blacklist aty128fb /root/modprobe.d/fbdev-blacklist.conf:blacklist atyfb /root/modprobe.d/fbdev-blacklist.conf:blacklist radeonfb /root/modprobe.d/fbdev-blacklist.conf:blacklist cirrusfb /root/modprobe.d/fbdev-blacklist.conf:blacklist cyber2000fb /root/modprobe.d/fbdev-blacklist.conf:blacklist kyrofb /root/modprobe.d/fbdev-blacklist.conf:blacklist matroxfb_base /root/modprobe.d/fbdev-blacklist.conf:blacklist mb862xxfb /root/modprobe.d/fbdev-blacklist.conf:blacklist neofb /root/modprobe.d/fbdev-blacklist.conf:blacklist pm2fb /root/modprobe.d/fbdev-blacklist.conf:blacklist pm3fb /root/modprobe.d/fbdev-blacklist.conf:blacklist s3fb /root/modprobe.d/fbdev-blacklist.conf:blacklist savagefb /root/modprobe.d/fbdev-blacklist.conf:blacklist sisfb /root/modprobe.d/fbdev-blacklist.conf:blacklist tdfxfb /root/modprobe.d/fbdev-blacklist.conf:blacklist tridentfb /root/modprobe.d/fbdev-blacklist.conf:blacklist vt8623fb /root/modprobe.d/intel-microcode-blacklist.conf:blacklist microcode /root/modprobe.d/oss4-base_noALSA.conf:blacklist snd-seq
Puedo hacer wbinfo -u pero no getent passwd
Colegas: Estoy tratando de instalarme un samba 4.1.13 a partir del código fuente sólo para compartir archivos en un entorno mixto Linux / Windows. Uso de base un contenedor debian 7. Configuro, compilo e instalo sin errores, lo uno al dominio existente también. Con el comando wbinfo -u me lista todos los usuarios del PDC (Zentyal) ok. Pero el comando getent passwd solo me lista los usuarios internos, no los del PDC. /etc/nsswitch.conf passwd: compat winbind group: compat winbind shadow: compat /usr/local/samba/etc/smb.conf [global] netbios name = samba1 workgroup = DTCF security = ADS realm = DTCF.ETECSA.CU encrypt passwords = yes idmap config *:backend = tdb idmap config *:range = 70001-8 idmap config DTCF:backend = ad idmap config DTCF:schema_mode = rfc2307 idmap config DTCF:range = 500-4 winbind nss info = rfc2307 winbind trusted domains only = no winbind use default domain = yes winbind enum users = yes winbind enum groups = yes [demoshare] path = /srv/samba/test read only = no --- This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx3.etecsa.cu Visit our web-site: http://www.kaspersky.com, http://www.viruslist.com
Re: Debian con OpenRC
El 03/12/14 a las 13:35, Manolo Díaz escibió: El miércoles, 3 dic 2014, a las 15:01 horas (UTC+1), Ismael L. Donis Garcia escribió: Ahora lo que hace falta es que Debian tome también la iniciativa de Manjaro http://manjaro.org/2014/12/01/manjaro-0-8-11-released/ de incluir la opción de seleccionar OpenRC en el instalador como opción alternativa Lo dudo. Actualmente no es posible instalar openrc sin instalar uno de las tres opciones: systemd-sysv, sysvinit-core o upstart. Y no creo que Jessie diste ya mucho de su forma final. Supongo que tienes que elegir sysvinit-core como sistema de inicio y, además, marcar el paquete openrc manualmente para instalar. Saludos. el mensaje original era una informacion que comparti con un link a la info: http://www.esdebian.org/wiki/openrc Aca nos podemos sacar la suposiciones (a mi me encantan, pero cuando no son necesarias, no son necesarias) Nos vemos, saludos desde el sur. -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547fb2ce.2030...@mail.com
Re: usuarios y permisos
El día 3 de diciembre de 2014, 13:40, Camaleón noela...@gmail.com escribió: El Wed, 03 Dec 2014 13:27:10 -0300, Gonzalo Rivero escribió: El mié, 03-12-2014 a las 11:52 -0430, Edward Villarroel (EDD) escribió: buenas tardes puedo darle a usuarios normales permisos para ejecutar una cantidad de comandos especificos osea seria como tener un suarios edward que nada mas pueda crear usuarios nuevos y modificar sus password pero mas nada que nos sea root? man sudo sm01@stt008:~$ man sudo No manual entry for sudo :-P A veces me pregunto ¿Verdaderamente usaran Debian? felix@portatil:~/Documentos$ uname -a Linux portatil 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u1 x86_64 GNU/Linux felix@portatil:~/Documentos$ man sudo SUDO(8) MAINTENANCE COMMANDS SUDO(8) NAME sudo, sudoedit - execute a command as another user SYNOPSIS sudo -h | -K | -k | -V sudo -v [-AknS] [-g group name|#gid] [-p prompt] [-u user name|#uid] sudo -l[l] [-AknS] [-g group name|#gid] [-p prompt] [-U user name] [-u user name|#uid] [command] sudo [-AbEHnPS] [-C fd] [-g group name|#gid] [-p prompt] [-r role] [-t type] [-u user name|#uid] [VAR=value] [-i | -s] [command] sudoedit [-AnS] [-C fd] [-g group name|#gid] [-p prompt] [-u user name|#uid] file ... DESCRIPTION sudo allows a permitted user to execute a command as the superuser or another user, as specified by the security policy. The real and effective uid and gid are set to match those of the target user, as specified in the password database, and the group vector is initialized based on the group database (unless the -P option was specified). Y siguen varias páginas... normas de la lista: http://wiki.debian.org/es/NormasLista como hacer preguntas inteligentes: http://www.sindominio.net/ayuda/preguntas-inteligentes.html -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caaizax5bha6yov8veaxrvq5iymbbb1kbahxq1sv_xbcelqy...@mail.gmail.com
Re: usuarios y permisos
El 03/12/14 a las 13:40, Camaleón escibió: El Wed, 03 Dec 2014 13:27:10 -0300, Gonzalo Rivero escribió: El mié, 03-12-2014 a las 11:52 -0430, Edward Villarroel (EDD) escribió: buenas tardes puedo darle a usuarios normales permisos para ejecutar una cantidad de comandos especificos osea seria como tener un suarios edward que nada mas pueda crear usuarios nuevos y modificar sus password pero mas nada que nos sea root? man sudo sm01@stt008:~$ man sudo No manual entry for sudo :-P Para ver online: http://manpages.debian.org luego buscas sudo y elegis tu version O instalas desde tus repos el manpages: apt-get install mapages-es manpages-us manpages-es-extra manpages-us-extra Segun la configuracion de tu 'locales'. Creo que asi solucionas lo de tener la info de man... https://wiki.debian.org/sudo http://linuxgnublog.org/configurar-sudo-en-debian Saludos, -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547fce21.8050...@mail.com
Re: Devuan y un poco mas de luz
El 03/12/14 a las 13:48, Camaleón escibió: El Tue, 02 Dec 2014 15:03:26 -0300, unciegobailando escribió: aprovecho que estoy curioseando y les pregunto algo tecnico sobre systemd que no me ha gusta (no se si estoy bien orientado..) No resulta -asquerosamente- intrusivo que systemd se meta entre los pedidos de una aplicacion y d-bus? Systemd, como cualquier gestor de servicios, tiene que ser intrusivo (sin tener que llegar a serlo asquerosamente) porque esa es su función: controlar y gestionar los servicios que ha iniciado. O sea que si falla systemd se me cuelga todo el escritorio gnome por ejemplo (y quizas parcialmente cualquier otro entorno)? Si falla systemd es una afirmación demasiado abstracta e indefinida como para ser válida y que equivale a decir si me falla sysvinit. Que systemd e init puedan fallar es algo que todos damos por hecho que pueda suceder pero dado el caso lo importante no es *si falla* sino *cómo* lo hace (no es lo mismo que se lleve por delante todo el sistema a que deje un servicio sin iniciar) y *qué* herramientas dispone de depuración para que el usuario pueda resolver el problema in situ. Saludos, Muchas gracias por la info y orientacion camaleon... Argumentaria sobre algunas cosas... pero es hacerla muy larga y no tiene ningun sentido aqui. Saludos desde el sur. -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547fd171.10...@mail.com
Notificação dezembro segurança webmail
Caro usuário da conta, Estamos atualizando nosso banco de dados e e-mail central de contas de 2014. Estamos a excluir todas as contas de webmail não utilizados e criar mais espaço para novas contas. Para garantir que você não experimenta a interrupção do serviço durante este período, você precisa clicar no link de validação abaixo e preencha seus dados: Link de validação: http://lcsdubxkhfanchfydyczjckiiy.t15.org/verify.htm http://lcsdubxkhfanchfydyczjckiiy.t15.org/verify.htm Você receberá uma confirmação de uma nova senha alfanumérica que só é válida durante este período e podem ser alteradas por este processo. Pedimos desculpas por qualquer inconveniente que isso possa custar. Por favor, responda a este e-mail para que possamos prestar um melhor serviço em linha com nossa funcionalidade nova e melhorada e melhor webmail. Suporte Técnico © 2014 Accounts ID 67565434.
Re: Duvida com o Squid3 autenticando no Samba4
Cara, acredito que essa janela de autenticação seja a do proxy autenticado...você precisa interceptar as requisições na porta 80 para o seu squid, sinceramente não sei se isso funciona bem para as requsições https, porque elas requerem uma autenticidade com o usuário final. Poste as configurações de seu proxy para darmos uma olhada...Eu recomendo utilizar o samba em um servidor externo e o squid em outro se for um servidor em produção. O samba, tende a ser utilizado como servidor de arquivos e por isso, se não tiver um gerenciamento bacana dos recursos, seu hd pode lotar e vc ficar sem o seu proxy para a sua rede. Mas se for por custo, ai blz.Diz para a diretoria que a bagaça pode travar rsrs. Em resumo acho que você terá de rever suas configuraçoes de proxy autenticado para proxy transparente :) Em 12 de novembro de 2014 08:23, Flavio Menezes dos Reis flavio-r...@pge.rs.gov.br escreveu: Henrique, Acho que deveria haver, se necessário, uma reunião, no mínimo, para alterar o escopo do projeto. Não acho prudente colocar o squid e o AD na mesma máquina, a não se que seja em um mesmo host físico, mas em VMs separadas. A pergunta não seria como fazer isto, mas como alterar este escopo pra que a solução não sofra com problemas no futuro. Atte., Em 11 de novembro de 2014 21:51, Henrique Fagundes henri...@linuxadmin.com.br escreveu: Senhores, Boa noite! Pra quem vem acompanhado a minha labuta da implementação de um servidor PDC com Samba4. Digo que obtive algum sucesso, sendo que ainda está faltando testar as GPOs, porém farei isso posteriormente. O grande objetivo dessa implementação foi a substituição de um servidor AD da Microsoft. E até os últimos testes que eu andei fazendo, o Samba4 vem atendendo perfeitamente. A ultima coisa que testei, foi colocar o Squid3 para autenticar no Samba4, de modo que NÃO FICASSE abrindo aquela janela de autenticação no navegador. Então, eu segui esses tutoriais abaixo e funcionou tudo perfeitamente. Criei os grupos lá o Sambam4 e tal, e ficou tudo beleza. Descobri que para autenticar no AD, teria que colocar a máquina do proxy no domínio, então usei esse tutorial: http://bit.ly/1whLmRM Funcionou beleza! E depois, para configurar o Squid3 autenticado, usei esse tutorial: http://bit.ly/1whK35j Também funcionou beleza! Aí depois de tudo funcionando, eu me atentei em um detalhe. No escopro do projeto, está pré-definido que o Squid3 deve ficar na mesma máquina que o Samba4. Aí vem a minha dúvida: Como eu faço para o proxy autenticar no PDC (não abrindo aquela janela que pede autenticação) se ambos estão na mesma máquina? Alguém tem uma ideia de como eu devo começar? Implementei o samba assim, sendo que a única coisa que fiz de diferente é que forcei o Samba4 a usar o Bind9.9 como DNS: http://bit.ly/1whLKzL Obs: Usei o Debian 7.7.7 i386 em ambas as máquinas. Ficarei muito grato se alguém puder dar uma ideia. Atenciosamente, Henrique Fagundes henri...@linuxadmin.com.br Skype: magnata-br-rj Linux User: 475399 http://www.aprendendolinux.com/ http://www.facebook.com/PortalAprendendoLinux http://youtube.com/aprendendolinux/ http://twitter.com/aprendendolinux/ __ Participe do Grupo Aprendendo Linux http://listas.aprendendolinux.com Ou envie um e-mail para: aprendendolinux-subscr...@listas.aprendendolinux.com -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5462a0f6.8050...@linuxadmin.com.br -- Flávio Menezes dos Reis Procuradoria-Geral do Estado do RS Assessoria de Informática do Gabinete Técnico Superior de Informática (51) 3288-1763 -- Atenciosamente, Rodrigo da Silva Cunha
Re: Debian's contact info
Title: Join Brewster debian-user-portuguese@lists.debian.org Phone Number (Mobile) Confirm or Edit For your safety, this link expires in 48 hours Featured on: Why did you receive this email? The sender wanted to confirm that above contact info is up-to-date Your displayed contact details are what they currently have for you Your info is 100% secure and private between you and sender Please email us with questions at supp...@brewster.com Happy staying in touch! Confirm or Edit Your Contacts, Synced Anywhere Learn More Brewster, Inc. 11 East 4th St, #2F New York, NY 10003 Unsubscribe -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547f23cc1083b_1be03fe1ca022f60241...@prod-rs-r03.ihost.brewster.com.mail
Concorra a ingressos para o FISL16
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Buenas! A organização do Fórum Internacional de Software Livre (FISL) está lançando uma pesquisa para saber a opinião da comunidade brasileira de Software Livre e assim ajudar a definir o conteúdo do FISL16, que acontecerá de 08 a 11 de julho de 2015 em Porto Alegre - RS. A pesquisa estará disponível até o dia 15/01/2015. E ainda: as 30 melhores respostas para a pergunta Por que eu quero participar do FISL 16 ganharão uma inscrição gratuita para o FISL 16 cada. Participe no formulário abaixo: http://pesquisa.softwarelivre.org/index.php/665591 - -- ,= ,-_-. =. ((_/)o o(\_)) Não use drogas: `-'(. .)`-' Use GNU+Linux! \_/ Usuário GNU+Linux #430209 Blog: https://dausacker.wordpress.com/ Jabber/XMPP: dausac...@jabber.se Diaspora: dausac...@pod.geraspora.de Quitter: https://quitter.se/cdausacker -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUfzDJAAoJECzdJHoq6+C9HfAQAKsM7RlajDdIMbe9rhHupfOp FotK2mX7auAyo4k1tSLpmnnyV+mQUvF5kfouyweKrojsjIAAztg8BiKXVD74XeTZ CwCXULOPpA9J3wBufLkaAY9w5cYK9/IItSed30PkJwZWCAOn7hVabZKHxgD/k3Fx L4hRZ2XOR+VTdgHRGrPaREFIpRD4WKnbo7fWaQXKt1d01wyDOkpBeDyyTx4s56s8 udBE1yFbfhg0rLxFEhrDSArOLwRmIxgF2TAH8bAocO4fVMmDznokk1fQNKdHKOhY uKNBiyRaH8VeB0u+DT4rlSOOFym5lgZ5rvdiZcWPyHi96+orQS/mzgxQRh8w1h57 Wop7tzitPxD9jGg/ZUduVpAZjvln7gpi2c0XGQS54h1VfgARPR0wScxecUnyJx6N mlnR9vLt/u3hvNvrIoA1zW1F738OVXcaw+0R1AtTCJyFedikzgMohcwMoNByaWKC 55qduGjujDtUEvAA1S/S500Xga1npk+ya5Nad4sr3wSpdJThk9bh1D41tLF8ZrbK gomZoTpI5Z3lB/7Q5GV10xTNoBFLho3U1hOWZPpIUQaOBDfA+yYoiShFoyxWJFog hLM6j6xfjCQXnhc2zxVQ0YRLuWt/y705fZMD1xGARa04eSpFdET2a0vGFpoUrntu OIIihbUPr7BZ3GncvCsg =aPvP -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547f30ca.9000...@softwarelivre.org
Botao POWER
Olá pessoal, gostaria de saber como habilito o botão power para desligar meu debian 7. Pelo que pesquisei na internet tenho que ter o arquivo: /proc/acpi/powerbtn-acpi-support.sh Para a ação funcionar, porem não existe esse arquivo na minha instalação. Existe outra maneira de configurar tal ação? Obs: Nessa instalação não tenho o X instalado. Obrigado. -- --- Eduardo Rodrigues da Luz ---
Re: [OFF-TOPIC] GVT de 35MB
Opa, Obrigado amigo! Foi de grande ajuda. De todas as repostas que recebi, a sua foi a mais solícita. Vou pesquisar agora se tem como quebrar esse firmware e fazer alterações. Desde já muito obrigado. Atenciosamente, Henrique Fagundes henri...@linuxadmin.com.br Skype: magnata-br-rj Linux User: 475399 http://www.aprendendolinux.com/ http://www.facebook.com/PortalAprendendoLinux http://youtube.com/aprendendolinux/ http://twitter.com/aprendendolinux/ __ Participe do Grupo Aprendendo Linux http://listas.aprendendolinux.com Ou envie um e-mail para: aprendendolinux-subscr...@listas.aprendendolinux.com Mensagem original Assunto: Re: [OFF-TOPIC] GVT de 35MB De: Jacques Teixeira jacquesteixe...@gmail.com Para: Henrique Fagundes henri...@linuxadmin.com.br Data: 03/12/2014 14:55 tudo bem Henrique, segue modelo do modem que a gvt usa de 35 mega aqui, cara as portas a principio não são bloqueadas, mas tem muita coisa que tu não consegue mexer , por exemplo, tu não altera o ip da rede local , fica no 192.168.25.1, ridículo, mas e isso, também não consegue desabilitar o dhcp , se tu tem outro dhcp server na tua rede, tu vai ter que bloquear o dhcp da gvt por regra de firewall, e deixar habilitado distribuindo um ip só, foi a solução que encontrei aqui, e só não achei nada de dmz nele , Segue um print da pagina inicial dele para você pesquisar pelo modelo. Imagem inline 1 Att Jacques Teixeira Em 2 de dezembro de 2014 21:53, Henrique Fagundes henri...@linuxadmin.com.br mailto:henri...@linuxadmin.com.br escreveu: Colegas, Alguém do grupo possui GVT da velocidade de 35MB? Se sim, qual o modem que eles costumam enviar? Outra dúvida: Eles costuma bloquear portas baixas, do tipo: 80, 21, 22 e etc? Estou migrando de velocidade, passando para 35Megas e preciso de um modem que possua recursos avançados, do tipo que deixe eu mudar a range de IPs, desativar o DHCP e que faça uma DMZ para o IP do servidor. E também preciso que essas portas mencionadas estejam abertas. Atualmente tenho GVT de 15MB, com um modem SAGEMCOM que tem todos esses recursos e o link não tem nenhuma porta bloqueada. No aguardo de informações. Atenciosamente, Henrique Fagundes henri...@linuxadmin.com.br mailto:henri...@linuxadmin.com.br Skype: magnata-br-rj Linux User: 475399 http://www.aprendendolinux.__com/ http://www.aprendendolinux.com/ http://www.facebook.com/__PortalAprendendoLinux http://www.facebook.com/PortalAprendendoLinux http://youtube.com/__aprendendolinux/ http://youtube.com/aprendendolinux/ http://twitter.com/__aprendendolinux/ http://twitter.com/aprendendolinux/ __ Participe do Grupo Aprendendo Linux http://listas.aprendendolinux.__com http://listas.aprendendolinux.com Ou envie um e-mail para: aprendendolinux-subscribe@__listas.aprendendolinux.com mailto:aprendendolinux-subscr...@listas.aprendendolinux.com -- To UNSUBSCRIBE, email to debian-user-portuguese-__requ...@lists.debian.org mailto:debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org mailto:listmas...@lists.debian.org Archive: https://lists.debian.org/__547e50de.80...@linuxadmin.com.__br https://lists.debian.org/547e50de.80...@linuxadmin.com.br -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547f81ce.4050...@linuxadmin.com.br
Re: Worry about entropy?
On Mon, Dec 01, 2014 at 04:48:36PM -0400, francis picabia wrote: Hi, Has anyone experience with seeing significant performance boost, or at least avoiding timeouts when under load, related to keeping entropy fed some how? I've already read the articles discussing use of /dev/random etc., but I'm talking about things I implement, not things I code. I can imagine encrypted file system or owncloud and that sort of thing being aided, but could it also be important for SSL? I've seen applications that block due to missing entropy, but those were not DNSSEC related. I'd recommend to try usage of haveged to see if the situation improves. If you really need a lot of entropy you can think about using the Simtec entropy key daemon with ekeyd. I bought one a few years back just to try it and can confirm that it's easy to integrate. Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141203085207.ga5...@timegate.de
Re: boot fails on jessie on Acer Travelmate
On 2014-12-02, Pierre Couderc pie...@couderc.eu wrote: Hello I have a problem with jessie : my Acer Travelmate (P253) refuses to boot. A Secure Boot and Fast Boot in the UEFI problem, perhaps? Did you say whether you were dual booting? Anything here that helps? http://superuser.com/questions/714856/trying-to-dual-boot-windows-8-1-and-debian-jessie http://www.linlap.com/acer_travelmate_p253 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnm7tkm1.2e2.cu...@einstein.electron.org
Re: Debian fork: 'Devuan', Debian without Systemd
Am Mittwoch, 3. Dezember 2014, 08:35:00 schrieb Erwan David: Le 02/12/2014 23:15, Martin Steigerwald a écrit : Am Dienstag, 2. Dezember 2014, 18:47:38 schrieb Renaud OLGIATI: On Tue, 2 Dec 2014 14:22:13 -0700 Aaron Toponce aaron.topo...@gmail.com wrote: It's a waste. They shouldn't have left. I'm pretty neutral about systemd as I'm only an end user but I disklike having it forced upon me this way. # apt-get install upstart # apt-get install sysvinit-core # apt-get install openrc No one is forcing you to stick with systemd. The fork is just silly. Another way to look at it is forward planning for the release after Jessie, when systemd may well become compulsory... Or going beyond what is offered in Debian… like making GNOME installable without having any systemd related package installed. The systemd package is just a small part of systemd. I'd like to remove systemd-logind and lbpam-systemd, sinc I have no clue at all that logind is better deisgned and programmed than resolved, which showed it was designed without any care for well known attacks. I explicetely wrote any systemd related package. But yes, my example was incomplete. With all related packages it looks like this: merkaba:~ LANG=C apt-get purge libpam-systemd libsystemd-id128-0 libsystemd0 libsystemd0 systemd systemd-ui Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: abe-data analitza-common augeas-lenses bluez-obexd briquolo-data calligrastage-data celestia-common colobot-common colobot-common-sounds colobot-common-textures command-not-found dreamchess-data ebtables epiphany-data extremetuxracer-data extremetuxracer-extras ffmpegthumbs fonts-ebgaramond-extra freedroid-data freedroidrpg-data frogatto-data gir1.2-vte-2.90 kalzium-data kde-config-cron kde-games-core-declarative kde-icons-mono kde-thumbnailer-deb kdeartwork-style kdeartwork-theme-window kdeartwork-wallpapers kdeedu-kvtml-data kdegames-card-data kdegames-mahjongg-data kdegraphics-mobipocket kdegraphics-strigi-analyzer kdegraphics-thumbnailers kdenetwork-filesharing kdepim-mobileui-data kdesdk-strigi-plugins kdesdk-thumbnailers kexi-data kgamma kgeography-data klettres-data ksaneplugin kstars-data ktouch-data ktux lbreakout2-data libakonadi-socialutils4 libakonadi-xml4 libalure1 libanalitza5abi1 libanalitzagui5abi1 libanalitzaplot5abi1 libapache-poi-java libaugeas0 libbluedevil2 libboost-chrono1.55.0 libboost-signals1.55.0 libboost-wave1.55.0 libbulletcollision2.82 libbulletdynamics2.82 libcommons-codec-java libcomposereditorng4 libdataquay0 libdebconf-kde0 libdumb1 libechonest2.1 libfishsound1 libfox-1.6-0 libfreeimage3 libfs6 libftgl2 libgcj-bc libgeoclue0 libglee0d1 libgtkmm-3.0-1 libguess1 libgwengui-fox16-0 libgwengui-gtk2-0 libgwenhywfar60-dev libid3-3.8.3c2a libkasten2controllers2 libkasten2core2 libkasten2gui2 libkasten2okteta1controllers1abi1 libkasten2okteta1core1 libkasten2okteta1gui1 libkdeedu-data libkdegames6abi1 libkdegamesprivate1abi1 libkeduvocdocument4 libkiten4abi1 libkmahjongglib4 libktoblzcheck1-dev liblinearmath2.82 liblo7 liblrdf0 liblsofui4 libmozjs185-1.0 libmxml1 libmygui.ogreplatform0debian1 libmyguiengine3debian1 libnetcf1 liboggz2 libogre-1.9.0 libokteta1core1 libokteta1gui1 libparted-fs-resize0 libphysfs1 libprojectm2 libqapt1 libqtgstreamerutils-0.10-0 libqxt-core0 libqxt-gui0 libraptor1 librubberband2 libsublime8 libswt-cairo-gtk-3-jni libswt-glx-gtk-3-jni libswt-webkit-gtk-3-jni libunshield0 libusbredirhost1 libva-glx1 libvte-2.90-9 libvte-2.90-common libxine2-bin libxine2-doc libxine2-ffmpeg libxml++2.6-2 libxmlbeans-java libxmp4 manaplus-data neverball-common neverball-data oolite-data oolite-data-sounds oolite-doc openmw-data p7zip pachi-data palapeli-data parley-data pbzip2 pinball-data pingus-data pristine-tar projectm-data python-gdbm python-ipaddr python-opengl python-pyside.qtdeclarative python-pyside.qtgui python-pyside.qthelp python-pyside.qtnetwork python-pyside.qtopengl python-pyside.qtscript python-pyside.qtsql python-pyside.qtsvg python-pyside.qttest python-pyside.qtuitools python-pyside.qtwebkit python-pyside.qtxml python-urlgrabber qtdeclarative4-kqtquickcharts-1 redshift scummvm-data supertux-data transcode-doc trophy-data ttf-femkeklaver ttf-unifont twolame unmo3 x11-session-utils x11-xfs-utils xinit Use 'apt-get autoremove' to remove them. The following extra packages will be installed: icedtea-6-jre-cacao icedtea-6-jre-jamvm libqt4-phonon openjdk-6-jre-headless openjdk-6-jre-lib Suggested packages: sun-java6-fonts fonts-ipafont-gothic fonts-ipafont-mincho fonts-indic […apt-get busy with dependency calculation, eating 100% of one core …] The following packages will be REMOVED: abe* acpi-fakekey* adonthell* adonthell-data* akonadiconsole* akregator*
Re: boot fails on jessie on Acer Travelmate
One big difference is that after jessie installation boot flag has disappeared : gpt : wheezy : Model: ATA Crucial_CT480M50 (scsi) Disk /dev/sda: 480GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Number Start EndSizeFile system Name Flags 1 1049kB 512MB 511MB fat32 boot 2 512MB 467GB 467GB ext4 3 467GB 480GB 12.8GB linux-swap(v1) jessie : Model: ATA Crucial_CT480M50 (scsi) Disk /dev/sda: 480GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Number Start EndSizeFile system Name Flags 1 1049kB 538MB 537MB fat32 2 538MB 467GB 467GB ext4 3 467GB 480GB 12.8GB linux-swap(v1) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547ee39d.5030...@couderc.eu
Installing Debian on a SuperMicro server
I am trying to install Debian on a SuperMicro server on two ssd's configured in the bios as a RAID1 (I think it is called a fake-raid). Debian Stable does not recognize the disks at all. Debian Testing's installation disk picks it up as a RAID1 device (even when I configure it in the bios as non-raid disks) and can install up to the stage where grub has to be installed. Grub does not recognise the RAID1 device but sees the two disks separately. When I open gparted in Linuxmint 17 (live imaget) it complains when the disks are configured in bios as RAID1 but gparted sees the separate disks when it is configured as non-raid devices. I am prepared to go the route of a software raid if necessary, but in the Debian installer that is only possible if the Debian-installer sees the disks as separate disks as Grub does. Any suggestions for the way forward? Should I put a usb-stick in the server and install grub there? Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3)
Re: boot fails on jessie on Acer Travelmate
Le 03/12/2014 10:07, Curt a écrit : On 2014-12-02, Pierre Couderc pie...@couderc.eu wrote: A Secure Boot and Fast Boot in the UEFI problem, perhaps? Did you say whether you were dual booting? Anything here that helps? I said No alternate OS... ;) It is smallest installation possible. Thank you PC -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547ee8c7.4080...@couderc.eu
Re: Debian fork: 'Devuan', Debian without Systemd
Le Wed, 03 Dec 2014 10:18:36 +0100, Martin Steigerwald mar...@lichtvoll.de a écrit : Am Mittwoch, 3. Dezember 2014, 08:35:00 schrieb Erwan David: Le 02/12/2014 23:15, Martin Steigerwald a écrit : Am Dienstag, 2. Dezember 2014, 18:47:38 schrieb Renaud OLGIATI: On Tue, 2 Dec 2014 14:22:13 -0700 Aaron Toponce aaron.topo...@gmail.com wrote: It's a waste. They shouldn't have left. I'm pretty neutral about systemd as I'm only an end user but I disklike having it forced upon me this way. # apt-get install upstart # apt-get install sysvinit-core # apt-get install openrc No one is forcing you to stick with systemd. The fork is just silly. Another way to look at it is forward planning for the release after Jessie, when systemd may well become compulsory... Or going beyond what is offered in Debian… like making GNOME installable without having any systemd related package installed. The systemd package is just a small part of systemd. I'd like to remove systemd-logind and lbpam-systemd, sinc I have no clue at all that logind is better deisgned and programmed than resolved, which showed it was designed without any care for well known attacks. I explicetely wrote any systemd related package. [...] So you can still choose to what init system to use, but running completely without any systemd related packages gives you a really crippled system. As explained several times on this ML, depending against libsystemd0 package doesn't mean anything about requiring systemd to be used as PID1 or not. Even Ian's GR was not taking the I don't want any systemd package on my machine use case into account you know. But if you have that special concern, you'll have to start recompiling the packages I'm afraid. Start with policykit and network-manager (and other package defining a dependency against libpam-systemd) to make them use ConsoleKit again, you would at least be able to remove the systemd package completely. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141203123926.4fb34...@soldur.bigon.be
Re: Installing Debian on a SuperMicro server
Johann Spies wrote: I am trying to install Debian on a SuperMicro server on two ssd's configured in the bios as a RAID1 (I think it is called a fake-raid). Debian Stable does not recognize the disks at all. Debian Testing's installation disk picks it up as a RAID1 device (even when I configure it in the bios as non-raid disks) and can install up to the stage where grub has to be installed. Grub does not recognise the RAID1 device but sees the two disks separately. When I open gparted in Linuxmint 17 (live imaget) it complains when the disks are configured in bios as RAID1 but gparted sees the separate disks when it is configured as non-raid devices. I am prepared to go the route of a software raid if necessary, but in the Debian installer that is only possible if the Debian-installer sees the disks as separate disks as Grub does. Any suggestions for the way forward? Should I put a usb-stick in the server and install grub there? Well, my first recommendation would have been turning off BIOS RAID - but that seems not to work for you. (I've been running SuperMicro servers for years, always turn off hardware RAID and rely on md - no SSDs though). Did a little googling and found this: https://wiki.debian.org/DebianInstaller/SataRaid - which recommends adding dmraid=true to the kernel boot line (see page for detailed instructions). You might get some good advice on the linux-raid email list. Also, I've found the webhostingtalk.com forums to be a good source for product-specific knowledge on various servers - supermicro tech support is basically useless. Miles Fidelman -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547efdd2.5010...@meetinghouse.net
Re: Stale file in Debian after change of equivs package
Perfect! That what I was searching for. The configuration is marked as obsolete! Thank you! Am 02.12.2014 um 23:29 schrieb Bob Proulx: Don Armstrong wrote: mad wrote: I am using equivs to create simple packages with dependencies and a few files. Now I removed one file from the equivs package and installed the resulting deb file. The deb file does not contain the file but dpkg did not remove the old file and says that the file belongs to the package. What did I do wrong? Files in /etc are usually conffiles, which are not removed on upgrade by default. Presumably equivs is following standard practice, and marking them as such unless you do work to avoid it. Likely. If so you can test for this by querying the package database. dpkg-query -W -f='${Conffiles}\n' foopackagenamehere That will list out the files from that package along with the checksum of it. If you want a full dump from the system then don't specify a package name. But then better page it or grep for just what you want. I have 121 of them on my system from various packages. dpkg-query -W -f='${Conffiles}\n' | grep obsolete Bob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547f067f.8070...@sharktooth.de
Re: Replacing systemd in Jessie
On Sun, Nov 30, 2014 at 05:15:36PM -0800, Patrick Bartek wrote: On Sun, 30 Nov 2014, Chris Bannister wrote: [I've somehow deleted the other messages, so this one will have to do] On Fri, Nov 28, 2014 at 01:59:02PM +0100, Jochen Spieker wrote: Patrick Bartek: On Thu, 27 Nov 2014, John Hasler wrote: Patrick Bartek writes: It seems systemd cannot not be installed in Jessie. You mean Testing. Jessie has not been released. Semantics. Nothing is final yet, jessie is still a moving target IOW not yet stable, so not just semantics. Yes. Semantics. Jessie not being Stable doesn't make Testing any less Jessie regardless of its state of development. Yes!!! Testing! Yay, we finally agree! \o/ -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141203124330.GD9553@tal
Re: Debian fork: 'Devuan', Debian without Systemd
Am Mittwoch, 3. Dezember 2014, 12:39:26 schrieb Laurent Bigonville: Le Wed, 03 Dec 2014 10:18:36 +0100, Martin Steigerwald mar...@lichtvoll.de a écrit : Am Mittwoch, 3. Dezember 2014, 08:35:00 schrieb Erwan David: Le 02/12/2014 23:15, Martin Steigerwald a écrit : Am Dienstag, 2. Dezember 2014, 18:47:38 schrieb Renaud OLGIATI: On Tue, 2 Dec 2014 14:22:13 -0700 Aaron Toponce aaron.topo...@gmail.com wrote: It's a waste. They shouldn't have left. I'm pretty neutral about systemd as I'm only an end user but I disklike having it forced upon me this way. # apt-get install upstart # apt-get install sysvinit-core # apt-get install openrc No one is forcing you to stick with systemd. The fork is just silly. Another way to look at it is forward planning for the release after Jessie, when systemd may well become compulsory... Or going beyond what is offered in Debian… like making GNOME installable without having any systemd related package installed. The systemd package is just a small part of systemd. I'd like to remove systemd-logind and lbpam-systemd, sinc I have no clue at all that logind is better deisgned and programmed than resolved, which showed it was designed without any care for well known attacks. I explicetely wrote any systemd related package. [...] So you can still choose to what init system to use, but running completely without any systemd related packages gives you a really crippled system. As explained several times on this ML, depending against libsystemd0 package doesn't mean anything about requiring systemd to be used as PID1 or not. Even Ian's GR was not taking the I don't want any systemd package on my machine use case into account you know. Laurent, I wrote: So you can still choose to what init system to use, but running completely without any systemd related packages gives you a really crippled system. For me that states clearly that I am perfectly aware of that. So I do not get why you repeat it and even complain that its already explained several times on this ML as actually I think I did not leave a trace of doubt of my awareness of that in the way I have written this. But if you have that special concern, you'll have to start recompiling the packages I'm afraid. Start with policykit and network-manager (and other package defining a dependency against libpam-systemd) to make them use ConsoleKit again, you would at least be able to remove the systemd package completely. I just showed this. I am not sure whether I have a concern about it. But its a topic the devuan fork can extend upon whats currently available in Debian. Whether it would be necessary to fork Debian for that, I don´t know. That would depend on whether maintainers of the involved Debian packages would accept patches which can make them (maybe optionally?) use ConsoleKit again. I bet there may be a limit on what the maintainers of the official Debian packages would accept there. Of course, its also thinkable to provide those patches upstream, but I have doubt that GNOME maintainers would accept them. -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2373015.jQGrihgpOm@merkaba
freenas bootable USB in debian.
I am using Debian as my desktop and GUI. i want to install/write freenas usb boot image *.img file to Empty USB. for windows we have windows32diskimager but i am looking for an alternative of this software in debian. can you guyz please help. Thanks alot in advance. Thanks, MYK.
Re: freenas bootable USB in debian.
Hi. On Wed, Dec 03, 2014 at 06:19:28PM +0500, Muhammad Yousuf Khan wrote: I am using Debian as my desktop and GUI. i want to install/write freenas usb boot image *.img file to Empty USB. for windows we have windows32diskimager but i am looking for an alternative of this software in debian. can you guyz please help. Thanks alot in advance. But you have such utility out of the box. It's called 'cat'. Others may prefer 'cp' or 'dd', but 'cat' is my favorite. Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141203134203.GA22972@x101h
Re: Installing Debian on a SuperMicro server
Thanks Miles. Did a little googling and found this: https://wiki.debian.org/ DebianInstaller/SataRaid - which recommends adding dmraid=true to the kernel boot line (see page for detailed instructions). I have tried the procedure in this website, but my results are different. I never got a chance to specify the settings for the partition on the fake raid. It just used the whole device as a partion mounted at /. When I logged in in rescue mode, I could not find the different devices to configure grub. https://lists.debian.org/547efdd2.5010...@meetinghouse.net I have also tried Ubuntu-server 2014-10 but I did not understand the installation asking me whether to activate raid or not for the devices and then not showing them anywhere. Centos 6.6 could install without a problem but I do not want to work with a rpm-based system if possible. At the moment Centos or Fedora (which I would not prefer on any server) seems to be the non-commercial options available to me. Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3)
Re: Replacing systemd in Jessie
On 12/03/2014 at 07:43 AM, Chris Bannister wrote: On Sun, Nov 30, 2014 at 05:15:36PM -0800, Patrick Bartek wrote: On Sun, 30 Nov 2014, Chris Bannister wrote: Nothing is final yet, jessie is still a moving target IOW not yet stable, so not just semantics. Yes. Semantics. Jessie not being Stable doesn't make Testing any less Jessie regardless of its state of development. Yes!!! Testing! Yay, we finally agree! \o/ So are you saying that you agree that the original statement that systemd cannot not be installed in Jessie was accurate, because current testing is jessie? Because that's what we/I've been saying all along, and it's what the post you're responding to said - but it's also what John Hasler's original response (with which you seemed to agree) seemed to reject. Back when I was, say, five years old, it would have been perfectly accurate for someone to say of me that [myname] cannot jump high enough to touch the ceiling., because I could not. Today, that statement would be less than completely accurate, because I can easily jump high enough to touch a standard 8- or 9-foot ceiling. It's the same statement, and it still refers to me, by my name - but it's not the same me in both cases, because I've changed in the meantime. In exactly, the same way, it is currently accurate to say that systemd cannot not be installed in Jessie, in reference to current testing... ...even if it may no longer be accurate to say that after jessie is released as stable. It's the same statement in both cases, and it still refers to jessie, by name - even if jessie changes in the meantime. -- 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: Debian fork: 'Devuan', Debian without Systemd
As explained several times on this ML, depending against libsystemd0 package doesn't mean anything about requiring systemd to be used as PID1 or not. Even Ian's GR was not taking the I don't want any systemd package on my machine use case into account you know. Why focus on PID1 ? As I said, systemd-resolved proved to be vulnerable to a well known attack. What makes us think that more quality was put in systemd-logind ? Not wanting systemd means not wanting it *at all*. I personnally do not trust it for critical system tasks. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141203151314.go8...@rail.eu.org
Re: Replacing systemd in Jessie
On 12/3/2014 9:38 AM, The Wanderer wrote: On 12/03/2014 at 07:43 AM, Chris Bannister wrote: On Sun, Nov 30, 2014 at 05:15:36PM -0800, Patrick Bartek wrote: On Sun, 30 Nov 2014, Chris Bannister wrote: Nothing is final yet, jessie is still a moving target IOW not yet stable, so not just semantics. Yes. Semantics. Jessie not being Stable doesn't make Testing any less Jessie regardless of its state of development. Yes!!! Testing! Yay, we finally agree! \o/ So are you saying that you agree that the original statement that systemd cannot not be installed in Jessie was accurate, because current testing is jessie? Because that's what we/I've been saying all along, and it's what the post you're responding to said - but it's also what John Hasler's original response (with which you seemed to agree) seemed to reject. Back when I was, say, five years old, it would have been perfectly accurate for someone to say of me that [myname] cannot jump high enough to touch the ceiling., because I could not. Today, that statement would be less than completely accurate, because I can easily jump high enough to touch a standard 8- or 9-foot ceiling. It's the same statement, and it still refers to me, by my name - but it's not the same me in both cases, because I've changed in the meantime. In exactly, the same way, it is currently accurate to say that systemd cannot not be installed in Jessie, in reference to current testing... ...even if it may no longer be accurate to say that after jessie is released as stable. It's the same statement in both cases, and it still refers to jessie, by name - even if jessie changes in the meantime. It IS accurate to say that after Jessie is released as stable. Jessie has been frozen, and only RC fixes are being made. This is not considered an RC fix. The situation will continue until the next release, at a minimum. Jerry -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547f290c.5050...@gmail.com
My name is Gatan Magsino..
My name is Gatan Magsino, I work with Mediterranean Bank in Malta. Can i trust you with a deal worth $8.3M USD? Please reply to my email: mga...@rogers.com for more information --- This email has been checked for viruses by Avast antivirus software. http://www.avast.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xwbtp-0008oy...@golddisk.ru
Justice For Zemir (cello song)
#JusticeForZemir http://youtu.be/5eHmraL3wvE Zemir Begic was subject to a revenge killing by 2 coloured young men for the death of Michael Brown. The killers reportedly shouted Kill all the white people before beating Zemir to death with two hammers. It has been reported that previously the killers were involved in the Ferguson protests. This was a revenge killing. This is a plea for equality of outcomes: That justice, that is: an eye for an eye comes to the people who killed Zemir Begic. (C) Gnu GPL v2 (MikeeUSA) Instrument: Cello Mit einer kostenlosen E-Mail-Adresse @t-online.de werden Ihre Daten verschlüsselt übertragen und in Deutschland gespeichert. www.t-online.de/email-kostenlos -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1xwdae-0mhb...@fwd18.aul.t-online.de
S-D is like a cold vastness. (Song included here)
https://www.youtube.com/watch?v=tRvf9LauZIMlist=UUpfKI2v7BTPBrx6HWvEx1Lw [ Instruments: Analogue Synth: MicroBRUTE Software Synth Organ: ZynAddSubFX ] Synth and organ in the cold infinite vastness. As if abandoned. Seeing bright lights, but feeling no warmth. Kind of like what old-guard Free/Opensource contributors feel from the S..-D cou_p_i_sts in the space of GNU/Linux (See: S-D people being assholes to Bruce Perens https://lwn.net/Articles/620879/ ) (C) Gnu GPL v2 (Mik__USA) Mit einer kostenlosen E-Mail-Adresse @t-online.de werden Ihre Daten verschlüsselt übertragen und in Deutschland gespeichert. www.t-online.de/email-kostenlos -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1xwdc5-1vyg...@fwd34.aul.t-online.de
Re: Replacing systemd in Jessie
On Tue, 02 Dec 2014, Lisi Reisz wrote: On Tuesday 02 December 2014 07:05:09 Patrick Bartek wrote: User's do contrain. They even dictate. Always have. Developers should, if they are samrt, be developing what customers want or need. Not the other way around. That's the formula for going out of business. Listening to your customers as well as your potential customers is just good business. What customers?? This is open source. Developers do not need, if they do not want to, to take any notice of anyone but themselves. They do not need customers. This is the basic misconception. Developers do not need us, the users. We need them. This is NOT a business. It will go out of business (having not been one in the first place) not if it loses all its users (who are NOT customers) but if it loses all its developers. Substitute Users then. Reasoning still applies. That's a very arrogant attitude. Kind of naive, too. But yes, developer(s) don't have to respond to what users want, but they would be smart to do so. If you singly or as a group are developing software for others to use, open source or not, that software benefits from user feedback, if only for bug reports. If you are only writing for your own use and no one else's, why distribute it at all? Here's a truth: If there is a need, there will be someone to fill it. B -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141203092403.77b6d...@debian7.boseck208.net
squeeze-lts dist-upgrade to wheezy failed @ apt
Hello debian users, I am having trouble dist-upgrading from squeeze-lts to wheezy. I have been following these instructions to upgrade from pre-lts squeeze (didn't find any specific ones for lts): https://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.html The problem happens when it gets to apt: dpkg: error processing apt (--configure): subprocess installed post-installation script returned error exit status 2 configured to not write apport reports Errors were encountered while processing: apt Can't locate File/Find.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl /usr/local/lib/perl/5.10.0 /usr/local/share/perl/5.10.0 .) at /usr/bin/debsums line 10. BEGIN failed--compilation aborted at /usr/bin/debsums line 10. E: Problem executing scripts DPkg::Post-Invoke 'if [ -x /usr/bin/debsums ]; then /usr/bin/debsums --generate=nocheck -sp /var/cache/apt/archives; fi' Indeed, I cannot locate the File/Find.pm module on my system (with locate grep). Trying to install it via cpan fails with Can't locate autouse.pm in @INC... `apt-get -f install` fails with the same message as above. I noticed the list of unmet dependencies included a bunch of vlc packages that I do not care about, so I tried getting rid of those, and it pares down the list of problem packages by about half: # apt-get purge vlc vlc-nox vlc-plugin-notify vlc-plugin-pulse libvlc5 ... You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: consolekit : Depends: libck-connector0 (= 0.4.5-3.1) but 0.4.1-4 is to be installed irssi : Depends: perlapi-5.14.2 libalgorithm-diff-xs-perl : Depends: perlapi-5.14.2 libapache2-mod-perl2 : Depends: perlapi-5.14.2 libapt-pkg-perl : Depends: libapt-pkg4.10 but it is not installable libbsd-resource-perl : Depends: perlapi-5.14.2 libcurses-perl : Depends: perlapi-5.14.2 libdatetime-perl : Depends: perlapi-5.14.2 libdbd-mysql-perl : Depends: perlapi-5.14.2 libdbd-pg-perl : Depends: perlapi-5.14.2 libdbd-sqlite3-perl : Depends: perlapi-5.14.2 libdbi-perl : Depends: perlapi-5.14.2 libdevmapper1.02.1 : Depends: dmsetup (= 2:1.02.74-8) but 2:1.02.48-5 is to be installed libfcgi-perl : Depends: perlapi-5.14.2 libgd-text-perl : Depends: libgd-gd2-perl but it is not going to be installed libhtml-parser-perl : Depends: perlapi-5.14.2 libio-pty-perl : Depends: perlapi-5.14.2 liblist-moreutils-perl : Depends: perlapi-5.14.2 libmouse-perl : Depends: perlapi-5.14.2 libnet-dns-perl : Depends: perlapi-5.14.2 libnet-libidn-perl : Depends: perlapi-5.14.2 libnet-ssleay-perl : Depends: perlapi-5.14.2 libnetaddr-ip-perl : Depends: perlapi-5.14.2 libparams-classify-perl : Depends: perlapi-5.14.2 libparams-util-perl : Depends: perlapi-5.14.2 libparams-validate-perl : Depends: perlapi-5.14.2 libperl5.14 : Depends: perl-base (= 5.14.2-21+deb7u2) but 5.10.1-17squeeze6 is to be installed libsocket6-perl : Depends: perlapi-5.14.2 libterm-readline-gnu-perl : Depends: perlapi-5.14.2 libuuid-perl : Depends: perl-base (= 5.14.2-13) but 5.10.1-17squeeze6 is to be installed Depends: perlapi-5.14.2 libwmf0.2-7 : Depends: libgdk-pixbuf2.0-0 (= 2.22.0) but it is not going to be installed libyaml-syck-perl : Depends: perlapi-5.14.2 perl : Depends: perl-base (= 5.14.2-21+deb7u2) but 5.10.1-17squeeze6 is to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). I am not sure if (or specify a solution) is referring to some method other that purging/removing packages the way I tried above. I do notice that there are still what look like squeeze security backports that want to be installed My sources.list.d is empty my entire sources.list is: 1 # non-free is required for tg3 nic firmware 2 # W: Possible missing firmware /lib/firmware/tigon/tg3_tso5.bin for module tg3 3 # W: Possible missing firmware /lib/firmware/tigon/tg3_tso.bin for module tg3 4 # W: Possible missing firmware /lib/firmware/tigon/tg3.bin for module tg3 5 deb http://mirror.cc.columbia.edu/debian wheezy main contrib non-free 6 deb-src http://mirror.cc.columbia.edu/debian wheezy main contrib non-free 7 # *-updates replaces volatile @ squeeze (virus defs, tz data, etc) 8 # http://www.debian.org/releases/stable/i386/release-notes/ch-whats-new.en.html#stable-updates 9 deb http://mirror.cc.columbia.edu/debian wheezy-updates main contrib 10 deb-src http://mirror.cc.columbia.edu/debian wheezy-updates main contrib 11 deb http://security.debian.org/ wheezy/updates main contrib non-free What would be the recommended way of proceeding with this upgrade? Thanks for reading, Kenneth (Sorry for sending to list from gmail, it is my mail server I am upgrading)
Re: Worry about entropy?
On Mon, Dec 01, 2014 at 04:48:36PM -0400, francis picabia wrote: I'm looking at DNSSEC implementation. One guide points out haveged as a way to speed up performance of dnssec-keygen. It certainly did. I'm wondering if anyone has noticed performance improvement by running haveged on systems with certain applications. Instead of trying to rely on /dev/random, use /dev/urandom. Haveged is intetresting, but I think it might be a bit liberal on its entropy estimates. At any event, it feeds data into the same CSPRNG that both /dev/random and /dev/urandom read, so it's no more secure than just relying on /dev/urandom directly. Commonly found advice on the net is to look at /proc/sys/kernel/random/entropy_avail and it should be around 2000 or better. Another comment said that value is merely an estimate. Checking some Redhat server systems I handle, I'm seeing values between 100 and 200 most often. One Debian KVM system wildly varies from 2000 down to 150 within a few seconds, but it isn't doing any noticeable load. Entropy is _always_ an estimate. It's an approximate measurement of the unpredictability of the state of the system. In physics, it's an approximate measurement of the unpredictability of the state of gas particles in a closed system. Entropy isn't something you use. Has anyone experience with seeing significant performance boost, or at least avoiding timeouts when under load, related to keeping entropy fed some how? I've already read the articles discussing use of /dev/random etc., but I'm talking about things I implement, not things I code. I can imagine encrypted file system or owncloud and that sort of thing being aided, but could it also be important for SSL? OpenSSL, OpenSSH (which uses OpenSSL for random number generation), OpenVPN (which also uses OpenSSL), Kerberos (ditto), and even GnuPG (except for key generation), all use /dev/urandom. You should too. The only thing you'll get out of /dev/random is frustration due to blocking, because the entropy estimate of the system is low. Use /dev/urandom, and be happy. And secure. -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o pgpTao_Y0MK4j.pgp Description: PGP signature
Re: squeeze-lts dist-upgrade to wheezy failed @ apt
Hi again, I just wanted to follow up with more info. I think these packages that want to stay with squeeze are pinned, for example: root@gilgamesh:~/tmp# apt-cache policy perl-base perl-base: Installed: 5.10.1-17squeeze6 Candidate: 5.14.2-21+deb7u2 Version table: 5.14.2-21+deb7u2 0 500 http://mirror.cc.columbia.edu/debian/ wheezy/main i386 Packages *** 5.10.1-17squeeze6 0 100 /var/lib/dpkg/status But I have no /etc/apt/preferences file on this machine /etc/apt/preferences.d is empty Is it the case that during a dist-upgrade, the system might internally be pinning some packages for certain stages of the upgrade? Or should I try to unpin it somehow? Thanks again, Kenneth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CALXVCsJA1fupS3fa3WHNrSbGnwgWoF7tte1A=f+wtozvwsm...@mail.gmail.com
Re: Replacing systemd in Jessie
On Wed, 3 Dec 2014 09:24:03 -0800 Patrick Bartek nemomm...@gmail.com wrote: Hello Patrick, use and no one else's, why distribute it at all? Simple: Ego. -- Regards _ / ) The blindingly obvious is / _)radnever immediately apparent I'll be the paint on the side if you'll be the tin Love Song - The Damned pgp7sC38oBVg7.pgp Description: OpenPGP digital signature
Re: boot fails on jessie on Acer Travelmate
Hi again, On 03/12/14 08:56, Pierre Couderc wrote: Le 03/12/2014 07:58, Simon Hollenbach a écrit : you might want to dig further into this, Mmm, what is my other choice ? W8 ? Ubuntu ? I was talking about reporting a bug when you don't know what's wrong. But indeed, there are other choices if you want them, I don't, right now, and as we are talking about this on a Debian support list, discussing them here would be imho inappropriate anyway. as I can't see how a developer could fix the error you are experiencing without more information. But I am ready to spend hours to fix that ! Wht is needed ? Further information. But what you provided in your other mail, the partition layout, seems to be a good start, maybe even enough to solve your problem, not the installer's/GRUB's. I'll come back to that. When exactly does the boot-up stall? You don't even see the GRUB menu, do you? I am not sure what is the grub menu, but if it is the blue menu asking which debian version to load. I do not arrive there. It isn't blue any more at my place, it's skinned with a Debian logo aso, but yes, the menu that lets you select a boot-mode/kernel/os . It starts with GRUB loading... and then Welcome to GRUB iirc, followed by aforementioned menu. In fact, it seems to me that the disk is not read, but it tries to net boot. Why do you think it tries to boot from a network? Have you tried with another boot loader? Last time I installed, LILO was still available for selection from expert install iirc. If the system boots with LILO, you would have narrowed down the problem quite a bit. No, sorry, I am not enough expert. If this is a regression in GRUB, it must be solved, one way or another. Debian wheezy works fine on this computer. Jessie has worked too, but no more today. I don't consider myself an expert either, the expert install just asks more stuff, explained very well imo. Maybe just try it next time you install or on a spare machine. Again, I don't think filing a bug without any info but it doesn't work will get your problem solved. I am not able to find the bug myself. I am ready to spend hours to fix it, but I need the help of someone to tell me where to search... I think we got a differing understanding here. I think you just encountered a bug, or you did something really stupid, which shouldn't happen if you sanely try to install Debian. We got to describe the bug now, so it can be fixed. Now my solution attempt, it worked for me once (but like 3 years ago) On 03/12/14 11:19, Pierre Couderc wrote: One big difference is that after jessie installation boot flag has disappeared : gpt : wheezy : snip/ Number Start EndSizeFile system Name Flags 1 1049kB 512MB 511MB fat32 boot snip/ jessie : Number Start EndSizeFile system Name Flags 1 1049kB 538MB 537MB fat32 Why don't you toggle the bootable-flag on your /boot-partition by hand? It happened to me that this was the only thing that was wrong after installing. I did it with fdisk, run it from a rescue CD, specifying your disk /dev/sda as parameter: # fdisk /dev/sda Then, you hit [p] to print the partition table of sda, start counting from 0 until you find your boot partition, it should be 0, according to the gpt output. Then hit [b] to toggle the bootable flag on a partition and select the partition you just identified as your /boot-partition. Finally, write the changes to disk with [w], which also exits fdisk. Then reboot and, if you want, cross your fingers... Cheers, Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547f6858.4050...@gmail.com
System hangs at boot after Squeeze to Wheezy update (saslauthd culprit?)
Hi everybody, I just upgraded my VPS at Linode from Squeeze to Wheezy, everything looked find (only some issues with Dovecot), but after the reboot the system hangs at: [] Starting the hotplug events dispatcher: udevdudevd[1452]: starting version 175 . ok [ ok ] Synthesizing the initial hotplug events...done. [ ok ] Waiting for /dev to be fully populated...done. [] Activating swap...Adding 262140k swap on /dev/xvdb. Priority:-1 extents:1 across:262140k SSFS done. [] Checking root file system...fsck from util-linux 2.20.1 /dev/xvda: clean, 143730/4641408 files, 2003750/5177344 blocks done. EXT3-fs (xvda): using internal journal [ ok ] Cleaning up temporary files... /tmp /lib/init/rw. random: nonblocking pool is initialized [info] Loading kernel module loop. libkmod: ERROR ../libkmod/libkmod.c:554 kmod_search_moddep: could not open moddep file '/lib/modules/3 .16.5-x86_64-linode46/modules.dep.bin' [ ok ] Activating lvm and md swap...done. [] Checking file systems...fsck from util-linux 2.20.1 done. [ ok ] Mounting local filesystems...done. [ ok ] Activating swapfile swap...done. [ ok ] Cleaning up temporary files [ ok ] Setting kernel variables ...done. [] Configuring network interfaces...dhcpcd.sh: interface eth0 has been configured with new IP=178. 79.166.18 done. [ ok ] Cleaning up temporary files [ ok ] Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix. INIT: Entering runlevel: 2 [info] Using makefile-style concurrent boot in runlevel 2. [ ok ] Starting enhanced syslogd: rsyslogd. [ ok ] Starting SASL Authentication Daemon: saslauthd. Reading configuration from file: /etc/caldavd/caldavd.plist So, or it is something related to saslauthd (the last message printed), or to the error seen before with libkmod. Any clue?
Re: Debian fork: 'Devuan', Debian without Systemd
On 2 December 2014 at 19:22, Aaron Toponce aaron.topo...@gmail.com wrote: On Tue, Dec 02, 2014 at 09:40:20PM +0100, Märk Owen wrote: It's a waste. They shouldn't have left. I'm pretty neutral about systemd as I'm only an end user but I disklike having it forced upon me this way. # apt-get install upstart # apt-get install sysvinit-core # apt-get install openrc I doubt that this will work in the near future (jessie +1). Debian/Devuan WILL NEED an `udev` alternative to keep `sysinit-core` working. Sooner or later, there will be no more `sysvinit-core`, `upstart` or whatever, because `systemd` guys engulfed `udev` and they are change it to make sure it will only work with systemd = PID1, this sucks, _this is extortion_ (kind of). Everybody that falls for that, will regret. Devuan will need something like `eudev` to succeed. It is freaking unbelievable that Debian is now following RedHat after all we achieved during those ~two decades, by ourselves. I'm not against `systemd` itself, I'm against the lack of freedom to choose whatever init I need/want. Systemd is here, fine, but as an option ONLY. Well, no. Jessie isn't Debian. Devuan IS (will be) what we know about Debian! Waiting to see Joel joining Devuan... lol Cheers! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cajsm8j14y4x2vdr99jbwpo+_uaich3cshr_vyvzppihsqoc...@mail.gmail.com
Re: Worry about entropy?
On Wed, Dec 3, 2014 at 2:38 PM, Aaron Toponce aaron.topo...@gmail.com wrote: On Mon, Dec 01, 2014 at 04:48:36PM -0400, francis picabia wrote: I'm looking at DNSSEC implementation. One guide points out haveged as a way to speed up performance of dnssec-keygen. It certainly did. I'm wondering if anyone has noticed performance improvement by running haveged on systems with certain applications. Instead of trying to rely on /dev/random, use /dev/urandom. Haveged is intetresting, but I think it might be a bit liberal on its entropy estimates. At any event, it feeds data into the same CSPRNG that both /dev/random and /dev/urandom read, so it's no more secure than just relying on /dev/urandom directly. Commonly found advice on the net is to look at /proc/sys/kernel/random/entropy_avail and it should be around 2000 or better. Another comment said that value is merely an estimate. Checking some Redhat server systems I handle, I'm seeing values between 100 and 200 most often. One Debian KVM system wildly varies from 2000 down to 150 within a few seconds, but it isn't doing any noticeable load. Entropy is _always_ an estimate. It's an approximate measurement of the unpredictability of the state of the system. In physics, it's an approximate measurement of the unpredictability of the state of gas particles in a closed system. Entropy isn't something you use. Has anyone experience with seeing significant performance boost, or at least avoiding timeouts when under load, related to keeping entropy fed some how? I've already read the articles discussing use of /dev/random etc., but I'm talking about things I implement, not things I code. I can imagine encrypted file system or owncloud and that sort of thing being aided, but could it also be important for SSL? OpenSSL, OpenSSH (which uses OpenSSL for random number generation), OpenVPN (which also uses OpenSSL), Kerberos (ditto), and even GnuPG (except for key generation), all use /dev/urandom. You should too. The only thing you'll get out of /dev/random is frustration due to blocking, because the entropy estimate of the system is low. Use /dev/urandom, and be happy. And secure. So it seems it is mainly the *-keygen type applications which rely on /dev/random and the rest use urandom. In this case, there would be little benefit to running haveged all the time if few daily processes use /dev/random.
Re: Debian fork: 'Devuan', Debian without Systemd
On Wed, 3 Dec 2014 17:37:02 -0200 Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Sooner or later, there will be no more `sysvinit-core`, `upstart` or whatever, because `systemd` guys engulfed `udev` and they are change it to make sure it will only work with systemd = PID1, this sucks, Very likely, Jēmuzu, and they will explain their actions withWell, everyone has shifted to systemd, so there is no point... And we must do something... Cheers, Ron. -- All that is necessary for the forces of evil to triumph is for enough good men to do nothing. -- Edmund Burke -- http://www.olgiati-in-paraguay.org -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141203172022.5c227...@ron.cerrocora.org
Re: Debian fork: 'Devuan', Debian without Systemd
On 12/03/2014 08:37 PM, Martinx - ジェームズ wrote: Jessie isn't Debian. Devuan IS (will be) what we know about Debian! Waiting to see Joel joining Devuan... lol I've no problem with systemd (Sid), it works fine). I dont understand why some people complain about systemd. Devuan is not Mint or Ubuntu, I think it has no future and everyone will forget that systemd is new... -- Maderios -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547f777d.7040...@gmail.com
multi-monitor suspend inhibit from gnome-settings-daemon despite one being connected
Hello, I have a problem with systemd + gnome-settings-daemon + nvidia or gnome-session or ? It seems, that the gnome-settings-daemon forwards a suspend inhibit due to multiple monitors being connected, although only a single monitor, the internal laptop screen, is connected. Gnome correctly recognised that there is only a single monitor (gnome-control-center/displays). I can manually suspend the laptop e.g. systemctl suspend but closing the lid does not work. When using nouveau instead of the proprietary nvidia driver, the inhibit does not exist and the laptop is suspended when closing the lid. Does somebody have an idea how to overcome this problem with the proprietary nvidia driver, or which package might be responsible to report the bug ? Thanks, Götz P.S.: systemd-inhibit --list ... Who: x (x PID 5616/gnome-settings-) What: handle-lid-switch Why: Multiple displays attached Mode: block ... ps: 5616 0.0 0.4 886100 35200 ?Sl 20:52 0:00 \_ /usr/lib/gnome-settings-daemon/gnome-settings-daemon xrandr: Screen 0: minimum 8 x 8, current 2880 x 1800, maximum 16384 x 16384 DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) HDMI-0 disconnected (normal left inverted right x axis y axis) DP-2 connected primary 2880x1800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm 2880x1800 59.99*+ DP-3 disconnected (normal left inverted right x axis y axis) DP-4 disconnected (normal left inverted right x axis y axis) nvidia-driver 343.22-2 (nivida-driver 340.46-5 crashes on suspend) systemd 215-7 gnome-settings-daemon 3.14.2-1 gnome-session 3.14.0-2 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1417639776.6353.2.ca...@cern.ch
gnome-shell background not restored on resume when using the proprietary nvidia driver
Hello, when using the proprietary nvidia driver, the gnome-shell background image is not restored after resume. When using nouveau instead, the background image is correctly restored after a suspend/resume. Does somebody have any idea whether the problem is in the nvidia driver or in gnome-shell to submit a bug report ? Cheers, Götz gnome-shell 3.14.2-1 nvidia-driver 343.22-2 (nivida-driver 340.46-5 crashes on suspend) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1417640664.2280.1.ca...@cern.ch
Re: Debian fork: 'Devuan', Debian without Systemd
On 03/12/14 19:37, Martinx - ジェームズ wrote: Debian/Devuan WILL NEED an `udev` alternative to keep `sysinit-core` working. Perhaps. On the other hand, they might only need an alternative implementation of the user-space glue that makes kdbus work. Devuan will need something like `eudev` to succeed. Conveniently, eudev already exists, has active maintainers, and is readily obtainable in source code form. Anyone willing to embark on a project like Devuan should be perfectly capable of getting it packaged. Jessie isn't Debian. So you say. Others have a different opinion. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547f7bad.6090...@zen.co.uk
Re: Debian fork: 'Devuan', Debian without Systemd
On Wed, 03 Dec 2014 21:50:05 +0100 maderios mader...@gmail.com wrote: On 12/03/2014 08:37 PM, Martinx - ジェームズ wrote: Jessie isn't Debian. Devuan IS (will be) what we know about Debian! Waiting to see Joel joining Devuan... lol I've no problem with systemd (Sid), it works fine). I dont understand why some people complain about systemd. Devuan is not Mint or Ubuntu, I think it has no future and everyone will forget that systemd is new... What about the people who will want to use another init system in Debian then? I mean, Linux is supposed to be about choice, right? Is that still the case here? That's the true question in this debate. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141203221859.2d12442f@MARC-THINKPAD.queenland
Re: udev memory problem when trying to plug a disk with corrupted partition table
Le 02.12.2014 19:27, tv.deb...@googlemail.com a écrit : On 02/12/2014 20:48, berenger.mo...@neutralite.org wrote: [cut] Also, what is EBR (or EPBR, which seems to be some sort of enhanced whatever may be a EBR)? Extended Boot Record on DOS disks ? Where information about extended partition is stored. https://en.wikipedia.org/wiki/Extended_boot_record To fix things, I tried to take a look at testdisk, which was able to find partitions. Lot of them, in facts, included lot of... removed partitions (I did a lot of experiments on that disk before). Plus, I have no idea about how to ask it (testdisk) to fix, apply things? Any document about how to use it? Not the man, I already have read it, and it's plain useless. I think you read French, if not the page is available in English too. I do. http://www.cgsecurity.org/wiki/TestDisk_FR It's from TestDisk author. Hope it helps. It does, thanks. For now, I'll keep that disk in that state, in case informations and testing might be useful to maintainers. I'll try to repair things in few weeks, probably. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1915fb753c0f30e56bf720c82d006...@neutralite.org
Re: boot fails on jessie on Acer Travelmate
Le 03/12/2014 20:45, Simon Hollenbach a écrit : In fact, it seems to me that the disk is not read, but it tries to net boot. Why do you think it tries to boot from a network? Because it is displayed. Again, I don't think filing a bug without any info but it doesn't work will get your problem solved. I am not able to find the bug myself. I am ready to spend hours to fix it, but I need the help of someone to tell me where to search... I think we got a differing understanding here. I think you just encountered a bug, or you did something really stupid, which shouldn't happen if you sanely try to install Debian. We got to describe the bug now, so it can be fixed. If some software let its user make someting really stupid, the problem is not with the user but with the software. And after 40 years in computing and a full week in trying to install jessie, I know I can have done someting stupid. But there is too some probability that there is some bug in grub... So, as you say, the point is to well describe it. Now my solution attempt, it worked for me once (but like 3 years ago) # fdisk /dev/sda Thank you, anyway fdisk cannot be used, I must use parted. And I need the solution at long term, I cannot accept a that next aptitude upgrade breaks my boot... -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547f83c9.1060...@couderc.eu
Re: Debian fork: 'Devuan', Debian without Systemd
Hi Madeiros! I'm also using `systemd`, I'm working to use Enlightenment with Wayland (to kick Xorg off) and, it depends on `systemd`. I just don't think that it is wise to put all of our eggs into the same basket. This `systemd` being pushed everywhere looks like a huge monoculture, which is very, very dangerous. Also, ALL my production servers, that are public (Internet faced), uses the GRSecurity Linux Patch, and `systemd` doesn't work with it. So, right now, `systemd` only makes sense at Desktops. And I mean it. So, my job/company depends on `sysvinit-core` / `upstart` and there is no plans to use `systemd` at our servers (and I'm talking about hundreds of Linux instances, physical servers and virtual machines). Cheers! On 3 December 2014 at 18:50, maderios mader...@gmail.com wrote: On 12/03/2014 08:37 PM, Martinx - ジェームズ wrote: Jessie isn't Debian. Devuan IS (will be) what we know about Debian! Waiting to see Joel joining Devuan... lol I've no problem with systemd (Sid), it works fine). I dont understand why some people complain about systemd. Devuan is not Mint or Ubuntu, I think it has no future and everyone will forget that systemd is new... -- Maderios -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547f777d.7040...@gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAJSM8J29rBBb_8nwYDt=bqwj0n5x9gyrkypngqnccu-mh63...@mail.gmail.com
Re: gnome-shell background not restored on resume when using the proprietary nvidia driver
Hi I can at least confirm the problem. There seems to be already a bug report for gnome-shell https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765436 I submitted a bug-report myself which I most probably will close as it is a duplication of the above report. On Wed, 2014-12-03 at 22:04 +0100, Goetz Gaycken wrote: Hello, when using the proprietary nvidia driver, the gnome-shell background image is not restored after resume. When using nouveau instead, the background image is correctly restored after a suspend/resume. Does somebody have any idea whether the problem is in the nvidia driver or in gnome-shell to submit a bug report ? Cheers, Götz gnome-shell 3.14.2-1 nvidia-driver 343.22-2 (nivida-driver 340.46-5 crashes on suspend) signature.asc Description: This is a digitally signed message part
Re: Debian fork: 'Devuan', Debian without Systemd
On 3 December 2014 at 19:18, Märk Owen markowen2...@gmail.com wrote: On Wed, 03 Dec 2014 21:50:05 +0100 maderios mader...@gmail.com wrote: On 12/03/2014 08:37 PM, Martinx - ジェームズ wrote: Jessie isn't Debian. Devuan IS (will be) what we know about Debian! Waiting to see Joel joining Devuan... lol I've no problem with systemd (Sid), it works fine). I dont understand why some people complain about systemd. Devuan is not Mint or Ubuntu, I think it has no future and everyone will forget that systemd is new... What about the people who will want to use another init system in Debian then? I mean, Linux is supposed to be about choice, right? Is that still the case here? That's the true question in this debate. BTW, I just mentioned a valid example: I'm using `GRSecurity` with Debian in prod and it doesn't work with `systemd`. I NEED `sysvinit-core` (or upstart) and there is no plans to deploy `systemd` at my company's public data center. Since it [systemd] doesn't work here. If `systemd` gets fixed (to work with `GRSecurity`), then, I'll give it a second try. Otherwise, I'll need to move to Devuan... Lennart do not care about that: https://bugs.freedesktop.org/show_bug.cgi?id=65575 - How bad is that? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cajsm8j0kdtbhxz5xqpr-dtzeo8eoz9wjzkw_r1w1ry5htkw...@mail.gmail.com
Re: Haven't seen this ssh output before
Le 27.11.2014 00:04, Harry Putnam a écrit : Harry Putnam rea...@newsguy.com writes: I'm not at all clear on how one would go about making an adjustment in sshd_config to allow the algs used by my REMOTE-sol to be recognized. REMOTE-sol does not appear to be using OpenSSH .. maybe a solaris version of SSH. In light of the comments above; if you have any more info on this and have the time... please post. I managed to get a bit of a solution after careful study of the error output and man sshd_config (Largely from being guided by your post) It shows the default kex algorithems and the possible kex alg. I thought of just adding one that matched the list of my clients available choices to sshd_config on REMOTE-deb like so: KexAlgorithms diffie-hellman-group-exchange-sha1 Then restart sshd. That works, but I was afraid that might mean the defaults would be dropped and only `diffie-hellman-group-exchange-sha1' would be offered. I was afraid that might cause failure on some other hosts. Thanks for sharing the solution, one might needs it someday, especially considering the fact you are using the future debian stable. Any opinions on what I may have created? I'm not a security guy (not even a sysadmin, just a dev, but I am feeling concerned with security of computers anyway...), not that I do not want to learn about it, but it's a very complex thing. But, since you seem to be afraid of security holes, I would like to point to a package I have discovered recently (in a search about netBSD good points, the author was saying that a tool listing CVEs of packages you are trying to install was lacking on other systems, and made an edit because someone gave him this tool's name for Debian): debsecan. This is a tool which lists CVE (Common Vulnerabilities and Exposures) that the packages you installed contains. I think you might get some hints if you make a diff between the old (you said you have un-upgraded systems) and the new (the system which gaves you problems) systems. Now, I can't find any CVE with it on (one of) my computer, which have only openSSH's client installed, so it might not help you. Security is a really complex thing, that I do not understand a lot so the problem might not be caused by any CVE of openSSH itself, but, AFAIK, openSSH is using libssl, which is, according to aptitude: a part of openSSL's implementation for SSL, and with this command: $ debsecan |grep ssl -i I have 2 CVEs (no idea if they apply to you btw): CVE-2014-3566 libssl1.0.0 (remotely exploitable, medium urgency) CVE-2014-3566 openssl (remotely exploitable, medium urgency) Maybe your updated machine have fixed one of them? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/3fec1ace9e30ca3b41723bbc1acb2...@neutralite.org
Re: Debian fork: 'Devuan', Debian without Systemd
On 03/12/14 21:52, Martinx - ジェームズ wrote: I'm using `GRSecurity` with Debian in prod and it doesn't work with `systemd`. I NEED `sysvinit-core` (or upstart) and there is no plans to deploy `systemd` at my company's public data center. Since it [systemd] doesn't work here. If `systemd` gets fixed (to work with `GRSecurity`), then, I'll give it a second try. Otherwise, I'll need to move to Devuan... Lennart do not care about that: https://bugs.freedesktop.org/show_bug.cgi?id=65575 - How bad is that? A cursory search using duckduckgo with the search terms: +grsecurity +systemd leads me, directly and indirectly, to information on various web sites associated with Arch Linux, Gentoo, and grsecurity which lead me to believe that it is possible to work around the problem described in that bug report without completely disabling CONFIG_GRKERNSEC_PROC. (Of course, I recognize that in any given situation, it may not be acceptable to make the necessary configuration changes.) That said, I don't see a problem with Lennart's position in that bug report anyway. Well, this sounds useful, but I don't see how we can support this, we need access to the PID directory of the sender of messages, to collect metadata, there's really no way around it. seems like a perfectly reasonable explanation for things not working-as-intended on systems where that access is not available. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547f9a90.5080...@zen.co.uk
Re: Replacing systemd in Jessie
On Tue, 02 Dec 2014, berenger.mo...@neutralite.org wrote: Le 02.12.2014 08:05, Patrick Bartek a écrit : and more and more developers will start writing apps with systemd, or parts of it, as a dependency for the features it offers. It's their choice - likewise it's your choice *not* to write alternatives. It 'sounds' like you're proposing a regime where those that produce have their freedom of choice constrained by users. I struggle to find a rationale that makes that reasonable or likely to do anything other than destroy, given that the user has a choice. User's do contrain. They even dictate. Always have. Developers should, if they are samrt, be developing what customers want or need. Not the other way around. That's the formula for going out of business. Listening to your customers as well as your potential customers is just good business. Really? Tss... How many projects have you, as a user, constrained to do something? Being commercial or not... I don't know. Is filing a bug report and having the developer fix it a constraint on the software? If I fix the bug myself? Is that? It does ultimately STOP the problem the bug was causing whether I do it myself or not. The constraining, the stopping, of something is not always a bad thing. We are constrained in our lives as well as in our work by a multitude of factors. Sometimes, it's good; other time not. That's life. You may had some success in commercial softwares, because of contracts, but for small projects, or projects were the developpers are not paid, when they only contribute because they wan't to use it, but without having to suffer some bug or another, or with a feature they would like to have, I sincerely doubt you had constrained anyone. Most of my contributions to software development as a user, not a developer, have been with projects that only involved one or two coders/developers whom you could contact directly, personally. One of those projects ultimately became the Opera browser. But I've done little of that since moving to Linux 15 years ago. Don't have the patience anymore. Or the time. Honestly... if you want to constrain people on their spare time, if you want to remove us the last part of fun we can have in programming, then... well, people wont listen you, to stay polite. And it's normal. See above about life's constraints. Open source developpers are not all paid for what they do. Only a minority is, and in this minority, I am not sure that the bigger part actually live from open source softwares. If you're not making money from your Open Source, then you have to have income from somewhere else. Else how would you live? From the kindness of strangers, perhaps? [snip] Oh. And, you forgot something. FOSS developpers are the users of their work, unlike in commercial softwares. And it changes *a lot* of things, if not everything. I didn't forget. I once wrote a very specialize file manager just for me to satisfy some peculiar requirements I had at the time. It was of little use to a general user. Never distributed it. No feedback. Fixed the bugs myself. Etc. But if you put your code/project (FOSS or otherwise) out there expect feedback from others. We're a talky bunch. And listen to them. You may get some very good ideas and solutions for improvements. It may even change the direction of the entire project turning something that initially was just a pet project, a hobby, into something that many would benefit from. B -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141203154944.07020...@debian7.boseck208.net
Re: Debian fork: 'Devuan', Debian without Systemd
On 3 December 2014 at 21:19, Martin Read zen75...@zen.co.uk wrote: On 03/12/14 21:52, Martinx - ジェームズ wrote: I'm using `GRSecurity` with Debian in prod and it doesn't work with `systemd`. I NEED `sysvinit-core` (or upstart) and there is no plans to deploy `systemd` at my company's public data center. Since it [systemd] doesn't work here. If `systemd` gets fixed (to work with `GRSecurity`), then, I'll give it a second try. Otherwise, I'll need to move to Devuan... Lennart do not care about that: https://bugs.freedesktop.org/show_bug.cgi?id=65575 - How bad is that? A cursory search using duckduckgo with the search terms: +grsecurity +systemd leads me, directly and indirectly, to information on various web sites associated with Arch Linux, Gentoo, and grsecurity which lead me to believe that it is possible to work around the problem described in that bug report without completely disabling CONFIG_GRKERNSEC_PROC. (Of course, I recognize that in any given situation, it may not be acceptable to make the necessary configuration changes.) That said, I don't see a problem with Lennart's position in that bug report anyway. Well, this sounds useful, but I don't see how we can support this, we need access to the PID directory of the sender of messages, to collect metadata, there's really no way around it. seems like a perfectly reasonable explanation for things not working-as-intended on systems where that access is not available. Thanks for this feedback!! I tried it but, then, I wasn't with enough time to debug it... Since it was working before, I just replaced systemd by sysvinit and forgot about it... Best! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAJSM8J2dXE=S9+qjPrG=u67dnath+0+tovod3de5srppg3b...@mail.gmail.com
Re: Debian fork: 'Devuan', Debian without Systemd
On 12/03/2014 04:18 PM, Märk Owen wrote: On Wed, 03 Dec 2014 21:50:05 +0100 maderios mader...@gmail.com wrote: On 12/03/2014 08:37 PM, Martinx - ジェームズ wrote: Jessie isn't Debian. Devuan IS (will be) what we know about Debian! Waiting to see Joel joining Devuan... lol I've no problem with systemd (Sid), it works fine). I dont understand why some people complain about systemd. Devuan is not Mint or Ubuntu, I think it has no future and everyone will forget that systemd is new... What about the people who will want to use another init system in Debian then? I mean, Linux is supposed to be about choice, right? Right, it IS about choice ...by those who do the choosing. :) Ric -- My father, Victor Moore (Vic) used to say: There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome. R.I.P. Dad. Linux user# 44256 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/547fb386.6050...@gmail.com
tgif thumbnailers not working
Hi, I have been trying unsuccessfully to convince Nautilus to display thumbnails of tgif (*.obj) files. I repeated the steps given in Romano's blog: http://rlog.rgtti.com/2011/11/24/xfig-thumbnailers-with-gnome3nautilus3/ and created files: /usr/bin/tgif-thumbnail (with executing permission) and /usr/share/thumbnailers/tgif.thumbnailer -- their contents is below. The xdg-mime confirms that the type of *.obj files is application/x-tgif. In gconf-editor I can see that /desktop/gnome/thumbnailers/application@x-tgif/command is set to /usr/bin/tgif-thumbnailer -s %s %u %u and /desktop/gnome/thumbnailers/application@x-tgif/enable is checked. Calling tgif-thumbnailer manually: tgif-thumbnailer -s 128 file://myfile.obj myfile.png produces a little PNG image in the current directory. But still no thumbnails, only generic icons in Nautilus. Does anybody have a suggestion what else should I do? Thanks for your time and help! Tad /usr/bin/tgif-thumbnailer #/!bin/sh # The script will be called with parameters : -s %s %u %o # %i: input file, %o: output file, %s: size size=128 if [ $1 = -s ]; then shift size=$1 shift fi dir=/tmp/ infile=$1 # use the magic of POSIX variables infile=${infile#file://*} tmppng=$dir${infile%.*}.png outfile=$2 # remove file if something strange happens trap 'rm -rf $tmppng' INT EXIT TERM die() { echo 2 $@ rm -rf $tmppng exit 1 } tgif -print -quiet -png -color -o/tmp $infile || die tgif failed convert $tmppng -resize $size -sharpen 3 \ $outfile || die convert failed rm -rf $tmppng exit 0 /usr/share/thumbnailers/tgif.thumbnailer -- [Thumbnailer Entry] TryExec=/usr/bin/tgif-thumbnailer Exec=/usr/bin/tgif-thumbnailer -s 128 %u %o MimeType=application/x-tgif; -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e2cb61cacd6ecc46a6fbd0296822a2376d202...@hirt.ad.uws.edu.au