Backup ... men hvordan
Kære Alle Hvordan bakker i op? Tidligere har jeg bakket op med rsync skripts. Men nu har jeg tænkt mig at bruge rdiff-backup og mariabackup. Det er sådan set nemt nok. Bortset fra at mariabackup får en til at tænke over hvad man skal med f.eks. 2 års backup bestående af 730 mapper der alle linker tilbage til den forrige incrementelle backup og til sidst til den oprindelige full backup - og det forkommer også at være en ret sårbar backup. Et lignende problem er der vel også med rdiff-backup. Nu er jeg nok ikke den første der har tænkt på dette ;-) Alligevel har jeg ledt forgæves efter relevante skrifts o. lign. på nettet. Hvad gør I? Flemming PS: Jeg er indtil videre tilfreds med contabo.com: 60 kr/md for 300 MB debian 11 VPS med ganske meget ram og cpu. Supporten er ret hjælpsom, og jeg har ikke noget at udsætte på den. Jeg havde dog et seriøst problem. Jeg havde løbende lavet bakop af /etc, og da noget var gået galt, ville jeg lige gå et par dage tilbage, og så purgede jeg relevante programpakker. Og så slettede jeg lige (med hovedet under armen) /etc og erstattede den med en 2 dage gammel /etc. Det skulle jeg ikke have gjort, for så kunne jeg ikke genstarte. Det var noget med at boot-processen ikke kunne finde min virtuelle harddisk. Jeg (gennem VNC) og supporten prøvede at forklare fstab at den skulle bare bruge min virtuelle harddisk, men det ville den ikke høre tale om. Det syntes hurtigt lettere at starte forfra og resette debian. Og jeg vidste jo faktisk godt at jeg netop ikke kunne regne med at bare kunne kopiere hele en gammel version af /etc.
lists | Business clients
Hi lists, I understand that you are a Certified Partner of Veeam, Would you like to connect with Key Decision Makers from companies currently using Veeam Software? The contacts were verified & updated last month for all marketing initiatives. Do let us know your current focus as requested below and I shall revert back with the volume of contacts, samples and a quote for your review; Target Technology:?, Target Job Titles:_?, Target Geography:___? Look forward to your feedback. Thanks & Regards, Gary Wozniak Business Development
latest testing update broke my laptop
My laptop no longer boots thanks to the latest update. It stops after I select a normal boot - it goes to the text mode console and displays an error message about: [ 0.717939] ACPI BIOS Error (bug). If I go into recovery mode, I don't get that error but then it stops after a message about the nouveau driver. I never get to a command prompt. I can boot from System Rescus CD. I get the same BIOS error message but then it continues on as if it wasn't important. I tried updating the BIOS but that did nothing to resolve the problem. I did a reinstall and the problem survives. The problem actually started earlier in the day, when I did the apt full-upgrade. It updated the nvidia drivers so it wanted a reboot. When I rebooted, it refused to start sddm. It just sat there. I rebooted into recovery mode and changed to lightdm, which did the same thing. Gdm3 actually switched into a graphics mode before hanging. I purged the nvidia drivers and that was when the message cropped up. I tried booting from system rescue cd then switching into a bash shell on my / partition but lost my DNS so I couldn't (re) install the nouveau drivers (didn't want to touch the nvidia ones again). I did try updating initramfs, in case there was some nvidia stuff hanging around but it didn't help. That led to me reinstalling. I copied the Bookworm netinst to my Ventoy USB stick, but it wouldn't boot so I went back to Bullseye - which installed but wouldn't bring up a GUI. Booted to recovery mode, brought up the network and upgraded to Bookworm. That is where I am now - with the error message appearing after I leave the boot menu. This is basically clean install - just done in two parts. My laptop had been running fine since I got it and installed Debian.
Re: kernels in testing (was: Re: Debian failed)
On Fri, Dec 16, 2022 at 2:05 PM songbird wrote: > Timothy M Butterworth wrote: > ... > > Testing and Sid track pretty close to the latest kernel releases. Testing > > currently has version 6.0.10. New kernel versions are first uploaded to > Sid > > then after about a week they are uploaded to testing. Testing, when not > in > > freeze, is more like a rolling distro than a stable distro. > > yes, and i've had very few problems with it for a long time, > but i still also keep a bootable stable partition because when > you need something to work for sure it is better than trying to > fix testing quickly > I'm currently running on testing. I have to in order to get my HDMI Audio to work. I have stable on my media center PC. I have had more problems with stable than with testing. Elisa on stable crashes when there is a large number of songs or multiple cd's in an album. Elisa on Testing works just fine with no issues. I like testing and surprisingly it does not get that many updates. I had openSUSE Tumbleweed rolling installed and there were hundreds of updates every day and they were not all using delta-RPM. > > songbird > > -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
Re: apt update fails due to Label and Version changes for buster security
On 2022-12-16 13:00, Tim Woodall wrote: Thanks Tim, I will root around in the docs a little more. Strange because I've done multiple updates since your last backup date of Dec 2nd and not had this issue. H. -- Regards, John Boxall
Re: Dell Precision 3570 - Debian instead of Ubuntu
On Fri, 2022-12-16 at 18:12 +0100, B.M. wrote: > Hi, > > The new laptop just arrived and I had a first look what the people > did > at Dell or Canonical: > > After switching it on the first time, I was asked to enter > / configure > WLAN, username, password, hostname, keyboard layout, time zone. It > also > let me create a recovery USB stick. After a reboot I now could just > use > it. But of course I had a look behind the scenes...: > > It came with Ubuntu 20.04.4 LTS and Gnome 3.36.8 running on X11. > > The internal disk is formatted as > - 891 MB EFI mounted at /boot/efi > - 8.6 GB FAT not mounted, disks reports it as "Microsoft Reserved" > - 503 GB Ext4 Root Partition > > The USB stick I used as recovery medium got formatted as > - 4 GB 0x00 (Bootable) ISO 9660 mounted at > /media//DellRecoveryMedia > - 4.1 MB EFI FAT not mounted > - and some GB free space > > After installing Synaptic I found out that there are some more > Origins > with installed packages as listed here: > local/main (dell.archive.canonical.com): > oem-fix-misc-cnl-tlp-estar-conf, 5.0.3.4, maintainer > commercial.engineering(at)canonical.com: > This package carrys agressive policy to pass energy-star, and > also > some blacklist for problematic devices > oem-somerville-factory-meta, 20.04ubuntu9, maintainer > commercial.engineering(at)canonical.com: > It installs packages needed to support this hardware fully. > oem-somerville-factory-paras-35-meta, 20.04ubuntu3, maintainer > commercial.engineering(at)canonical.com: > It installs packages needed to support this hardware fully. > (factory) > oem-somerville-meta, 20.04ubuntu9, maintainer > commercial.engineering(at)canonical.com: > This is a metapackage for Somerville platform. It installs > packages > needed to support this hardware fully. > oem-somerville-paras-35-meta, 20.04ubuntu3, maintainer > commercial.engineering(at)canonical.com: > This is a metapackage for Somerville Paras-35 platform. It > installs > packages needed to support this hardware fully. > oem-somerville-partner-archive-keyring, 20.04ubuntu2, maintainer > commercial.engineering(at)canonical.com: > Somerville project keyring. > local/universe (dell.archive.canonical.com): > tlp, 1.3.1-2, maintainer ubuntu-devel-discuss(at)lists.ubuntu.com: > Save battery power on laptops > (Description) > tlp-rdw, 1.3.1-2, maintainer ubuntu-devel- > discuss(at)lists.ubuntu.com: > Radio device wizard > (Description) > focal/universe (dell.archive.canonical.com): > tlp, 1.3.1-2, maintainer ubuntu-devel-discuss(at)lists.ubuntu.com: > tlp-rdw, 1.3.1-2, maintainer ubuntu-devel- > discuss(at)lists.ubuntu.com: > stable/main (dl.google.com): > google-chrome-stable is installed > > Now my thoughts are: > - Chrome not necessary... > - tlp, tlp-rdw: also in Debian Testing (Bookworm), but with higher > version number (1.5.0-1), but also with a different maintainer > (raphael.hal...@gmail.com) > oem-fix-misc-cnl-tlp-estar-conf: does it make sense to keep this > package? > oem-somerville-*: could make sense to keep... > > --> Can I re-install these packages after installing Debian Testing > by > adding and enabling these Dell repositories? > > Under /etc/apt/trusted.gpg.d/ there are some files that might be > corresponding to these repos and maybe I should keep them: > ubuntu-keyring-2008-oem.gpg > ubuntu-keyring-2008-oem.key.gpg > ubuntu-keyring-2020-oem.gpg > > and under /etc/apt/sources.list.d/ there are: > focal-oem.list > oem-somerville-paras-35-meta.list > > But: as far as I remember, one should not mix Debian packages /repos > with Ubuntu packages / repos, but I might work. > > What do you think? > > (Of course I could just keep it as it is, but I'd prefer having a > Debian-only setup in our family across all devices.) > > (Fun fact also mentioned: on the Dell website for the laptop there is > a > Q section where is stated that the laptop comes without any OS pre- > installed but one could install Ubuntu on it while when asking their > chat the answer was that it's not allowed to sell computers without > any > OS installed (at least here in Switzerland)...) > > Have a nice day, > Bernd > > > PS: Please add me CC since I'm currently not subscribed to this list. > Thanks. > Hi again, Looking a bit further, it seems that all these packages are not containing more than 3 config files within /etc/tlp.d/ And the tlp and tlp-rdw packages itself. Does someone have an idea what it means that these packages have higher version numbers in Debian Testing but a different maintainer (see my last mail)? Going back in the Debian changelog file there hasn't been a change in the maintainer, i.e. I have to assume that the packages are not identical? Should/could I compare their config files? Thank you and have a nice day, Bernd
Re: kernels in testing (was: Re: Debian failed)
Timothy M Butterworth wrote: ... > Testing and Sid track pretty close to the latest kernel releases. Testing > currently has version 6.0.10. New kernel versions are first uploaded to Sid > then after about a week they are uploaded to testing. Testing, when not in > freeze, is more like a rolling distro than a stable distro. yes, and i've had very few problems with it for a long time, but i still also keep a bootable stable partition because when you need something to work for sure it is better than trying to fix testing quickly. songbird
Re: apt update fails due to Label and Version changes for buster security
On Fri, 16 Dec 2022, Tim Woodall wrote: On Fri, 16 Dec 2022, Tim Woodall wrote: On Thu, 15 Dec 2022, John Boxall wrote: The following happened just now when updating my Buster system: + apt update Hit:1 http://deb.debian.org/debian buster InRelease Get:2 http://security.debian.org/debian-security buster/updates InRelease [34.8 kB] Hit:3 http://dl.google.com/linux/chrome/deb stable InRelease Hit:4 http://deb.debian.org/debian buster-updates InRelease E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Label' value from 'Debian' to 'Debian-Security' N: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Version' value from '10.13' to '10' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. Do you want to accept these changes and continue updating from this repository? [y/N] n Hit:5 https://download.virtualbox.org/virtualbox/debian buster InRelease Hit:6 https://updates.signal.org/desktop/apt xenial InRelease Reading package lists... Done E: Failed to fetch http://security.debian.org/debian-security/dists/buster/updates/InRelease E: Some index files failed to download. They have been ignored, or old ones used instead. - I didn't have this issue about four hours ago. Does anyone have any ideas? I think there's an apt option APT::AllowReleaseInfoChange (or soemthing very similar). Check /usr/share/doc/apt/examples/configure.gz Sorry, don't remember the exact setting nor the exact file to check for it off the top of my head. Having said that, I don't have this issue (yet...) Hmmm: Origin: Debian Label: Debian-Security Suite: oldstable Version: 10 Codename: buster Date: Fri, 16 Dec 2022 09:35:11 UTC So I do have these values. But I didn't get any alert that they had changed. Sorry for the separate messages, I should have done all this before I posted. The oldest backup I have available online is from 2nd December and it hasn't changed: Origin: Debian Label: Debian-Security Suite: oldstable Version: 10 Codename: buster Date: Fri, 02 Dec 2022 21:33:08 UTC I'm not going to go digging through my old offline backups to see if/when this was different. But it's not something that changed recently. Tim.
Re: apt update fails due to Label and Version changes for buster security
On Fri, 16 Dec 2022, Tim Woodall wrote: On Thu, 15 Dec 2022, John Boxall wrote: The following happened just now when updating my Buster system: + apt update Hit:1 http://deb.debian.org/debian buster InRelease Get:2 http://security.debian.org/debian-security buster/updates InRelease [34.8 kB] Hit:3 http://dl.google.com/linux/chrome/deb stable InRelease Hit:4 http://deb.debian.org/debian buster-updates InRelease E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Label' value from 'Debian' to 'Debian-Security' N: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Version' value from '10.13' to '10' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. Do you want to accept these changes and continue updating from this repository? [y/N] n Hit:5 https://download.virtualbox.org/virtualbox/debian buster InRelease Hit:6 https://updates.signal.org/desktop/apt xenial InRelease Reading package lists... Done E: Failed to fetch http://security.debian.org/debian-security/dists/buster/updates/InRelease E: Some index files failed to download. They have been ignored, or old ones used instead. - I didn't have this issue about four hours ago. Does anyone have any ideas? I think there's an apt option APT::AllowReleaseInfoChange (or soemthing very similar). Check /usr/share/doc/apt/examples/configure.gz Sorry, don't remember the exact setting nor the exact file to check for it off the top of my head. Having said that, I don't have this issue (yet...) Hmmm: Origin: Debian Label: Debian-Security Suite: oldstable Version: 10 Codename: buster Date: Fri, 16 Dec 2022 09:35:11 UTC So I do have these values. But I didn't get any alert that they had changed. Tim.
Re: apt update fails due to Label and Version changes for buster security
On Thu, 15 Dec 2022, John Boxall wrote: The following happened just now when updating my Buster system: + apt update Hit:1 http://deb.debian.org/debian buster InRelease Get:2 http://security.debian.org/debian-security buster/updates InRelease [34.8 kB] Hit:3 http://dl.google.com/linux/chrome/deb stable InRelease Hit:4 http://deb.debian.org/debian buster-updates InRelease E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Label' value from 'Debian' to 'Debian-Security' N: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Version' value from '10.13' to '10' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. Do you want to accept these changes and continue updating from this repository? [y/N] n Hit:5 https://download.virtualbox.org/virtualbox/debian buster InRelease Hit:6 https://updates.signal.org/desktop/apt xenial InRelease Reading package lists... Done E: Failed to fetch http://security.debian.org/debian-security/dists/buster/updates/InRelease E: Some index files failed to download. They have been ignored, or old ones used instead. - I didn't have this issue about four hours ago. Does anyone have any ideas? I think there's an apt option APT::AllowReleaseInfoChange (or soemthing very similar). Check /usr/share/doc/apt/examples/configure.gz Sorry, don't remember the exact setting nor the exact file to check for it off the top of my head. Having said that, I don't have this issue (yet...) Tim.
Re: Ma console ne sait pas effacer correctement un e accentué.
Bonjour Olivier, Pour ce qui est du problème avec les caractères accentués, est-ce que le paquet locales ont été configurées pour compiler au moins un environnement gérant l'unicode ? $ sudo dpkg-reconfigure locales Si non, il faut sélectionner une langue en mode UTF-8 (par exemple fr_FR.UTF-8 ou en_US.UTF-8) puis sélectionne une valeur de LANG par défaut (fr_FR.UTF-8, C.UTF-8, etc). La reconfiguration va compiler les données pour les locales sélectionnées et régler les variables d'environnement de manière adéquate, et peut-être que c'est l'étape de compilation qui a manqué jusqu'ici ? Je n'ai pas regardé de près comment gérer cette configuration en preseed (j'utilise FAI[1], qui est un outil d'installation via PXE très puissant dès que le nombre de machines et de configurations à installer devient excessivement élevé). [1] : https://fai-project.org/ En espérant que ça aide, -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/1, please excuse my verbosity. On air: Happy Family - Animal Spirit signature.asc Description: PGP signature
Re: Debian failed
On Thu, 15 Dec 2022 22:35:04 -0600 George Olson wrote: > I had enough of a functional > graphics environment and terminal to change all my sources to > Testing, which goes by the codename Bookworm, because to me that was > easier than trying to figure out how to use backports to install a > newer kernel. It isn't hard to use backports. Backports strikes me as much less problematic than testing. https://backports.debian.org/Instructions/ -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: Dell Precision 3570 - Debian instead of Ubuntu
Hi, The new laptop just arrived and I had a first look what the people did at Dell or Canonical: After switching it on the first time, I was asked to enter / configure WLAN, username, password, hostname, keyboard layout, time zone. It also let me create a recovery USB stick. After a reboot I now could just use it. But of course I had a look behind the scenes...: It came with Ubuntu 20.04.4 LTS and Gnome 3.36.8 running on X11. The internal disk is formatted as - 891 MB EFI mounted at /boot/efi - 8.6 GB FAT not mounted, disks reports it as "Microsoft Reserved" - 503 GB Ext4 Root Partition The USB stick I used as recovery medium got formatted as - 4 GB 0x00 (Bootable) ISO 9660 mounted at /media//DellRecoveryMedia - 4.1 MB EFI FAT not mounted - and some GB free space After installing Synaptic I found out that there are some more Origins with installed packages as listed here: local/main (dell.archive.canonical.com): oem-fix-misc-cnl-tlp-estar-conf, 5.0.3.4, maintainer commercial.engineering(at)canonical.com: This package carrys agressive policy to pass energy-star, and also some blacklist for problematic devices oem-somerville-factory-meta, 20.04ubuntu9, maintainer commercial.engineering(at)canonical.com: It installs packages needed to support this hardware fully. oem-somerville-factory-paras-35-meta, 20.04ubuntu3, maintainer commercial.engineering(at)canonical.com: It installs packages needed to support this hardware fully. (factory) oem-somerville-meta, 20.04ubuntu9, maintainer commercial.engineering(at)canonical.com: This is a metapackage for Somerville platform. It installs packages needed to support this hardware fully. oem-somerville-paras-35-meta, 20.04ubuntu3, maintainer commercial.engineering(at)canonical.com: This is a metapackage for Somerville Paras-35 platform. It installs packages needed to support this hardware fully. oem-somerville-partner-archive-keyring, 20.04ubuntu2, maintainer commercial.engineering(at)canonical.com: Somerville project keyring. local/universe (dell.archive.canonical.com): tlp, 1.3.1-2, maintainer ubuntu-devel-discuss(at)lists.ubuntu.com: Save battery power on laptops (Description) tlp-rdw, 1.3.1-2, maintainer ubuntu-devel- discuss(at)lists.ubuntu.com: Radio device wizard (Description) focal/universe (dell.archive.canonical.com): tlp, 1.3.1-2, maintainer ubuntu-devel-discuss(at)lists.ubuntu.com: tlp-rdw, 1.3.1-2, maintainer ubuntu-devel- discuss(at)lists.ubuntu.com: stable/main (dl.google.com): google-chrome-stable is installed Now my thoughts are: - Chrome not necessary... - tlp, tlp-rdw: also in Debian Testing (Bookworm), but with higher version number (1.5.0-1), but also with a different maintainer (raphael.hal...@gmail.com) oem-fix-misc-cnl-tlp-estar-conf: does it make sense to keep this package? oem-somerville-*: could make sense to keep... --> Can I re-install these packages after installing Debian Testing by adding and enabling these Dell repositories? Under /etc/apt/trusted.gpg.d/ there are some files that might be corresponding to these repos and maybe I should keep them: ubuntu-keyring-2008-oem.gpg ubuntu-keyring-2008-oem.key.gpg ubuntu-keyring-2020-oem.gpg and under /etc/apt/sources.list.d/ there are: focal-oem.list oem-somerville-paras-35-meta.list But: as far as I remember, one should not mix Debian packages /repos with Ubuntu packages / repos, but I might work. What do you think? (Of course I could just keep it as it is, but I'd prefer having a Debian-only setup in our family across all devices.) (Fun fact also mentioned: on the Dell website for the laptop there is a Q section where is stated that the laptop comes without any OS pre- installed but one could install Ubuntu on it while when asking their chat the answer was that it's not allowed to sell computers without any OS installed (at least here in Switzerland)...) Have a nice day, Bernd PS: Please add me CC since I'm currently not subscribed to this list. Thanks. On Mon, 2022-11-28 at 10:04 +0100, B.M. wrote: > Hi, > > I'm going to buy a Dell Precision 3570 laptop in the next couple of > weeks. > Since it's a Build Your Own device, I can order it with Ubuntu 20.04 > LTS pre- > installed instead of paying for an never used Win 11 :-) > > Since all our other computers are happily running Debian, I'd like to > replace > this Ubuntu by Debian Testing (later Bookworm). I've already decided > to run it > on a single btrfs partition and learn something about subvolumes... I > assume > the machine should work well - but who knows? How would you proceed? > > a) leave it running Ubuntu forever > b) replace Ubuntu by Debian, fiddling around issues if there are any > later > c) resize the partition, install Debian side-by-side, check than if > anything > works as expected > d) analyze the installed system (how?) to find out any special > configs etc. > before replacing Ubuntu by Debian > e) other... > >
Re: Ma console ne sait pas effacer correctement un e accentué.
Olivier, on 2022-12-16: > En comparant le contenu de /etc/default/console-setup, je ne vois pas > de différence ou d'anomalie: > > # cat /etc/default/console-setup > # CONFIGURATION FILE FOR SETUPCON > # Consult the console-setup(5) manual page. > ACTIVE_CONSOLES="/dev/tty[1-6]" > CHARMAP="UTF-8" > CODESET="Lat15" Pour ce que ça vaut, je m'en tiens au CODESET="guess", mais ça ne devrait de toutes façons pas affecter les connexions ssh, donc le problème est ailleurs. > FONTFACE="Fixed" > FONTSIZE="8x16" > VIDEOMODE= > # The following is an example how to use a braille font > # FONT='lat9w-08.psf.gz brl-8x8.psf' -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/1, please excuse my verbosity. On air: Opeth - Hjartat Vet Vad Handen Gor signature.asc Description: PGP signature
Re: Ma console ne sait pas effacer correctement un e accentué.
1. sur la machine "qui ne marche pas", la variable LC_ALL n'est pas définie. En la valorisant à C, les caractères é ne s'affichent plus. 2. sur la machine "qui marche pas", la variable LC_ALL n'est pas définie. 3. en lançant un deuxième /bin/bash, ça ne fonctionne pas mieux sur la machine "qui ne marche pas" 4. en lançant un /bin/dash, sur la machine "qui ne marche pas": tout fonctionne (affichage ou effacement de é) 5. sur la machine "qui ne marche pas", la saisie de fonctionne normalement Le ven. 16 déc. 2022 à 16:02, JARRIGE Virgile (DNUM) a écrit : > > Bonjour, > > Il semble que vous ayez un problème de configuration de la console de votre > système. Le message d'erreur indique que la commande exit n'a pas été trouvée > par le shell, alors que vous essayiez simplement de quitter la session en > cours. Cela peut être causé par un problème de configuration du codage de > caractères de la console, qui pourrait entraîner une interprétation > incorrecte des caractères que vous tapez au clavier. > > Pour résoudre ce problème, voici quelques étapes à suivre : > > Vérifiez que la configuration de la console spécifiée dans le fichier > /etc/default/console-setup est correcte. Assurez-vous que le paramètre > CHARMAP est correctement défini sur "UTF-8" et que le paramètre CODESET est > défini sur "Lat15", qui est le jeu de caractères latin utilisé par défaut > dans les distributions Debian. > > Vérifiez que le fichier de configuration du shell que vous utilisez (par > exemple .bashrc ou .bash_profile) contient la ligne suivante : > > export LC_ALL=C > > Cela permet de définir le jeu de caractères par défaut du shell sur le jeu de > caractères ASCII, qui devrait être compatible avec tous les claviers. > > Vérifiez que vous utilisez bien un clavier compatible avec le jeu de > caractères UTF-8. Si vous utilisez un clavier physique, assurez-vous qu'il > est configuré correctement dans le BIOS de la machine. Si vous utilisez un > clavier virtuel via SSH, vérifiez que vous utilisez un client SSH compatible > avec le jeu de caractères UTF-8. > > Si le problème persiste, vous pouvez essayer de réinitialiser la > configuration de la console en exécutant la commande suivante : > > sudo dpkg-reconfigure console-setup > > Cela vous permettra de reconfigurer les paramètres de la console à l'aide de > l'interface graphique de configuration de Debian. > > J'espère que ces suggestions vous aideront à résoudre votre problème de > configuration de la console. > > Bonne journée, > > Virgile > > - Mail original - > > De: "Olivier" > > À: "ML Debian User French" > > Envoyé: Vendredi 16 Décembre 2022 15:04:00 > > Objet: Ma console ne sait pas effacer correctement un e accentué. > > > Bonjour, > > > > Je patauge dans mes premières configuration PXE/Preseed. > > Ma cible est l'installation de serveurs "headless" sous Bullseye. > > > > À ce stade, j'arrive à installer un système minimal fonctionnel. > > Le seul truc qui ne marche pas parfaitement, c'est la console. > > > > Que ce soit en SSH ou avec un clavier USB directement connecté à la > > machine, je constate l'anomalie suivante: > > > > - je tape au clavier les caractères <é> > > - la machine m'affiche : > > -bash: $'\303exit' : commande introuvable > > - j'attendais qu'elle quitte simplement la session en cours. > > > > En comparant le contenu de /etc/default/console-setup, je ne vois pas > > de différence ou d'anomalie: > > > > # cat /etc/default/console-setup > > # CONFIGURATION FILE FOR SETUPCON > > # Consult the console-setup(5) manual page. > > ACTIVE_CONSOLES="/dev/tty[1-6]" > > CHARMAP="UTF-8" > > CODESET="Lat15" > > FONTFACE="Fixed" > > FONTSIZE="8x16" > > VIDEOMODE= > > # The following is an example how to use a braille font > > # FONT='lat9w-08.psf.gz brl-8x8.psf' > > > > Comment corriger ? > > > > Slts
Re: kernels in testing (was: Re: Debian failed)
On Fri, Dec 16, 2022 at 8:01 AM wrote: > On Thursday, December 15, 2022 11:35:04 PM George Olson wrote: > > I have an RX 6600 XT also. I use a 4 monitor setup and had to configure > > things so that it would work with 2 on top and 2 on the bottom. I can't > > remember exactly how I did it, but I first installed Bullseye and > > figured out it wasn't going to work. I had enough of a functional > > graphics environment and terminal to change all my sources to Testing, > > which goes by the codename Bookworm, because to me that was easier than > > trying to figure out how to use backports to install a newer kernel. > > From the peanut gallery (I almost always run with the default kernel in > whatever distro I'm using), I'm guessing that if the only thing you > installed > from Testing was a kernel, that would be fairly stable. (I imagine (but > don't > know) that when kernels get to testing they have been tested fairly well, > even > before showing up in Debian. > Testing and Sid track pretty close to the latest kernel releases. Testing currently has version 6.0.10. New kernel versions are first uploaded to Sid then after about a week they are uploaded to testing. Testing, when not in freeze, is more like a rolling distro than a stable distro. > > Once I got that running, it has basically been going without a hitch. > > Testing seems to be almost as stable as regular Debian Bullseye like I > > have on my laptop. I haven't run into any major snags yet. > > -- > rhk > > (sig revised 20221206) > > If you reply: snip, snip, and snip again; leave attributions; avoid HTML; > avoid top posting; and keep it "on list". (Oxford comma (and semi-colon) > included at no charge.) If you revise the topic, change the Subject: > line. > If you change the topic, start a new thread. > > Writing is often meant for others to read and understand (legal documents > excepted?) -- make it easier for your reader by various means, including > liberal use of whitespace (short paragraphs, separated by whitespace / > blank > lines) and minimal use of (obscure?) jargon, abbreviations, acronyms, and > references. > > If someone has already responded to a question, decide whether any > response > you add will be helpful or not ... > > A picture is worth a thousand words. A video (or "audio"): not so much -- > divide by 10 for each minute of video (or audio) or create a transcript > and > edit it to 10% of the original. > > A speaker who uses ahhs, ums, or such may have a real physical or mental > disability, or may be showing disrespect for his listeners by not properly > preparing in advance and thinking before speaking. (Remember Cicero who > did > not have enough time to write a short missive.) (That speaker might have > been > "trained" to do this by being interrupted often if he pauses.) > > A radio (or TV) station which broadcasts speakers with high pitched voices > (or > very low pitched / gravelly voices) (which older people might not be able > to > hear properly) disrespects its listeners. Likewise if it broadcasts > extraneous or disturbing sounds (like gunfire or crying), or broadcasts > speakers using their native language (with or without an overdubbed > translation). > > A person who writes a sig this long probably has issues and disrespects > (and > offends) a large number of readers. ;-) > ' > > -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
Re: Debian failed
On 2022-12-15 08:36 hw wrote: It turned out that the AMD card is not even an option anymore because it's built so badly that not only the height but also the width exceeds the slot size. It's a few millimeters too wide and as a result, the fans won't spin and the card overheats. That doesn't means it's built badly, but it simply doesn't fit your needs. I'm pretty sure higher end NVidias typically are even built more badly in this regard. I doubt you will add in here to call them "built badly". That's like with: Debian needs to fix that. ... or ... obviously not ... or not with Debian Your expectation is not a general rule. If your hardware needs more recent Kernel and Mesa, Debian Stable is simply not the best distribution to choose for your* Desktop. It doesn't mean Debian stable is built badly, it simply doesn't fit your needs. But that's ok. There are many alternatives. Use Debian testing or some other more bleeding edge distribution like Fedora. Btw: Why not choose RHEL? Typically this is - like Debian stable - not to be expected to run on more recent hardware but currently RHEL 9 is quite new and it should support the RX 6000 series (besides the fact that you came to the conclusion not to use the RX 6600 at all). On my gaming-PC I'm running Arch Linux. Even more bleeding edge than Fedora (I think). I'm using a modern AMD card in there and I'd say that's much more straight forward than using NVidia hardware (no extra driver needed) - YMMV. *) To be clear, your individual case doesn't count for a general rule. As a counterexample I'm writing this message on a modern 2in1 flip/tablet Laptop running Debian Stable and Gnome via Wayland for modern features like auto-screen-rotation and auto-on-screen Keyboards. Works. hede
Re: Ma console ne sait pas effacer correctement un e accentué.
En effet, le fichier /root/.bashrc a l'air particulièrement suspect:
# cat /root/.bashrc
# ~/.bashrc: executed by bash(1) for non-login shells.
# Note: PS1 and umask are already set in /etc/profile. You should not
# need this unless you want different defaults for root.
# PS1='${debian_chroot:+($debian_chroot)}\h:\w\$ '
# umask 022
# You may uncomment the following lines if you want `ls' to be colorized:
# export LS_OPTIONS='--color=auto'
# eval "$(dircolors)"
# alias ls='ls $LS_OPTIONS'
# alias ll='ls $LS_OPTIONS -l'
# alias l='ls $LS_OPTIONS -lA'
#
# Some more alias to avoid making mistakes:
# alias rm='rm -i'
# alias cp='cp -i'
# alias mv='mv -i'
Pourtant, son contenu est exactement le même que sur une machine
initialisée normalement (ie sans PXE/preseed) et idem pour les fichier
/etc/default/locale:
# cat /etc/default/locale
# File generated by update-locale
LANG="fr_FR.UTF8"
Pour l'utilisateur lambda, créé par l'installeur, j'observe la même
impossibilité d'effaçage du é alors que:
$ locale
LANG=fr_FR.UTF8
LANGUAGE=
LC_CTYPE="fr_FR.UTF8"
LC_NUMERIC="fr_FR.UTF8"
LC_TIME="fr_FR.UTF8"
LC_COLLATE="fr_FR.UTF8"
LC_MONETARY="fr_FR.UTF8"
LC_MESSAGES="fr_FR.UTF8"
LC_PAPER="fr_FR.UTF8"
LC_NAME="fr_FR.UTF8"
LC_ADDRESS="fr_FR.UTF8"
LC_TELEPHONE="fr_FR.UTF8"
LC_MEASUREMENT="fr_FR.UTF8"
LC_IDENTIFICATION="fr_FR.UTF8"
LC_ALL=
Re: Ma console ne sait pas effacer correctement un e accentué.
- Mail original - > De: "Olivier" > À: "ML Debian User French" > Envoyé: Vendredi 16 Décembre 2022 15:04:00 > Objet: Ma console ne sait pas effacer correctement un e accentué. > > Bonjour, > > Je patauge dans mes premières configuration PXE/Preseed. > Ma cible est l'installation de serveurs "headless" sous Bullseye. > > À ce stade, j'arrive à installer un système minimal fonctionnel. > Le seul truc qui ne marche pas parfaitement, c'est la console. > > Que ce soit en SSH ou avec un clavier USB directement connecté à la > machine, je constate l'anomalie suivante: > > - je tape au clavier les caractères <é> > > - la machine m'affiche : > -bash: $'\303exit' : commande introuvable > - j'attendais qu'elle quitte simplement la session en cours. > > En comparant le contenu de /etc/default/console-setup, je ne vois pas > de différence ou d'anomalie: > > # cat /etc/default/console-setup > # CONFIGURATION FILE FOR SETUPCON > # Consult the console-setup(5) manual page. > ACTIVE_CONSOLES="/dev/tty[1-6]" > CHARMAP="UTF-8" > CODESET="Lat15" > FONTFACE="Fixed" > FONTSIZE="8x16" > VIDEOMODE= > # The following is an example how to use a braille font > # FONT='lat9w-08.psf.gz brl-8x8.psf' > > Comment corriger ? > > Slts > Bonjour Olivier, Essayes de vérifier les paramètres contenus dans ~/.bashrc export LC_ALL=en_US.UTF-8 export LANG=en_US.UTF-8 export LANGUAGE=en_US.UTF-8 la commande locale : LANG=fr_FR.UTF-8 LANGUAGE= LC_CTYPE="fr_FR.UTF-8" LC_NUMERIC="fr_FR.UTF-8" LC_TIME="fr_FR.UTF-8" LC_COLLATE="fr_FR.UTF-8" LC_MONETARY="fr_FR.UTF-8" LC_MESSAGES="fr_FR.UTF-8" LC_PAPER="fr_FR.UTF-8" LC_NAME="fr_FR.UTF-8" LC_ADDRESS="fr_FR.UTF-8" LC_TELEPHONE="fr_FR.UTF-8" LC_MEASUREMENT="fr_FR.UTF-8" LC_IDENTIFICATION="fr_FR.UTF-8" documentation : https://wiki.debian.org/Locale Merci @+ bernard
Re: stopping mass surveillance
On 12/15/22 17:34, operation.privacyenforcem...@secure.mailbox.org wrote: Dan Ritter wrote: operation.privacyenforcem...@mailbox.org wrote: On 1/9/84 19:84, Jeremy Hendricks message was saved by the all seeing eye: Please provide code examples, flow chart, or a white paper. Releasing anything of requested documents is not desired yet. The idea is not patented yet and will make the developers a high value target for a lot of agencies worldwide. If your project is going to be patented, it can't be part of Debian unless you want to give a patent license to everyone in the world, which defeats the point of patenting it in the first place. A patent can protect only a brand or product name. A patent doesn't protect anything. It provides a place to register the inventor. If the patent is infringed the inventor has the right to hire an attorney and sue. It is entirely up to the patent holder protect his patent. I am looking for people, developers, companies that would be interested in using or developing such a solution, planning a commercial high price launch on the market, licensed will be current revisions. Older revisions with less features or security will be released under an open source license. If this is impossible I am open minded to release the idea confidentially to a trustworthy developer group of an open source project to let them develop it and make it available as FLOSS completely for everyone. It needs to be built before privacy is dead, with or without earning money. It needs to be enforced before we will loose privacy forever. Governments, police, politicians will be excluded via license in any case. None of the open source licenses that Debian will accept can be limited in that way, so, again, Debian is not the home for your project. This >> I am open minded to release the idea confidentially to a >> trustworthy developer group of an open source project to let them develop it >> and make it available as FLOSS completely for everyone. It needs to be built >> before privacy is dead, with or without earning money. It needs to be >> enforced before we will loose privacy forever. would match Debians policies? Curious about everyones opinion regarding this. It might be interesting, but it's definitely not suitable for this mailing list. I wanted to request a feedback how important this topic seems to be for the Debian user base, would you use it? Would you prefer it to be open source? Do you feel unprotected on Debian? Do you think this is neccessary? Later I want to find potentially interested developers if the Debian priciples would be applied and released completely FLOSS. The release of the solution is more important then profit. operation privacyenforcement
Again, stop feeding the troll (Was: Re: stopping mass
On Thu, Dec 15, 2022 at 08:48:44PM -0500, Dan Ritter wrote: > operation.privacyenforcem...@secure.mailbox.org wrote: > > Dan Ritter wrote: > > > operation.privacyenforcem...@mailbox.org wrote: > > > > On 1/9/84 19:84, Jeremy Hendricks message was saved by the all seeing > > > > eye: > [...] > You say contradictory things. You shift positions. You don't > give details as to how this hypothetical thing might work. Yes he does. [...] > > Why don't you start a discussion group, forum, mailing list, or > similar communications methodology, tell us about that, and then > come back when you have a first working draft? > Yes, please go somewhere else unless you have something tangible to contribute which somehow relates to debian. -H -- Henning Follmann | hfollm...@itcfollmann.com
Ma console ne sait pas effacer correctement un e accentué.
Bonjour, Je patauge dans mes premières configuration PXE/Preseed. Ma cible est l'installation de serveurs "headless" sous Bullseye. À ce stade, j'arrive à installer un système minimal fonctionnel. Le seul truc qui ne marche pas parfaitement, c'est la console. Que ce soit en SSH ou avec un clavier USB directement connecté à la machine, je constate l'anomalie suivante: - je tape au clavier les caractères <é> - la machine m'affiche : -bash: $'\303exit' : commande introuvable - j'attendais qu'elle quitte simplement la session en cours. En comparant le contenu de /etc/default/console-setup, je ne vois pas de différence ou d'anomalie: # cat /etc/default/console-setup # CONFIGURATION FILE FOR SETUPCON # Consult the console-setup(5) manual page. ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" CODESET="Lat15" FONTFACE="Fixed" FONTSIZE="8x16" VIDEOMODE= # The following is an example how to use a braille font # FONT='lat9w-08.psf.gz brl-8x8.psf' Comment corriger ? Slts
kernels in testing (was: Re: Debian failed)
On Thursday, December 15, 2022 11:35:04 PM George Olson wrote: > I have an RX 6600 XT also. I use a 4 monitor setup and had to configure > things so that it would work with 2 on top and 2 on the bottom. I can't > remember exactly how I did it, but I first installed Bullseye and > figured out it wasn't going to work. I had enough of a functional > graphics environment and terminal to change all my sources to Testing, > which goes by the codename Bookworm, because to me that was easier than > trying to figure out how to use backports to install a newer kernel. From the peanut gallery (I almost always run with the default kernel in whatever distro I'm using), I'm guessing that if the only thing you installed from Testing was a kernel, that would be fairly stable. (I imagine (but don't know) that when kernels get to testing they have been tested fairly well, even before showing up in Debian. > Once I got that running, it has basically been going without a hitch. > Testing seems to be almost as stable as regular Debian Bullseye like I > have on my laptop. I haven't run into any major snags yet. -- rhk (sig revised 20221206) If you reply: snip, snip, and snip again; leave attributions; avoid HTML; avoid top posting; and keep it "on list". (Oxford comma (and semi-colon) included at no charge.) If you revise the topic, change the Subject: line. If you change the topic, start a new thread. Writing is often meant for others to read and understand (legal documents excepted?) -- make it easier for your reader by various means, including liberal use of whitespace (short paragraphs, separated by whitespace / blank lines) and minimal use of (obscure?) jargon, abbreviations, acronyms, and references. If someone has already responded to a question, decide whether any response you add will be helpful or not ... A picture is worth a thousand words. A video (or "audio"): not so much -- divide by 10 for each minute of video (or audio) or create a transcript and edit it to 10% of the original. A speaker who uses ahhs, ums, or such may have a real physical or mental disability, or may be showing disrespect for his listeners by not properly preparing in advance and thinking before speaking. (Remember Cicero who did not have enough time to write a short missive.) (That speaker might have been "trained" to do this by being interrupted often if he pauses.) A radio (or TV) station which broadcasts speakers with high pitched voices (or very low pitched / gravelly voices) (which older people might not be able to hear properly) disrespects its listeners. Likewise if it broadcasts extraneous or disturbing sounds (like gunfire or crying), or broadcasts speakers using their native language (with or without an overdubbed translation). A person who writes a sig this long probably has issues and disrespects (and offends) a large number of readers. ;-) '
Secret Keyboard code in KDE/Plasma?
Hi Folks, does somebody know, if there is a secret code or key combination, that switches off the internal keyboard in a laptop? It is since years, that suddenly the keyboard is deactivated during typing. As I am not a good typist, it happens, that I am pressing some keys together or touching the touchpad during typing, too. This happens only in KDE / Plasma5, in any other windowmanagers like LXQT, XFCE or LXDE this issue never appeard. I could not discover this, when I deactivated the touchpad in KDE (which is of course not wanted), but that might be by pure chance. There appeared nothing about this in any logs. Does someone know more? Best regards Hans
Re: wget et ping refusent d'utiliser l'adresse source spécifiée
De guerre lasse et pressé par le temps, j'ai demandé à un collaborateur sur place de changer l'adresse de son PC puis de changer l'IP de gestion du switch DLink afin de l'intégrer au plan d'adressage local. J'avais pensé à un problème de routage mais le fait que tshark/wireshark montrait des pings émis avec l'IP source par défaut en 192.168.X.Y, et non l'IP dans le réseau 10.90.90.x a stoppé mes investigations. Un point que je n'avais pas mentionné est le suivant: - la machine relais avec laquelle j'essayais de joindre le nouveau switch DLink était membre de deux réseaux disjoints en 10.X.X.0/24 et 10.Y.Y.0/24 - que le paramétrage par défaut, pas très malin, à mon avis, du DLink est en 10.90.90.90/8 - or ce réseau 10.90.90.90/8 alias 10.0.0.0/8 englobant les deux 10.X.X.0/24 et 10.Y.Y.0/24, c'était peut-être la cause d'une confusion dans le choix initial des routes par la machine relais. Merci à tous pour vos réponses. Si j'en ai la possibilité, je re-construirai au labo un environnement analogue pour investiguer au calme. Le ven. 16 déc. 2022 à 07:26, Pierre Malard a écrit : > > Bonjour, > > Il ne me semble pas que ce soit un problème de route si il a attribué à son > serveur une IP dans la même classe réseau. Dans ce cas c’est le broadcast qui > est utilisé pour trouver la destination. Par contre pour éviter un problème > de routage avec le switch intermédiaire, j’aurai connecté mon serveur > directement sur le switch DLink. Par contre le fait que le switch ne réponde > pas n’est pas forcément anormal. Peut-être que le DLink filtre ce genre de > traffic. > > Ce que je proposerai c’est de connecter directement un poste quelconque > configuré dans la classe du DLink directement sur le DLink et de suivre la > doc pour le configurer. Cela m’étonne que DLink n’ai pas une description de > la mise en route de son switch et qu’ils n’est pas prévu, par exemple, un > accès en IPv6 locale ou une possibilité de connexion en mode console. > > Sinon, dans la configuration actuelle je tenterai un « nmap -sS 10.90.90.90 » > (ou avec « -Pn » pour savoir sur quels ports répond, ou pas. > > Le 15 déc. 2022 à 20:02, Erwann Le Bras a écrit : > > bonsoir > > il ne manquerait pas une route pour utiliser l'interface en 10.90.90 pour > joindre spécifiquement ce sous-réseau? > > Ta route par défaut doit indiquer d'utiliser la mauvaise interface réseau, > d'où l'échec du ping. > > Le 12/12/2022 à 18:07, Olivier a écrit : > > Bonjour, > > J'ai une machine distante sous Stretch indirectement connectée à un > nouveau commutateur DLink de la façon suivante: > Serveur - Switch Mikrotik - Switch DLink > > Comme chacun sait, les nouveaux commutateurs DLink sont livrés avec > une IP par défaut égale à 10.90.90.90/8. > > Afin de configurer ce switch pour la première fois, j'ai attribué à > mon serveur l'IP 10.90.90.91/24 à l'unique interface Ethernet de mon > serveur (avec la commande ip addr add 10.90.90.91/8 dev eno1). > > À ma grande surprise, chaque ping depuis le serveur vers le nouveau > commutateur, avec la commande ping -c1 -I 10.90.90.91 10.90.90.90, > échoue (pas de réponse) > > J'ai pourtant utilisé des dizaines et des dizaines de fois l'option -I > de ping permettant de spécifier l'adresse ou l'interface source > utilisée lors du ping. > > Avec la commande tshark, j'ai: > > # tshark -f 'ip host 10.90.90.90' -i eno1 > Running as user "root" and group "root". This could be dangerous. > Capturing on 'eno1' > 1 0.0 192.168.1.24→ 10.90.90.90 ICMP 98 Echo (ping) > request id=0x15e9, seq=1/256, ttl=64 > > Ceci me laisse penser que l'option -I est ignorée puisque le serveur > semble émettre avec son adresse par défaut 192.168.1.24. > > En utilisant une commande wget --bind-address 10.90.90.91 > http://10.90.90.90, tshark indique une IP source en 192.168.1.24 et > non en 10.90.90.91, comme demandé. > > En attribuant une autre adresse du réseau 10.0.0.0/8 au switch > Mikrotik, le ping de celui-ci vers 10.90.90.90 réussit, ce qui me > confirme que le switch DLink répond. > > Une piste ? > > Slts > > > -- > Pierre Malard > Responsable architectures système CDS DINAMIS/THEIA Montpellier > IRD - UMR Espace-Dev - UAR CPST - IR Data-Terra > Maison de la Télédétection > 500 rue Jean-François Breton > 34093 Montpellier Cx 5 > France > >« le passé n'éclairant plus l'avenir, l'esprit marche dans les ténèbres » > Alexis de Tocqueville - Démocratie en > Amérique >|\ _,,,---,,_ >/,`.-'`'-. ;-;;,_ > |,4- ) )-,_. ,\ ( `'-' > '---''(_/--' `-'\_) πr > > perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. > ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): > 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' > - --> Ce message n’engage que son auteur <-- >
