Bug#986491: Acknowledgement (fails to fully configure with debconf low priority)

My main reason for running installs at low priority both at the main debian-installer screen and wanting to do so after the base system is installed is so I can have a fully configured system and not have to go back and reconfigure everything after the installation is finished.  If the debconf

Re: Should /boot be ext2, instead of ext4?

Hello, Le 05/09/2021 à 18:47, J. William Campbell a écrit : AFAIK, the on disk format for ext4 is the same as ext2. If the code can read an ext2 filesystem, it can read an ext4 filesystem. I am not sure about that. AFAIK, some ext4 features such as extents create a different on-disk format

Re: Should /boot be ext2, instead of ext4?

On 9/7/2021 12:58 AM, Pascal Hambourg wrote: Hello, Le 05/09/2021 à 18:47, J. William Campbell a écrit : AFAIK, the on disk format for ext4 is the same as ext2. If the code can read an ext2 filesystem, it can read an ext4 filesystem. I am not sure about that. AFAIK, some ext4 features such

Bug#592834: Just saw this when using autoremove

I just updated my 20.04 install, it installed 5.4.0-84 (among other things). I rebooted and then used apt autoremove to remove anything old. Here's what I got: root@rct2:/home/farokh# apt autoremove Reading package lists... Done Building dependency tree Reading state information...

Bug#932939: Unable to reproduce in Bullseye (Debian 11)

Hi, Just an update here, I just provisioned a host with Debian GNU/Linux Bullseye with "console=tty0 console=ttyS0,115200n8" present in installer kernel command-line, and it seems to have provisioned just fine. Feel free to mark this bug as resolved. Thanks! -- Ashish SHUKLA | GPG: F682 CDCC