Re: Upgrade testing to unstable but debian_version and os-release not changing to sid
On Mon 16 Aug 2021 at 21:47:08 (-0400), Greg Wooledge wrote: > On Tue, Aug 17, 2021 at 09:21:52AM +0800, Robbi Nespu wrote: > > $ cat /etc/debian_version > > 11.0 > > > > $ cat /etc/os-release > > PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" > > NAME="Debian GNU/Linux" > > VERSION_ID="11" > > VERSION="11 (bullseye)" > > VERSION_CODENAME=bullseye > > ID=debian > > HOME_URL="https://www.debian.org/; > > SUPPORT_URL="https://www.debian.org/support; > > BUG_REPORT_URL="https://bugs.debian.org/; > > > > Hurmm.. that is unexpected, are this is normal or did I missed something? > > Be patient. A new base-files package hasn't been uploaded into unstable > yet. I'm sure it'll happen sooner or later. > > https://packages.debian.org/search?keywords=base-files And even then, take note of /usr/share/doc/base-files/README: “Q. Why "bookworm/sid" and not "testing/unstable" as it used to be? “A. The codename is a little bit more informative, as the meaning of "testing" changes over time. “Q. Ok, but how do I know which distribution I'm running? “A. If you are running testing or unstable, then /etc/debian_version is not a reliable way to know that anymore. Looking at the contents of your /etc/apt/sources.list file is probably a much better way.” Cheers, David.
Re: Debian 11 installer crashed and reboot
Many thanks Chuck. On Tue, Aug 17, 2021 at 6:36 AM Chuck Zmudzinski wrote: > > On 8/16/2021 1:40 PM, Chuck Zmudzinski wrote: > > On 8/16/2021 12:49 PM, Chuck Zmudzinski wrote: > >> On 8/16/2021 4:25 AM, Andrew M.A. Cater wrote: > >>> On Mon, Aug 16, 2021 at 02:30:33PM +0800, John Mok wrote: > Hi all, > > Tried to install Debian 11 guest using netinst, but the installer > crashed and reboot automatically. > > Host: Xen 4.11.4 on Debian 10 > Guest: Debian 11 (kernel 5.10) > > Here is the steps to reproduce the problem:- > 1) Either guest BIOS or OVMF boot > 2) Select "Expert install" on installation menu > > Then, the guest crashed and reboot. > > Another try with the installer on Debian Live 11, it immediately > crashed and reboot. > > Is it a installer bug or something ? > > Thanks a lot. > > John Mok > > >>> I think people would need many more details as to exactly what > >>> happens and > >>> when it reboots. > >>> > >>> So: You boot the installer - from just a .iso file / from the .iso > >>> flashed > >>> to a USB? Can you show what works and at what point it fails? > >>> > >>> The quick suggestion would be that it's something to do with Xen > >>> hypervisor > >>> but I'm not in any better position than to guess, since I don't use > >>> Xen here. > >>> > >>> I do know that none of the tests the media team do involve booting > >>> on Xen: > >>> in most cases we prefer to run on real hardware. Occasionally, some > >>> of the > >>> tests have to be run on KVM/QEMU. Xen as DomU is untested then. > >>> > >>> All the very best, as ever, > >>> > >>> Andy Cater > >>> > >> > >> I can say bullseye runs fine as a Xen DomU on both the buster xen-4.11 > >> hypervisor and the bullseye xen-4.14 hypervisor on my workstation, with > >> either BIOS or OVMF boot, but mine is a bullseye image upgraded from > >> buster several months ago. I have not tried the bullseye debian > >> installer > >> on the xen hypervisor. Maybe for installing bullseye on xen you can try > >> installing buster first then upgrade it to bullseye if the debian > >> bullseye > >> installer does not work on the xen hypervisor. > >> > >> Chuck Zmudzinski > >> > > > > I would also ask if you have successfully booted another linux distro > > (an earlier Debian or another distribution such as ubuntu) on your > > Debian 10 xen-4.11.4 hypervisor. If not, the problem may be with your > > xen configuration files on your Debian 10 host system, not with the > > Debian 11 installer. Maybe some tweaks to the DomU xl.cfg configuration > > file for your Debian 11 DomU or to the xen hypervisor boot options > > (usually set in /etc/default/grub) might get it working. > > > > Chuck Zmudzinski > > > > I tested the debian-11.0.0-amd64-netinst.iso image on my Debian 10 > xen-4.11.4 hypervisor using both OVMF and BIOS boot using an HVM > type Xen guest, and in both cases, I can confirm the same behavior as > the OP: crash and restart after selecting any of the installation options > from the grub menu that is displayed after booting. Nevertheless, a > full installation of Debian 11 boots and runs fine in the same environment > under Xen. > > Browsing the files in the iso image, I can see there is a folder for xen: > /install.amd/xen with three files in it: vmlinuz, initrd.gz, and debian.cfg. > > However, these files in the xen folder are never referenced anywhere from > the menu or submenu items in the /boot/grub/grub.cfg file on the iso image. > So a workaround would be to create an iso image with a menu entry in the > /boot/grub/grub.cfg file for an installation on xen, and that grub menu item > would be configured to load the vmlinuz kernel and initrd.gz image in the > /install.amd/xen directory. > > It might also be possible to escape to the grub command shell > instead of selecting one of the installation options after booting and > manually enter the commands to load the xen-enabled kernel and initrd.gz > images in the /install.amd/xen folder on the netinst iso, but that is not > very user friendly, and I am not even sure if those images are mainly for > a PV type Xen guest rather that an HVM type Xen guest that really should > not need a special kernel or initrd image, but I could be wrong about that. > > Also, the debian.cfg file in /install.amd/xen mentions the need to use an > iso image that supports installation under xen, and it references things > like multi-arch iso images which I don't think exist anymore in modern > Debian. Anyway, I suggest the OP read this debian.cfg file and try using > the suggestions there to get the debian 11 installer running under xen. > > To summarize, I do not think the Debian installer is designed for easy > installation under Xen, and it is not clear exactly which iso is needed, > nor is it > clear which type of Xen guest should be configured (PV or HVM) to enable > installation of Debian 11 under Xen. > >
Re: Upgrade testing to unstable but debian_version and os-release not changing to sid
On Tue, Aug 17, 2021 at 09:21:52AM +0800, Robbi Nespu wrote: > $ cat /etc/debian_version > 11.0 > > $ cat /etc/os-release > PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" > NAME="Debian GNU/Linux" > VERSION_ID="11" > VERSION="11 (bullseye)" > VERSION_CODENAME=bullseye > ID=debian > HOME_URL="https://www.debian.org/; > SUPPORT_URL="https://www.debian.org/support; > BUG_REPORT_URL="https://bugs.debian.org/; > > Hurmm.. that is unexpected, are this is normal or did I missed something? Be patient. A new base-files package hasn't been uploaded into unstable yet. I'm sure it'll happen sooner or later. https://packages.debian.org/search?keywords=base-files
Upgrade testing to unstable but debian_version and os-release not changing to sid
I have been using debian testing (bullseye) for 1 year (plus) and I want to use sid as my daily driver. I change source.list to sid $ cat /etc/apt/sources.list deb http://ftp.jp.debian.org/debian/ sid main contrib non-free deb-src http://ftp.jp.debian.org/debian/ sid main contrib non-free do the update and upgrade ... $ sudo apt-get update $ sudo apt-get dist-upgrade $ sudo apt-get autoremove $ sudo reboot when booted, I checked systemd os-release and debian release still on bullseye codename $ cat /etc/debian_version 11.0 $ cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/; SUPPORT_URL="https://www.debian.org/support; BUG_REPORT_URL="https://bugs.debian.org/; Hurmm.. that is unexpected, are this is normal or did I missed something? -- Robbi Nespu D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA https://robbinespu.gitlab.io | https://mstdn.social/@robbinespu
Relatively boring bullseye upgrade reports
rock: ASRock DeskMini 300 with a 3400G, 32GB RAM, NVMe disk. Used as an XFCE4 desktop. No issues at all. shield: Asus AM1I-A with AMD 5150 quad0core, 4GB RAM, SATA SSD, lots of gigabit ethernet nics. Used as router, firewall, and infrastructure server. No issues at all. tao: ASRock X570 motherboard, 3600, 64GB RAM, SSD root, SSD ZFS mirror pair, spinning ZFS RAID10. Runs all the server stuff for randomstring.org, including a Postgresql database, many web services, wiki, mail, and so forth and so on. No serious issues. Upgrading from php7.3 to php7.4 wasn't automatic and several packages needed to be installed by hand. ZFS went perfectly transparently. Postgresql 11 to 13 wasn't done automatically, but pg_upgradecluster makes it very very easy. -dsr-
debian10/11 ssh from ipv6 address not in /etc/hosts.allow = sshd segfault segfault
Hi, I just noticed many many sshd segfaults listed in /var/log/kern.log. There are two versions. They look like this: sshd[1086]: segfault at 7fff615eaec8 ip 7ff2a586f42f sp 7fff615eaed0 error 6 in libwrap.so.0.7.6[7ff2a586e000+5000] sshd[1094]: segfault at 7ffcd3ff6f08 ip 7f18d4f5dac7 sp 7ffcd3ff6ed0 error 6 in libc-2.31.so[7f18d4f2a000+14b000] The hex addresses are different each time, but the rest is the same. It happens every time there's an incoming ssh connection attempt via IPv6 when the IPv6 address isn't listed in /ertc/hosts.allow. There are many because it's a cronned backup. I am using /etc/hosts.allow for sshd and have a mixture of IPv4 and IPv6 addresses in it. When I added the IPv6 address in question to /etc/hosts.allow, the segfaults stopped and the connections worked. This started 2 days before I upgraded to debian11 and there was a different version number for libc (so it's not new), but it's still happening with debian11. It might be a bug in libwrap0 (whose version number didn't change much), or in how openssh-server is using it. cheers, raf
Re: Moving from Testing to Stable + Backports
On Mon, Aug 16, 2021 at 03:07:06PM -0400, songbird wrote: > Greg Wooledge wrote: > ... > >> deb http://deb.debian.org/debian/ experimental main contrib non-free > >> deb-src http://deb.debian.org/debian/ experimental main contrib non-free > > > > And this is just stupid. Remove this immediately. > > some of us don't mind trying out more recent versions of > some packages: You CANNOT install binary packages from experimental on stable safely. It's nonsensical. https://wiki.debian.org/DontBreakDebian Experimental may be mixed with UNSTABLE if you are brave AND clueful. It may NOT be mixed with stable. I don't know how you can possibly think otherwise. https://wiki.debian.org/DontBreakDebian
Re: Moving from Testing to Stable + Backports
Greg Wooledge wrote: ... >> deb http://deb.debian.org/debian/ experimental main contrib non-free >> deb-src http://deb.debian.org/debian/ experimental main contrib non-free > > And this is just stupid. Remove this immediately. some of us don't mind trying out more recent versions of some packages: frex: uname -a Linux ant 5.13.0-trunk-amd64 #1 SMP Debian 5.13.9-1~exp2 (2021-08-10) x86_64 GNU/Linux it's not stupid, it's just one way of doing things. songbird
Re: Debian 11 bullseye Gdm3 nvidia 7200go nouveau glitches and more
On Mon Aug 16 16:05:28 2021 "dimitris.varu" wrote: > Hi i recently install debian 11 stable. Amd64 in hp dv6300 laptop. > Gnome is very glitched from login through desktop. > Many textures missing > icons missing white squares everywhere... > Lxde runs ok without problems... > Gpu is nvidia 7200go nouveau driver. > I know is old hardware.. any help or advice is most welcome! > Tnx for your time For what it's worth, I've always been suspicious of nouveau. I too am running older hardware (GeForce 630), and I was getting frequent lockups on a previous version of Debian (either Jessie or Stretch, I think), so I switched to nVidia's proprietary driver and the problem went away. Somewhere along the line of Debian upgrades, the system reverted to using nouveau. I'm currently running Buster, and my machine spontaneously reboots once a day or so. I've just replaced nouveau with the nVidia driver (version 390.143). So far, so good. I'm hoping my machine will become stable once again. -- /~\ Charlie Gibbs | \ /| "Alexa, define 'bugging'." X I'm really at ac.dekanfrus | / \ if you read it the right way. |
Re: Debian 11 installer crashed and reboot
On 8/16/2021 1:40 PM, Chuck Zmudzinski wrote: On 8/16/2021 12:49 PM, Chuck Zmudzinski wrote: On 8/16/2021 4:25 AM, Andrew M.A. Cater wrote: On Mon, Aug 16, 2021 at 02:30:33PM +0800, John Mok wrote: Hi all, Tried to install Debian 11 guest using netinst, but the installer crashed and reboot automatically. Host: Xen 4.11.4 on Debian 10 Guest: Debian 11 (kernel 5.10) Here is the steps to reproduce the problem:- 1) Either guest BIOS or OVMF boot 2) Select "Expert install" on installation menu Then, the guest crashed and reboot. Another try with the installer on Debian Live 11, it immediately crashed and reboot. Is it a installer bug or something ? Thanks a lot. John Mok I think people would need many more details as to exactly what happens and when it reboots. So: You boot the installer - from just a .iso file / from the .iso flashed to a USB? Can you show what works and at what point it fails? The quick suggestion would be that it's something to do with Xen hypervisor but I'm not in any better position than to guess, since I don't use Xen here. I do know that none of the tests the media team do involve booting on Xen: in most cases we prefer to run on real hardware. Occasionally, some of the tests have to be run on KVM/QEMU. Xen as DomU is untested then. All the very best, as ever, Andy Cater I can say bullseye runs fine as a Xen DomU on both the buster xen-4.11 hypervisor and the bullseye xen-4.14 hypervisor on my workstation, with either BIOS or OVMF boot, but mine is a bullseye image upgraded from buster several months ago. I have not tried the bullseye debian installer on the xen hypervisor. Maybe for installing bullseye on xen you can try installing buster first then upgrade it to bullseye if the debian bullseye installer does not work on the xen hypervisor. Chuck Zmudzinski I would also ask if you have successfully booted another linux distro (an earlier Debian or another distribution such as ubuntu) on your Debian 10 xen-4.11.4 hypervisor. If not, the problem may be with your xen configuration files on your Debian 10 host system, not with the Debian 11 installer. Maybe some tweaks to the DomU xl.cfg configuration file for your Debian 11 DomU or to the xen hypervisor boot options (usually set in /etc/default/grub) might get it working. Chuck Zmudzinski I tested the debian-11.0.0-amd64-netinst.iso image on my Debian 10 xen-4.11.4 hypervisor using both OVMF and BIOS boot using an HVM type Xen guest, and in both cases, I can confirm the same behavior as the OP: crash and restart after selecting any of the installation options from the grub menu that is displayed after booting. Nevertheless, a full installation of Debian 11 boots and runs fine in the same environment under Xen. Browsing the files in the iso image, I can see there is a folder for xen: /install.amd/xen with three files in it: vmlinuz, initrd.gz, and debian.cfg. However, these files in the xen folder are never referenced anywhere from the menu or submenu items in the /boot/grub/grub.cfg file on the iso image. So a workaround would be to create an iso image with a menu entry in the /boot/grub/grub.cfg file for an installation on xen, and that grub menu item would be configured to load the vmlinuz kernel and initrd.gz image in the /install.amd/xen directory. It might also be possible to escape to the grub command shell instead of selecting one of the installation options after booting and manually enter the commands to load the xen-enabled kernel and initrd.gz images in the /install.amd/xen folder on the netinst iso, but that is not very user friendly, and I am not even sure if those images are mainly for a PV type Xen guest rather that an HVM type Xen guest that really should not need a special kernel or initrd image, but I could be wrong about that. Also, the debian.cfg file in /install.amd/xen mentions the need to use an iso image that supports installation under xen, and it references things like multi-arch iso images which I don't think exist anymore in modern Debian. Anyway, I suggest the OP read this debian.cfg file and try using the suggestions there to get the debian 11 installer running under xen. To summarize, I do not think the Debian installer is designed for easy installation under Xen, and it is not clear exactly which iso is needed, nor is it clear which type of Xen guest should be configured (PV or HVM) to enable installation of Debian 11 under Xen. Chuck Zmudzinski
Re: Debian 11 bullseye Gdm3 nvidia 7200go nouveau glitches and more
dimitris.varu writes: Hi i recently install debian 11 stable. Amd64 in hp dv6300 laptop.Gnome is very glitched from login through desktop. Many textures missing icons missing white squares everywhere... Lxde runs ok without problems... Gpu is nvidia 7200go nouveau driver. I know is old hardware.. any help or advice is most welcome! Tnx for your time Is there a specific reason for needing GNOME on this machine? From https://www.cnet.com/reviews/hp-pavilion-dv6300-preview/ I gather it has a rather old processor (Celeron M 440 to Core 2DuoT7200) -- which one do you have exactly? Also, it seems there would be at most 2 GiB of RAM. I'd thus suggest to install something lightweight like LXDE, Fluxbox, IceWM. Using a plain window manager will reduce the number of GUI background applications and that may free some essential RAM and CPU resources that you can use for your application of interest. Of course, if you need to stay with a mordern DE that requires GPU accelleration you could always try to install an old proprietary NVidia driver. The Debian package would be `nvidia-legacy-304xx-kernel-dkms` but I am afraid the last release it was part of was Debian Stretch (Debian 9). HTH Linux-Fan öö pgpvqdonhpurt.pgp Description: PGP signature
Debian 11 bullseye Gdm3 nvidia 7200go nouveau glitches and more
Hi i recently install debian 11 stable. Amd64 in hp dv6300 laptop. Gnome is very glitched from login through desktop. Many textures missing icons missing white squares everywhere... Lxde runs ok without problems... Gpu is nvidia 7200go nouveau driver. I know is old hardware.. any help or advice is most welcome! Tnx for your time
Re: PSA: 'apt-get update' new-Debian-release error fix
On 8/14/21, The Wanderer wrote: > On 2021-08-14 at 19:06, Greg Wooledge wrote: > >> On Sat, Aug 14, 2021 at 06:26:07PM -0400, The Wanderer wrote: >> >>> I had enough trouble with this at the last Debian release, >> >> ... but not this time, right? > > Yes, this time; in fact... > >>> For anyone who uses 'apt-get update' - and, I suspect, any other tool >>> than 'apt' itself - to update the list of available packages from the >>> new release, you're at least moderately likely to see the update attempt >>> fail with error messages like the following: >>> >>> > E: Repository 'http://ftp.us.debian.org/debian stable InRelease' >>> > changed its 'Codename' value from 'buster' to 'bullseye' >> >> You copied this from the NewInBuster wiki most likely. > > ...nope, I copied it from a terminal on my computer, where it had just > been output on my initial 'apt-get update' attempt. > >> That's where I put it, when I ran into this issue two years ago, and >> documented it there. It's even the same mirror that I use (which is >> no longer the default, hence it standing out). >> >> The issue did not happen this time around. Instead of getting an >> "E:" line (error), you only get a bunch of N: (warning) lines. >> >> You're trying to solve a problem that doesn't actually exist any >> more. > > I would love for that to have been the case, but my experience does not > reflect it being so. > > Maybe somehow I'm running an older apt-get version than what has the > fix(es)? But as far as I know that's shipped in the 'apt' package, and I > have that at version 2.2.4, which is what's currently in both stable and > testing (unsurprising given that they should currently be nearly > identical). Stuff's not totally caught up or something. I've encountered the following a couple of times. The latest was while playing along with a recent Debian-User Docker thread: https://packages.debian.org/search?keywords=docker That packages page says buster is stable and bullseye is still testing. That's possibly (likely?) not the only place still showing similar, too. Yesterday I debootstrap'ed in anticipation of new and not so stable. Only a couple font packages failed as no longer available, and the rest were already hoarded locally here. My previous experience had been that a LOT of packages are not available because Developers haven't brought them up to speed. Examples there would be something like GIMP and Inkscape. This morning there were a lot of upgrades and incidental deletions that were more as expected. Things are slowly rolling along and catching up to speed, I guess. :) OR not.. Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with birdseed *
Re: Sources list with contrib repositories on DVD-1
On Sun 15 Aug 2021 at 22:07:27 (+), Ramon Mulin wrote: > The DVD-1 image is coming with contrib enabled on the cd-rom, > security and update lines. This is normal? AIUI the selection of software on DVD-1 is designed to give as comprehensive a collection as possible, based partly on popularity, so that the occasions on which DVD-2, 3… need to be mounted are minimised. As many people will wish to install some non-free software (which can't be included), there are packages from contrib (dependencies of non-free) which make the grade for inclusion on DVD-1. > The netinstall image is just with main. In contrast, the netinst image has been pruned to a minimal set of packages that are able just to install a system, which can then, in turn, install anything and everything else from the internet. Unsurprisingly, just installing a Debian system can be achieved using only Debian software, ie from main. During the installation, you can add non-free (pulls in contrib) to your own list of sources. However, because so many people run machines having hardware devices that require non-free firmware blobs /before/ any initial installation step, (mainly laptops being installed over WiFi), the website also offers unofficial netinst images which include collections of such firmware. AFAICT there are no packages from contrib required, because each (free) device driver already includes the ability to load its own non-free firmware blob. > P.S.: Sorry for my english. It's fine. Cheers, David.
Re: what binds to port
On Mon 16 Aug 2021 at 19:51:50 +0200, Nicolas George wrote: > Brian (12021-08-02): > > My thinking is that a USB printer uses libusb, just as a scanner does. > > No kernel driver involved. The printer drivers are "internal" to CUPS. > > The output of `/sbin/modinfo usblp` confirms there is a kernel driver > for USB printers. > > filename: /lib/modules/5.10.0-8-amd64/kernel/drivers/usb/class/usblp.ko > license:GPL > description:USB Printer Device Class driver > author: Michael Gee, Pavel Machek, Vojtech Pavlik, Randy Dunlap, Pete > Zaitcev, David Paschal The existence of the usblp kernel module is not in doubt. > It is entirely possible that both this and generic libusb access are > supported. The printing system detaches usblp when it is met. -- Brian.
RE: Motores de Busqueda para Encontrar Talento en LinkedIn, Facebook, Instagram
Búsquedas booleanas de candidatos. NOMBRE, AND, UBICACION, NOT, ESCOLARIDAD... RECLUTAMIENTO Y SELECCIÓN 4.0 Motores de Búsqueda, Redes Sociales y Nuevas Tecnologías Online en Vivo 01 y 08 de Septiembre 2021 Gracias a la TECNOLOGÍA de hoy en día las y los RECLUTADORES tenemos la posibilidad de acceder a motores de búsqueda que nos facilita encontrar candidatos en redes sociales de una forma mucho más rápida y segura. Participe en esta clínica de lo último en reclutamiento y revolucione la forma de encontrar talento en su Organización. FOLLETO COMPLETO RECLUTAMIENTO 4.0 >>>Deseo mayores informes a través de WhatsAppp Estamos comprometidos con usted y su Organización, puede comunicarse con alguno de nuestros ejecutivos para cualquier duda, con mucho gusto le atenderemos: Guadalajara, Jal. 33 2005 0994 Ciudad de México 55 2450 6187 Monterrey, N.L. 81 2974 7731 Este boletín informativo tiene como objetivo generar valor en usted y en su Organización. Si usted desea dejar de recibir este tipo de información conteste con la palabra BAJARECLUTAMIENTO402. O en su defecto haga click en el siguiente enlace: unsubscribe from this list
Re: what binds to port
Brian (12021-08-02): > My thinking is that a USB printer uses libusb, just as a scanner does. > No kernel driver involved. The printer drivers are "internal" to CUPS. The output of `/sbin/modinfo usblp` confirms there is a kernel driver for USB printers. filename: /lib/modules/5.10.0-8-amd64/kernel/drivers/usb/class/usblp.ko license:GPL description:USB Printer Device Class driver author: Michael Gee, Pavel Machek, Vojtech Pavlik, Randy Dunlap, Pete Zaitcev, David Paschal It is entirely possible that both this and generic libusb access are supported. Regards, -- Nicolas George signature.asc Description: PGP signature
Re: Debian 11 installer crashed and reboot
On 8/16/2021 12:49 PM, Chuck Zmudzinski wrote: On 8/16/2021 4:25 AM, Andrew M.A. Cater wrote: On Mon, Aug 16, 2021 at 02:30:33PM +0800, John Mok wrote: Hi all, Tried to install Debian 11 guest using netinst, but the installer crashed and reboot automatically. Host: Xen 4.11.4 on Debian 10 Guest: Debian 11 (kernel 5.10) Here is the steps to reproduce the problem:- 1) Either guest BIOS or OVMF boot 2) Select "Expert install" on installation menu Then, the guest crashed and reboot. Another try with the installer on Debian Live 11, it immediately crashed and reboot. Is it a installer bug or something ? Thanks a lot. John Mok I think people would need many more details as to exactly what happens and when it reboots. So: You boot the installer - from just a .iso file / from the .iso flashed to a USB? Can you show what works and at what point it fails? The quick suggestion would be that it's something to do with Xen hypervisor but I'm not in any better position than to guess, since I don't use Xen here. I do know that none of the tests the media team do involve booting on Xen: in most cases we prefer to run on real hardware. Occasionally, some of the tests have to be run on KVM/QEMU. Xen as DomU is untested then. All the very best, as ever, Andy Cater I can say bullseye runs fine as a Xen DomU on both the buster xen-4.11 hypervisor and the bullseye xen-4.14 hypervisor on my workstation, with either BIOS or OVMF boot, but mine is a bullseye image upgraded from buster several months ago. I have not tried the bullseye debian installer on the xen hypervisor. Maybe for installing bullseye on xen you can try installing buster first then upgrade it to bullseye if the debian bullseye installer does not work on the xen hypervisor. Chuck Zmudzinski I would also ask if you have successfully booted another linux distro (an earlier Debian or another distribution such as ubuntu) on your Debian 10 xen-4.11.4 hypervisor. If not, the problem may be with your xen configuration files on your Debian 10 host system, not with the Debian 11 installer. Maybe some tweaks to the DomU xl.cfg configuration file for your Debian 11 DomU or to the xen hypervisor boot options (usually set in /etc/default/grub) might get it working. Chuck Zmudzinski
Re: Kmail - Message d'erreur
Le lundi 16 août 2021, 13:57:06 CEST Tulum a écrit : > Bonjour, > > Depuis quelques temps, j'ai un message d'erreur de Kmail lorsque je veux > > écrire un message. Le message est lié à la correction orthographique : > > Une erreur s'est produite lors du chargement de la liste des langues : > > Error transferring https://languagetool.org/api/v2/languages - server > > replied: Forbidden > > Suis-je le seul ? Une solution ? Je n'ai rien trouvé avec Qwant. > > Merci > > Kmail : Version 5.15.3 (20.08.3) Ah si ! Dans la configuration des modules externes de Kmail, le module correction orthographique (LanguageTool), cliquer sur le bouton de config et rentrer une URL d'API "locale" : https://api.languagetoolplus.com/v2/ Voilou.
Re: deprecated options in openssh
On Mon 16 Aug 2021 at 16:49:16 (+0100), Adam Weremczuk wrote: > Installation and configuration was straightforward: > > sudo apt install logwatch > > /etc/cron.daily/00logwatch > #execute > /usr/sbin/logwatch --detail low --mailto x...@domain.com > > The master config file /usr/share/logwatch/default.conf/logwatch.conf > left with defaults. > > Only one report per day arrives. Same as for the other dozen of Debian > (mostly older) machines it's installed on and which don't show this > issue. I presume logwatch is watching your logs, so the first place to check is the actual logs themselves. My guess (it's no more than that) is that one of the other dozen machines that you occasionally log into has a slightly different configuration from this one, perhaps older, with options that are now considered less secure (but no extra lines inserted). The options that are commented out in each machine's config file are the defaults being used by the server, so they /are/ in force. When you connect to a remote machine's server, I'm assuming it gets told what the remote's options are, and it's remonstrating about them. (The fact that options are commented will be irrelevant, therefore.) Note that I may have all this in reverse: the remote machine could be complaining about yours, and sending you the log by email. So, as I say, the first step is to find the log entries that logwatch has watched for. Cheers, David.
Re: Bulleye sécurité
Le lundi 16 août 2021, 13:09:05 CEST Patrick ZAJDA a écrit : > Bonjour, > > > C'est parce que le nom a changé, maintenant il faut utiliser > stable-security à la place de stable/update C'est bien la solution à mon problème. Merci à tous. Philippe Merlin ^
Re: Debian 11 installer crashed and reboot
On 8/16/2021 4:25 AM, Andrew M.A. Cater wrote: On Mon, Aug 16, 2021 at 02:30:33PM +0800, John Mok wrote: Hi all, Tried to install Debian 11 guest using netinst, but the installer crashed and reboot automatically. Host: Xen 4.11.4 on Debian 10 Guest: Debian 11 (kernel 5.10) Here is the steps to reproduce the problem:- 1) Either guest BIOS or OVMF boot 2) Select "Expert install" on installation menu Then, the guest crashed and reboot. Another try with the installer on Debian Live 11, it immediately crashed and reboot. Is it a installer bug or something ? Thanks a lot. John Mok I think people would need many more details as to exactly what happens and when it reboots. So: You boot the installer - from just a .iso file / from the .iso flashed to a USB? Can you show what works and at what point it fails? The quick suggestion would be that it's something to do with Xen hypervisor but I'm not in any better position than to guess, since I don't use Xen here. I do know that none of the tests the media team do involve booting on Xen: in most cases we prefer to run on real hardware. Occasionally, some of the tests have to be run on KVM/QEMU. Xen as DomU is untested then. All the very best, as ever, Andy Cater I can say bullseye runs fine as a Xen DomU on both the buster xen-4.11 hypervisor and the bullseye xen-4.14 hypervisor on my workstation, with either BIOS or OVMF boot, but mine is a bullseye image upgraded from buster several months ago. I have not tried the bullseye debian installer on the xen hypervisor. Maybe for installing bullseye on xen you can try installing buster first then upgrade it to bullseye if the debian bullseye installer does not work on the xen hypervisor. Chuck Zmudzinski
Re: [WAS Re: Grub efi etc - specific mention of WSL - Windows Subsystem for Linux]
On 2021-08-16 6:44 a.m., Andrew M.A. Cater wrote: > On Mon, Aug 16, 2021 at 06:19:47AM -0400, Polyna-Maude Racicot-Summerside > wrote: >> Hi, >> >> On 2021-08-16 2:30 a.m., to...@tuxteam.de wrote: >>> On Sun, Aug 15, 2021 at 05:21:41PM -0400, Polyna-Maude Racicot-Summerside >>> wrote: On 2021-08-15 4:31 p.m., Andrew M.A. Cater wrote: >>> >>> [...] >>> > Keep notes as you go. Try and raise single issues - it'll help. > > All the very best, as ever, I'd like to have as much patience you do ;-) >>> >>> Not only patience, but knowledge. >>> >>> I just keep trying :-) >>> >> Knowledge is not like magic, it comes with time for a specific domain. >> We all have knowledge but it's split between all that we do in life. We >> can't expect to have the same knowledge as someone else who's older than us. >> >> For myself, I try to find answer by myself as often I can before going >> out and asking others, this way I can gain a better understanding of the >> process around me. If I do ask others, I try to also ask *why* they gave >> me such answer. I don't accept only *do this and it will work*, if one >> answer doesn't allow me a better understanding then I don't take it >> because not only will it won't help me by just repeating what others >> tell me, it can also be dangerous. >> >> I don't have as much knowledge than many of you regarding Debian because >> for most of my life, computer related task wasn't a 40+ hours a week job. >> >> And one of the best way of learning is by trial and error. Having good >> methods of separating cause and effects, taking time to read (always a >> bit stupid not to read the release note to only find afterward that you >> forgot a very important thing that wasn't needed for the past 20 &+ >> release but is so now). >> >> And one of the best hint for learning is to ask the good persons. I >> don't use *Windows Subsystem for Linux* and if I would, then it's not >> here that I'd ask. Same goes for any Debian derivative. > > If you _did_ use WSL, I'd be willing and able to help you as I've installed > this and run Debian under it. There is also a #debian-wsl IRC channel on OFTC > run by the Debian maintainer of WSL packages, though it has almost no > traffic. > > It would probably be on-topic for debian-user since there isn't another > mailing list for it, I think. Oh well maybe I didn't choose the best example ! > > All best, as ever, > > Andy Cater >> >> >>> Cheers >>> - t >>> >> >> -- >> Polyna-Maude R.-Summerside >> -Be smart, Be wise, Support opensource development >> > > > -- Polyna-Maude R.-Summerside -Be smart, Be wise, Support opensource development OpenPGP_signature Description: OpenPGP digital signature
Re: deprecated options in openssh
Installation and configuration was straightforward:
sudo apt install logwatch
/etc/cron.daily/00logwatch
#execute
/usr/sbin/logwatch --detail low --mailto x...@domain.com
The master config file /usr/share/logwatch/default.conf/logwatch.conf
left with defaults.
Only one report per day arrives. Same as for the other dozen of Debian
(mostly older) machines it's installed on and which don't show this issue.
I've run a recursive search across the entire file system but no other
occurrences of the problematic options have been found:
sudo find / -type f -exec grep -l UsePrivilegeSeparation {} \;
Still puzzled...
On 16/08/2021 15:34, Greg Wooledge wrote:
On Mon, Aug 16, 2021 at 03:06:30PM +0100, Adam Weremczuk wrote:
I run openssh 7.9p1-10+deb10u2 on Debian 10.10.
Logwatch, which runs daily, occasionally (maybe 2-3 times per month) reports
the following:
Sometimes you get warnings, and sometimes you don't? That's a red flag
right off the bat.
Is this "logwatch" thing run by a crontab entry, or by a systemd timer?
Are the ones that give warnings run by a *different* crontab entry, or
a *different* systemd timer?
Why is logwatch still complaining and why is it getting the line numbers
wrong?
My first guess is that there's another sshd_config file somewhere else
that it's reading, on the occasions where you get the warnings, possibly
due to a second crontab entry or whatever.
Or maybe logwatch has a configuration file that defines different tasks
depending on the day, and one of the tasks is set to read the wrong file?
Re: moderators, I would appreciate if you could interfere
Jeremy Ardley wrote: > I don't think this is accidental, and you can see clear signs of > continuous influence by major players using Wikipedia 'editors' to > further various agendas. +1 China and North Korea getting envy. -- FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
Re: Can't boot following re-install to LVM on LUKS [was: can't login via gdm]
On Mon, Aug 16, 2021 at 03:46:51PM +0100, Morgan Read wrote: > On 11/08/2021 11:30 pm, David Christensen wrote: > > On 8/11/21 6:45 AM, Morgan Read wrote: > >> After having overcome a fairly fundamental bug with calamares as > >> described here: > >> https://github.com/calamares/calamares/issues/1564#issuecomment-846321060 > >> And, (unnecessarily as it turned out) re-installed my system, I find > >> I'm unable to boot. ... > ... Morgan, Possibly just don't use calamares. Use the standard Debian installer (d-i for short). Either the standard or expert installs offer you "ordinary" LVM or encrypted LVM with LUKS, made even more straightforward if you can choose guided partitioning. Do be aware, however, that if you choose multi-filesystem, then you might have to check that the appropriate partition sizes are correct for you. In testing, we often have to swap the mount point labels around. Also: the standard size for swap is now 1G and for a dedicated /tmp partition of 2G. All the very best, as ever, Andy Cater > > When a system image is damaged or doubtful, I restore the last raw > > binary image onto a blank device, check out the configuration files, and > > restore local data. The computer is back in operation in a predictable > > amount of time with a high level of confidence that everything is correct. > > Thanks David - I do have my home directories all comfortably backed-up > to a raid device on my local server - I stopped taking stuff off-site a > year or so ago. However, it's still a right royal pita when both the > live CD and full install DVD are broken, see commentary from here: > https://github.com/calamares/calamares/issues/1564#issuecomment-898246354 > > I do find it puzzling that there's not straight forward way of doing > LVM-on-LUKS. > > Regards, > -- > Morgan Read >
Bulleye sécurité
Bonjour, Depuis deux jours j'ai ce message lorsque je lance apt update : Le dépôt http://security.debian.org stable/updates Release ne contient plus de fichier Release . Ce message ne m'inquiéterai pas trop si je n'avais eu lors d'une mise à jour hier un message disant que le nom d'une release n'était pas Bullseye mais je ne m'en rappelle plus exactement un nom contenant ...Worn il fallait répondre par O ou N N étant proposé par défaut j'ai répondu O. Avez vous le même problème. Merci d'avance. Philippe Merlin
Re: Can't boot following re-install to LVM on LUKS [was: can't login via gdm]
On 11/08/2021 11:30 pm, David Christensen wrote: > On 8/11/21 6:45 AM, Morgan Read wrote: >> After having overcome a fairly fundamental bug with calamares as >> described here: >> https://github.com/calamares/calamares/issues/1564#issuecomment-846321060 >> And, (unnecessarily as it turned out) re-installed my system, I find >> I'm unable to boot. ... ... > When a system image is damaged or doubtful, I restore the last raw > binary image onto a blank device, check out the configuration files, and > restore local data. The computer is back in operation in a predictable > amount of time with a high level of confidence that everything is correct. Thanks David - I do have my home directories all comfortably backed-up to a raid device on my local server - I stopped taking stuff off-site a year or so ago. However, it's still a right royal pita when both the live CD and full install DVD are broken, see commentary from here: https://github.com/calamares/calamares/issues/1564#issuecomment-898246354 I do find it puzzling that there's not straight forward way of doing LVM-on-LUKS. Regards, -- Morgan Read OpenPGP_signature Description: OpenPGP digital signature
Re: deprecated options in openssh
On Mon, Aug 16, 2021 at 03:06:30PM +0100, Adam Weremczuk wrote: > I run openssh 7.9p1-10+deb10u2 on Debian 10.10. > > Logwatch, which runs daily, occasionally (maybe 2-3 times per month) reports > the following: Sometimes you get warnings, and sometimes you don't? That's a red flag right off the bat. Is this "logwatch" thing run by a crontab entry, or by a systemd timer? Are the ones that give warnings run by a *different* crontab entry, or a *different* systemd timer? > Why is logwatch still complaining and why is it getting the line numbers > wrong? My first guess is that there's another sshd_config file somewhere else that it's reading, on the occasions where you get the warnings, possibly due to a second crontab entry or whatever. Or maybe logwatch has a configuration file that defines different tasks depending on the day, and one of the tasks is set to read the wrong file?
Re: Grub efi etc
> And one of the best way of learning is by trial and error Dear Polly, but, you are so beautiful : not only Beautiful, but, French-Canadienne-Beautiful thank you : bless you .
deprecated options in openssh
Hi all, I run openssh 7.9p1-10+deb10u2 on Debian 10.10. Logwatch, which runs daily, occasionally (maybe 2-3 times per month) reports the following: - SSHD Begin Deprecated options in SSH config: KeyRegenerationInterval - line 28 RSAAuthentication - line 49 RhostsRSAAuthentication - line 57 ServerKeyBits - line 29 UsePrivilegeSeparation - line 25 I've checked /etc/ssh/sshd_config and the options are there but: - they are all commented out with ## (why should I be forced to delete commented out lines?) - none of these options is mentioned in any other file under /etc - the line numbers are shifted by 2 (e.g. line 25 is in fact line 27) because of 2 custom lines that I added at the very beginning of the file I've definitely restarted ssh service since making the changes. Why is logwatch still complaining and why is it getting the line numbers wrong? Regards, Adam
Re: Grub efi etc
And one of the best way of learning is by trial and error Dear Polly, but, you are so beautiful . regards .
Re: Issues with Bullseye
On Sun 15 Aug 2021 at 09:52:01 -0500, David Wright wrote: > On Sun 15 Aug 2021 at 15:36:05 (+0100), Brian wrote: > > On Sun 15 Aug 2021 at 16:13:51 +0200, Hans wrote: > > > > > Yeah, not quite. I was already aware, that https won't improve security > > > much. > > > > > > I just wondered, why the docu once is telling "use https" and once > > > "http". If > > > only using https or either http, this would not create confuseness. > > > > > > Looks like I am too critical. am I not? :) > > > > There isn't any such thing as being "too critical" when it comes to > > technical matters :). > > > > A link to the page you were looking at might help. > > I assume this refers to § 5.1.3 in the Release Notes. > > A browser has no problem reaching the site with/without the http"s", > but I don't know about APT. However, the OP had the (usual) syntax > error, so that may be the cause of their specific problem. I asked on -doc but there isn't any definitive answer yet. So then I looked to see what the bullseye installer does when configuring the package manager. The protocol choice is still between http, https and ftp. I chose http as I always have done. The lines put in /etc/apt/sources.list both begin with http://. Back to the menu and select https. No choice of country mirroe is allowed. The only offering is deb.debian.org. I assume that is because it is the only mirror that can be assumed to support https. The security mirror is still http://... . The other is https://... . My conclusion is that the line in § 5.1.3 in the Release Notes is either an overenthusiastic entry or a typo. Either way the advice there should really be consistent with what the installer does, even if it does not lead to any problems. -- Brian.
Re: On improving mailing list [was: How to Boot Linux ISO Images Directly From Your Hard Drive Debian]
On Mon, Aug 16, 2021 at 08:26:34AM -0400, SDA wrote: BTW there has been an off-topic list introduced by a community member, but it seems has had little uptake. I looked into this the other day, because I hadn't seen reference to it for a while. It was called d-community-offtopic; it was hosted on the Alioth server, and I think its eventual demise was when Alioth was turned off in around 2018. The last non-spam message to it was, I think, in 2016. The archives are here: https://alioth-lists-archive.debian.net/pipermail/d-community-offtopic.mbox/ -- Please do not CC me for listmail. Jonathan Dowland ✎j...@debian.org https://jmtd.net
Re: Moving from Testing to Stable + Backports
On Mon, Aug 16, 2021 at 08:29:36AM -0400, Michael Grant wrote: > Ok I added bullseye-updates now, thanks. > > What priority should I apply to bullseye-update in preferences? Get rid of ALL of that crap, if you are running stable. No pinning. No preferences. (Backports are automatically pinned, so you don't have to do anything.) You run stable. That's it. unicorn:~$ cat /etc/apt/sources.list deb http://ftp.us.debian.org/debian bullseye main contrib non-free deb http://security.debian.org/debian-security bullseye-security main contrib non-free deb http://ftp.us.debian.org/debian bullseye-updates main contrib non-free deb-src http://ftp.us.debian.org/debian unstable main unicorn:~$ ls /etc/apt/preferences.d/ unicorn:~$ deb-src lines are OK, because they allow you to build your own backports if need be. I haven't had to build one in a while, certainly not since bullseye was released, so at the moment that deb-src line isn't doing anything for me. I should probably go comment it out now.
Re: Bulleye sécurité
Le 16/08/2021 à 12:50, MERLIN Philippe a écrit : Bonjour, Depuis deux jours j'ai ce message lorsque je lance apt update : Le dépôt http://security.debian.org stable/updates Release ne contient plus de fichier Release . Ce message ne m'inquiéterai pas trop si je n'avais eu lors d'une mise à jour hier un message disant que le nom d'une release n'était pas Bullseye mais je ne m'en rappelle plus exactement un nom contenant ...Worn il fallait répondre par O ou N N étant proposé par défaut j'ai répondu O. Avez vous le même problème. Merci d'avance. Philippe Merlin le nom de la future version 12 de debian: BookWorm https://www.debian.org/releases/bookworm/ Tu dois avoir un dépot (/etc/apt/sources.list) qui n'est pas bon suite à la sortie de Bullseye en version stable. Le message devait probablement te demander si tu voulais garder ou modifier cette ligne alors qu'elle ne pointe plus sur le bon endroit... Tu es Buster ou en BullSeye?
Re: Moving from Testing to Stable + Backports
> You're missing the "bullseye-updates" repository, but it's optional. If > the lines above were the only lines in your sources.list, you would be > doing it correctly. > > Bullseye-backports is also optional, and there probably aren't any yet. > And even when there are some, there's no guarantee that you'll need them. > Personally, I prefer to leave the -backports out of it unless and until > I actually need one. But if you want to bring it in proactively, that's > acceptable. > > > deb http://deb.debian.org/debian/ testing main contrib non-free > > deb-src http://deb.debian.org/debian/ testing main contrib non-free > > *THIS*, however, is wrong. > > With testing lines added to your sources.list, you are not running stable > (bullseye) any longer. You are still running testing, just with a > fallback option to retrieve bullseye packages as well. > > > deb http://deb.debian.org/debian/ experimental main contrib non-free > > deb-src http://deb.debian.org/debian/ experimental main contrib non-free > > And this is just stupid. Remove this immediately. > Ok I added bullseye-updates now, thanks. What priority should I apply to bullseye-update in preferences? With respect to having testing and experimental in the sources.list, I had testing prioritized at 250 and experimental at 1. The idea was that if some new package came along that I wanted to mess with, I could install it easily but if the there was a package belonging to bullseye, it would be installed there by priority. I am vigilant not to install things that contain dependencies that might update my entire system to, say, testing. Given that, are these lines still insane? Is there some way to tell apt to ask me if I want to install something from a particular repository, for example, something I want to test. I would like to have apt tell me "that's not in one of these repositories but it's in one of these other repositories you have in sources.list, ok to install it from there?" Something like a warn-me flag? Or something that shows me what repository I'm about to install something from? I was sort of hoping that's what setting a priority <500 would do. Here's an updated version now of what I have, though I would uncomment testing and experimental if I understand correctly. Wondering if I should also add unstable in there at an equally low priority. /etc/apt/sources.list deb http://security.debian.org/debian-security/ bullseye-security main contrib non-free deb-src http://security.debian.org/debian-security/ bullseye-security main contrib non-free deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free deb-src http://deb.debian.org/debian/ bullseye-updates main contrib non-free deb http://deb.debian.org/debian/ bullseye-backports main contrib non-free deb-src http://deb.debian.org/debian/ bullseye-backports main contrib non-free deb http://deb.debian.org/debian/ bullseye main contrib non-free deb-src http://deb.debian.org/debian/ bullseye main contrib non-free #deb http://deb.debian.org/debian/ testing main contrib non-free #deb-src http://deb.debian.org/debian/ testing main contrib non-free #deb http://deb.debian.org/debian/ experimental main contrib non-free #deb-src http://deb.debian.org/debian/ experimental main contrib non-free /etc/apt/preferences Package: * Pin: release a=bullseye-security Pin-Priority: 1000 Package: * Pin: release a=bullseye-updates Pin-Priority: 950 Package: * Pin: release a=bullseye-backports Pin-Priority: 950 Package: * Pin: release a=bullseye Pin-Priority: 900 Package: * Pin: release a=testing Pin-Priority: 250 Package: * Pin: release a=experimental Pin-Priority: 1 signature.asc Description: PGP signature
Re: Bulleye sécurité
Le 16/08/2021 à 12:50, MERLIN Philippe a écrit : Bonjour, Depuis deux jours j'ai ce message lorsque je lance apt update : Le dépôt http://security.debian.org stable/updates Release ne contient plus de fichier Release . Ce message ne m'inquiéterai pas trop si je n'avais eu lors d'une mise à jour hier un message disant que le nom d'une release n'était pas Bullseye mais je ne m'en rappelle plus exactement un nom contenant ...Worn il fallait répondre par O ou N N étant proposé par défaut j'ai répondu O. Le nom de contenant Worn est "Bookworm", la prochaine version de Debian, celle qui succède à Bullseye. Samedi, Bullseye est passé de testing à stable, et Bookworm est devenu la nouvelle testing. -- == | FRÉDÉRIC MASSOT | | http://www.juliana-multimedia.com | | mailto:frede...@juliana-multimedia.com | | +33.(0)2.97.54.77.94 +33.(0)6.67.19.95.69 | ===Debian=GNU/Linux===
Re: On improving mailing list [was: How to Boot Linux ISO Images Directly From Your Hard Drive Debian]
On Mon, Aug 09, 2021 at 06:05:58PM -0700, Weaver wrote: > I'm afraid this conversation is a waste of time. > The goal posts are moved around at convenience, rather in than any > serious manner at resolving an issue that is minor, if even existent. > Cheers! > > Harry. Oh it exists Harry! I've been on this list (usually lurking) for almost 20 years. The off topic posts often go on to enormous lengths often withouit a subject change (which itself is problematic). Way too much noise to signal ration lately, and it's often a handful of users who think this is their debate club. I'm for this being an on topic user support list and that posters/users that want to talk off topic be sanctioned appropriately. This list through the eyes of a beginner wanting help has been atrocius lately. Can you imagine trying to search for a given subject through the archives and having to wade through all the noise in these mega threads in case something relevant is in them? Ridicoulous. BTW there has been an off-topic list introduced by a community member, but it seems has had little uptake. So I agree completely with Andy Smith's (and others) statements and support this list being actively monitored for such off topic breaches. It would make the list what it's supposed to be, and make the archives better quality when searching for terms.
Re: bookworm
On Mon, Aug 16, 2021 at 12:14:41PM +0100, mick crane wrote: > Are there release notes for bookworm somewhere ? > mick > -- > Key ID4BFEBB31 > No, not yet. It only forked on Saturday: I suggest that the differences from Bullseye are relatively minimal at the moment and also that release goals have not yet been set by the new releae managers. Bullseye - Debian 11 - current stable release -release notes are linked here : https://www.debian.org/releases/bullseye/ This all to the best of my knowledge. All the very best, as ever, Andy Cater
Re: Bulleye sécurité
RTFM ;-) Il est indiqué dans ma documentation sur Bullseye (https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information#security-archive) : 5.1.3. Changement de l’organisation de l’archive security For bullseye, the security suite is now named bullseye-security instead of codename/updates and users should adapt their APT source-list files accordingly when upgrading. La ligne de sécurité dans votre configuration APT devrait ressembler à : deb https://deb.debian.org/debian-security bullseye-security main contrib If your APT configuration also involves pinning or APT::Default-Release, it is likely to require adjustments as the codename of the security archive no longer matches that of the regular archive. An example of a working APT::Default-Release line for bullseye looks like: APT::Default-Release "/^bullseye(|-security|-updates)$/"; which takes advantage of the undocumented feature of APT that it supports regular expressions (inside /). That’s falks… > Le 16 août 2021 à 12:50, MERLIN Philippe a > écrit : > > Bonjour, > Depuis deux jours j'ai ce message lorsque je lance apt update : > Le dépôt http://security.debian.org stable/updates Release ne contient plus > de fichier Release . > Ce message ne m'inquiéterai pas trop si je n'avais eu lors d'une mise à jour > hier un message disant que le nom d'une release n'était pas Bullseye mais je > ne m'en rappelle plus exactement un nom contenant ...Worn il fallait répondre > par O ou N N étant proposé par défaut j'ai répondu O. > Avez vous le même problème. > Merci d'avance. > Philippe Merlin > -- Pierre Malard Responsable architectures système GeoSUD IRD - UMR Espace-Dev - UMS CPST Maison de la Télédétection 500 rue Jean-François Breton 34093 Montpellier Cx 5 France « L'émancipation politique doit marcher de pair avec l'émancipation sociale ou les résultats sont désastreux » Romain Gary - "Les racines du ciel" |\ _,,,---,,_ /,`.-'`'-. ;-;;,_ |,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 <-- signature.asc Description: Message signed with OpenPGP
Kmail - Message d'erreur
Bonjour, Depuis quelques temps, j'ai un message d'erreur de Kmail lorsque je veux écrire un message. Le message est lié à la correction orthographique : > Une erreur s'est produite lors du chargement de la liste des langues : > Error transferring https://languagetool.org/api/v2/languages - server > replied: Forbidden Suis-je le seul ? Une solution ? Je n'ai rien trouvé avec Qwant. Merci Kmail : Version 5.15.3 (20.08.3)BEGIN:VCARD VERSION:3.0 EMAIL;TYPE:tu...@free.fr N: NICKNAME:Tulum UID:4d162a53-38e0-42c1-8855-2a85da07fa7d X-KADDRESSBOOK-MailAllowToRemoteContent:TRUE END:VCARD
Re: bookworm
* 2021-08-16 12:14:41+0100, mick crane wrote: > Are there release notes for bookworm somewhere ? https://duckduckgo.com/?q=debian+release+notes+bookworm -- /// Teemu Likonen - .-.. https://www.iki.fi/tlikonen/ // OpenPGP: 4E1055DC84E9DFF613D78557719D69D324539450 signature.asc Description: PGP signature
Re: Moving from Testing to Stable + Backports
On Mon, Aug 16, 2021 at 05:10:36AM -0400, Michael Grant wrote: > I've been using Testing for about a decade now with very few problems. > But now I'm moving to Stable. > sources.list > deb http://security.debian.org/debian-security/ bullseye-security main > contrib non-free > deb-src http://security.debian.org/debian-security/ bullseye-security main > contrib non-free > > deb http://deb.debian.org/debian/ bullseye-backports main contrib non-free > deb-src http://deb.debian.org/debian/ bullseye-backports main contrib non-free > > deb http://deb.debian.org/debian/ bullseye main contrib non-free > deb-src http://deb.debian.org/debian/ bullseye main contrib non-free You're missing the "bullseye-updates" repository, but it's optional. If the lines above were the only lines in your sources.list, you would be doing it correctly. Bullseye-backports is also optional, and there probably aren't any yet. And even when there are some, there's no guarantee that you'll need them. Personally, I prefer to leave the -backports out of it unless and until I actually need one. But if you want to bring it in proactively, that's acceptable. > deb http://deb.debian.org/debian/ testing main contrib non-free > deb-src http://deb.debian.org/debian/ testing main contrib non-free *THIS*, however, is wrong. With testing lines added to your sources.list, you are not running stable (bullseye) any longer. You are still running testing, just with a fallback option to retrieve bullseye packages as well. > deb http://deb.debian.org/debian/ experimental main contrib non-free > deb-src http://deb.debian.org/debian/ experimental main contrib non-free And this is just stupid. Remove this immediately.
Re: bookworm
On Mon 16 Aug 2021 at 12:14:41 +0100, mick crane wrote: > Are there release notes for bookworm somewhere ? > mick https://www.debian.org/releases/bookworm/releasenotes -- Brian.
Re: Bulleye sécurité
Bonjour, C'est parce que le nom a changé, maintenant il faut utiliser stable-security à la place de stable/update Sources : https://www.debian.org/releases///bullseye/s390x/release-notes/ch-information.fr.html#security-archive https://wiki.debian.org/fr/DebianBullseye#FAQ Le 16/08/2021 à 12:50, MERLIN Philippe a écrit : Bonjour, Depuis deux jours j'ai ce message lorsque je lance apt update : Le dépôt http://security.debian.org stable/updates Release ne contient plus de fichier Release . Ce message ne m'inquiéterai pas trop si je n'avais eu lors d'une mise à jour hier un message disant que le nom d'une release n'était pas Bullseye mais je ne m'en rappelle plus exactement un nom contenant ...Worn il fallait répondre par O ou N N étant proposé par défaut j'ai répondu O. Avez vous le même problème. Merci d'avance. Philippe Merlin -- Patrick ZAJDA
bookworm
Are there release notes for bookworm somewhere ? mick -- Key ID4BFEBB31
Re: Grub efi etc
On Sun 15 Aug 2021 at 20:31:36 +, Andrew M.A. Cater wrote: > On Sun, Aug 15, 2021 at 10:13:07PM +0300, Gunnar Gervin wrote: [...] > > Debian and Devuan obviously don't mix with Mint. And vice versa. Why not, > > really? You can learn around Efi & Grub from each other. Now you're both > > leaving it all up to Rod Smith. > > But to me it seems a bit too much for 1 man/team. Is Linux necessary to be > > such a mess ? > > Gunnar, > > If Devuan don't support EFI, they don't support EFI - but that's off-topic > here anyway. As with all Debian derivatives, they do things differently - > our efforts here can only ever be best endeavors > > Refracta is not a Debian installer. Nor is rEFInd Devuan is not a Debian derivative. It is a fork of Debian. Please see its homepage. Refacta is based on Devuan. Both OSs have active support channels. The present Mint is based on Ubuntu 20.04. Its very active forum has many knowledgeable users. Specific technica suppoert for all three OSs is off-topic on -user, just as support for Debian is off-topic on their channels. -- Brian.
[WAS Re: Grub efi etc - specific mention of WSL - Windows Subsystem for Linux]
On Mon, Aug 16, 2021 at 06:19:47AM -0400, Polyna-Maude Racicot-Summerside wrote: > Hi, > > On 2021-08-16 2:30 a.m., to...@tuxteam.de wrote: > > On Sun, Aug 15, 2021 at 05:21:41PM -0400, Polyna-Maude Racicot-Summerside > > wrote: > >> > >> > >> On 2021-08-15 4:31 p.m., Andrew M.A. Cater wrote: > > > > [...] > > > >>> Keep notes as you go. Try and raise single issues - it'll help. > >>> > >>> All the very best, as ever, > >> I'd like to have as much patience you do ;-) > > > > Not only patience, but knowledge. > > > > I just keep trying :-) > > > Knowledge is not like magic, it comes with time for a specific domain. > We all have knowledge but it's split between all that we do in life. We > can't expect to have the same knowledge as someone else who's older than us. > > For myself, I try to find answer by myself as often I can before going > out and asking others, this way I can gain a better understanding of the > process around me. If I do ask others, I try to also ask *why* they gave > me such answer. I don't accept only *do this and it will work*, if one > answer doesn't allow me a better understanding then I don't take it > because not only will it won't help me by just repeating what others > tell me, it can also be dangerous. > > I don't have as much knowledge than many of you regarding Debian because > for most of my life, computer related task wasn't a 40+ hours a week job. > > And one of the best way of learning is by trial and error. Having good > methods of separating cause and effects, taking time to read (always a > bit stupid not to read the release note to only find afterward that you > forgot a very important thing that wasn't needed for the past 20 &+ > release but is so now). > > And one of the best hint for learning is to ask the good persons. I > don't use *Windows Subsystem for Linux* and if I would, then it's not > here that I'd ask. Same goes for any Debian derivative. If you _did_ use WSL, I'd be willing and able to help you as I've installed this and run Debian under it. There is also a #debian-wsl IRC channel on OFTC run by the Debian maintainer of WSL packages, though it has almost no traffic. It would probably be on-topic for debian-user since there isn't another mailing list for it, I think. All best, as ever, Andy Cater > > > > Cheers > > - t > > > > -- > Polyna-Maude R.-Summerside > -Be smart, Be wise, Support opensource development >
Re: Moving from Testing to Stable + Backports
On Mon, Aug 16, 2021 at 05:10:36AM -0400, Michael Grant wrote: > I've been using Testing for about a decade now with very few problems. > But now I'm moving to Stable. Just wanted to mae sure I'm doing this > right. > > I last updated using Testing on the friday, then the release happened > on saturday. I changed my sources.list as below, did an apt update; > apt upgrade, and uncerimoniously there were no updates to install, my > system was already on bullseye. Easy. > > My intention is that when I upgrade or install something from now on, > I want to take the latest most resonable version of it. > > If there's a security update, I want that version first. > > Normally if I install something, it should come from stable. However, > if there's a backport of that thing, I prioritize the newer backport > instead. > > But what if something got updated from backports and then later > there's a security update for it in bullseye-security. Since I > prioritize bullseye-security, what's going to happen? Is it going to > reinstall a lower version number from bullseye-security? > > Lastly, I want to be able to manually install things from testing and > from experimental. > > Here's my apt config files: > > sources.list > deb http://security.debian.org/debian-security/ bullseye-security main > contrib non-free > deb-src http://security.debian.org/debian-security/ bullseye-security main > contrib non-free > > deb http://deb.debian.org/debian/ bullseye-backports main contrib non-free > deb-src http://deb.debian.org/debian/ bullseye-backports main contrib non-free > > deb http://deb.debian.org/debian/ bullseye main contrib non-free > deb-src http://deb.debian.org/debian/ bullseye main contrib non-free > > deb http://deb.debian.org/debian/ testing main contrib non-free > deb-src http://deb.debian.org/debian/ testing main contrib non-free > > deb http://deb.debian.org/debian/ experimental main contrib non-free > deb-src http://deb.debian.org/debian/ experimental main contrib non-free > > preferences > Package: * > Pin: release a=bullseye-security > Pin-Priority: 1000 > > Package: * > Pin: release a=bullseye-backports > Pin-Priority: 950 > > Package: * > Pin: release a=bullseye > Pin-Priority: 900 > > Package: * > Pin: release a=testing > Pin-Priority: 250 > > Package: * > Pin: release a=experimental > Pin-Priority: 1 > I don't know about the pinning priorities ... [Taken from https://wiki.debian.org/SourcesList] deb http://deb.debian.org/debian bullseye main contrib non-free deb-src http://deb.debian.org/debian bullseye main contrib non-free deb http://deb.debian.org/debian-security/ bullseye-security main contrib non-free deb-src http://deb.debian.org/debian-security/ bullseye-security main contrib non-free deb http://deb.debian.org/debian bullseye-updates main contrib non-free deb-src http://deb.debian.org/debian bullseye-updates main contrib non-free are the primarly /etc/apt/sources.list entries. Security updates will normally be applied to stable anyway but if you've got bullseye-security in there, they get pulled in. I also have unattended-updates or whatever it's called enabled. deb http://deb.debian.org/debian bullseye-backports main contrib non-free deb-src http://deb.debian.org/debian bullseye-backports main contrib non-free are the corresponging backports lines - I suspect there's nothing there at the moment but you normally have to explicitly pull backports by name - they're not installed by default, even if you have them enabled. Hope this helps, all the best, as ever, Andy Cater
Re: Grub efi etc
Hi, On 2021-08-16 2:30 a.m., to...@tuxteam.de wrote: > On Sun, Aug 15, 2021 at 05:21:41PM -0400, Polyna-Maude Racicot-Summerside > wrote: >> >> >> On 2021-08-15 4:31 p.m., Andrew M.A. Cater wrote: > > [...] > >>> Keep notes as you go. Try and raise single issues - it'll help. >>> >>> All the very best, as ever, >> I'd like to have as much patience you do ;-) > > Not only patience, but knowledge. > > I just keep trying :-) > Knowledge is not like magic, it comes with time for a specific domain. We all have knowledge but it's split between all that we do in life. We can't expect to have the same knowledge as someone else who's older than us. For myself, I try to find answer by myself as often I can before going out and asking others, this way I can gain a better understanding of the process around me. If I do ask others, I try to also ask *why* they gave me such answer. I don't accept only *do this and it will work*, if one answer doesn't allow me a better understanding then I don't take it because not only will it won't help me by just repeating what others tell me, it can also be dangerous. I don't have as much knowledge than many of you regarding Debian because for most of my life, computer related task wasn't a 40+ hours a week job. And one of the best way of learning is by trial and error. Having good methods of separating cause and effects, taking time to read (always a bit stupid not to read the release note to only find afterward that you forgot a very important thing that wasn't needed for the past 20 &+ release but is so now). And one of the best hint for learning is to ask the good persons. I don't use *Windows Subsystem for Linux* and if I would, then it's not here that I'd ask. Same goes for any Debian derivative. The force of Debian is not only the number of users who use it but the *why* user chose Debian. Most people choose some fork over Debian for pretty bad reason like "It use X desktop by default", "it include Y application", "it's more up to date for Z application", etc. Most person who have enough knowledge wouldn't take a fork based on these motivation, they'd simply *compile and/or install the needed application*, *choose* the desktop they *want*, *compile and/or install* a updated version of application either from *testing or from outside source*. If you choose a distribution that most people using it make this choice because it include *codec by default* won't give you chances to meet people who have a good technical background because installing codec is pretty easy. And using a distribution that make the choice of having the latest over the most stable (and safest) won't have a user base who have some important need for their system. I always laughed at Ubuntu that took years until they got out a version that is *server oriented* as they call it. Or when I talk with a user who tells me he's using Mint because it offers him a Cinammon Desktop by default (not sure was Mint). That just sound crazy ! Those are not good reason to choose one distribution over another one. Why have I chosen Debian ? *1st* : some package it's somewhat lagging behind because of all the test done before a package is approved for inclusion and the same test go one for updates. There's a truckload of compatibility test done, rules for compilation (default flags) and the maintainer / developer don't accept easily that you go away from those requirement. So the risk of a new update crashing the whole system is pretty low. *2nd* : There's a long support period for the distribution. *3rd* : Never found a fork who had a good reason of being alive. *4th* : The documentation is present in many language. *5th* : There's no commercial group behind who can push their own motivation for having choices made. So choice shall be made on technical reason and not based on what will drive a user base (for example accepting unstable driver that will attract gamer). *6th* : Has a huge set of developer application for doing package development and validation. *7th* : In 1997 and since, I've read in all the review around the same thing *Debian is appreciated by system operator for it's stability*. > Cheers > - t > -- Polyna-Maude R.-Summerside -Be smart, Be wise, Support opensource development OpenPGP_signature Description: OpenPGP digital signature
[PLEASE DISCARD] [OT] [Was] Re: l'actu chargée du 16/8
Please accept my APOLOGIES for posting by error the previous message that was to be sent to a friend of mine Didier
[PLEASE DISCARD] [OT] [Was:] Re: l'actu chargée du 16/8
> Please accept my APOLOGIES for posting by error the previous message that was to be sent to a friend of mine Sorry for that, Didier
l'actu chargée du 16/8
SPORT - [Tennis, Federer] : nouvelle opération du genou pour Roger Federer. ça commence à faire beaucoup d'opérations au même genou et ça risque d'être difficile de revenir... https://www.lemonde.fr/sport/article/2021/08/16/tennis-nouvelle-operation-du-genou-pour-roger-federer_6091540_3242.html - [Foot, Disparition, Gerd Müller] mort d’une légende du foot allemand. ça nous rajeunit pas. Et on peut se demander si le jeu de tête pratiqué dans ces années-là n'a pas causé des problèmes neurologiques à beaucoup de joueurs (Müller: Alzheimer). Je lisais un article y a pas longtemps sur l'équipe anglais championne du monde en 66, ils ont tous eu des séquelles. https://www.liberation.fr/sports/football/gerd-muller-mort-dune-legende-du-foot-allemand-20210815_FG64TCQBUZFNTBRYJ5JY5LATPU/ - [24H du Mans auto] Le Mans c'est ce WE et la Glickenhaus n°708 signe le meilleur temps de la journée test https://www.lequipe.fr/Sport-auto/Actualites/La-glickenhaus-n-708-signe-le-meilleur-temps-de-la-journee-test-des-24-heures-du-mans/1278565 - [MotoGP, GP Autriche] si t'as regardé le GP, t'as pas dû t'endormir. Impressionnante démonstration de la plupart des pilotes dans des conditions piégeuses. Et coup de chapeau à Binder, magistral! https://www.lequipe.fr/Moto/Actualites/-l-enorme-pari-de-brad-binder-vainqueur-du-gp-d-autriche/1278506 Zarco conclut 2 courses de rentrée post-vacances pas très enthousiasmantes: d'un côté il est un peu retombé dans ses travers, semble-t-il, en termes de pilotage naturel peu adapté à la Ducati, et d'autre part après la victoire de Martin la semaine dernière il a voulu prendre plus de risques pour ne pas rester cantonné aux places d'honneur: pour l'instant c'est pas très concluant. J'espère qu'il va profiter des 15j avant la prochaione course pour se réentraîner avec sa Panigale https://www.lequipe.fr/Moto/Actualites/Septieme-du-gp-d-autriche-fabio-quartararo-est-satisfait-d-avoir-limite-les-degats/1278522 Quant à Pol Espargaro, c'est pas mon pilote préféré, loin de là, mais en ce moment il fait de la peine (quasi systématiquement le moins bon pilote honda, dans les tréfonds du classement, il doit commencer à comprendre le calvaire de Zarco chez KTM) https://www.gp-inside.com/autriche-espargaro-16e-je-ne-sais-pas-quoi-dire-ni-quoi-faire-dautre/ - [MotoGP, 1001 nuits, arnaque] Les rumeurs se font inquiétantes: Rossi et la VR46 se seraient fait entuber par des escrocs se présentant comme des émissaires du prince Machin-Chose https://www.paddock-gp.com/motogp-selon-les-italiens-rossi-aurait-ete-victime-dune-mascarade-avec-tanal-entertainment/ SPORT & INFO - La directrice du circuit de Spa-Francorchamps et une de ses amies assassinées par son mari https://www.lequipe.fr/Rallye/Actualites/La-directrice-du-circuit-de-spa-francorchamps-retrouvee-morte-a-son-domicile/1278502 INFO - [Retour à l'âge de pierre] L'Afghanistan est désormais de nouveau totalement sous contrôle taliban après leur entrée dans la capitale. Quand je vois des connasses (oui, j'assume le terme) manifester contre "la dictature sanitaire" en France sans comprendre que d'autres femmes n'ont pas leur chance et à quel point les droits dont elles jouissent ont été difficles à obtenir et restent fragiles, je suis furax. - [Retour au moyen-âge, Canal+] le groupe Canal+ et le groupe TV Fox, même combat. Je te replonge dans tes études, il a fallu que je révise aussi: hier 15 août, pour les catholiques c'est l'Assomption (décès et montée au paradis de la vierge Marie): la chaîne C8 a diffusé hier 12 heures de programmes pro-catholiques. Cerise sur le gâteau, la diffusion en prime time d'un téléfilm anti-IVG bien chargé. C'est merveilleux, Canal+, depuis que Bolloré est arrivé. Quand on se souvient à quel point le Canal+ des débuts était aux antipodes de tout ça :-( https://www.lemonde.fr/actualite-medias/article/2021/08/16/le-chaine-c8-provoque-la-polemique-en-diffusant-un-film-contre-le-droit-a-l-avortement-en-prime-time_6091526_3236.html
Moving from Testing to Stable + Backports
I've been using Testing for about a decade now with very few problems. But now I'm moving to Stable. Just wanted to mae sure I'm doing this right. I last updated using Testing on the friday, then the release happened on saturday. I changed my sources.list as below, did an apt update; apt upgrade, and uncerimoniously there were no updates to install, my system was already on bullseye. Easy. My intention is that when I upgrade or install something from now on, I want to take the latest most resonable version of it. If there's a security update, I want that version first. Normally if I install something, it should come from stable. However, if there's a backport of that thing, I prioritize the newer backport instead. But what if something got updated from backports and then later there's a security update for it in bullseye-security. Since I prioritize bullseye-security, what's going to happen? Is it going to reinstall a lower version number from bullseye-security? Lastly, I want to be able to manually install things from testing and from experimental. Here's my apt config files: sources.list deb http://security.debian.org/debian-security/ bullseye-security main contrib non-free deb-src http://security.debian.org/debian-security/ bullseye-security main contrib non-free deb http://deb.debian.org/debian/ bullseye-backports main contrib non-free deb-src http://deb.debian.org/debian/ bullseye-backports main contrib non-free deb http://deb.debian.org/debian/ bullseye main contrib non-free deb-src http://deb.debian.org/debian/ bullseye main contrib non-free deb http://deb.debian.org/debian/ testing main contrib non-free deb-src http://deb.debian.org/debian/ testing main contrib non-free deb http://deb.debian.org/debian/ experimental main contrib non-free deb-src http://deb.debian.org/debian/ experimental main contrib non-free preferences Package: * Pin: release a=bullseye-security Pin-Priority: 1000 Package: * Pin: release a=bullseye-backports Pin-Priority: 950 Package: * Pin: release a=bullseye Pin-Priority: 900 Package: * Pin: release a=testing Pin-Priority: 250 Package: * Pin: release a=experimental Pin-Priority: 1 signature.asc Description: PGP signature
Re: Debian 11 installer crashed and reboot
On Mon, Aug 16, 2021 at 02:30:33PM +0800, John Mok wrote: > Hi all, > > Tried to install Debian 11 guest using netinst, but the installer > crashed and reboot automatically. > > Host: Xen 4.11.4 on Debian 10 > Guest: Debian 11 (kernel 5.10) > > Here is the steps to reproduce the problem:- > 1) Either guest BIOS or OVMF boot > 2) Select "Expert install" on installation menu > > Then, the guest crashed and reboot. > > Another try with the installer on Debian Live 11, it immediately > crashed and reboot. > > Is it a installer bug or something ? > > Thanks a lot. > > John Mok > I think people would need many more details as to exactly what happens and when it reboots. So: You boot the installer - from just a .iso file / from the .iso flashed to a USB? Can you show what works and at what point it fails? The quick suggestion would be that it's something to do with Xen hypervisor but I'm not in any better position than to guess, since I don't use Xen here. I do know that none of the tests the media team do involve booting on Xen: in most cases we prefer to run on real hardware. Occasionally, some of the tests have to be run on KVM/QEMU. Xen as DomU is untested then. All the very best, as ever, Andy Cater
Re: moderators, I would appreciate if you could interfere
On Sun, Aug 15, 2021 at 06:45:56PM -0700, Weaver wrote: > On 16-08-2021 11:29, lou wrote: > > Andrew, i thought you r moderator because you post monthly list guideline > > > > and you speak kindly with some authority when some list user deviate [...] > small collective of the politically correct [...] Pushing buttons? This one gets old. Yawn. Cheers - t signature.asc Description: Digital signature
Debian 11 installer crashed and reboot
Hi all, Tried to install Debian 11 guest using netinst, but the installer crashed and reboot automatically. Host: Xen 4.11.4 on Debian 10 Guest: Debian 11 (kernel 5.10) Here is the steps to reproduce the problem:- 1) Either guest BIOS or OVMF boot 2) Select "Expert install" on installation menu Then, the guest crashed and reboot. Another try with the installer on Debian Live 11, it immediately crashed and reboot. Is it a installer bug or something ? Thanks a lot. John Mok
Re: Grub efi etc
On Sun, Aug 15, 2021 at 05:21:41PM -0400, Polyna-Maude Racicot-Summerside wrote: > > > On 2021-08-15 4:31 p.m., Andrew M.A. Cater wrote: [...] > > Keep notes as you go. Try and raise single issues - it'll help. > > > > All the very best, as ever, > I'd like to have as much patience you do ;-) Not only patience, but knowledge. I just keep trying :-) Cheers - t signature.asc Description: Digital signature
