lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <45AB8CB9.2000209@walrond.org>
Date:	Mon, 15 Jan 2007 14:16:25 +0000
From:	Andrew Walrond <andrew@...rond.org>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: Initramfs and /sbin/hotplug fun

If the initramfs root filesystem contains /sbin/hotplug, the kernel 
starts calling it very early in the kernel boot process, well before 
/init has been called. In my case this resulted in lots of hotplug 
segfault messages as the kernel boots, followed by a thoroughly unhappy 
hotplug+udev once /init actually gets control.

To solve this, I deleted /sbin/hotplug from the initramfs archive and 
modified /init to reinstate it once it gets control. This works fine, 
but seems inelegant. Is there a better solution? Should sbin/hotplug be 
called at all before the kernel has passed control to /init?

Andrew Walrond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ