Re: Firefox resource utilization (was Re: A case for supporting antiquated hardware, was Re: A hypervisor for a headless server?)
On Mon, Jun 05, 2023 at 05:59:11PM -0400, Celejar wrote: [...] > The only case I can see in which such offloading would > be unethical is where the website operator is somehow engaging in > deceptive behavior, but assuming it is not [...] A pretty strong assumption given that the crushing maturity of the internet is fuelled by the ad industry, which, barred some exceptions, can be characterised as "deception for hire". Cheers -- t signature.asc Description: PGP signature
Re: Lanzamiento de Debian 12 Bookworm
Yo lo instale hace un mes y algunos dias en una PS y una notebook. Hasta ahora funciono todo perfecto. Una la actualice desde Bullseye y la otra hice una instalacion limpia. En el funcionamiento no veo diferencias. El 5/6/23 a las 18:07, Eliecer Rangel escribió: Les comento algo para que lo tengan en cuenta, lo bueno de Debian es su estabilidad por eso antes de cada lanzamiento de una nueva versión se realizan una serie de revisiones antes de su lanzamiento a eso se le llama TESTING. Y ya pasada por esas revisiones se publica la versión oficial ESTABLE, no quiere decir que no vayan a ver errores; por eso somos parte de esta comunidad y se informa de cualquier error para posteriormente ser corregido en la menor brevedad posible. Somos Debianitas, no olvidar eso! El lun, 5 de jun. de 2023 15:46, JavierDebian escribió: 1 11 28 me me m El 5/6/23 a las 17:30, José Manuel (Abogado) escribió: > > > El 5/6/23 a las 16:24, Camaleón escribió: >> El 2023-06-05 a las 09:00 -0500, Eliecer Rangel escribió: >> >>> Esperando con ansías el lanzamiento de Debian 12 Bookworm, este >>> sábado 10 >>> de Junio del 2023. >>> >>> Fuente oficial de la noticia: >>> https://wiki.debian.org/ReleasePartyBookworm >> Pues sale con 100 BUGS conocidos :-/ >> >> https://www.phoronix.com/news/Debian-12-Next-Week >> >> Sugerencias a quien vaya a instalarlo: >> >> 1. Que espere a que salga la primera «point release» (un mes más tarde) >> 2. Que LEA BIEN las notas de la versión para evitar sustos y desastres >> >> Saludos, >> > Hola > Que nos recomiendas para los que tenemos en los repositorios puesto la > palabra stable en vez de bullseye > Gracias 1 - No hacer un "upgrade" así no más. 2 - Leer bien https://www.debian.org/releases/stable/mips/release-notes/ch-upgrading.es.html Lo que salga para Bookworm no va a diferir en mucho, diría en nada, excepto por "non-free-firmware". Yo cuando hago una actualización, voy de a poco. A - Anulo (#) todos los repositorios que no sean el básico de Debian "bookworm". B - apt update | apt upgrade (Se instala núcleo nuevo). C - Reiniciar equipo D - apt dist-upgrade y luego, DE A UNO, ir reactivando las demás fuentes y actualizando, empezando por "bookworm-security", luego "bookworm-updates", luego el resto (google, edge, dropbox...) ATENCIÖN ESPECIAL: Nuevo componente del repositorio además de "main contrib non-free": non-free-firmware https://wiki.debian.org/Firmware Saludos. JAP -- */Gerardo Braica */gbra...@gmail.com.ar /*/*
Re: Debian 10 planté par mise à jour pour autre version (+ récente)
Le 07/05/2023 à 20:50, Romain P. a écrit : Le 14/02/2023 à 11:00, Sébastien NOBILI a écrit : Si la réponse est oui, alors sauvegarde ce qui t'est cher et (au choix) : - installe le .deb de la libc que tu as téléchargé (via la commande wget) avec la commande suivante : dpkg -i libc-bin_2.36-8_amd64.deb - télécharge apt/stable et installe-le avec dpkg : wget http://ftp.fr.debian.org/debian/pool/main/a/apt/apt_2.2.4_amd64.deb dpkg -i apt_2.2.4_amd64.deb Ça risque de commencer à coincer dès cette étape, il faudra analyser pourquoi et insister. Ensuite il faudra faire le downgrade du système. Sébastien Bonjour ☺ En effet ça coince et je devrais peut-être passer à Debian 11 !? " sudo dpkg -i libc-bin_2.36-8_amd64.deb (Lecture de la base de données... 337832 fichiers et répertoires déjà installés.) Préparation du dépaquetage de libc-bin_2.36-8_amd64.deb ... Dépaquetage de libc-bin (2.36-8) sur (2.36-8) ... dpkg: des problèmes de dépendances empêchent la configuration de libc-bin : libc-bin dépend de libc6 (>> 2.36) ; cependant : La version de Iibc6:amd64 sur le système est 2.28-10+debl0u2. dpkg: erreur de traitement du paquet libc-bin (—install) : problèmes de dépendances - laissé non configuré Traitement des actions différées (« triggers ») pour man-db (2.8.5-2) ... Des erreurs ont été rencontrées pendant l'exécution : libc-bin " # " sudo dpkg -i apt_2.2.4_amd64.deb (Lecture de la base de données... 337832 fichiers et répertoires déjà installé Préparation du dépaquetage de apt_2.2.4_amd64.deb ... Dépaquetage de apt (2.2.4) sur (2.2.4) ... dpkg: des problèmes de dépendances empêchent la configuration de apt : apt dépend de libapt-pkg6.0 (>= 2.2.4) ; cependant : Le paquet libapt-pkg6.0 n'est pas installé, apt dépend de libgcc-s1 (>= 3.0) ; cependant : Le paquet libgcc-s1:amd64 n'est pas encore configuré, apt dépend de libgnutls30 (>= 3.7.0) ; cependant : La version de libgnutls30:amd64 sur le système est 3.6.7-4+debl0u9. apt dépend de libseccomp2 (>= 2.4.2) ; cependant : La version de libseccomp2:amd64 sur le système est 2.3.3-4. apt dépend de libstdc++6 (>= 9) ; cependant : La version de libstdc++6:amd64 sur le système est 8.3.0-6. dpkg: erreur de traitement du paquet apt (—install) : problèmes de dépendances - laissé non configuré Traitement des actions différées (« triggers ») pour man-db (2.8.5-2) Des erreurs ont été rencontrées pendant l'exécution : apt " Merci Romain # Bonsoir ☺ Dans mon cas de Debian 10 planté, puis-je installer Debian 11 par dessus Debian 10 planté, ou dois-je formater les partitions d’installation de Debian avant ? Merci Romain
Re: Firefox resource utilization (was Re: A case for supporting antiquated hardware, was Re: A hypervisor for a headless server?)
On Sun, 4 Jun 2023 16:17:47 +0800 Bret Busby wrote: > On 4/6/23 14:32, Max Nikulin wrote: > > > > > I believe, web site creators should be blamed more aggressively than > > browser developers for RAM requirements of contemporary web applications. > > > > That was the point that I was making - I had not, as a twisted response > indicated, criticised Firefox regarding the misuse of resources - I > explicitly referred to malignant web application developers (for those > that do not understand the term, a web application is the application, > on the web application hosting server, that the user accesses, using a > web browser, not the web browser itself) that steal users' resources > using client-side processing (by using malware such as javascript using > client side processing), rather than properly and ethically using > server-side processing, such as .jsp or Perl .cgi applications. > > The problem is that some web developers (and, especially, their > employers) offload the processing that should be done on the business > web application hosting server, to the victim users' personal computers. > It is a malignant exploitation, like the "gig economy". I am quite puzzled by your perspective: you repeatedly express moral indignation at the offloading of processing to users' machines, calling this "malignant exploitation" and "steal[ing]" and implying that it is unethical. Why? What duty does the website owe you to do any processing at all for you? The only case I can see in which such offloading would be unethical is where the website operator is somehow engaging in deceptive behavior, but assuming it is not, why do you feel that there is an ethical problem here? What right does a user have to demand that someone else perform some processing for him? -- Celejar
Re: problem with local DNS
Sorry for the double post but I did not see the first answer any where. Thank you. It was a lot easier than I thought it would be. Again Thank you. On 6/5/23 3:45 AM, Brad Rogers wrote: On Mon, 05 Jun 2023 08:49:11 +0200 Michel Verdier wrote: Hello Michel, I already answered to your problem : I suspect OP is of the belief that we will respond to them directly and, as a consequence, they are not reading the list.
Re: It's that time of the year again
Good morning Reco, Reco writes: > Dear list, > > [1] came to my attention today. Quoting the most relevant part (emphasis > mine): > > There are still about 100 known RC bugs affecting bookworm, but we have > accepted *to release having them included*. > > > Forewarned is forearmed, as they say. > > > [1] https://lists.debian.org/debian-devel-announce/2023/06/msg0.html > Good news, thanks! I'm waiting for her[bookworm] to come in South Korea. Sincerely, Byung-Hee (Bullseye user) -- ^고맙습니다 _布德天下_ 감사합니다_^))//
Re: Lanzamiento de Debian 12 Bookworm
Les comento algo para que lo tengan en cuenta, lo bueno de Debian es su estabilidad por eso antes de cada lanzamiento de una nueva versión se realizan una serie de revisiones antes de su lanzamiento a eso se le llama TESTING. Y ya pasada por esas revisiones se publica la versión oficial ESTABLE, no quiere decir que no vayan a ver errores; por eso somos parte de esta comunidad y se informa de cualquier error para posteriormente ser corregido en la menor brevedad posible. Somos Debianitas, no olvidar eso! El lun, 5 de jun. de 2023 15:46, JavierDebian escribió: > > 1 11 28 me me m > El 5/6/23 a las 17:30, José Manuel (Abogado) escribió: > > > > > > El 5/6/23 a las 16:24, Camaleón escribió: > >> El 2023-06-05 a las 09:00 -0500, Eliecer Rangel escribió: > >> > >>> Esperando con ansías el lanzamiento de Debian 12 Bookworm, este > >>> sábado 10 > >>> de Junio del 2023. > >>> > >>> Fuente oficial de la noticia: > >>> https://wiki.debian.org/ReleasePartyBookworm > >> Pues sale con 100 BUGS conocidos :-/ > >> > >> https://www.phoronix.com/news/Debian-12-Next-Week > >> > >> Sugerencias a quien vaya a instalarlo: > >> > >> 1. Que espere a que salga la primera «point release» (un mes más tarde) > >> 2. Que LEA BIEN las notas de la versión para evitar sustos y desastres > >> > >> Saludos, > >> > > Hola > > Que nos recomiendas para los que tenemos en los repositorios puesto la > > palabra stable en vez de bullseye > > Gracias > > > 1 - No hacer un "upgrade" así no más. > > 2 - Leer bien > > https://www.debian.org/releases/stable/mips/release-notes/ch-upgrading.es.html > Lo que salga para Bookworm no va a diferir en mucho, diría en nada, > excepto por "non-free-firmware". > > Yo cuando hago una actualización, voy de a poco. > A - Anulo (#) todos los repositorios que no sean el básico de Debian > "bookworm". > B - apt update | apt upgrade (Se instala núcleo nuevo). > C - Reiniciar equipo > D - apt dist-upgrade > > y luego, DE A UNO, ir reactivando las demás fuentes y actualizando, > empezando por > > "bookworm-security", luego > "bookworm-updates", luego el resto (google, edge, dropbox...) > > ATENCIÖN ESPECIAL: > Nuevo componente del repositorio además de "main contrib non-free": > non-free-firmware > > https://wiki.debian.org/Firmware > > Saludos. > > JAP > >
Re: Debian USB Wifi
> I believe that there are at least some 11ac cards supported by the > vanilla kernel and open source firmware: > > https://wireless.wiki.kernel.org/en/users/Drivers/ath10k > https://wireless.wiki.kernel.org/en/users/Drivers/ath10k/firmware Oh so the Free ath10k firmwares have now grown support for 11ac? Someone should tell Purism, because they still sell their Librem mini with an ath9k 11n card and the reason is/was that it's the best they could find without resorting to a proprietary blob :-( Stefan
Re: Lanzamiento de Debian 12 Bookworm
El 5/6/23 a las 17:30, José Manuel (Abogado) escribió: El 5/6/23 a las 16:24, Camaleón escribió: El 2023-06-05 a las 09:00 -0500, Eliecer Rangel escribió: Esperando con ansías el lanzamiento de Debian 12 Bookworm, este sábado 10 de Junio del 2023. Fuente oficial de la noticia: https://wiki.debian.org/ReleasePartyBookworm Pues sale con 100 BUGS conocidos :-/ https://www.phoronix.com/news/Debian-12-Next-Week Sugerencias a quien vaya a instalarlo: 1. Que espere a que salga la primera «point release» (un mes más tarde) 2. Que LEA BIEN las notas de la versión para evitar sustos y desastres Saludos, Hola Que nos recomiendas para los que tenemos en los repositorios puesto la palabra stable en vez de bullseye Gracias 1 - No hacer un "upgrade" así no más. 2 - Leer bien https://www.debian.org/releases/stable/mips/release-notes/ch-upgrading.es.html Lo que salga para Bookworm no va a diferir en mucho, diría en nada, excepto por "non-free-firmware". Yo cuando hago una actualización, voy de a poco. A - Anulo (#) todos los repositorios que no sean el básico de Debian "bookworm". B - apt update | apt upgrade (Se instala núcleo nuevo). C - Reiniciar equipo D - apt dist-upgrade y luego, DE A UNO, ir reactivando las demás fuentes y actualizando, empezando por "bookworm-security", luego "bookworm-updates", luego el resto (google, edge, dropbox...) ATENCIÖN ESPECIAL: Nuevo componente del repositorio además de "main contrib non-free": non-free-firmware https://wiki.debian.org/Firmware Saludos. JAP
Re:
El 5/6/23 a las 16:24, Camaleón escribió: El 2023-06-05 a las 09:00 -0500, Eliecer Rangel escribió: Esperando con ansías el lanzamiento de Debian 12 Bookworm, este sábado 10 de Junio del 2023. Fuente oficial de la noticia: https://wiki.debian.org/ReleasePartyBookworm Pues sale con 100 BUGS conocidos :-/ https://www.phoronix.com/news/Debian-12-Next-Week Sugerencias a quien vaya a instalarlo: 1. Que espere a que salga la primera «point release» (un mes más tarde) 2. Que LEA BIEN las notas de la versión para evitar sustos y desastres Saludos, Hola Que nos recomiendas para los que tenemos en los repositorios puesto la palabra stable en vez de bullseye Gracias -- Un saludo, José Manuel Gran Canaria/España Si vas a escribir.. piensa en esto: no digas nada que no sea mas precioso que el silencio!!!
Re: Debian USB Wifi
On Mon, 05 Jun 2023 13:51:21 -0400 Stefan Monnier wrote: ... > The best option is to buy one that says clearly that it works with the > vanilla kernel and without requiring proprietary firmware blobs. > These are hard to come by and will usually be sold by companies > specializing in this market like tehnoetic.com, thinkpenguin.com, ... ... > Be aware that there is simply no wifi card (USB or otherwise) that > satisfies this requirement beyond the 11n spec: beyond 11n you currently > have to accept the use of a proprietary binary blob :-( I believe that there are at least some 11ac cards supported by the vanilla kernel and open source firmware: https://wireless.wiki.kernel.org/en/users/Drivers/ath10k https://wireless.wiki.kernel.org/en/users/Drivers/ath10k/firmware -- Celejar
Re: Debian USB Wifi
> I want to buy a usb to wifi network. How do I check if the hardware(usb) > has debian support? That's tricky: - It's fairly frequent that manufacturers change the underlying hardware without changing the product name (presumably because they find that some other wifi chipset provides the same featureset at a lower cost). So you can't really trust info about "FooBar 250++ works" nor the reverse. - There's "supported" and "supported": some chipsets are well supported by the vanilla Linux kernel (tho often requiring non-Free firmware blobs), which is generally a guarantee that it will stay supported in the foreseeable future and will work reliably and without much effort (if any). Other chipsets are supported only via drivers not included in the kernel (or tentatively included in the vanilla kernel but not "yet" well integrated), and your mileage will definitely vary with those: some features may not be supported (e.g. `hostapd`), and configuring them and keeping them working in the face of upgrades can be a constant struggle. The best option is to buy one that says clearly that it works with the vanilla kernel and without requiring proprietary firmware blobs. These are hard to come by and will usually be sold by companies specializing in this market like tehnoetic.com, thinkpenguin.com, ... https://ryf.fsf.org/ can be a good starting point for that, tho it has very few products and most of them are old, but it can help find companies that care. Be aware that there is simply no wifi card (USB or otherwise) that satisfies this requirement beyond the 11n spec: beyond 11n you currently have to accept the use of a proprietary binary blob :-( Otherwise it can be worthwhile to buy secondhand, in which case the product is "fixed", so you can check which chipset it uses, and then figure out what's the status of the drivers for this chipset. Stefan
Re: Cable colors and urban legends
On Mon Jun 5 09:58:04 2023 gene heskett wrote: > I could go on with my war stories, but I'm boring the list > with off topic rattling. Just suffice to say I've BT & DT many times. Come on over to alt.folklore.computers. It exists to exchange war stories. -- /~\ Charlie Gibbs | They don't understand Microsoft \ /| has stolen their car and parked X I'm really at ac.dekanfrus | a taxi in their driveway. / \ if you read it the right way. |-- Mayayana
Re: Debian USB Wifi
On Sun, 4 Jun 2023 21:56:03 -0600 Charles Curley wrote: > I can suggest that you should avoid the ASUS USB-N 13 > Adapter Wireless-N300. This, in spite of the claim of Linux support on > the box. I retract this for Bookworm. It appears to be running just fine on my i386 Lenovo R51 running Bookworm. Bus 001 Device 003: ID 0b05:17ab ASUSTek Computer, Inc. USB-N13 802.11n Network Adapter (rev. B1) [Realtek RTL8192CU] -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re:
El 5/6/23 a las 12:24, Camaleón escribió: El 2023-06-05 a las 09:00 -0500, Eliecer Rangel escribió: Esperando con ansías el lanzamiento de Debian 12 Bookworm, este sábado 10 de Junio del 2023. Fuente oficial de la noticia: https://wiki.debian.org/ReleasePartyBookworm Pues sale con 100 BUGS conocidos :-/ https://www.phoronix.com/news/Debian-12-Next-Week Sugerencias a quien vaya a instalarlo: 1. Que espere a que salga la primera «point release» (un mes más tarde) 2. Que LEA BIEN las notas de la versión para evitar sustos y desastres Saludos, Buen día. Por razones que no vienen al caso, hace un par de meses debí reinstalar sistema, y lo hice con bookworm, habida cuenta que faltaba tan poco. El entorno Wayland da dolores de cabeza, no todo anda bien. 1 - Flameshot: después de buscar en toda la red, encontré la solución para que copie imágenes al portapapeles; hay que bajar los fuentes y compilarlo a mano con una llave activada. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910970 2 - Avidemux: NO FUNCIONA, y por lo que vi por ahí, no va a funcionar en mucho tiempo; es un problema del programa en sí. 3 - MEGASync de repo Mega: el sensor de ratón se "cuelga" del ángulo superior izquierdo de la pantalla. Se soluciona abriendo desde aplicación en bandeja "Mostrar estado", y ahí se ubica la ventana donde debe, y no molesta más. 4 - Firefox: hay que activar una variable de entorno en ~/.profile: # Firefox wayland: if [ "$XDG_SESSION_TYPE" == "wayland" ]; then export MOZ_ENABLE_WAYLAND=1 fi Por lo menos hasta ahora, los problemas que he tenido yo. Si pasan a bookworm, recomiendo se mantengan en X11 si no tienen ganas de divertirse. JAP
Re: Mount Permissions (btrfs subvolumes)
On 6/5/23 7:23 AM, Greg Wooledge wrote: > > You can run the command "mount" with no arguments to see the details of > each mounted file system. You don't even have to be root. I don't know > how btrfs subvolumes work, so I don't know whether they appear in the > output of mount, but you could try it and see. > This part is fine. I think when no subvolume is peocified with `-o`, it will mount subvolid=5, the default subvolume. Use `-o subvol=$NAME` to mount one of your choosing. I'll be back to show the efects of `noauto`.
Re:
El 2023-06-05 a las 09:00 -0500, Eliecer Rangel escribió: > Esperando con ansías el lanzamiento de Debian 12 Bookworm, este sábado 10 > de Junio del 2023. > > Fuente oficial de la noticia: > https://wiki.debian.org/ReleasePartyBookworm Pues sale con 100 BUGS conocidos :-/ https://www.phoronix.com/news/Debian-12-Next-Week Sugerencias a quien vaya a instalarlo: 1. Que espere a que salga la primera «point release» (un mes más tarde) 2. Que LEA BIEN las notas de la versión para evitar sustos y desastres Saludos, -- Camaleón
Re:
Hola a tod@s ! Con ansias esperamos "Debian 12". Saludos On Mon, Jun 5, 2023 at 10:23 AM Marcelo Eduardo Giordano < contadorgiord...@gmail.com> wrote: > Yo igual > > > -- -- * Rolando Duarte G.* * +56 9 77597370* --
Re:
Yo igual
[no subject]
Esperando con ansías el lanzamiento de Debian 12 Bookworm, este sábado 10 de Junio del 2023. Fuente oficial de la noticia: https://wiki.debian.org/ReleasePartyBookworm
Re: Debian USB Wifi
Ciao a tutti, I am using BrosTrend Ac1200 and it works fine.
Re: Évènement parisen pour la sortie de Debian 12 / Bookworm
Merci à l'April! J'irai, heureux de te retrouver après si longtemps Aurélien, et ceux qui viendront :) Jean-Philippe MENGUAL Debian Developer non uploading Community team member Accessibility team member debian-l10n-french team member President of Debian France non-profit organization Le 05/06/2023 à 13:29, Aurélien COUDERC a écrit : Bonjour à toutes et tous, pour la sortie de Debian 12 prévue ce samedi, l’April [0] a la gentillesse nous accueillir à son local dans le 14e arrondissement de Paris pour fêter l’évènement. L’idée est de se retrouver autour d’un verre et d’échanger sur la nouvelle version de Debian. Développeurs / développeuses, utilisateurs / utilisatrices et curieux / curieuses sont les bienvenues. C’est un apéro dont vous êtes le héro / l’héroïne donc vous y trouverez ce que vous voudrez bien apporter à boire ou à manger. ;) Nous pouvons accueillir jusqu’à *25 - 30 personnes* de manière confortable et l’évènement sera organisé sous réserve d’un nombre minimal de participants donc si vous êtes intéressés prière de vous inscrire ici : [1] https://date.chapril.org/7VUNrINkvPu8wDK9 et de vous désinscrire si vous avez un empêchement. Où : local de l’association April, 44/46 rue de l'Ouest (cour intérieure), Paris 14e Quand : samedi 10 juin 2023 à partir de 18H Quoi : à vous de nous dire sur le lien [2] ci-dessous Contacts : - par courriel : couc...@debian.org - via Mastodon : @couc...@framapiaf.org Vous pouvez me contacter directement pour plus d’informations. Prière d’éviter les réponses à tout le monde sauf si approprié. [0] https://www.april.org/ [1] https://date.chapril.org/7VUNrINkvPu8wDK9 [2] https://pad.april.org/p/ap%C3%A9ro-debian-12-paris Librement, -- Aurélien
Screen locker
Hi. I need a screen lock mechanism that does not let another user open a new session (= if you lock to go to the bathroom, you get your place back), but after a configurable amount of time (= if you lock and go to the movies, you might not get your place back) has a dialog “this computer is locked since…” and a button “force logout” (= your processes will not waste resources until the next reboot). Is there something like that available in Debian? Or not in Debian? (We are using lightdm, but since we do not want to let extra sessions, the solution does not need to cooperate with the display manager, so that information should not be relevant. It is not an issue if users can ctrl-alt-F2 to another VT and startx.) Oh, I forgot: it needs to work with passwd and shadow from NIS, because it's still the 20th century around here. Regards, -- Nicolas George
Mastering regular expressions: la lecture qu'elle en est bien
Le Sat, Jun 03, 2023 at 02:08:55PM +0200, Dethegeek a écrit :
> Par exemple, dans un texte contenant des chaînes délimitées soit par des
> doubles quotes ou des simples quotes (le HTML apr exemple) alors tu peux
si il y a bien *un* truc à ne jamais parser avec des regexps autrement
que pour du one shot, c'est tous ces formats dont la structure est très
complexe (xml,html,yaml, …
> capturer le début d'une chaîne avec ("|') puis trouver la fin de cette chaîne
> avec \1.
GNI? non …
* on capture avec des parenthèses qui expliquent ou commencent
et finissent la capture
* la capture numero N (\N) est celle de la Nième (
sed -r '
s/(.*-(.*)) (.*)/ 1: \1\n 2: \2\n 3: \3\n/
' <<%
Saint-Exupery Antoine
te donneras
1: Saint-Exupery
2: Exupery
3: Antoine
les | servent à écrire des Atomes alteratifs
sed -rn 's/Saint-(Exupery|Hilaire) (.*)/\2 est saint /p' <<%
Saint-Exupery Antoine
Saint-Thomas d'Aquin
Donne:
Antoine est saint
> Tu as aussi des outils sympas pour tester tes regexes,
> https://regex101.com/
ou vim avec
:set is hls
et les verymagic (\v)
ou tout simplement des exos de sed. j'avoue ne pas piger pourquoi
tous ces millions de lignes de code et du réseau gachés juste pour
s'amuser avec des outils qui ne pèsent rien sur ta machine.
> Et une excellente documentation sur les regexes, celle qui m'a permis de tout
> en apprendre il y a bien longtemps. Pour moi c'est une référence dans le
> domaine.
De *très très très* loin, ce que j'ai pu lire de mieux sur les regexps est
https://www.oreilly.com/library/view/mastering-regular-expressions/0596528124/
Non seulement c'est techniquement très précis (les types de moteurs,
avantages comparés de NFA et DFA, tout ça …) mais en plus c'est *très
bien écrit* et ca donne envie d'essayer les trucs. A lire entre amis
avec les laptops à porté de main, ça remplace aisément les soirées
jeu de plateaux ou netflix.
cordialement,
marc
Évènement parisen pour la sortie de Debian 12 / Bookworm
Bonjour à toutes et tous, pour la sortie de Debian 12 prévue ce samedi, l’April [0] a la gentillesse nous accueillir à son local dans le 14e arrondissement de Paris pour fêter l’évènement. L’idée est de se retrouver autour d’un verre et d’échanger sur la nouvelle version de Debian. Développeurs / développeuses, utilisateurs / utilisatrices et curieux / curieuses sont les bienvenues. C’est un apéro dont vous êtes le héro / l’héroïne donc vous y trouverez ce que vous voudrez bien apporter à boire ou à manger. ;) Nous pouvons accueillir jusqu’à *25 - 30 personnes* de manière confortable et l’évènement sera organisé sous réserve d’un nombre minimal de participants donc si vous êtes intéressés prière de vous inscrire ici : [1] https://date.chapril.org/7VUNrINkvPu8wDK9 et de vous désinscrire si vous avez un empêchement. Où : local de l’association April, 44/46 rue de l'Ouest (cour intérieure), Paris 14e Quand : samedi 10 juin 2023 à partir de 18H Quoi : à vous de nous dire sur le lien [2] ci-dessous Contacts : - par courriel : couc...@debian.org - via Mastodon : @couc...@framapiaf.org Vous pouvez me contacter directement pour plus d’informations. Prière d’éviter les réponses à tout le monde sauf si approprié. [0] https://www.april.org/ [1] https://date.chapril.org/7VUNrINkvPu8wDK9 [2] https://pad.april.org/p/ap%C3%A9ro-debian-12-paris Librement, -- Aurélien
Re: Re : Re: sed ignorer une occurence
salut,
> J'utilise plutôt emacs et ne connais pas bien vi autrement que pour
> éditer des fichiers de config.
/!\: message à caractère informatif sans volonté prosélyte
une des raisons qui me font aimer vim est justement la simplicité avec
laquelle tu peux interagir avec les autres commandes. j'ai fais toute
une conférence là dessus (c'est en euuuhh-anglais)
https://github.com/eiro/talk-acme-changed-my-life
je fais des demos qui illustrent ce que je te proposais de faire.
> Il me manquais deux notions :
> [^.\n] non match (la négation de la correspondance
> \1 backreference dans l'expression régulière, là par contre il va
> falloir que je lise une bonne doc sur le sujet, G pas tout compris !
ah ben sans rentrer dans les détails (attention: le -r est important)
soit une liste de tu veux transformer. disons la liste suivante:
Manipulation - Au commencement, le troisième homme - Ep 1⧸6 - Documentaire sur
l'affaire Clearstream [vzKpalcKfF4].webm
Manipulation - Clearstream, la banque des banques - Ep 2⧸6 - Documentaire sur
l'affaire Clearstream [RaDFbeO94Rg].webm
Manipulation - Jean-Luc Lagardère, le scénario noir - Ep 3⧸6 - l'affaire
Clearstream - Y [a7glzdg_1ng].webm
Manipulation - Karachi et le trésor de guerre - Ep 5⧸6 - l'affaire Clearstream
- Y [SePDLJt85bw].webm
Manipulation - La république des mallettes - Ep 6⧸6 - l'affaire Clearstream - Y
[QrdpPCZfA1w].webm
Manipulation - Taïwan, naissance de la zone grise - Ep 4⧸6 - l'affaire
Clearstream - Y [qYzEW7rZkn0].webm
en la liste suivante
1_Au_commencement_le_troisième_homme.webm
2_Clearstream_la_banque_des_banques.webm
3_Jean-Luc_Lagardère_le_scénario_noir.webm
5_Karachi_et_le_trésor_de_guerre.webm
6_La_république_des_mallettes.webm
4_Taïwan_naissance_de_la_zone_grise.webm
la première étape c'est de trouver la structure
Manipulation - (TITRE) - Ep 1⧸(NUMERO) - (RESTE)
que je veux transformer en
(NUMERO)_(TITRE).webm
* le titre arrive en premier (\1) et est composé de n'importe quoi (.*)
* le numéro arrive en second (\2) et est composé d'un numéro
* j'aurais pu écrire [0-9]
* je suis une flême: dans notre cas, '.' fait bien l'affaire
* tout le reste (.*), on s'en fout
j'ai donc le motif /^Manipulation - (.*) - Ep 1⧸(.) - .*/
que je veux transformer en \2_\1.webm
ensuite je repasse derrière pour virer les caractères étranges:
s/[ ,]+/_/g
donc si je fais
sed -r '
# afficher le nom actuel
p
# modifier la structure
s!^Manipulation - (.*) - Ep (.).*!\2_\1.webm!
# virer les caractères pourris
s/[ ,]+/_/g
' <<%
…
J'ai une nouvelle liste avec pour chaque épisode:
* nouveau nom
* ancien nom
si je demande à xargs de prendre ces noms 2 par 2 pour les filer
à mv, je fais du renommage de masse:
{ sed -r '
# afficher le nom actuel
p
# modifier la structure
s!^Manipulation - (.*) - Ep (.).*!\2_\1.webm!
# virer les caractères pourris
s/[ ,]+/_/g
' | xargs -d'\n' -n2 mv <<%
…
et tout ça quand tu le fais depuis vim c'est très interactif parceque
chaque étape est du texte que tu peux modifier.
elle est pas belle la vie ?
à nouveau: si je suis allé trop vite, hésite pas à demander :)
cordialement,
marc
Re: Mount Permissions (btrfs subvolumes)
On Sun, Jun 04, 2023 at 11:00:18PM -0400, ce wrote: > On 6/4/23 5:46 PM, Greg Wooledge wrote: > > What kind of hardware is this file system on? > > > > What kind of file system is it? > > > > How did you mount it? (Show the command you used, and any output that > > it produced.) > > > > What does "mount" with no arguments say about the file system? (Hint: > > you can grep for the name of the file system.) > > > > What does the root level of the file system look like in "ls -la"? > > > > What did you EXPECT it to look like? > > sid amd64 with btrfs > > /etc/fstab: > > ``` > LABEL=part2 /mnt/part2 btrfs compress=lzo 0 1 > ``` > > $ ls -l /mnt/part2 > ``` > drwxr-xr-x 1 me root 34 May 01 00:40 @subvolume > ``` > > $ ls -l /mnt/part2/@subvolume > > Some entries have user `me` but most entries have user `fuse`. > > Idk what mount says it's mounted automatically. > > chmod allows changing the group. > > Let's see what a reboot does. OK, thank you for the details. Unfortunately, I know nothing about btrfs, so I can't provide much help beyond this. I can only address this part: > Idk what mount says it's mounted automatically. You can run the command "mount" with no arguments to see the details of each mounted file system. You don't even have to be root. I don't know how btrfs subvolumes work, so I don't know whether they appear in the output of mount, but you could try it and see.
It's that time of the year again
Dear list, [1] came to my attention today. Quoting the most relevant part (emphasis mine): There are still about 100 known RC bugs affecting bookworm, but we have accepted *to release having them included*. Forewarned is forearmed, as they say. [1] https://lists.debian.org/debian-devel-announce/2023/06/msg0.html -- Reco
Re: exim - bad file descriptor
Le 05-06-2023, à 10:50:00 +0200, Michel Verdier a écrit : Le 5 juin 2023 Steve a écrit : if one succeed without message and with code 0, add in /etc/logrotate.d/exim4-base and /etc/logrotate.d/exim4-paniclog postrotate systemctl exim4-base endscript if you add reload but still get the error try restart, I don't know if the reload free the files Since this is a vanilla setup, I might as well uninstall and purge exim4 and re-install it (or postfix), what do you think? Yes I wonder why debian don't add the postrotate. But there is a specific package exim4-config. So you can do dpkg-reconfigure exim4-config Just did that, left unchanged except for the minimize DNS request, which I enabled. you should ask to use syslog and not direct logging I did. it will add log_file_path in config files (you can check after) Now: log_file_path = /var/log/exim4/%slog I only use postfix for me and clients for a long time, so don't ask me : postfix rules :) Maybe another story later… :)
Re: exim - bad file descriptor
Le 5 juin 2023 Steve a écrit : >>if one succeed without message and with code 0, add in >>/etc/logrotate.d/exim4-base and /etc/logrotate.d/exim4-paniclog >> >>postrotate >>systemctl exim4-base >>endscript >> >>if you add reload but still get the error try restart, I don't know if >>the reload free the files > > Since this is a vanilla setup, I might as well uninstall and purge exim4 > and re-install it (or postfix), what do you think? Yes I wonder why debian don't add the postrotate. But there is a specific package exim4-config. So you can do dpkg-reconfigure exim4-config you should ask to use syslog and not direct logging it will add log_file_path in config files (you can check after) I only use postfix for me and clients for a long time, so don't ask me : postfix rules :)
Re: exim - bad file descriptor
Le 05-06-2023, à 10:21:52 +0200, Michel Verdier a écrit : Le 5 juin 2023 Steve a écrit : Merci pour ton aide Michel. De rien :) Let's continue in english for the list Sure. log_file_path = /var/log/exim4/%slog log_selector = +smtp_protocol_error +smtp_syntax_error +tls_certificate_verified +tls_peerdn exim writes directly to the logfiles. If you get the error almost every day it can be because of the rotation. This error appears everyday. I boot my machine every morning at 6 am. I don't know it exim provide a reload command, so try systemctl reload exim4-base systemctl reload exim4-base.service Failed to reload exim4-base.service: Job type reload is not applicable for unit exim4-base.service. systemctl status exim4-base.service ○ exim4-base.service - exim4-base housekeeping Loaded: loaded (/lib/systemd/system/exim4-base.service; static) Active: inactive (dead) TriggeredBy: ● exim4-base.timer Docs: man:exim4(8) it should be exim4-base but if the service is not found type exim and TAB to find the actual service name if it fails try systemctl restart exim4-base I stopped and restarted the service. Now I get: systemctl status exim4-base.service ○ exim4-base.service - exim4-base housekeeping Loaded: loaded (/lib/systemd/system/exim4-base.service; static) Active: inactive (dead) since Mon 2023-06-05 10:29:02 CEST; 35s ago TriggeredBy: ● exim4-base.timer Docs: man:exim4(8) Process: 41181 ExecStart=/etc/cron.daily/exim4-base systemd-timer (code=exited, status=0/SUCCESS) Main PID: 41181 (code=exited, status=0/SUCCESS) CPU: 63ms jun 05 10:29:02 box.lan systemd[1]: Starting exim4-base.service - exim4-base housekeeping... jun 05 10:29:02 box.lan systemd[1]: exim4-base.service: Deactivated successfully. jun 05 10:29:02 box.lan systemd[1]: Finished exim4-base.service - exim4-base housekeeping. if one succeed without message and with code 0, add in /etc/logrotate.d/exim4-base and /etc/logrotate.d/exim4-paniclog postrotate systemctl exim4-base endscript if you add reload but still get the error try restart, I don't know if the reload free the files Since this is a vanilla setup, I might as well uninstall and purge exim4 and re-install it (or postfix), what do you think?
Re: exim - bad file descriptor
Le 5 juin 2023 Steve a écrit : > Merci pour ton aide Michel. De rien :) Let's continue in english for the list > log_file_path = /var/log/exim4/%slog > log_selector = +smtp_protocol_error +smtp_syntax_error > +tls_certificate_verified +tls_peerdn exim writes directly to the logfiles. If you get the error almost every day it can be because of the rotation. I don't know it exim provide a reload command, so try systemctl reload exim4-base it should be exim4-base but if the service is not found type exim and TAB to find the actual service name if it fails try systemctl restart exim4-base if one succeed without message and with code 0, add in /etc/logrotate.d/exim4-base and /etc/logrotate.d/exim4-paniclog postrotate systemctl exim4-base endscript if you add reload but still get the error try restart, I don't know if the reload free the files
Re: problem with local DNS
On Mon, 05 Jun 2023 08:49:11 +0200
Michel Verdier wrote:
Hello Michel,
>I already answered to your problem :
I suspect OP is of the belief that we will respond to them directly and,
as a consequence, they are not reading the list.
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately apparent"
/ _)rad "Is it only me that has a working delete key?"
Well I don't want you to think I'm being obscene
Fish - The Damned
pgpwHys5EQi9m.pgp
Description: OpenPGP digital signature
Re: exim - bad file descriptor
Le 05-06-2023, à 09:09:05 +0200, Michel Verdier a écrit :
Le 5 juin 2023 Steve a écrit :
Yes, nothing is done after rotation. But I don't remember the default
exim logging mechanism. Can you provide
grep -r log_file_path /etc/exim*
This gives nothing.
Then can you provide
exim -bP
(snip ip adresses if you want)
See attached file.
Merci pour ton aide Michel.
accept_8bitmime
acl_not_smtp =
acl_not_smtp_start =
acl_smtp_auth =
acl_smtp_connect =
acl_smtp_data = acl_check_data
acl_smtp_data_prdr = accept
acl_smtp_dkim =
acl_smtp_etrn =
acl_smtp_expn =
acl_smtp_helo =
acl_smtp_mail = acl_check_mail
acl_smtp_mailauth =
acl_smtp_notquit =
acl_smtp_predata =
acl_smtp_quit =
acl_smtp_rcpt = acl_check_rcpt
acl_smtp_starttls =
acl_smtp_vrfy =
add_environment =
admin_groups =
no_allow_domain_literals
no_allow_mx_to_ip
no_allow_utf8_domains
auth_advertise_hosts = *
auto_thaw = 0s
bi_command =
bounce_message_file =
bounce_message_text =
bounce_return_body
bounce_return_linesize_limit = 998
bounce_return_message
bounce_return_size_limit = 100K
bounce_sender_authentication =
callout_domain_negative_expire = 3h
callout_domain_positive_expire = 1w
callout_negative_expire = 2h
callout_positive_expire = 1d
callout_random_local_part = $primary_hostname-$tod_epoch-testing
check_log_inodes = 100
check_log_space = 10M
check_rfc2047_length
check_spool_inodes = 100
check_spool_space = 10M
chunking_advertise_hosts = *
no_commandline_checks_require_admin
daemon_smtp_ports = smtp
daemon_startup_retries = 9
daemon_startup_sleep = 30s
no_debug_store
delay_warning = 1d
delay_warning_condition = ${if or {{
!eq{$h_list-id:$h_list-post:$h_list-subscribe:}{} }{
match{$h_precedence:}{(?i)bulk|list|junk} }{
match{$h_auto-submitted:}{(?i)auto-generated|auto-replied} }} {no}{yes}}
no_deliver_drop_privilege
deliver_queue_load_max =
delivery_date_remove
no_disable_ipv6
dkim_verify_hashes = sha256:sha512
dkim_verify_keytypes = ed25519:rsa
dkim_verify_min_keysizes = rsa=1024 ed25519=250
no_dkim_verify_minimal
dkim_verify_signers = $dkim_signers
dns_again_means_nonexist =
dns_check_names_pattern = (?i)^(?>(?(1)\.|())[^\W](?>[a-z0-9/_-]*[^\W])?)+(\.?)$
dns_cname_loops = 1
dns_csa_search_limit = 5
dns_csa_use_reverse
dns_dnssec_ok = 1
dns_ipv4_lookup =
dns_retrans = 0s
dns_retry = 0
dns_trust_aa =
dns_use_edns0 = -1
no_drop_cr
dsn_advertise_hosts =
dsn_from = Mail Delivery System
envelope_to_remove
errors_copy =
errors_reply_to =
event_action =
exim_group = Debian-exim
exim_path = /usr/sbin/exim4
exim_user = Debian-exim
exim_version = 4.96
extra_local_interfaces =
extract_addresses_remove_arguments
finduser_retries = 0
freeze_tell = postmaster
gecos_name = $1
gecos_pattern = ^([^,:]*)
no_gnutls_allow_auto_pkcs11
no_gnutls_compat_mode
header_line_maxsize = 0
header_maxsize = 1048576
headers_charset = UTF-8
helo_accept_junk_hosts =
helo_allow_chars =
helo_lookup_domains = @ : @[]
helo_try_verify_hosts =
helo_verify_hosts =
hold_domains =
host_lookup = *
host_lookup_order = bydns:byaddr
host_reject_connection =
hosts_connection_nolog =
hosts_require_alpn =
hosts_require_helo = *
hosts_treat_as_local =
ignore_bounce_errors_after = 2d
ignore_fromline_hosts =
no_ignore_fromline_local
keep_environment =
keep_malformed = 4d
no_local_from_check
local_from_prefix =
local_from_suffix =
local_interfaces = <; 127.0.0.1 ; ::1
local_scan_path =
local_scan_timeout = 5m
local_sender_retain
localhost_number =
log_file_path = /var/log/exim4/%slog
log_selector = +smtp_protocol_error +smtp_syntax_error
+tls_certificate_verified +tls_peerdn
no_log_timezone
lookup_open_max = 25
max_username_length = 0
no_message_body_newlines
message_body_visible = 500
message_id_header_domain =
message_id_header_text =
message_logs
message_size_limit = 50M
no_move_frozen_messages
no_mua_wrapper
never_users =
notifier_socket = $spool_directory/exim_daemon_notify
openssl_options =
percent_hack_domains =
pid_file_path = /run/exim4/exim.pid
pipelining_advertise_hosts = *
pipelining_connect_advertise_hosts = *
prdr_enable
no_preserve_message_logs
primary_hostname = box.lan
no_print_topbitchars
process_log_path = /var/spool/exim4/exim-process.info
prod_requires_admin
qualify_domain = box.lan
qualify_recipient = box.lan
queue_domains =
no_queue_fast_ramp
queue_list_requires_admin
no_queue_only
queue_only_file =
queue_only_load =
queue_only_load_latch
queue_only_override
no_queue_run_in_order
queue_run_max = 5
queue_smtp_domains =
receive_timeout = 0s
received_header_text = Received: ${if def:sender_rcvhost {from
$sender_rcvhost\n\t}{${if def:sender_ident {from
${quote_local_part:$sender_ident} }}${if def:sender_helo_name
{(helo=$sender_helo_name)\n\tby $primary_hostname ${if
def:received_protocol {with $received_protocol }}${if def:tls_in_ver{
($tls_in_ver)}}${if def:tls_in_cipher_std { tls $tls_in_cipher_std\n\t}}(Exim
$version_number)\n\t${if def:sender_address {(envelope-from
<$sender_address>)\n\t}}id
Re: exim - bad file descriptor
Le 5 juin 2023 Steve a écrit : >>Yes, nothing is done after rotation. But I don't remember the default >>exim logging mechanism. Can you provide >> >>grep -r log_file_path /etc/exim* > > This gives nothing. Then can you provide exim -bP (snip ip adresses if you want)
Re: Fwd: problem with local DNS
Le 5 juin 2023 Maureen L. Thomas a écrit : > Forwarded Message > Subject: problem with local DNS > > I am using a Lonova all in one computer with the latest debian on it. > Bullseye is working fine except for the warning I get as follows: your > current proxy settings do not allow local DNS req > (network.proxy.socks_remote)dns). I already answered to your problem : > I suppose this message is from firefox and is about > network.proxy.socks_remote_dns. If so look at > > https://superuser.com/questions/103593/how-to-do-dns-through-a-proxy-in-firefox Did you read and follow this link ?
Re: exim - bad file descriptor
Le 04-06-2023, à 19:11:57 +0200, Michel Verdier a écrit : Le 4 juin 2023 Steve a écrit : Does this help? Yes, nothing is done after rotation. But I don't remember the default exim logging mechanism. Can you provide grep -r log_file_path /etc/exim* This gives nothing.
