Thorsten Glaser dixit:
>I’ve recently been getting filesystem corruption on this system, which,
>incidentally, is a fresh-ish installation since I’ve been hit by the
I have somewhat reason to at least suspect the µSD card this was
installed on. But there was never anything in syslog/dmesg about
i
I do get at all of my Debian bullseye VPS at Hetzner this message during
boot (once):
Aug 16 06:08:42 uhu kernel: [1726344.567946] device-mapper: uevent:
version 1.0.3
Aug 16 06:08:42 uhu kernel: [1726344.571939] device-mapper: ioctl:
4.43.0-ioctl (2020-10-01) initialised: dm-de...@redhat.com
On Wed, Sep 07, 2022 at 09:32:15AM -0700, Noah Meyerhans wrote:
> The cloud team publishes images for various cloud environments
> (OpenStack, Amazon EC2, etc). The primary (and most popular, from the
> data I have) images use the main kernel, but we publish alternative
> images that boot the back
On Wed, Sep 07, 2022 at 09:32:15AM -0700, Noah Meyerhans wrote:
> Is there a plan to continue offering new kernels for buster LTS?
Yes, the same as with the older ones. It just is broken right now.
Bastian
--
Lots of people drink from the wrong bottle sometimes.
-- Edith Keeler
On Wed, Sep 07, 2022 at 07:37:45AM +0200, Alexander Wirt wrote:
> > > Now that buster is LTS and no longer officially supported, should the
> > > -backports pocket be closed? AFAIK, buster just receives the security
> > > uploads by the -security pocket and shouldn't have -backports open
> > > anym
Hi folks,
what is Debian's policy wrt using the current stable version with
current hardware? Am I supposed to create a bug report about
linux-signed-amd64 or firmware-nonfree, if (lets say) WLAN is
broken on a 1 year old notebook? Use backports or unstable instead?
Regards
Harri
6 matches
Mail list logo
