Bug#749991: A tiresome subject for YEARS.
On 10/25/18 11:06 AM, Oliver Riesener wrote: On 10/25/18 1:45 AM, Ben Hutchings wrote: On Wed, 2018-10-24 at 18:44 +0200, John Paul Adrian Glaubitz wrote: On 10/24/18 6:42 PM, Oliver Riesener wrote: No unetbootin, it’s the stock stretch netboot installation. initrd kernel from actual Debian9.5/…./amd64/netboot/netboot.tar.gz didn’t find kernel modules anymore. The old one before too. It’s a point release problem. Older versions of modules (.udeb ?) seems to be from debian repo. Are you sure you used a matching kernel image and initrd? Both have to match their version otherwise it won't work. But when you use netboot the udebs in the archive *also* have to match. And they don't after a point release. Ben. Yes, that's the point. Packages are updated, today it runs perfect again. Oh, i am sorry, i got the issue yesterday with jessie 8.0 point release, becource my (old) bootp entry points to 8.0/pxelinux.0. Upgraded to jessie/current/netboot image, works also fine. Oliver I'm creating debian-installer images myself on a regular basis and from my current knowledge and testing, it's very unlikely that there is a bug in the kernel and initrd matching.
Bug#749991: A tiresome subject for YEARS.
On 10/25/18 1:45 AM, Ben Hutchings wrote: On Wed, 2018-10-24 at 18:44 +0200, John Paul Adrian Glaubitz wrote: On 10/24/18 6:42 PM, Oliver Riesener wrote: No unetbootin, it’s the stock stretch netboot installation. initrd kernel from actual Debian9.5/…./amd64/netboot/netboot.tar.gz didn’t find kernel modules anymore. The old one before too. It’s a point release problem. Older versions of modules (.udeb ?) seems to be from debian repo. Are you sure you used a matching kernel image and initrd? Both have to match their version otherwise it won't work. But when you use netboot the udebs in the archive *also* have to match. And they don't after a point release. Ben. Yes, that's the point. Packages are updated, today it runs perfect again. I'm creating debian-installer images myself on a regular basis and from my current knowledge and testing, it's very unlikely that there is a bug in the kernel and initrd matching.
Bug#749991: A tiresome subject for YEARS.
No unetbootin, it’s the stock stretch netboot installation. initrd kernel from actual Debian9.5/…./amd64/netboot/netboot.tar.gz didn’t find kernel modules anymore. The old one before too. It’s a point release problem. Older versions of modules (.udeb ?) seems to be from debian repo. > Am 24.10.2018 um 17:26 schrieb John Paul Adrian Glaubitz > : > > On 10/24/18 5:15 PM, Oliver Riesener wrote: >> Debian Stretch 9.5 (stable) kernel 3.16.0-4 >> * no packages matching kernel failed. > > This error usually comes up with installation media created using > unetbootin. Have you, by any chance, used unetbootin to create your > installation medium? > > 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 >
Bug#749991: A tiresome subject for YEARS.
A tiresome subject for YEARS. It has happened again today. Debian Stretch 9.5 (stable) kernel 3.16.0-4 * no packages matching kernel failed.
Bug#834589: mkhomedir_helper: fails if skeleton directory is on autofs with kernel 4.x
Package: libpam-modules-bin Version: 1.1.8-3.1+deb8u1+b1 Severity: important Tags: patch Dear Maintainer, * What led up to the situation? If skeleton path is automounted with --nobrowse and isn't previously fstat'ed (mounted) then opendir() from mkhomedir_helper will fail and no skeleton files are copied. openat(AT_FDCWD, "/opt/skeleton", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory) * Logfile: auth.log: mkhomedir_helper: PAM unable to read directory /opt/skeleton: No such file or directory * What exactly did you do (or not do) that was effective (or ineffective)? Fails on backports kernel 4.6 but works on 3.16 (jessie) * What was the outcome of this action? Switched to backports kernel for skylake support. * What outcome did you expect instead? mkhomedir_helper works like expected and copy skeleton files. * Patch that works for me: *** orig/pam-1.1.8/modules/pam_mkhomedir/mkhomedir_helper.c 2013-06-18 16:11:21.0 +0200 --- work/pam-1.1.8/modules/pam_mkhomedir/mkhomedir_helper.c 2016-08-17 13:08:40.684977517 +0200 *** *** 54,57 --- 54,61 } +/* First stat for hidden autofs entries, otherwise openat() failed at kernel 4.x */ +struct stat buf; +stat( source, &buf); + /* Scan the directory */ d = opendir(source); -- System Information: Debian Release: 8.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-0.bpo.1-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages libpam-modules-bin depends on: ii libaudit11:2.4-1+b1 ii libc62.19-18+deb8u4 ii libpam0g 1.1.8-3.1+deb8u1+b1 ii libselinux1 2.3-2 libpam-modules-bin recommends no packages. libpam-modules-bin suggests no packages. -- no debconf information -- debsums errors found: debsums: changed file /sbin/mkhomedir_helper (from libpam-modules-bin package)
