Re: Should /boot be ext2, instead of ext4?
On 9/4/2021 4:47 PM, Hideki Yamane wrote: On Sat, 4 Sep 2021 14:00:06 -0700 "J. William Campbell" wrote: but if we are talking about a /boot partition, there is no good reason to change it to ext4. Ext4 is reliable than ext2, I guess. And, /boot needs it. Ext4 is more reliable than ext2 in that it journals it's metadata changes so that if a write doesn't complete for some reason the volume can be recovered the next time it is mounted. However, on a boot partition which receives essentially no writes after it is initially created, this is no advantage at all, as there are no writes being done. Since this change may cause some people trouble and doesn't help anything as far as I can see, why do it? Best Regards, Bill Campbell
Re: Should /boot be ext2, instead of ext4?
Would it be possible to make uboot (and/or any of the other non-grub boot loaders) load grub, which then would load and configure the kernel from an ext4 or LVM partition? Rick
Re: Should /boot be ext2, instead of ext4?
On Sat, 4 Sep 2021 21:43:50 +0100 Steve McIntyre wrote: > Ummm. In my experience quite a number of older armel/armhf devices > booting using U-Boot may *not* be able to boot using ext4. I don't have any knowledge about U-Boot and arm devices, so here's a question. Is U-Boot different on each devices? It means, U-Boot on device A can read ext4 but on device B cannot. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#993668: CUPS is missing after a default GNOME Desktop Install
Sorry, I should have mentioned that I have the packages you mention as well as ipp-usb. Will Debian detect and add both driverless-enabled printers and ones that require drivers? When I check Settings -> Printers in GNOME I am presented with this "Sorry! The system printing service doesn't seem to be available." I don't have a printer available to test, but I was under the impression that libcups2 wasn't the only library required for printing. On Sat, Sep 4, 2021 at 9:43 PM Holger Wansing wrote: > Hi, > > Holger Wansing wrote (Sat, 4 Sep 2021 21:09:56 > +0200): > > (BTW: CUPS also gets installed with the other desktops via > > gnome-core -> system-config-printer-common -> cups-pk-helper -> libcups2) > > Hrr, copy-and-paste error here. > Should have been: > > (BTW: CUPS also gets installed with the other desktops via > task-xxyy-desktop -> system-config-printer -> libcups2 ) > > > > And: > KDE's dependency chain: > task-kde-desktop -> print-manager -> libcups2 > > > > -- > Holger Wansing > PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076 >
Re: Should /boot be ext2, instead of ext4?
On Sat, 4 Sep 2021 14:00:06 -0700 "J. William Campbell" wrote: > but if we are talking about a > /boot partition, there is no good reason to change it to ext4. Ext4 is reliable than ext2, I guess. And, /boot needs it. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#993668: CUPS is missing after a default GNOME Desktop Install
Hi, Holger Wansing wrote (Sat, 4 Sep 2021 21:09:56 +0200): > (BTW: CUPS also gets installed with the other desktops via > gnome-core -> system-config-printer-common -> cups-pk-helper -> libcups2) Hrr, copy-and-paste error here. Should have been: (BTW: CUPS also gets installed with the other desktops via task-xxyy-desktop -> system-config-printer -> libcups2 ) And: KDE's dependency chain: task-kde-desktop -> print-manager -> libcups2 -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#993668: CUPS is missing after a default GNOME Desktop Install
Hi, Nader Nooryani wrote (Sat, 4 Sep 2021 16:16:50 +0200): > As of Debian 11, Print Server is no longer included as an option in the > Debian installer if you use the defaults: Debian desktop environment, GNOME > and standard system utilities. Ref: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950553 > > This leaves the user without CUPS after a default install. This should > perhaps be included in task-gnome-desktop I have tested this, and CUPS got installed here with GNOME desktop (default install). The dependency chain turns out to be: task-gnome-desktop -> gnome-core -> system-config-printer-common -> cups-pk-helper -> libcups2 (BTW: CUPS also gets installed with the other desktops via gnome-core -> system-config-printer-common -> cups-pk-helper -> libcups2) So, I cannot reproduce this. Do you have the installation logs available? Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Re: Should /boot be ext2, instead of ext4?
On 9/4/2021 1:44 PM, John Paul Adrian Glaubitz wrote: On 9/4/21 22:32, Hideki Yamane wrote: On Tue, 10 Aug 2021 19:33:37 +0200 Ben Hutchings wrote: This is bug #985463. If we can confirm no architecture has a limit to use ext2 now, then we can change it to ext4, right? I may have missed some of the discussion, but if we are talking about a /boot partition, there is no good reason to change it to ext4. The performance advantages of a JFS just don't matter on a partition that seldom changes. Since ext2 can be read by any system that can read ext4, that also is not an issue. So why change? If we are talking about a /boot directory that is part of a larger partition that contains other things that are regularly written to, that is a different case. Bill Campbell We should make a list with the bootloaders in use. Many architectures use GRUB but some architectures use boot loaders that use blocklists so they still may work with ext4. Architectures that use GRUB are: - amd64 - arm64 - i386 - ia64 - powerpc - ppc64 - ppc64el - riscv64 (not sure if supported on all boards) - sparc64 - s390x (loaded from zIPL) - x32 Other bootloaders are: - armel - u-boot - armhf - u-boot - alpha - aboot - hppa - palo - m68k - amiboot, atariboot, emile - mipsel - u-boot - mips64el - u-boot - riscv64 - u-boot - sh4 - u-boot Adrian
Re: Should /boot be ext2, instead of ext4?
On 9/4/21 22:32, Hideki Yamane wrote: > On Tue, 10 Aug 2021 19:33:37 +0200 > Ben Hutchings wrote: >> This is bug #985463. > > If we can confirm no architecture has a limit to use ext2 now, > then we can change it to ext4, right? We should make a list with the bootloaders in use. Many architectures use GRUB but some architectures use boot loaders that use blocklists so they still may work with ext4. Architectures that use GRUB are: - amd64 - arm64 - i386 - ia64 - powerpc - ppc64 - ppc64el - riscv64 (not sure if supported on all boards) - sparc64 - s390x (loaded from zIPL) - x32 Other bootloaders are: - armel - u-boot - armhf - u-boot - alpha - aboot - hppa - palo - m68k - amiboot, atariboot, emile - mipsel - u-boot - mips64el - u-boot - riscv64 - u-boot - sh4 - u-boot Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Should /boot be ext2, instead of ext4?
On Sun, Sep 05, 2021 at 05:32:51AM +0900, Hideki Yamane wrote: >On Tue, 10 Aug 2021 19:33:37 +0200 >Ben Hutchings wrote: >> This is bug #985463. > > If we can confirm no architecture has a limit to use ext2 now, > then we can change it to ext4, right? Ummm. In my experience quite a number of older armel/armhf devices booting using U-Boot may *not* be able to boot using ext4. Whether we should change the default on other arches is a useful discussion, but I'd be worried about maybe breaking support here. -- Steve McIntyre, Cambridge, UK.st...@einval.com Mature Sporty Personal More Innovation More Adult A Man in Dandism Powered Midship Specialty
Re: Should /boot be ext2, instead of ext4?
On Tue, 10 Aug 2021 19:33:37 +0200 Ben Hutchings wrote: > This is bug #985463. If we can confirm no architecture has a limit to use ext2 now, then we can change it to ext4, right? -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Re: Need help debootstrapping Ubuntu impish
On Sat, Sep 04, 2021 at 03:50:39PM +, Joshua Peisach wrote: > Hello Boot team, > > I'm coming after asking for help from the live-team. The issue was narrowed > to debootstrap. I'm trying to build an impish image for Ubuntu Cinnamon > Remix, and I'm having issues with the base packages. > > Last time I had an issue was with pinetab/pine64 stuff, and we could safely > exclude it, but these are issues with base packages like bsdutils, > base-passwd and others I didn't want to fully track down and remove. Some of > the files already exist and then the package manager steps on top of it. > Instead of doing anything about it, it complains that a file already exists > and just quits. > > I'm not sure what's going on, so can someone give a hint? > > Thanks, > -Josh > > Repo: https://github.com/Ubuntu-Cinnamon-Remix/iso-builder Hi Joshua, Ubuntu does things very differently - can I suggest you chat first to the folks who produce the main Ubuntu install media (which does have a live image buried inside to do the install with) / some of the other Ubuntu desktop variants and remixes. It's likely that we won't be able to help directly because Ubuntu does things differently - in Debian, this would be done by installing a desktop metapackage or equivalent, but Ubuntu suggests a remix per desktop. All the very best, as ever, Andy Cater
Need help debootstrapping Ubuntu impish
Hello Boot team, I'm coming after asking for help from the live-team. The issue was narrowed to debootstrap. I'm trying to build an impish image for Ubuntu Cinnamon Remix, and I'm having issues with the base packages. Last time I had an issue was with pinetab/pine64 stuff, and we could safely exclude it, but these are issues with base packages like bsdutils, base-passwd and others I didn't want to fully track down and remove. Some of the files already exist and then the package manager steps on top of it. Instead of doing anything about it, it complains that a file already exists and just quits. I'm not sure what's going on, so can someone give a hint? Thanks, -Josh Repo: https://github.com/Ubuntu-Cinnamon-Remix/iso-builder
Bug#993668: CUPS is missing after a default GNOME Desktop Install
Package: task-gnome-desktop Version: 3.68 As of Debian 11, Print Server is no longer included as an option in the Debian installer if you use the defaults: Debian desktop environment, GNOME and standard system utilities. Ref: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950553 This leaves the user without CUPS after a default install. This should perhaps be included in task-gnome-desktop Suggestion: It may be wise to include CUPS in task-gnome-desktop or somewhere else, since there are no instructions informing the user how they can enable support for printing. I am using Linux debian 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 (2021-08-03) x86_64 GNU/Linux
Re: Bug#992693: bullseye-pu: package glibc/2.31-13+deb11u1
Control: tags -1 + confirmed d-i On Sun, 2021-08-22 at 14:58 +0200, Aurelien Jarno wrote: > During the upgrade from Buster to Bullseye, the SSH server is not > restarted following the libc6 upgrade, causing new SSH connections to > get rejected until the SSH server is restarted later in the upgrade. > > It could be considered as a regression as it didn't happen during the > upgrade from Stretch to Buster. > > [ Impact ] > Upgrade might fail or get stuck for remote upgrade using SSH if for > some reason the SSH connection breaks. Using screen or tmux doesn't > help here as it is not possible to connect again using SSH. [...] > The change consist in updating the regex getting the list of services > in the "installed" state, to also consider openssh-server in > 'unpacked' state. +glibc (2.31-13+deb11u1) unstable; urgency=medium The distribution there should be "bullseye". I realise that the changes don't affect the udeb, but for completeness this wants a kibi-ack; CCed and tagging appropriately. Please feel free to go ahead on that basis. Regards, Adam
CUPS missing after default desktop install
Hello I am not quite sure where to file this, so apologies if I send this to the wrong place. Since Print Server is no longer included as an option in the Debian installer it leaves users without CUPS after a default install. This should perhaps be included in task-gnome-desktop? I have written a bit more about this on Reddit as well. https://www.reddit.com/r/debian/comments/pgl6c9/debian_11_and_printing/ Best regards, Nader Nooryani
