Re: Acentos ñ en xfce
El 2021-06-15 a las 23:59 +, Ricardo Delgado escribió: > El problema es el siguiente, cuando recibo archivos (via OWNCLOUD, correo, > copia por algun soporte (pendrive, cd, dvd, etc) al pasar los archivos a mi > notebook (corriendo DEBIAN estable con XFCE) los mismos tienen problemas para > copiar todo archivo que tenga ACENTO, EÑE. > > En primer lugar necesitaria RENOMBRAR todos los archivos y que respeten el > formato original (sea Ñ o acento) > > Particularmente cuando SINCRONIZO, desde OWNCLOUD. (...) ¿Y qué mensaje de error recibes cuando intentas copiar esos archivos? Yo empezaría probando con algo sencillo (crear un archivo de texto y nombrarlo con acentos y eñes, copiarlo a un directorio). Desde una terminal: sm01@stt008:~$ echo 'prueba roñosa' > $HOME/Escritorio/áéñ.txt sm01@stt008:~$ cat $HOME/Escritorio/áéñ.txt prueba sm01@stt008:~$ cp $HOME/Escritorio/áéñ.txt $HOME A ver si se queja. Saludos, -- Camaleón
Re: upgrade to testing
On Tue, Jun 15, 2021 at 06:03:20PM +, Andrew M.A. Cater wrote: On Tue, Jun 15, 2021 at 05:26:29PM +, Wil wrote: How do I upgrade from Debian stable to Debain testing? Hi Wil, Don't - at least not directly. If your /etc/apt/sources.list says "stable" anywhere in it, you probably want to change that to reference "buster" today, anyway. Bullseye - Debian 11 - is likely to be released within 8 weeks and will become the new "stable" immediately - at whihc point, there will be a huge amount of package churn. If you want to update to what is _currently_ Debian testing - now is a relatively safe time to do so because it's in a state of freeze before it is released as Debian 11. Look at the release notes for Bullseye and the posts on Debian Planet for "what's new in Bullseye" and update carefully. [Change /etc/apt/sources.list to suit: apt-get update ; apt-get upgrade ; apt-get autoremove ; apt-get dist-upgrade ; apt-get autoremove is one sequence that will get you there. if you want to upgrade to what will be the new Testing, I'd honestly suggest waiting six weeks or so, upgrading to Bullseye as it comes out and _then_ upgrading to Bookworm. There's information on Debian codenames and also "Which Debian distribution should I use" on the Debian wiki at wiki.debian.org. In general terms: if you can't handle breakage, which may occasionally last for weeks or months, don't run Testing until you are happy troubleshooting and dealing with upgrading/holding versions of packages. The package churn on testing is correspondingly higher and there is no particular security support. Just my €0.02 All the best, as ever Andy C Thank you for all that you wrote. I will change the sources.list to use "bullseye" and then run "apt-get update ; apt-get upgrade; apt-get autoremove ; apt-get dist-upgrade ; apt-get autoremove". After doing so the system will be on current Debian testing and it will become Debian stable within a few weeks. After that the system will remain on Debian stable and not become Debian testing, correct? Wil signature.asc Description: PGP signature
Re: Preserving locally modified configuration files - Dpkg::Options --force-confdef & --force-confold not working on command line
On Tue, Jun 15, 2021 at 4:22 PM Brian wrote: > On Tue 15 Jun 2021 at 14:34:12 +0530, Jaikumar Sharma wrote: > I wonder whether using dpkg-divert(1) would help in preserving your > modified file? > > Yes, this option was intentionally avoided by me because of scripting the maintainer scripts. I only have the option to use this now. Thanks Brian :) -- Jaikumar
Re: upgrade to testing
On 6/16/21 1:56 AM, Gary Dale wrote: On 2021-06-15 13:26, Wil wrote: How do I upgrade from Debian stable to Debain testing? It's not really an upgrade. It's more a switch in priorities. However to answer your question directly, as root do either sed -i -s 's/buster/bullseye/g' /etc/apt/sources.list or sed -i -s 's/stable/testing/g' /etc/apt/sources.list depending on how your source.list file refers to the current stable distribution. After that, do apt update apt full-upgrade apt autoremove then reboot. I like this way, it easier and i don't need to open file and change it manually. -- Robbi Nespu D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA https://robbinespu.gitlab.io | https://mstdn.social/@robbinespu
Re: [jo...@debian.org: Debian Presence on Freenode]
On 6/16/21 9:11 AM, Steve McIntyre wrote: Forwaring for information... - Forwarded message from Joerg Jaspert - From: Joerg Jaspert To: debian-devel-annou...@lists.debian.org Date: Tue, 15 Jun 2021 18:44:28 +0200 Subject: Debian Presence on Freenode Hello everyone, as you may know, Debians official IRC presence moved from Freenode to OFTC 15 years ago. Freenode still had a lively community of users remaining and the #debian channel was pretty active too. As of today, this is no longer true. Debians IRC presence continues to be on OFTC and we have a nice growing community on the new Libera.Chat network, but anything on Freenode is neither official Debian supported nor endorsed. Quite the contrary, we urge anyone to drop their connections to freenode and join us in safer, more trustworthy places. Anything on Freenode that looks like Debian is to be considered unofficial, not supported and generally hostile. For those not closely following the events that lead us to this: A hostile takeover with an entirely new set of staff, most of which we would not accept as members in Debian, happened. Over the last weeks they have acted irrationally taking over many other communities channels and groups. Today that new staff made it worse and decided to drop *all* nick and channel registrations, forcibly taking control over many of those "in their new part of freenode". So, again: You are best of disconnecting from Freenode, if you haven't already, and join us on OFTC or Libera. For the new Libera.Chat network, we established a group registration and will also hand out Debian cloaks to members again. Please open an issue in our new Salsa project, if you want one: https://salsa.debian.org/debian-irc-team/libera-cloak (Please be patient, we will group them together and try not overwhelming Libera Staff with too many small requests). Many thanks to the #debian ops team who have spent the last 3 weeks setting up channels on irc.libera.chat and walking on eggshells trying to siphon off users from freenode to safer places while avoiding getting k:lined by the new staff of freenode for doing so. Most of them aren't DDs but spend huge numbers of hours looking after our community for us. I am not DD or DM but do Debian user are eligible to claim this cloak? -- Robbi Nespu D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA https://robbinespu.gitlab.io | https://mstdn.social/@robbinespu
Re: [jo...@debian.org: Debian Presence on Freenode]
On 2021-06-15 at 22:07, Greg Wooledge wrote: > On Tue, Jun 15, 2021 at 09:53:09PM -0400, Polyna-Maude Racicot-Summerside > wrote: > >> I was sure to have seen something about a new software going to be >> implemented when I read thru the different post regarding the action >> done by "Korean King" & friends + Christelle. Something about a new IRC >> daemon being in testing and soon release... >> >> Must have been a mistake from myself. > > I don't recognize all of those names, but let's see. I looked on > the libera.chat web site first, but they don't mention the server > software there, at least not in a place I could find. > > So, I connected, and then scrolled back to see the announcements: > > 22:05 Your host is silver.libera.chat[172.106.11.86/6697], running version > solanum-1.0-dev > > I'm not really familiar with IRC server software, but "apt-cache search > solanum" in bullseye turns up nothing. So it might not be packaged > in Debian. *shrug* https://github.com/solanum-ircd/solanum, probably. See also https://lists.debian.org/debian-user/2021/05/msg00877.html, in which you yourself apparently participated. It's also mentioned in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981009, which indicates that there are people working to package it - but as this was already well after the soft freeze (it was January/February) and we're about to hit the hard freeze before long, it's clearly not going to make the upcoming stable release. -- 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: [jo...@debian.org: Debian Presence on Freenode]
On Tue, Jun 15, 2021 at 09:53:09PM -0400, Polyna-Maude Racicot-Summerside wrote: > I was sure to have seen something about a new software going to be > implemented when I read thru the different post regarding the action > done by "Korean King" & friends + Christelle. Something about a new IRC > daemon being in testing and soon release... > > Must have been a mistake from myself. I don't recognize all of those names, but let's see. I looked on the libera.chat web site first, but they don't mention the server software there, at least not in a place I could find. So, I connected, and then scrolled back to see the announcements: 22:05 Your host is silver.libera.chat[172.106.11.86/6697], running version solanum-1.0-dev I'm not really familiar with IRC server software, but "apt-cache search solanum" in bullseye turns up nothing. So it might not be packaged in Debian. *shrug*
Re: [jo...@debian.org: Debian Presence on Freenode]
Hi, On 2021-06-15 9:27 p.m., The Wanderer wrote: > On 2021-06-15 at 21:15, Polyna-Maude Racicot-Summerside wrote: > >> Hi, >> Does the new IRC server used by Libra.chat will include a version >> release as Debian package ? > > ...huh? > > Do you have a reason to believe that libra.chat is using new software, > not already in use on other IRC servers, such as Freenode? > > If it is, I haven't heard about it - and I've been hearing about this > Freenode meltdown situation from my brother, who's very active on IRC, > for weeks now. > Maybe I had a bad understanding. I was sure to have seen something about a new software going to be implemented when I read thru the different post regarding the action done by "Korean King" & friends + Christelle. Something about a new IRC daemon being in testing and soon release... Must have been a mistake from myself. -- Polyna-Maude R.-Summerside -Be smart, Be wise, Support opensource development OpenPGP_signature Description: OpenPGP digital signature
Re: [jo...@debian.org: Debian Presence on Freenode]
On 2021-06-15 at 21:15, Polyna-Maude Racicot-Summerside wrote: > Hi, > Does the new IRC server used by Libra.chat will include a version > release as Debian package ? ...huh? Do you have a reason to believe that libra.chat is using new software, not already in use on other IRC servers, such as Freenode? If it is, I haven't heard about it - and I've been hearing about this Freenode meltdown situation from my brother, who's very active on IRC, for weeks now. -- 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: [jo...@debian.org: Debian Presence on Freenode]
Hi, Does the new IRC server used by Libra.chat will include a version release as Debian package ? On 2021-06-15 9:11 p.m., Steve McIntyre wrote: > Forwaring for information... > > - Forwarded message from Joerg Jaspert - > > From: Joerg Jaspert > To: debian-devel-annou...@lists.debian.org > Date: Tue, 15 Jun 2021 18:44:28 +0200 > Subject: Debian Presence on Freenode > > Hello everyone, > > as you may know, Debians official IRC presence moved from Freenode to > OFTC 15 years ago. Freenode still had a lively community of users > remaining and the #debian channel was pretty active too. > > As of today, this is no longer true. Debians IRC presence continues to > be on OFTC and we have a nice growing community on the new Libera.Chat > network, but anything on Freenode is neither official Debian supported > nor endorsed. Quite the contrary, we urge anyone to drop their > connections to freenode and join us in safer, more trustworthy places. > Anything on Freenode that looks like Debian is to be considered > unofficial, not supported and generally hostile. > > For those not closely following the events that lead us to this: A > hostile takeover with an entirely new set of staff, most of which we > would not accept as members in Debian, happened. Over the last weeks > they have acted irrationally taking over many other communities channels > and groups. Today that new staff made it worse and decided to drop *all* > nick and channel registrations, forcibly taking control over many of > those "in their new part of freenode". > > So, again: You are best of disconnecting from Freenode, if you haven't > already, and join us on OFTC or Libera. > > > For the new Libera.Chat network, we established a group registration and > will also hand out Debian cloaks to members again. Please open an issue > in our new Salsa project, if you want one: > > https://salsa.debian.org/debian-irc-team/libera-cloak > > (Please be patient, we will group them together and try not overwhelming > Libera Staff with too many small requests). > > > Many thanks to the #debian ops team who have spent the last 3 weeks > setting up channels on irc.libera.chat and walking on eggshells trying > to siphon off users from freenode to safer places while avoiding getting > k:lined by the new staff of freenode for doing so. Most of them aren't > DDs but spend huge numbers of hours looking after our community for us. > -- Polyna-Maude R.-Summerside -Be smart, Be wise, Support opensource development OpenPGP_signature Description: OpenPGP digital signature
[jo...@debian.org: Debian Presence on Freenode]
Forwaring for information... - Forwarded message from Joerg Jaspert - From: Joerg Jaspert To: debian-devel-annou...@lists.debian.org Date: Tue, 15 Jun 2021 18:44:28 +0200 Subject: Debian Presence on Freenode Hello everyone, as you may know, Debians official IRC presence moved from Freenode to OFTC 15 years ago. Freenode still had a lively community of users remaining and the #debian channel was pretty active too. As of today, this is no longer true. Debians IRC presence continues to be on OFTC and we have a nice growing community on the new Libera.Chat network, but anything on Freenode is neither official Debian supported nor endorsed. Quite the contrary, we urge anyone to drop their connections to freenode and join us in safer, more trustworthy places. Anything on Freenode that looks like Debian is to be considered unofficial, not supported and generally hostile. For those not closely following the events that lead us to this: A hostile takeover with an entirely new set of staff, most of which we would not accept as members in Debian, happened. Over the last weeks they have acted irrationally taking over many other communities channels and groups. Today that new staff made it worse and decided to drop *all* nick and channel registrations, forcibly taking control over many of those "in their new part of freenode". So, again: You are best of disconnecting from Freenode, if you haven't already, and join us on OFTC or Libera. For the new Libera.Chat network, we established a group registration and will also hand out Debian cloaks to members again. Please open an issue in our new Salsa project, if you want one: https://salsa.debian.org/debian-irc-team/libera-cloak (Please be patient, we will group them together and try not overwhelming Libera Staff with too many small requests). Many thanks to the #debian ops team who have spent the last 3 weeks setting up channels on irc.libera.chat and walking on eggshells trying to siphon off users from freenode to safer places while avoiding getting k:lined by the new staff of freenode for doing so. Most of them aren't DDs but spend huge numbers of hours looking after our community for us. -- bye, Joerg - End forwarded message - -- Steve McIntyre, Cambridge, UK.st...@einval.com "Since phone messaging became popular, the young generation has lost the ability to read or write anything that is longer than one hundred and sixty characters." -- Ignatios Souvatzis
Re: Acentos ñ en xfce
Hola a todos, Gracias por las respuestas; si efectivamente no fue claro mi correo anterior. El problema es el siguiente, cuando recibo archivos (via OWNCLOUD, correo, copia por algun soporte (pendrive, cd, dvd, etc) al pasar los archivos a mi notebook (corriendo DEBIAN estable con XFCE) los mismos tienen problemas para copiar todo archivo que tenga ACENTO, EÑE. En primer lugar necesitaria RENOMBRAR todos los archivos y que respeten el formato original (sea Ñ o acento) Particularmente cuando SINCRONIZO, desde OWNCLOUD. NO ES UN PROBLEMA de TECLADO. Es decir, como solucionar COPIAR/SINCRONIZAR archivos que tengan Ñ o acento. sin tener que recurrir a algun comando que realice la conversion de archivos. como dije mis LOCALES son LANG=es_AR.UTF-8 LANGUAGE= LC_CTYPE="es_AR.UTF-8" LC_NUMERIC="es_AR.UTF-8" LC_TIME="es_AR.UTF-8" LC_COLLATE="es_AR.UTF-8" LC_MONETARY="es_AR.UTF-8" LC_MESSAGES="es_AR.UTF-8" LC_PAPER="es_AR.UTF-8" LC_NAME="es_AR.UTF-8" LC_ADDRESS="es_AR.UTF-8" LC_TELEPHONE="es_AR.UTF-8" LC_MEASUREMENT="es_AR.UTF-8" LC_IDENTIFICATION="es_AR.UTF-8" LC_ALL= Espero que esta vea se entienda mejor Muchas Gracias El martes, 15 de junio de 2021 12:49:34 ART, Galvatorix Torixgalva escribió: Hola, al igual que otros compañeros de la lista, yo no termino de ver claro cual es el problema que tienes. He creido entender que tienes algun problema de configuracion en el keymap. Creo que lo mejor es que indiques directamente que problema te da. Un saludo
Maquina não carrega ambiente gráfico somente recovery mode
Boa noite, Sou iniciante com o Linux e acabei instalando a ultima versão 10.9.0 64 bits em um notebook para estudos e apesar da instalação ter transcorrido de forma normal o sistema inicia o carregamento do Debian após o GNU e aparentemente na hora de mostrar a tela do sistema gráfico ele hiberna e não sai mais da hibernação. Pelo modo recovery mode consigo acessar o terminal mas obviamente sem nada da parte gráfica. Agradeço se alguém puder me ajudar. Dados da maquina: CPU: AMD Turion (tm) Dual Core Mobile RM-70 CPU Speed: 2.0 GHz Hard Disk Drive: Hitachi HTS542520K9SA00 (S1) Optical Drive: TSSTcorp TS-L633P Total Memory: 3072 MB System Bios version: 1.2 Fico no aguardo. Cordialmente, Alessandro
Re: upgrade to testing
On 2021-06-15 13:26, Wil wrote: How do I upgrade from Debian stable to Debain testing? It's not really an upgrade. It's more a switch in priorities. However to answer your question directly, as root do either sed -i -s 's/buster/bullseye/g' /etc/apt/sources.list or sed -i -s 's/stable/testing/g' /etc/apt/sources.list depending on how your source.list file refers to the current stable distribution. After that, do apt update apt full-upgrade apt autoremove then reboot.
Re: upgrade to testing
On Tue, Jun 15, 2021 at 06:20:09PM -0400, Paul M. Foster wrote: > A lot of the people here don't have to look up the answer; > they know it already. And as demonstrated, the answer isn't that difficult > to express. At least two people have given a *wrong* answer in this thread.
Re: upgrade to testing
On 6/15/21 6:08 PM, Francisco M Neto wrote: Honestly worth a lot more. There are a lot of people that are not that familiar with Debian, and sometimes it's comprehensible that they don't look for search engines right away; a lot of times the answers that come up on a search apply to derivatives. Ubuntu is so ubiquitous these days that I've seen plenty of people that just follow instructions meant for it, but under Debian. So it's (from a certain point of view) comendable that they come to this list instead. After all this is _the_ Debian User Group; and it's sad that sometimes they are met with less-than-tolerant responses. Although I can completely understand (and to some extent, relate to) the way some people feel when a discussion list is sometimes treated as a support desk, a more welcoming response is more likely to create a more conscientious Debian user. That was MY €0.02. I must concur. I understand sending people away to research things on debian.org. But consider: googling across the internet's trillions of documents to find an answer, or filtering through the abundance of documentation on debian.org... it's a helluva lot easier to just ask the question here. A lot of the people here don't have to look up the answer; they know it already. And as demonstrated, the answer isn't that difficult to express. I've been using Debian from probably 20 years now. I'm just advocating for some more tolerance. Paul
Re: upgrade to testing
Hey there, I don't want to just add a meme here, but someone give this man a medal. On 2021-06-15 18:03, Andrew M.A. Cater wrote: > > If you want to update to what is _currently_ Debian testing - now is a > relatively safe time to do so because it's in a state of freeze before it > is released as Debian 11. Look at the release notes for Bullseye and the > posts on Debian Planet for "what's new in Bullseye" and update carefully. > [Change /etc/apt/sources.list to suit: apt-get update ; apt-get upgrade ; > apt-get autoremove ; apt-get dist-upgrade ; apt-get autoremove is one > sequence that will get you there. > > if you want to upgrade to what will be the new Testing, I'd honestly suggest > waiting six weeks or so, upgrading to Bullseye as it comes out and _then_ > upgrading to Bookworm. The above is the best advice anyone could get in regards to upgrading to testing or not. > Just my €0.02 Honestly worth a lot more. There are a lot of people that are not that familiar with Debian, and sometimes it's comprehensible that they don't look for search engines right away; a lot of times the answers that come up on a search apply to derivatives. Ubuntu is so ubiquitous these days that I've seen plenty of people that just follow instructions meant for it, but under Debian. So it's (from a certain point of view) comendable that they come to this list instead. After all this is _the_ Debian User Group; and it's sad that sometimes they are met with less-than-tolerant responses. Although I can completely understand (and to some extent, relate to) the way some people feel when a discussion list is sometimes treated as a support desk, a more welcoming response is more likely to create a more conscientious Debian user. That was MY €0.02. Cheers, Francisco signature.asc Description: PGP signature
Re: Plantages Xorg (i915, context reset due to GPU hang)
Bonjour Daniel, Daniel Caillibaud, on 2021-06-15: > Le 14/06/21 à 13:25, Daniel Caillibaud a écrit : > > Je teste ça et je vous dis dans qq j si ça a réglé le pb. > > Caramba encore raté :'-( > > ça tient 4~5h : > > Jun 14 19:43:01 dell kernel: [22501.752663] i915 :00:02.0: [drm] > Resetting rcs0 for preemption time out > Jun 14 19:43:01 dell kernel: [22501.752684] i915 :00:02.0: [drm] > Xorg[1988] context reset due to GPU hang > Jun 14 19:43:01 dell kernel: [22501.763575] i915 :00:02.0: [drm] GPU > HANG: ecode 11:1:86dd, in Xorg [1988] > > Jun 15 14:11:02 dell kernel: [19659.973156] i915 :00:02.0: [drm] > Resetting rcs0 for preemption time out > Jun 15 14:11:02 dell kernel: [19659.973181] i915 :00:02.0: [drm] > Xorg[2180] context reset due to GPU hang > Jun 15 14:11:02 dell kernel: [19659.980708] i915 :00:02.0: [drm] GPU > HANG: ecode 11:1:86dd, in Xorg [2180] Argh, dommage, bon au moins, ça valait le coup d'essayer… […] > /var/log/Xorg.0.log est vide Ça me surprend, en temps normal il y a toujours beaucoup de verbiage dans les journaux d'Xorg. Il a été remis à zéro, démarré en tant qu'utilisateur (~/.local/share/xorg/Xorg.0.log), ou démarré sur un autre display (Xorg.1.log) ? (Simple curiosité, pas sûr qu'on y retrouve grand chose de neuf.) > Pas encore pris le temps de me replonger dans tous les threads qui causent > de plantages i915, je vais essayer de prendre qq h pour le faire (même si je > ferais probablement mieux de prendre ces heures pour chercher un autre pc > sur le bon coin) Effectivement, quand quelque chose dans le matériel ne suit pas, on peut faire tout ce qu'on veut du côté du logiciel, il y a un moment ou ça finit par coincer. À vous de voir le temps que vous voulez y passer. Certains acharnés ont testé différents réglages du module[1]. Personnellement, je n'ai rien vu de franchement documenté quant à ces options, du coup je me suis gardé de les recommander en premier lieu ; mais qui sait, pour information. [1]: un exemple parmi beaucoup d'autre sur le pilote i915 : https://bbs.archlinux.org/viewtopic.php?pid=1903409#p1903409 Bonne journée, -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/tty1, please excuse my verbosity. signature.asc Description: PGP signature
Re: [HS] Utilisation de fibre dans des rocades inter-étages
Bonjour, Le 18793ième jour après Epoch, Olivier écrivait: > Voici des questions clairement indépendantes de Debian mais qui ne > manqueront pas, je pense, d'intéresser les administrateurs Debian qui > suivent cette liste. Même si ce sont des sujets potentiellement intéressants, j'avoue qu'un admin Debian (ou un simple user) ne se pose pas forcément ces questions. > 6. Conseils ? Suggestions ? Trouver une liste ou un forum plus adapté. Plus sérieusement, il me semble raisonnable de ta part, étant donné le travail de recherche en amont déjà effectué (bravo à toi en tout cas), d'aller trouver des forums plus spécifiquement dédié au câblage et à l'optique. Je te souhaite de trouver ici quelqu'un pouvant te répondre, mais j'en doute un peu. François -- Many pages make a thick book.
Re: xhost-command in Debian11 [solved]
On Tue, Jun 15, 2021 at 10:17:25PM +0200, BerndSchmittNews wrote: > Hello tomas, > > > thanks for your answer. > > On 15.06.21 21:51, to...@tuxteam.de wrote: > >No. It's the su, dropping the DISPLAY environment variable. Try adding > >the option `--whitelist-environment=DISPLAY to your su command > > works like a charm. Glad it helped. See the manual page for pam_env and especially /etc/security/pam_env.conf for a more permanent solution. Cheers - t signature.asc Description: Digital signature
Re: xhost-command in Debian11 [solved]
Hello tomas, thanks for your answer. On 15.06.21 21:51, to...@tuxteam.de wrote: No. It's the su, dropping the DISPLAY environment variable. Try adding the option `--whitelist-environment=DISPLAY to your su command works like a charm. Thank you Bernd
Re: xhost-command in Debian11
On Tue, Jun 15, 2021 at 09:21:10PM +0200, BerndSchmittNews wrote: > Hello. > > I used to use xhost-command and su -l ... -c ... to run programs as a > different user in debian10. In debian11 I get an error about having no > DISPLAY env variable specified. > > Does xhost work different now? No. It's the su, dropping the DISPLAY environment variable. Try adding the option `--whitelist-environment=DISPLAY to your su command (hint: you can add more variables to that whitelist, comma separated). HTH, cheers - t signature.asc Description: Digital signature
Re: upgrade to testing
On Tue 15 Jun 2021 at 17:26:29 +, Wil wrote: > How do I upgrade from Debian stable to Debain testing? Surely you are pulling out legs? You are well aware of the file /etc/apt/sources.list ? Maybe you have something else in mind apart from a ome sentence throwout? Hoping to hear from you. But fingers are not crossed. -- Brian.
xhost-command in Debian11
Hello. I used to use xhost-command and su -l ... -c ... to run programs as a different user in debian10. In debian11 I get an error about having no DISPLAY env variable specified. Does xhost work different now? $ uname -a Linux VB-Deb400 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 GNU/Linux $ xhost local: non-network local connections being added to access control list $ su -l notserious -c firefox Passwort: Error: no DISPLAY environment variable specified robert@VB-Deb400:~$ Thx Bernd
Re: Wiping an unencrypted SSD in preparation for encryption
> But in any case, I'm not sure about booting Grub on an SSD from the > BIOS, because AIUI Grub uses sector addresses to find its core.img, > and AIUI sectors get shuffled around by the SSD controller. That shuffling is purely internal and hence completely invisible (barring bugs and the need to sometimes make sure data is *really* erased), so that's a non-issue. Stefan
Re: upgrade to testing
> > On 6/15/2021 7:26 PM, Wil wrote: > > > How do I upgrade from Debian stable to Debain testing? https://www.debian.org/releases/bullseye/releasenotes https://wiki.debian.org/DebianBullseye https://wiki.debian.org/NewInBullseye
Re: upgrade to testing
On Tue, Jun 15, 2021 at 07:50:05PM +0200, john doe wrote: > On 6/15/2021 7:26 PM, Wil wrote: > > How do I upgrade from Debian stable to Debain testing? > > By following the instructions available on the Debian web site (1)! > > In a nutshell, change 'buster/stable' to 'bullseye/unstable' in > /etc/apt/sources.list'.: Not totally true though. There have been a few changes. So if you just replace buster with bullseye it might not work. Here is an example of an working bullseye sources.list # testing deb http://deb.debian.org/debian/ bullseye main contrib non-free deb-src http://deb.debian.org/debian/ bullseye main contrib non-free deb http://security.debian.org/debian-security bullseye-security main contrib non-free deb-src http://security.debian.org/debian-security bullseye-security main contrib non-free deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free deb-src http://deb.debian.org/debian/ bullseye-updates main contrib non-free > > $ apt-get update && apt-get full-upgrade > > > Note that you can also use 'apt' instead of 'apt-get'. > > Do not do this blindly on a production server though. > > 1) > https://www.debian.org/releases/bullseye/amd64/release-notes/ch-upgrading.en.html > > -- > John Doe > -- Henning Follmann | hfollm...@itcfollmann.com
Re: upgrade to testing
On Tue, Jun 15, 2021 at 05:26:29PM +, Wil wrote: > How do I upgrade from Debian stable to Debain testing? Hi Wil, Don't - at least not directly. If your /etc/apt/sources.list says "stable" anywhere in it, you probably want to change that to reference "buster" today, anyway. Bullseye - Debian 11 - is likely to be released within 8 weeks and will become the new "stable" immediately - at whihc point, there will be a huge amount of package churn. If you want to update to what is _currently_ Debian testing - now is a relatively safe time to do so because it's in a state of freeze before it is released as Debian 11. Look at the release notes for Bullseye and the posts on Debian Planet for "what's new in Bullseye" and update carefully. [Change /etc/apt/sources.list to suit: apt-get update ; apt-get upgrade ; apt-get autoremove ; apt-get dist-upgrade ; apt-get autoremove is one sequence that will get you there. if you want to upgrade to what will be the new Testing, I'd honestly suggest waiting six weeks or so, upgrading to Bullseye as it comes out and _then_ upgrading to Bookworm. There's information on Debian codenames and also "Which Debian distribution should I use" on the Debian wiki at wiki.debian.org. In general terms: if you can't handle breakage, which may occasionally last for weeks or months, don't run Testing until you are happy troubleshooting and dealing with upgrading/holding versions of packages. The package churn on testing is correspondingly higher and there is no particular security support. Just my €0.02 All the best, as ever Andy C
Re: upgrade to testing
On 6/15/2021 7:26 PM, Wil wrote: How do I upgrade from Debian stable to Debain testing? By following the instructions available on the Debian web site (1)! In a nutshell, change 'buster/stable' to 'bullseye/unstable' in /etc/apt/sources.list'.: $ apt-get update && apt-get full-upgrade Note that you can also use 'apt' instead of 'apt-get'. Do not do this blindly on a production server though. 1) https://www.debian.org/releases/bullseye/amd64/release-notes/ch-upgrading.en.html -- John Doe
Re: upgrade to testing
On Tue, 15 Jun 2021 17:26:29 + Wil wrote: > How do I upgrade from Debian stable to Debain testing? The first thing I'd do is some searching on the Internet. https://duckduckgo.com/?q=debian+upgrade+stable+testing=vivaldi=web -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/ pgpdRVTxiwIRP.pgp Description: OpenPGP digital signature
upgrade to testing
How do I upgrade from Debian stable to Debain testing? signature.asc Description: PGP signature
Re: Acentos ñ en xfce
Hola, al igual que otros compañeros de la lista, yo no termino de ver claro cual es el problema que tienes. He creido entender que tienes algun problema de configuracion en el keymap. Creo que lo mejor es que indiques directamente que problema te da. Un saludo
Re: Archiver mails : erratum
On Tuesday 15 June 2021 16:36:49 ajh-valmer wrote: Désolé, info incomplète : Commande d'envoi vers le serveur : rsync -azv /home/user/.trinity/share/apps/kmail/mail/ user@IP-SERVEUR:/home/user/.trinity/share/apps/kmail/mail/ Commande récupération sur mon PC : rsync -avz root@ :/home//.trinity/share/apps/kmail/ /home//.trinity/share/apps/kmail/
Re: Archiver mails
Bonjour, Je suis sous le bureau Kmail Trinity, J'utilise une technique très simple, je centralise mes mails sur un serveur externe, par cette commande sur une seule ligne : rsync -av root@ :/home//.trinity/share/apps/kmail/ /home//.trinity/share/apps/kmail/ Ou que je sois, je peux récupérer d'anciens mails. Hope you like it :-)
Re: HS: postfix relay denied en ipv6
Le 15/06/2021 à 16:16, Stephane Bortzmeyer a écrit : On Tue, Jun 15, 2021 at 03:56:13PM +0200, NoSpam wrote a message of 23 lines which said: Ceci doit être écrit sans les crochets et le masque ne fonctionne pas :( Dans la directive mynetworks, ça marche très bien. Peut être, mais pas lorsque mynetworks = hash:/etc/postfix/allowed-networks. Postfix 3.4.14-0+deb10u1 -- Daniel
Re: HS: postfix relay denied en ipv6
On Tue, Jun 15, 2021 at 03:56:13PM +0200, NoSpam wrote a message of 23 lines which said: > Ceci doit être écrit sans les crochets et le masque ne fonctionne pas :( Dans la directive mynetworks, ça marche très bien.
Re: HS: postfix relay denied en ipv6
La doc postfix n'est pas correcte Le 15/06/2021 à 11:44, NoSpam a écrit : [...] My allowed_network (part of) = 192.168.10.254 ok client.FQDN.hostname ok [2001:db8:b1:932c:212::1] ok [2001:db8:b1:932c:212::1]/128 ok [fd53:ac59:337:8b38::1] ok [fd53:ac59:337:8b38::]/64 ok Ceci doit être écrit sans les crochets et le masque ne fonctionne pas :( 2001:db8:b1:932c:212::1 ok fd53:ac59:337:8b38::1 ok À présent l'envoi en ipv6 est fonctionnel. -- Daniel
Re: Plantages Xorg (i915, context reset due to GPU hang)
Le 14/06/21 à 13:25, Daniel Caillibaud a écrit : > Je teste ça et je vous dis dans qq j si ça a réglé le pb. Caramba encore raté :'-( ça tient 4~5h : Jun 14 19:43:01 dell kernel: [22501.752663] i915 :00:02.0: [drm] Resetting rcs0 for preemption time out Jun 14 19:43:01 dell kernel: [22501.752684] i915 :00:02.0: [drm] Xorg[1988] context reset due to GPU hang Jun 14 19:43:01 dell kernel: [22501.763575] i915 :00:02.0: [drm] GPU HANG: ecode 11:1:86dd, in Xorg [1988] Jun 15 14:11:02 dell kernel: [19659.973156] i915 :00:02.0: [drm] Resetting rcs0 for preemption time out Jun 15 14:11:02 dell kernel: [19659.973181] i915 :00:02.0: [drm] Xorg[2180] context reset due to GPU hang Jun 15 14:11:02 dell kernel: [19659.980708] i915 :00:02.0: [drm] GPU HANG: ecode 11:1:86dd, in Xorg [2180] après un boot un `grep i915 /vl/kern.log` me donne ça Jun 15 14:12:15 dell kernel: [1.325096] i915 :00:02.0: vgaarb: deactivate vga console Jun 15 14:12:15 dell kernel: [1.357265] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Jun 15 14:12:15 dell kernel: [1.357742] i915 :00:02.0: [drm] Finished loading DMC firmware i915/icl_dmc_ver1_09.bin (v1.9) Jun 15 14:12:15 dell kernel: [1.395645] i915 :00:02.0: [drm] GuC firmware i915/icl_guc_49.0.1.bin version 49.0 submission:disabled Jun 15 14:12:15 dell kernel: [1.395649] i915 :00:02.0: [drm] HuC firmware i915/icl_huc_9.0.0.bin version 9.0 authenticated:yes Jun 15 14:12:15 dell kernel: [1.402366] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on minor 0 Jun 15 14:12:15 dell kernel: [1.438734] fbcon: i915drmfb (fb0) is primary device Jun 15 14:12:15 dell kernel: [2.606944] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device Jun 15 14:12:15 dell kernel: [ 12.669407] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) uname -a Linux dell 5.12.9 #2 SMP Wed Jun 9 22:51:28 CEST 2021 x86_64 GNU/Linux /var/log/Xorg.0.log est vide Pas encore pris le temps de me replonger dans tous les threads qui causent de plantages i915, je vais essayer de prendre qq h pour le faire (même si je ferais probablement mieux de prendre ces heures pour chercher un autre pc sur le bon coin) -- Daniel es de porter des lunettes de soleil est quand même un excellent commercial.
Re: Thunderbird problems
On 6/15/21 8:05 AM, Alexander V. Makartsev wrote: On 15.06.2021 06:46, Robbi Nespu wrote: On 6/15/21 6:24 AM, Frank McCormick wrote: ... I didn't had any issues with Thunderbird before and after update. It works normally as usual. I think, the root cause for this issue could be elsewhere. I would suspect "libc" version difference in Bullseye, or something else. Actually, +1 on this observation, for 1.78.11.0-1 not working on two Bullseye installs. Strangely, my personal gmail won't log in, but my university's mail -- managed by google -- does... Cheers! -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀https://www.debian.org ⠈⠳⣄
Re: Archiver mails
Le 15/06/21 à 08:36, Gabriel Moreau a
écrit :
> > ./backup-mailboxes.py && (find Mail -type f -ctime +90 | xargs gzip --best)
> >
>
> Amélioration possible
>
> xargs -r gzip --best
>
> J'utilise toujours avec -r xargs...
Sans xargs ça doit marcher aussi (à priori jamais besoin de xargs derrière un
find, sauf pour
des cas auxquels je n'ai jamais été confronté)
find Mail -type f -ctime +90 -exec gzip --best {} \;
--
Daniel
Quand le moi est haïssable, aimer son prochain
comme soi même devient une atroce ironie.
Paul Valéry.
Re: Thunderbird problems
On 15.06.2021 06:46, Robbi Nespu wrote: On 6/15/21 6:24 AM, Frank McCormick wrote: The latest version of Thunderbird which was updated recently is giving me problems connecting to gmail. How can I downgrade Thunderbird on this machine? I am running Bullseye Let me guess, you unable to connect imap and smtp right? I having that kind of issue. $ apt-cache policy thunderbird thunderbird: Installed: 1:78.11.0-1 Candidate: 1:78.11.0-1 Version table: *** 1:78.11.0-1 500 500 http://ftp.jp.debian.org/debian bullseye/main amd64 Packages 100 /var/lib/dpkg/status Just FYI, I have the same version of Thunderbird installed, except it is from Buster. ... thunderbird: Installed: 1:78.11.0-1~deb10u1 Candidate: 1:78.11.0-1~deb10u1 Version table: *** 1:78.11.0-1~deb10u1 500 500 http://security.debian.org/debian-security buster/updates/main amd64 Packages 100 /var/lib/dpkg/status ... I didn't had any issues with Thunderbird before and after update. It works normally as usual. I think, the root cause for this issue could be elsewhere. I would suspect "libc" version difference in Bullseye, or something else. -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Re: [HS] Utilisation de fibre dans des rocades inter-étages
Désolé, j'y connais vraiment rien :-) mais peut-être trouveras-tu des éléments de réponse en épluchant les liens suivants (on doit pouvpoir en trouver d'autres): https://www.arcep.fr/fileadmin/reprise/dossiers/fibre/251116-Guide-Immeubles-neufs-BD.pdf https://www.azenn.com/content/38-livres-blancs#bonnespratiques
Re: Preserving locally modified configuration files - Dpkg::Options --force-confdef & --force-confold not working on command line
On Tue 15 Jun 2021 at 14:34:12 +0530, Jaikumar Sharma wrote:
> Hi,
>
> In debian 9.13 server, i'm using custom configuration (locally modified)
> file /etc/samba/smb.conf , I do not want to upgrade this file and retain
> the old configuration file without prompting during automatic upgrades but
> it is still giving me the prompt even after specifying on command line :
>
> sudo apt-get dist-upgrade -o Dpkg::Options::=--force-confdef -o
> Dpkg::Options::=--force-confold -y --allow-unauthenticated
>
> Still prompt/complain about locally modified configuration file, as per
> documentation it should work.
>
> and
>
> I've also tried to put these below command in a config file under
> /etc/apt/apt.conf.d/50-unattended-upgrades :
>
> Dpkg::Options {
> "--force-confdef";
> "--force-confold";
> }
>
> but behaviour is the same in both cases.
>
> Does somebody know what may be wrong here? or i'm doing it wrong?
I wonder whether using dpkg-divert(1) would help in preserving your
modified file?
--
Brian.
Re: Preserving locally modified configuration files - Dpkg::Options --force-confdef & --force-confold not working on command line
On Tuesday, June 15, 2021 at 2:40:04 PM UTC+5:30, jaikuma...@gmail.com wrote:
> Hi,
>
> In debian 9.13 server, i'm using custom configuration (locally modified) file
> /etc/samba/smb.conf , I do not want to upgrade this file and retain the old
> configuration file without prompting during automatic upgrades but it is
> still giving me the prompt even after specifying on command line :
>
> sudo apt-get dist-upgrade -o Dpkg::Options::=--force-confdef -o
> Dpkg::Options::=--force-confold -y --allow-unauthenticated
>
> Still prompt/complain about locally modified configuration file, as per
> documentation it should work.
>
> and
>
> I've also tried to put these below command in a config file under
> /etc/apt/apt.conf.d/50-unattended-upgrades :
>
> Dpkg::Options {
> "--force-confdef";
> "--force-confold";
> }
Seems it co-relates with already filed bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=316049
Re: Preserving locally modified configuration files - Dpkg::Options --force-confdef & --force-confold not working on command line
On Tue, Jun 15, 2021 at 2:34 PM Jaikumar Sharma
wrote:
> Hi,
>
> In debian 9.13 server, i'm using custom configuration (locally modified)
> file /etc/samba/smb.conf , I do not want to upgrade this file and retain
> the old configuration file without prompting during automatic upgrades but
> it is still giving me the prompt even after specifying on command line :
>
> sudo apt-get dist-upgrade -o Dpkg::Options::=--force-confdef -o
> Dpkg::Options::=--force-confold -y --allow-unauthenticated
>
> Still prompt/complain about locally modified configuration file, as per
> documentation it should work.
>
> and
>
> I've also tried to put these below command in a config file under
> /etc/apt/apt.conf.d/50-unattended-upgrades :
>
> Dpkg::Options {
> "--force-confdef";
> "--force-confold";
> }
>
Seems it co-relates with already filed bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=316049
Re: HS: postfix relay denied en ipv6
Le 15/06/2021 à 11:28, Stephane Bortzmeyer a écrit : On Tue, Jun 15, 2021 at 10:10:19AM +0200, NoSpam wrote a message of 21 lines which said: Exact, cela ne change toutefois rien d'autant que certaines adresses sont des GUA que j'ai définies sans masque. Je viens de tenter en mettant le masque /128 sur ces GUA et le /64 comme ci dessus, résultat identique :( ... said 554 5.7.1: Relay access denied (in reply to RCPT TO command) CMCM (je viens de tester avec une machine acceptée et une rejetée et le mail.log montre bien ce qu'il faut) donc il faudrait regarder le message d'erreur complet, notamment l'adresse IP. NOQUEUE: reject: RCPT from unknown[2001:db8:b1:932c:212::1]: 554 5.7.1 : Relay access denied; f rom= to= proto=ESMTP helo= J'ai mis le mode debug et voici ce qui en sort: Jun 15 11:02:01 wwwmail10 postfix/smtpd[10960]: connect from unknown [2001:db8:b1:932c:212::1] Jun 15 11:02:01 wwwmail10 postfix/smtpd[10960]: smtp_stream_setup: maxtime=300 enable_deadline=0 Jun 15 11:02:01 wwwmail10 postfix/smtpd[10960]: match_hostname: smtpd_client_event_limit_exceptions: unknown ~? hash:/etc/postfix/allowed-networks(0,lock|utf8_request) Jun 15 11:02:01 wwwmail10 postfix/smtpd[10960]: match_hostname: smtpd_client_event_limit_exceptions: lookup hash:/etc/postfix/allowed-networks.db unknown: not found Jun 15 11:02:01 wwwmail10 postfix/smtpd[10960]: match_hostaddr: smtpd_client_event_limit_exceptions: 2001:db8:b1:932c:212::1 ~? hash:/etc/postfix/allowed-networks(0,lock|utf8_request) Jun 15 11:02:01 wwwmail10 postfix/smtpd[10960]: match_list_match: unknown: no match Jun 15 11:02:01 wwwmail10 postfix/smtpd[10960]: match_list_match: 2001:db8:b1:932c:212::1: no match My allowed_network (part of) = 192.168.10.254 ok client.FQDN.hostname ok [2001:db8:b1:932c:212::1] ok [2001:db8:b1:932c:212::1]/128 ok [fd53:ac59:337:8b38::1] ok [fd53:ac59:337:8b38::]/64 ok Rights == root@wwwmail10:/etc/postfix# ls -al allowed* -rw-r--r-- 1 root root 1011 juin 15 11:15 allowed-networks -rw-r--r-- 1 root root 12288 juin 15 11:15 allowed-networks.db Clairement il ne trouve pas l'adresse ni le hostbname dans le map allowed-networks.db ! Merci pour ton aide -- Daniel
Re: HS: postfix relay denied en ipv6
On Tue, Jun 15, 2021 at 10:10:19AM +0200, NoSpam wrote a message of 21 lines which said: > Exact, cela ne change toutefois rien d'autant que certaines adresses sont > des GUA que j'ai définies sans masque. Je viens de tenter en mettant le > masque /128 sur ces GUA et le /64 comme ci dessus, résultat identique :( > > ... said 554 5.7.1: Relay access denied (in reply to RCPT TO > command) CMCM (je viens de tester avec une machine acceptée et une rejetée et le mail.log montre bien ce qu'il faut) donc il faudrait regarder le message d'erreur complet, notamment l'adresse IP.
Re: Thunderbird problems
On Mon, 14 Jun 2021 23:22:41 -0400 Frank McCormick wrote: > I filed a bug report with Mozilla. Perhaps I should do the same with Debian? Of course, Mozilla cannot solve Debian bugs and it looks like the bug is from Debian. It is possible the bug is from Thunderburd (not Mozilla as Thunderbird is not part of Mozilla anymore), but still if you don't know it the correct way is to report the bug to Debian and if they determine the bug is upstream they will forward it.
Preserving locally modified configuration files - Dpkg::Options --force-confdef & --force-confold not working on command line
Hi,
In debian 9.13 server, i'm using custom configuration (locally modified)
file /etc/samba/smb.conf , I do not want to upgrade this file and retain
the old configuration file without prompting during automatic upgrades but
it is still giving me the prompt even after specifying on command line :
sudo apt-get dist-upgrade -o Dpkg::Options::=--force-confdef -o
Dpkg::Options::=--force-confold -y --allow-unauthenticated
Still prompt/complain about locally modified configuration file, as per
documentation it should work.
and
I've also tried to put these below command in a config file under
/etc/apt/apt.conf.d/50-unattended-upgrades :
Dpkg::Options {
"--force-confdef";
"--force-confold";
}
but behaviour is the same in both cases.
Does somebody know what may be wrong here? or i'm doing it wrong?
Thank you.
Regards,
Jaikumar
[HS] Utilisation de fibre dans des rocades inter-étages
Bonjour, Voici des questions clairement indépendantes de Debian mais qui ne manqueront pas, je pense, d'intéresser les administrateurs Debian qui suivent cette liste. D'ici quelques semaines j'envisage d'utiliser de la fibre optique à la place de cuivre, pour inter-connecter des switches au sein d'un immeuble. Les switches sont installés à quelques étages de distance (disons 40m max pour donner un ordre de grandeur) les uns des autres. Le switch central est installé dans un rack 19". Les autres sont installés "au mieux" (ie à l'arrache) dans des colonnes techniques. Les rocades empruntent normalement des colonnes techniques dédiées aux courants faibles (ie aux télécoms) mais les tubes inter-étages de celles-ci sont souvent "bien remplis" et rajouter des tubes n'est pas agréable ;-))).. Pourquoi de la fibre ? Pour pouvoir si besoin: - dépasser le Gigabit, - dépasser les 100m, - pouvoir plus facilement ajouter des switches dans les étages grâce à la compacité de la fibre, - occuper moins de place dans les tubes inter-étages voire utiliser des colonnes dédiées à d'autres usages (courants forts, eau, ...) grâce à l'immunité de la fibre. Pour éviter les travaux sur site, j'imagine utiliser des rocades optiques de longueurs standard (10m, 20m) en lovant à une extrémité l'excédent de longueur. Les prix des composants en fibre me semblent abordables. Voici des exemples: [1] https://www.fs.com/fr/products/80734.html?attribute=3821=170148 [2] https://www.fs.com/fr/products/41822.html?attribute=6485=259887 Je n'ai par contre aucune expérience de l'utilisation de fibre dans ce contexte. L'accès aux colonnes techniques n'est pas contrôlé : les sous-traitants des opérateurs télécoms interviennent "sans prévenir" pour modifier le câblage en cuivre ou optique (FTTH) existant. Même si je ne met pas en doute leurs intentions, on peut imaginer que pendant leurs interventions, ils tirent ou retirent des câbles dans les colonnes techniques et ses câbles peuvent frotter contre mes rocades optiques. Mes questions: 1. Une rocade MTP 12 brins OM3 ou OM4 (cf [1]) doit-elle être protégée dans une gaîne sur toute sa longueur dans une colonne technique verticale ou bien ses propres protections sont-elles suffisantes, même en cas de tirage de câble à proximité ? 2. Même question avec une jarretière optique avec armature en acier (cf [2]) ? 3. Est-il admissible d'assembler deux jarretières pour obtenir une longueur spécifique (20m + 3m=23m) ? Si oui quels précautions pour le point où s'opère la jonction ? 4. Est-il possible de lover 8m de longueur dans un tiroir optique mural ou 19" ? 5. Comment vérifie-t-on un câble optique après tirage ? 6. Conseils ? Suggestions ? Slts
Re: cannot mount smartphone anymore
Andrei POPESCU wrote: > This suggests (no pun intended) it was installed manually > (`apt list usbguard` would confirm this), as Suggests are > not installed by default. alias ai='sudo apt-get --install-suggests install' https://dataswamp.org/~incal/conf/.zsh/apt -- underground experts united https://dataswamp.org/~incal
Re: HS: postfix relay denied en ipv6
Le 15/06/2021 à 08:15, Stephane Bortzmeyer a écrit : On Mon, Jun 14, 2021 at 10:51:32PM +0200, NoSpam wrote a message of 48 lines which said: [fd53:ac59:337:8b38::/64] ok Il me semble que la syntaxe normale est : [fd53:ac59:337:8b38::]/64 ok Exact, cela ne change toutefois rien d'autant que certaines adresses sont des GUA que j'ai définies sans masque. Je viens de tenter en mettant le masque /128 sur ces GUA et le /64 comme ci dessus, résultat identique :( ... said 554 5.7.1: Relay access denied (in reply to RCPT TO command) -- Daniel
Re: Archiver mails
C'est du shell standard, il me semble. Oui, c'était du second degré. J'aurais tout fait en Bash si cela avait été moi ;-) A+ gaby -- Gabriel Moreau - IR CNRShttp://www.legi.grenoble-inp.fr LEGI (UMR 5519) Laboratoire des Ecoulements Geophysiques et Industriels Domaine Universitaire, CS 40700, 38041 Grenoble Cedex 9, France mailto:gabriel.mor...@legi.grenoble-inp.fr tel:+33.476.825.015 smime.p7s Description: Signature cryptographique S/MIME
Re: Archiver mails
On Tue, Jun 15, 2021 at 08:34:38AM +0200, Gabriel Moreau wrote a message of 113 lines which said: > > ./backup-mailboxes.py && (find Mail -type f -ctime +90 | xargs gzip --best) > > Je me disais, quoi que du bon gros Python pour faire ça, il y a un truc qui > ne vas pas ! Ça pourrait certainement se faire en Python, mais j'avais la flemme. > Heureusement, tout finit par une belle basherie ;-) C'est du shell standard, il me semble.
Re: Archiver mails
./backup-mailboxes.py && (find Mail -type f -ctime +90 | xargs gzip --best) Amélioration possible xargs -r gzip --best J'utilise toujours avec -r xargs... gaby -- Gabriel Moreau - IR CNRShttp://www.legi.grenoble-inp.fr LEGI (UMR 5519) Laboratoire des Ecoulements Geophysiques et Industriels Domaine Universitaire, CS 40700, 38041 Grenoble Cedex 9, France mailto:gabriel.mor...@legi.grenoble-inp.fr tel:+33.476.825.015 smime.p7s Description: Signature cryptographique S/MIME
Re: Archiver mails
./backup-mailboxes.py && (find Mail -type f -ctime +90 | xargs gzip --best) Je me disais, quoi que du bon gros Python pour faire ça, il y a un truc qui ne vas pas ! Heureusement, tout finit par une belle basherie ;-) gaby -- Gabriel Moreau - IR CNRShttp://www.legi.grenoble-inp.fr LEGI (UMR 5519) Laboratoire des Ecoulements Geophysiques et Industriels Domaine Universitaire, CS 40700, 38041 Grenoble Cedex 9, France mailto:gabriel.mor...@legi.grenoble-inp.fr tel:+33.476.825.015 smime.p7s Description: Signature cryptographique S/MIME
Re: HS: postfix relay denied en ipv6
On Mon, Jun 14, 2021 at 10:51:32PM +0200, NoSpam wrote a message of 48 lines which said: > [fd53:ac59:337:8b38::/64] ok Il me semble que la syntaxe normale est : [fd53:ac59:337:8b38::]/64 ok
Re: Archiver mails
On Mon, Jun 14, 2021 at 05:08:36PM +0200,
steve wrote
a message of 12 lines which said:
> > Un petit script Python lancé par cron tous les mois qui renomme les
> > boites par exemple debian/french -> debian/french-2021-06.
>
> Serait-ce possible de le partager ou est-ce secret défense ?
Attaché. À lancer, par exemple, avec :
./backup-mailboxes.py && (find Mail -type f -ctime +90 | xargs gzip --best)
#!/usr/bin/env python3
# $Id: backup-mailboxes.py 5778 2021-06-15 06:10:10Z stephane $
import os
import re
import time
startdir = os.environ['HOME'] + "/Mail"
filter = "-[-0-9]+(\.gz|\.bz2|.Z|)$"
regexp = re.compile(filter)
def display(name):
if not regexp.search(name):
newname = name + \
time.strftime("-%Y-%m", time.localtime(time.time()-\
(14*86400)))
if exists(newname):
print(newname + " already exists, skipping...")
else:
print(name + " -> " + newname)
os.rename (name, newname)
def exists(filename):
try:
values = os.stat(filename)
return 1
except os.error:
return 0
def listsub(dir, action):
try:
names = os.listdir(dir)
except os.error:
print("Can't list", dir)
names = []
for name in names:
fullname = os.path.join(dir, name)
if os.path.isfile(fullname):
action(*(fullname,))
elif os.path.isdir(fullname) and \
not os.path.islink(fullname):
listsub(fullname, action)
if __name__ == '__main__':
listsub(startdir, display)
