forwarded 679571 https://bugs.busybox.net/show_bug.cgi?id=5270 thanks
On 22.07.2012 10:11, Ben Hutchings wrote: [] > I've been meaning to fix this for a while. It seems to be a bug in the > minimal implementation of modprobe used in the initramfs, part of > 'busybox'. I'm attaching a patch that seems to do the right thing, > which I hope the busybox maintainer will apply. Thank you Ben for the patch. I've been, well, waiting for the upstream to show any reaction for https://bugs.busybox.net/show_bug.cgi?id=5270 (for which I forgot to set "forwarded", doing it now), and basically forgot about this stuff (since I still can't use debian initramfs I don't see this message on every boot myself). Your patch isn't exactly sufficient, -- well, the behavour should now match m-i-t/kmod as modprobe wont return error when asked to load a built-in module anymore, but it will still error out with --first-time (which should ignore loaded modules but not built-ins), and it will emit somewhat unclear error message when asked to _remove_ a built-in module. Maybe that's all just cosmetics, but these cosmetics are so easy to fix already... :) But anyway. I agree this needs to be fixed in busybox for sure. But do we really need this `modprobe unix' in the first place? It's been many years since this isn't needed for debian kernels, and it is difficult to imagine a custom kernel with unix.ko as a module. I had such a config for a while, but it gave me quite a few headaches already, so I changed from unix=m to unix=y. And 3rd, I'm not sure AF_UNIX is really needed for initramfs itself anymore - the module autoloads just fine on first access, when udev creates its first unix socket. So I'd say this 'modprobe unix' should be removed from udev hook. (Cc'ing Md for this). Thanks, /mjt -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/500ba8a1.6050...@msgid.tls.msk.ru
